CARD-MIB

All MIBs › CARD-MIB

Organization: Coriolis Networks

Last Updated: 2000-07-27

Category: Device Management, Hardware and Environment

Description: Manages generic hardware card (line card/module) insertion, removal, and operational state within a chassis-based network device.

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 CARD-MIB?

CARD-MIB is a generic hardware MIB, per its module description covering 'cards in coriolis boxes,' used to manage line card/module insertion, removal, and operational state within a chassis-based network device. Although no sample objects were supplied, such MIBs typically expose a card table listing physical slot position, card type, administrative and operational status, and possibly serial number/hardware revision. Its monitoring value is squarely hardware status: it lets an operator detect when a card is missing, has failed, or has changed operational state (e.g., from up to down) within a modular chassis, which is critical for diagnosing partial-outage or hardware-fault conditions. It likely complements the standard IETF ENTITY-MIB, which provides a more generic physical-entity inventory model, though the exact relationship cannot be confirmed without further detail. It is deployed in modular, chassis-based network equipment (the 'coriolis' platform referenced in its description) where individual line cards or modules can be independently inserted, removed, or replaced. Network engineers evaluating or troubleshooting this functionality can download the CARD-MIB file directly to load it into their MIB browser.

IPNetwork Monitor allows you to monitor SNMP objects defined in CARD-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

chassis-based network device (Coriolis platform)

Monitoring Examples

No sample_objects were provided for this MIB, so specific table or object names cannot be cited with confidence; however, given the module description referencing cards in 'coriolis boxes,' a realistic scenario would involve polling a card status table for administrative/operational state per chassis slot to detect a card that has gone offline or been physically removed. Without concrete object names, this description stops short of naming exact variables to avoid inventing implausible names.

What Can Be Monitored

card/module operational status
card presence per chassis slot
card administrative state

Imported Objects

From CORIOLIS-MIB

card	OBJECT-IDENTITY
coriolisMibs	OBJECT-IDENTITY

From RFC-1215

TRAP-TYPE

From SNMPv2-SMI

MODULE-IDENTITY
OBJECT-TYPE
Unsigned32

From SNMPv2-TC

TruthValue

OIDs

OID symbolic	OID numeric	Type	Access	Description
INT atmCardActivePortMask	1.3.6.1.4.1.5812.2.7.1.2	INTEGER	read-only	This returns a mask of active ports. An active port is one that has been created via a Port Create MO. A value of 1 in bit position N-1 indicates that port N has been created. For example, if port 1 has been created, then bit 0 is asserted. Since there are 2 ports for an ATM card, this can take the range of values from 0 to 3.
atmCardEntry	1.3.6.1.4.1.5812.2.7.1		not-accessible	Entry containing information about an atm module
INT atmCardOperState	1.3.6.1.4.1.5812.2.7.1.1	INTEGER	read-only	The oper state of the atm module
INT atmCardRowStatus	1.3.6.1.4.1.5812.2.7.1.3	INTEGER	read-write	This variable is used to create or delete instances of atm cards. This variable subsumes the admin state variable, and once the row is created, its value returns the admin state of the card
atmCardTable	1.3.6.1.4.1.5812.2.7		not-accessible	The table for atm cards
INT cardAssemblyClass	1.3.6.1.4.1.5812.2.3.1.8	INTEGER	read-only	Identifies the hardware class. This field is a duplicate of the assembly class portion of the assembly number. It is stored and displayed in Binary Encoded Decimal (BCD) format. The following list provide some of the Assembly Class and its description: 04 Mechanical Assembly Drawing (Legacy Only) 10 Discrete Resistors 11 Resistor Networks 14 Capacitors 16 Crystals 17 Oscillators 18 Magnetic Modules (inductors, filters, ferrites, power chokes, transformers) 20 Active Components 21 Transistors, Diodes, FET's 22 Mechanical Hardware (Legacy Only) 23 Connectors 24 Electromechanical Components (switches, motors, fans) 26 Circuit Protection Devices (Fuses, PTC) 27 Power Components (power supplies, fuses, line filters) 30 LED's 31 Logic Components 32 Memory 34 Application Specific 36 Optical Component (Active, Passive) 38 Programmable Device (Raw device prior to programming) 40 Module Assemblies (Secondary Assy Required i.e., Optics) 42 Mechanical Fasteners (Screws, Washers, Nuts, Tywraps) 43 Labels 44 Wire & Cable 46 Packaging (Shipping Materials) 47 Manuals (HW, SW, Release Notes, Misc) 50 PCB Assemblies 51 Schematic 54 Printed Circuit Boards 60 Cable Assemblies 70 Mechanical / Electromechanical Assemblies (Chassis, Fan Tray) 72 Fabricated Components 74 Sub Assembly (Legacy Only) 75 Finished Assembly 80 PLD Files 82 FPGA Code 84 Operational Software 85 Programmed Device Assembly 86 PLD Daisy Chain Test File 99 Rework Instructions
OCT cardAssemblyId	1.3.6.1.4.1.5812.2.3.1.9	OCTET STRING	read-only	Identifies the module type. This field is a duplicate of the assembly identifier portion of the assembly number. It is stored and displayed in Binary Encoded Decimal (BCD) format. It has the following format: NN -1234 -NN RevNo \| \| \| \|____ Part Revision Number \| \| \| \| \| \|_________ Suffix = PartID (01-99) \| \| \| \|______________ Main Body = Sequential No. (0001 - 9999) \| \|___________________ Prefix = Part Class Number or Tab Number (01 - 99).
OCT cardAssemblyNumString	1.3.6.1.4.1.5812.2.3.1.15	OCTET STRING	read-only	Module's assembly number.
U32 cardAssemblyRev	1.3.6.1.4.1.5812.2.3.1.11	Unsigned32	read-only	Identifies the assembly revision of the module. This field is a duplicate of the assembly revision field. It is stored and displayed in Binary Encoded Decimal (BCD) format. For example, a typical AssemblyID would be like '54-0001-01 Rev 2'.
OCT cardAssemblyRevString	1.3.6.1.4.1.5812.2.3.1.16	OCTET STRING	read-only	Revision level of the card.
INT cardAssemblyTabNum	1.3.6.1.4.1.5812.2.3.1.10	INTEGER	read-only	This field is a duplicate of the assembly tab number portion of the assembly number. It is stored and displayed in Binary Encoded Decimal (BCD) format. For Example, a Part Number like '60-3456-01' has the Tab Number -01. All new parts are released a tab number of -01. If a new member of a family of harwareType is introduced, then the tab number would be incremented. Its range is 01 - 99.
INT cardbrchecksum	1.3.6.1.4.1.5812.2.3.1.12	INTEGER	read-only	Contains a checksum calculated over the first 16 bytes of SID ROM data.
INT cardChecksum	1.3.6.1.4.1.5812.2.3.1.19	INTEGER	read-only	Contains a checksum calculated over the previous 252 bytes of SID ROM data.
OCT cardCLEICode	1.3.6.1.4.1.5812.2.3.1.17	OCTET STRING	read-only	Stores an ASCII String duplicating CLEI (Common Language Equipment Identifier ) Code encoded into the bar code. 10 ASCII characters of CLEI code
OCT cardCLEIECICode	1.3.6.1.4.1.5812.2.3.1.18	OCTET STRING	read-only	Stores an ASCII String duplicating CLEI ECI (Equipment Catalog Item) Code encoded into the bar code. Bar Code in numeric form
INT cardCount	1.3.6.1.4.1.5812.2.2	INTEGER	read-only	The number of active cards in the device
cardEEPromEntry	1.3.6.1.4.1.5812.2.3.1		not-accessible	Entry containing information about a card in the system.
cardEEPromTable	1.3.6.1.4.1.5812.2.3		not-accessible	The table containing various kinds of card information
OCT cardHwSubType	1.3.6.1.4.1.5812.2.3.1.4	OCTET STRING	read-only	Identifies the functional revision of this card. Example: Suppose a card's hardware could be configured with internal or external timing modes and suppose firmware initialization differed depending on the type of timing mode configured on the card hardware, then the value of the hardware subtype object could be used by firmware to initialize to the appropriate timing mode.
INT cardHwType	1.3.6.1.4.1.5812.2.3.1.3	INTEGER	read-only	An object which uniquely identifies the card type.
INT cardImageType	1.3.6.1.4.1.5812.2.3.1.5	INTEGER	read-only	An object which identifies the bootrom and system images to running on a card. This object only applies to card types with on-board processor. The values are: 0 - card without CPU or image. 3 - Management Module 4 - OptiFlow 3000/3500 Switch Module and OptiFlow 5000/5500 Switch Module 5 - OptiFlow 1010 (Pizza Box)
OCT cardMacAddress	1.3.6.1.4.1.5812.2.3.1.7	OCTET STRING	read-only	Stores the starting MAC Address for this module. All 6 bytes are zero when not applicable.
INT cardMACaddressNum	1.3.6.1.4.1.5812.2.3.1.6	INTEGER	read-only	Indicates the number of MAC Addresses allocated to this module. Current values range from 0 to 64. This value is 0 when not applicable.
cardMIB	1.3.6.1.4.1.5812.2.1			The MIB module for cards in coriolis boxes
OCT cardSerialNum	1.3.6.1.4.1.5812.2.3.1.14	OCTET STRING	read-only	Stores a 12 digit serial number associated with a module. (example: PLX1100-0100).
OCT cardSIDFVer	1.3.6.1.4.1.5812.2.3.1.2	OCTET STRING	read-only	SID ROM Version of the SID-ROM format which represents the 1st 20 bytes with a 1 byte value. This variable is used only during the boot process when a sanity check is made. If the current version is 0xF0 (which indicates the initial version), then the next version would be 0xE1 and so on.
U32 cardSIDInfoVersion	1.3.6.1.4.1.5812.2.3.1.13	Unsigned32	read-only	Reflects the revision level of the information portion of the SID-ROM data.
NTF emFlashLife	1.3.6.1.4.1.5812.0.46			Flash End-of-life alarm.
INT etherCardActivePortMask	1.3.6.1.4.1.5812.2.6.1.2	INTEGER	read-only	This returns a mask of active ports. An active port is one that has been created via a Port Create MO. A value of 1 in bit position N-1 indicates that port N has been created. For example, if port 1 has been created, then bit 0 is asserted. Since there are 16 ports, this can take the range of values from 0 to 65535.
etherCardEntry	1.3.6.1.4.1.5812.2.6.1		not-accessible	Entry containing information about an ethernet module
INT etherCardOperState	1.3.6.1.4.1.5812.2.6.1.1	INTEGER	read-only	The oper state of the ethernet module
INT etherCardPhyResetState	1.3.6.1.4.1.5812.2.6.1.3	INTEGER	read-write	The phy reset state of the module
INT etherCardRowStatus	1.3.6.1.4.1.5812.2.6.1.4	INTEGER	read-write	This variable is used to create or delete instances of ethernet cards. This variable subsumes the admin state variable, and once the row is created, its value returns the admin state of the card
etherCardTable	1.3.6.1.4.1.5812.2.6		not-accessible	The table for ethernet cards
NTF ioCardStatusChange	1.3.6.1.4.1.5812.0.45			Indicates the failure of IO card to respond.
NTF moduleStatusChange	1.3.6.1.4.1.5812.0.2			Change in the operational state of a module. 1 means the module went down, 2 means it went up
NTF moduleTempChange	1.3.6.1.4.1.5812.0.44			Indicates temperature (hot/normal) in the chassis.
opticalCardEntry	1.3.6.1.4.1.5812.2.8.1		not-accessible	Entry containing information about an optical module
INT opticalCardOpticsType	1.3.6.1.4.1.5812.2.8.1.2	INTEGER	read-write	The type of optics on the module
INT opticalCardRowStatus	1.3.6.1.4.1.5812.2.8.1.3	INTEGER	read-write	This variable is used to create or delete instances of optical cards
INT opticalCardSlotType	1.3.6.1.4.1.5812.2.8.1.1	INTEGER	read-write	The type of module - transmitter or receiver
opticalCardTable	1.3.6.1.4.1.5812.2.8		not-accessible	The table for optical cards
U32 posCardActivePortMask	1.3.6.1.4.1.5812.2.9.1.1	Unsigned32	read-only	Bitmap describing the active ports on this pos module
posCardEntry	1.3.6.1.4.1.5812.2.9.1		not-accessible	Entry containing information about an pos module
INT posCardPhyResetState	1.3.6.1.4.1.5812.2.9.1.2	INTEGER	read-write	The phy reset state of the module
posCardTable	1.3.6.1.4.1.5812.2.9		not-accessible	The table for pos cards
INT slotAdminState	1.3.6.1.4.1.5812.2.4.1.1	INTEGER	read-write	The slot admin state
INT slotCardType	1.3.6.1.4.1.5812.2.4.1.4	INTEGER	read-write	The type of card in the slot
INT slotConnectionSize	1.3.6.1.4.1.5812.2.4.1.5	INTEGER	read-write	The connection size to SM
slotEntry	1.3.6.1.4.1.5812.2.4.1		not-accessible	Entry containing information about a slot in the system.
INT slotFileState	1.3.6.1.4.1.5812.2.4.1.8	INTEGER	read-only	File locked or not
INT slotFlashSectorsOverThreshold	1.3.6.1.4.1.5812.2.4.1.13	INTEGER	accessible-for-notify	Indicates the number of sectors over threshold, applicable for only the active and standby MMs
INT slotFlashThreshold	1.3.6.1.4.1.5812.2.4.1.12	INTEGER	accessible-for-notify	Indicates the flash threshold, applicable for only the active and standby management modules
INT slotInsertState	1.3.6.1.4.1.5812.2.4.1.7	INTEGER	read-only	Whether a card is present in the slot or not
INT slotIoCardStatus	1.3.6.1.4.1.5812.2.4.1.11	INTEGER	accessible-for-notify	Indicates the responsiveness status of the module in the slot
INT slotModuleChangeStatus	1.3.6.1.4.1.5812.2.4.1.9	INTEGER	accessible-for-notify	This variable is sent out in a module change event to communicate what happened to the module.The 'FAILURE' and 'FAILOVER' values are used by the mmr task to report failover events. The 'INSERTED' and 'REMOVED' values are used by AI to report module configuration and de-configuration events. The 'INSERTED' event will change to be reported whenever a card is inserted. The 'CONFIGURED' event will be reported when the card completes chassis configuration. The 'REMOVED' event will be reported whenever a card is removed. The events 'SYNCPOINT_FAILURE' and 'CONFIG_FAILURE' will be reported when a card fails syncPoints or chassis configuration respectively. The event 'CONFIG_DELETED' will be reported when a card configuration file is deleted (indicating the card configuration has been lost).
INT slotModuleTempStatus	1.3.6.1.4.1.5812.2.4.1.10	INTEGER	accessible-for-notify	Indicates the temperature status of the module in the slot
INT slotNo	1.3.6.1.4.1.5812.2.3.1.1	INTEGER	not-accessible	This variable is used as an index in all card tables
INT slotOperState	1.3.6.1.4.1.5812.2.4.1.2	INTEGER	read-only	The slot oper state. removed - card not in slot and not connected syncWait - card in slot waiting for syncPoint synced - card passed a syncPoint syncFailed - card failed a syncPoint configStarted - configuration started configFailed - configuration failed configed - configuration passed ready - card ready for normal operation waitSM - card waiting for SM reboot waitDeconfig - waiting for deconfiguration to complete designModeReady - card is configured but removed.
INT slotSMSlot	1.3.6.1.4.1.5812.2.4.1.6	INTEGER	read-write	SM slot that this slot is connected to
slotTable	1.3.6.1.4.1.5812.2.4		not-accessible	The slot table
INT slotType	1.3.6.1.4.1.5812.2.4.1.3	INTEGER	read-write	The type of slot for this device. The following is a list of different kinds of slots: 1 - MMSlot (9,10 for optiFlow3X and 13,14 for optiFlow5x) 2 - optiFlow3xSMSlot (goes into slot 12) 3 - optiFlow5xSMSlot (goes into slots 7,9,18,20) 4 - regularIOSlot (goes into slots 3-6 in optiFlow3x, 1-6, 21-26 in optiFlow5x) The different types of cards that goes into this regular IO Slot are: A - 10/100 Ethernet B - Gigbit Ethernet C - DS1 TDM D - DS3 TDM E - OC12 ATM/POS F - OC12 TDM G - OC3 ATM H - OC48 POS I - Color Separator 5 - optiFlow3xSlotNumber1 The different types of cards that goes into this slot are: A - DS1 TDM B - DS3 TDM C - OC12 TDM 6 - optiFlow5x IO This type of slot takes: A - OC12 TDM (slots 5 and 21) 7 - optiFlow3x OpticsSlot (slots 11 and 12) This slot takes in: A - 1310TxRx B - 8 different cards with different lambdas (optiFlow3x OADM optics) C - 1550 TxRx 8 - optiFlow5x OpticsSlotType1 (slots 12 and 15 - Tx Only) This slot takes in: A - 1310 Tx / DWDM B - 8 different cards with different lambdas for DWDM Tx C - 1310 Tx D - 1550 Tx 9 - optiFlow5x OpticsSlotType2 (slots 11 and 16 - Rx only) This slot takes in: A - 1310 Rx / DWDM B - 8 different cards with different lambdas for DWDM Rx C - 1310 Rx 10 - optiFlow5x FM (goes into slots 8, 10, 17 and 19) 11 - colorSeparator (goes into slot 2 for OptiFlow3x) For an OAU, the slots are abstracted in the following manner: Slot 1 - IO (Eth16) Slot 2 - IO (GigIo) Slot 3 - MM Slot 4 - SM Slot 5 - OpRxTx
U32 tdmIoCardConfiguredPorts	1.3.6.1.4.1.5812.2.5.1.4	Unsigned32	read-only	Bitmap of ports configured on the module. The bit positions of the 1 bits in the binary form of this number give the ports configured in this card. For example, if all the 3 ports of a DS3 card are configured, you'll get a value of 14 which in binary gives 1110. If 1st and 3rd are configured, you'll see 10 (1010). For a DS1 card, if all 16 ports are configured, you'll a value of 131070. The number of 1's in the binary representation of the value gives the number of configured ports.
tdmIoCardEntry	1.3.6.1.4.1.5812.2.5.1		not-accessible	Entry containing information about an TDM IO module - DS1/DS3/E1/E3
INT tdmIoCardMode	1.3.6.1.4.1.5812.2.5.1.3	INTEGER	read-write	Whether this is an unchannelized or channelized module
U32 tdmIoCardNumPMIntervals	1.3.6.1.4.1.5812.2.5.1.6	Unsigned32	read-write	This is the number of performance monitoring intervals for the ports on this card
INT tdmIoCardOperState	1.3.6.1.4.1.5812.2.5.1.2	INTEGER	read-only	The oper state of the TDM IO module
INT tdmIoCardRowStatus	1.3.6.1.4.1.5812.2.5.1.5	INTEGER	read-write	This variable is used to create or delete instances of TDM IO cards. This variable subsumes the admin state variable, and once the row is created, its value returns the admin state of the card
tdmIoCardTable	1.3.6.1.4.1.5812.2.5		not-accessible	The table for TDM IO cards
INT tdmIoCardType	1.3.6.1.4.1.5812.2.5.1.1	INTEGER	read-write	The type of the TDM IO module

RFC description

Manages hardware cards in Coriolis network elements, including management modules, switch modules, and I/O modules.

Start monitoring Coriolis Networks chassis-based network devices (legacy) 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 CARD-MIB

What Is CARD-MIB?

Supported Devices

Monitoring Examples

What Can Be Monitored

This MIB depends on

Related MIBs

RFC description