CRESCENDO-MIB

All MIBs › CRESCENDO-MIB

Category: ATM

Description: Manages Crescendo Communications (pre-Cisco) ATM and FDDI network switch hardware and port statistics.

Start monitoring vendor-neutral, standards-based MIB, any SNMPv3-capable network device (SNMP engine identity/boot/clock status) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

What Is CRESCENDO-MIB?

CRESCENDO-MIB is a legacy vendor MIB from Crescendo Communications, a networking company acquired by Cisco in the early 1990s, covering its ATM and FDDI concentrator/switch hardware and management functions. It exposes device management configuration such as the concentrator's management IP address and netmask, SNMP trap receiver configuration, and SNMP community access control settings for the switch's management interface. Its monitoring value is largely around management-plane and network configuration status: verifying the concentrator's IP/netmask configuration is correct, confirming which trap receivers are registered to receive fault notifications, and auditing community strings and their access levels, which together determine whether the device can be properly managed and will alert operators to hardware or link faults. As an early enterprise MIB it predates and does not depend on later IETF standards, relying on its own concMgmtType-rooted structure. It would have been deployed on Crescendo/early-Cisco ATM or FDDI concentrator hardware in legacy campus backbone networks. Engineers can download the CRESCENDO-MIB file directly to load it into their MIB browser.

IPNetwork Monitor allows you to monitor SNMP objects defined in CRESCENDO-MIB. Use the built-in SNMP Monitoring Browser to explore available variables, view their current values and descriptions, and select the objects you want to monitor. You can then create SNMP monitors, configure thresholds, and receive alerts when monitored values change.

Supported Devices

Crescendo Communications ATM/FDDI concentrator
early Cisco-acquired switch hardware

Monitoring Examples

An administrator would check concIpAddr and concNetMask to confirm the concentrator's management addressing is correctly configured, and walk concTrapReceiverTable/concTrapReceiverEntry to verify the expected NMS station is registered via concTrapReceiverAddr to receive concTrapReceiverType notifications. The concCommunityTable/concCommunityEntry would be audited to ensure concCommunityAccess levels are appropriately restricted, since a misconfigured community with excessive access on this legacy device would be a security concern. This is fundamentally a configuration/management-access MIB rather than one exposing rich runtime port statistics.

What Can Be Monitored

management IP/netmask configuration
trap receiver registration
trap type delivered
SNMP community access level

Imported Objects

From RFC1155-SMI

Counter
Gauge
IpAddress
TimeTicks
enterprises

From RFC1212

OBJECT-TYPE

OIDs

OID symbolic	OID numeric	Type	Access	Description
crescendo	1.3.6.1.4.1.203
crescendoProducts	1.3.6.1.4.1.203.1
concentrator	1.3.6.1.4.1.203.1.1
conc	1.3.6.1.4.1.203.1.1.1
INT concMgmtType	1.3.6.1.4.1.203.1.1.1.1	INTEGER	read-only	The type of network management running on the concentrator.
IP concIpAddr	1.3.6.1.4.1.203.1.1.1.2	IpAddress	read-write	The concentrator's IP address.
IP concNetMask	1.3.6.1.4.1.203.1.1.1.3	IpAddress	read-write	The concentrator's subnet mask.
IP concBroadcast	1.3.6.1.4.1.203.1.1.1.4	IpAddress	read-write	The concentrator's broadcast address.
concTrapReceiverTable	1.3.6.1.4.1.203.1.1.1.5		not-accessible	The concentrator trap receiver table (0 to 10 entries). This table lists the addresses of Network Management Stations that should receive trap messages from this concentrator when an exception condition occurs.
concTrapReceiverEntry	1.3.6.1.4.1.203.1.1.1.5.1		not-accessible	A trap receiver table entry.
INT concTrapReceiverType	1.3.6.1.4.1.203.1.1.1.5.1.1	INTEGER	read-write	Setting this object to invalid(2) removes the corresponding entry from the concTrapReceiverTable. To add a new entry to the concTrapReceiverTable, set the concTrapReceiverAddr to an IpAddress which is not already in the table. The concTrapReceiverType for that entry is automatically set to other(1).
IP concTrapReceiverAddr	1.3.6.1.4.1.203.1.1.1.5.1.2	IpAddress	read-write	IP address for trap receiver.
STR concTrapReceiverComm	1.3.6.1.4.1.203.1.1.1.5.1.3	DisplayString	read-write	Community string used for trap messages to this trap receiver.
concCommunityTable	1.3.6.1.4.1.203.1.1.1.6		not-accessible	The concentrator community table (4 entries). This table lists community strings and their access levels. When an SNMP message is received by this concentrator, the community string in the message is compared with this table to determine access rights of the sender.
concCommunityEntry	1.3.6.1.4.1.203.1.1.1.6.1		not-accessible	A community table entry.
INT concCommunityAccess	1.3.6.1.4.1.203.1.1.1.6.1.1	INTEGER	read-only	A value of readWriteAll(4) allows the community to read and write all objects in the MIB. A value of readWrite(3) allows the community to read and write all objects except the concCommunityTable, which it cannot access at all. A value of readOnly(2) allows the community to read all objects except the concCommunityTable. A value of other(1) allows no access.
STR concCommunityString	1.3.6.1.4.1.203.1.1.1.6.1.2	DisplayString	read-write	Configurable community string with access rights defined by the value of concCommunityAccess.
INT concAttachType	1.3.6.1.4.1.203.1.1.1.7	INTEGER	read-write	The requested concentrator attachment type. For a dual attachment concentrator connected to the trunk ring, port 1 on the supervisor module (or single board concentrator) is configured as A and port 2 is configured as B. For a single attachment concentrator connected beneath another concentrator, port 1 is configured as S and port 2 is configured as M. For a null attachment concentrator at the root of the tree, ports 1 and 2 are configured as M. This object does not take effect until the concentrator is reset. The current attachment type can be determined from snmpFddiPORTPCType for ports 1 and 2. Note that a concentrator with no MAC is always null attachment type.
INT concTraffic	1.3.6.1.4.1.203.1.1.1.8	INTEGER	read-only	The percentage of bandwidth utilization on the network for the previous polling interval.
INT concReset	1.3.6.1.4.1.203.1.1.1.9	INTEGER	read-write	Writing a 2 to this object resets the control logic of all modules in the concentrator.
INT concBaudRate	1.3.6.1.4.1.203.1.1.1.10	INTEGER	read-write	The baud rate in bits per second of the concentrator RS-232 port.
chassis	1.3.6.1.4.1.203.1.1.2
INT chassisType	1.3.6.1.4.1.203.1.1.2.1	INTEGER	read-only	The chassis type.
INT chassisBkplType	1.3.6.1.4.1.203.1.1.2.2	INTEGER	read-only	The chassis backplane type.
INT chassisPs1Type	1.3.6.1.4.1.203.1.1.2.3	INTEGER	read-only	Type of power supply number 1.
INT chassisPs1Status	1.3.6.1.4.1.203.1.1.2.4	INTEGER	read-only	Status of power supply number 1. If the status is not ok, the value of chassisPs1TestResult gives more detailed information about the power supply's failure condition(s).
INT chassisPs1TestResult	1.3.6.1.4.1.203.1.1.2.5	INTEGER	read-only	Test result for power supply number 1. A zero indicates that the supply passed all tests. Bits set in the result indicate error conditions.
INT chassisPs2Type	1.3.6.1.4.1.203.1.1.2.6	INTEGER	read-only	Type of power supply number 2.
INT chassisPs2Status	1.3.6.1.4.1.203.1.1.2.7	INTEGER	read-only	Status of power supply number 2. If the status is not ok, the value of chassisPs2TestResult gives more detailed information about the power supply's failure condition(s).
INT chassisPs2TestResult	1.3.6.1.4.1.203.1.1.2.8	INTEGER	read-only	Test result for power supply number 2. A zero indicates that the supply passed all tests. Bits set in the result indicate error conditions.
INT chassisFanStatus	1.3.6.1.4.1.203.1.1.2.9	INTEGER	read-only	Status of the chassis fan. If the status is not ok, the value of chassisFanTestResult gives more detailed information about the fan's failure condition(s).
INT chassisFanTestResult	1.3.6.1.4.1.203.1.1.2.10	INTEGER	read-only	Test result for the chassis fan. A zero indicates that the fan passed all tests. Bits set in the result indicate error conditions.
INT chassisMinorAlarm	1.3.6.1.4.1.203.1.1.2.11	INTEGER	read-only	The chassis minor alarm status.
INT chassisMajorAlarm	1.3.6.1.4.1.203.1.1.2.12	INTEGER	read-only	The chassis major alarm status.
INT chassisTempAlarm	1.3.6.1.4.1.203.1.1.2.13	INTEGER	read-only	The chassis temperature alarm status.
INT chassisNumSlots	1.3.6.1.4.1.203.1.1.2.14	INTEGER	read-only	The number of slots in the chassis for plug-in modules.
INT chassisSlotConfig	1.3.6.1.4.1.203.1.1.2.15	INTEGER	read-only	An indication of which slots in the chassis have modules inserted. This is an integer value with bits set to indicate configured modules. It can be interpreted as a sum of f(x) as x goes from 1 to the number of slots, where f(x) = 0 module and f(x) = exp(2, x-1) for a module inserted.
moduleTable	1.3.6.1.4.1.203.1.1.3.1		not-accessible	A list of module entries. The number of entries is given by the value of chassisNumSlots.
moduleEntry	1.3.6.1.4.1.203.1.1.3.1.1		not-accessible	Entry containing information about one module in a slot of the concentrator.
INT moduleIndex	1.3.6.1.4.1.203.1.1.3.1.1.1	INTEGER	read-only	A unique value for each module within the concentrator. This value is determined by the chassis slot number where the module is inserted. Valid entries are 1 to the value of chassisNumSlots
INT moduleType	1.3.6.1.4.1.203.1.1.3.1.1.2	INTEGER	read-only	The type of module.
INT moduleSerialNumber	1.3.6.1.4.1.203.1.1.3.1.1.3	INTEGER	read-only	The serial number of the module.
INT moduleHwHiVersion	1.3.6.1.4.1.203.1.1.3.1.1.4	INTEGER	read-only	The high part of the hardware version of the module. For example, if the hardware version is 3.1, the value of moduleHwHiVersion is 3.
INT moduleHwLoVersion	1.3.6.1.4.1.203.1.1.3.1.1.5	INTEGER	read-only	The low part of the hardware version of the module. For example, if the hardware version is 3.1, the value of moduleHwLoVersion is 1.
INT moduleFwHiVersion	1.3.6.1.4.1.203.1.1.3.1.1.6	INTEGER	read-only	The high part of the firmware version number. For example, if the firmware version is 3.1, the value of moduleFwHiVersion is 3.
INT moduleFwLoVersion	1.3.6.1.4.1.203.1.1.3.1.1.7	INTEGER	read-only	The low part of the firmware version number. For example, if the firmware version is 3.1, the value of moduleFwLoVersion is 1.
INT moduleSwHiVersion	1.3.6.1.4.1.203.1.1.3.1.1.8	INTEGER	read-only	The high part of the software version number. For example, if the software version is 3.1, the value of moduleSwHiVersion is 3.
INT moduleSwLoVersion	1.3.6.1.4.1.203.1.1.3.1.1.9	INTEGER	read-only	The low part of the software version number. For example, if the software version is 3.1, the value of moduleSwLoVersion is 1.
INT moduleStatus	1.3.6.1.4.1.203.1.1.3.1.1.10	INTEGER	read-only	The operational status of the module. If the status is not ok, the value of moduleTestResult gives more detailed information about the module's failure condition(s).
INT moduleTestResult	1.3.6.1.4.1.203.1.1.3.1.1.11	INTEGER	read-only	The result of the module's self test. A zero indicates that the module passed all tests. Bits set in the result indicate error conditions.
INT moduleReset	1.3.6.1.4.1.203.1.1.3.1.1.12	INTEGER	read-write	Writing a 2 to this object resets the module's control logic. This has the same affect as pressing the reset button on the module.
STR moduleName	1.3.6.1.4.1.203.1.1.3.1.1.13	DisplayString	read-write	A descriptive string used by the network administrator to name the module.
INT moduleNumPorts	1.3.6.1.4.1.203.1.1.3.1.1.14	INTEGER	read-only	The number of ports supported by the module.
OCT modulePortStatus	1.3.6.1.4.1.203.1.1.3.1.1.15	OCTET STRING	read-only	A series of bytes containing status information about the module and each of the ports on the module. The first byte contains the status for the module (same value as moduleStatus), and subsequent bytes contain status for the first through the last ports on the module (same value as portStatus).
port	1.3.6.1.4.1.203.1.1.4
portTable	1.3.6.1.4.1.203.1.1.4.1		not-accessible	A list of port entries. The number of entries is determined by the number of modules in the concentrator and the number of ports on each module.
portEntry	1.3.6.1.4.1.203.1.1.4.1.1		not-accessible	Entry containing information for a particular port on a module.
INT portModuleIndex	1.3.6.1.4.1.203.1.1.4.1.1.1	INTEGER	read-only	A unique value for each module within the concentrator. This value is determined by the chassis slot number which the module is plugged into. Valid entries are 1 to the value of chassisNumSlots.
INT portIndex	1.3.6.1.4.1.203.1.1.4.1.1.2	INTEGER	read-only	A unique value for each port within a module. This value is determined by the location of the port on the module. Valid entries are 1 to the value of moduleNumPorts for this module.
INT portFddiIndex	1.3.6.1.4.1.203.1.1.4.1.1.3	INTEGER	read-only	The snmpFddiPORTIndex for this module/port.
STR portName	1.3.6.1.4.1.203.1.1.4.1.1.4	DisplayString	read-write	A descriptive string used by the network administrator to name the port.
INT portType	1.3.6.1.4.1.203.1.1.4.1.1.5	INTEGER	read-only	The type of physical layer medium dependent interface on the port.
INT portStatus	1.3.6.1.4.1.203.1.1.4.1.1.6	INTEGER	read-only	The operational status of the port. If the status is not ok, the values of snmpFddiPORTCEState and snmpFddiPORTConnectState give more detailed information about the port's failure condition(s).

RFC description

Vendor-private MIB available in MIB repositories; specific device/system details not publicly documented.

Start monitoring Crescendo Communications ATM/FDDI concentrator (legacy, early Cisco) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

Download CRESCENDO-MIB

What Is CRESCENDO-MIB?

Supported Devices

Monitoring Examples

What Can Be Monitored

This MIB depends on

Related MIBs

RFC description