CME-MIB :: bootInfoTopologyIndex

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsCME-MIBbootInfoTopologyIndex

bootInfoTopologyIndex

Module: CME-MIB

OID (symbolic): CME-MIB::bootInfoTopologyIndex

OID (numeric): 1.3.6.1.4.1.2.3.51.2.22.1.15.1.1

Node type: OBJECT-TYPE

Type: OCTET STRING

Access: read-only

Description: The unique identifier for a node containing boot devices in this table. The chassis and each installed component is represented by a hardware topology tree, where each node in the tree represents a component. The path to a particular component consists of one or more , pairs, where each successive pair is a child of the previous parent pair. As an example, the root of the tree is the chassis and is represented by the pair 'CHASSIS, 1'. This pair indicates the first instance of the chassis. If a blade is inserted in slot 4 of the chassis, its topology path is 'CHASSIS, 1, BLADE, 4'. With this format, the components in the chassis can be determined along with their relative hierarchy to each other. This component inventory table is indexed by this unique topology path and the relevant numeric designations for the components are: CHASSIS, 0x01 Chassis MM, 0x02 Management Module BLADE, 0x03 Main system board of a blade

What is bootInfoTopologyIndex?

This read-only octet string (up to 100 bytes) uniquely identifies, via a hardware topology tree of <component>,<instance> pairs rooted at the chassis, exactly which hardware node's boot devices are described by a row in the boot-device table. It matters because the chassis can contain many components at different topology levels (blades, expansion cards, etc.), and this path is what unambiguously ties a set of boot devices back to one specific physical component. An admin looking up boot devices for a specific blade's internal storage controller would use this topology path to make sure they're reading that exact component's boot device list and not a sibling component's.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.2.3.51.2.22.1.15.1.1
snmpwalk -v2c -c public <target> CME-MIB::bootInfoTopologyIndex

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.2.3.51.2.22.1.15.1.1.1
snmpget -v2c -c public <target> CME-MIB::bootInfoTopologyIndex.1

Start monitoring Cisco Communications Manager Express (CME) router/gateway with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the CME-MIB::bootInfoTopologyIndex OID value, configure state conditions and alerts, and monitor any Cisco Communications Manager Express (CME) router/gateway from a single console.

OID Breakdown

Upper-level ancestors (12 from the standard OID tree / other modules)
Numeric OIDNameModule
1isoLANART-AGENT
1.3orgAirPair-MIB
1.3.6dodAirPair-MIB
1.3.6.1internetAirPair-MIB
1.3.6.1.4privateAirPair-MIB
1.3.6.1.4.1enterprisesAirPair-MIB
1.3.6.1.4.1.2ibmBLADE-MIB
1.3.6.1.4.1.2.3ibmAgentsBLADE-MIB
1.3.6.1.4.1.2.3.51netfinitySupportProcessorAgentBLADE-MIB
1.3.6.1.4.1.2.3.51.2bladeCenterSnmpMIBBLADE-MIB
1.3.6.1.4.1.2.3.51.2.22bladeCenterBLADE-MIB
1.3.6.1.4.1.2.3.51.2.22.1processorBladeBLADE-MIB
Numeric OIDNameModule
1.3.6.1.4.1.2.3.51.2.22.1.15bootDeviceInfoTableCME-MIB
1.3.6.1.4.1.2.3.51.2.22.1.15.1bootDeviceInfoEntryCME-MIB
1.3.6.1.4.1.2.3.51.2.22.1.15.1.1bootInfoTopologyIndexCME-MIB