All MIBs › CME-MIB › bootSequenceInfoBootSequence
bootSequenceInfoBootSequence
Module: CME-MIB
OID (symbolic): CME-MIB::bootSequenceInfoBootSequence
OID (numeric): 1.3.6.1.4.1.2.3.51.2.22.1.16.1.3
Node type: OBJECT-TYPE
Type: OCTET STRING
Access: read-write
Description: A blank delimited string of device ids in the order of the boot sequence. For example, 00000001 00000002 00000005. Note that the boot sequence list can change from a given order and can grow from a given order, but cannot be reduced in length. For example, if the sequence starts as 00000001 00000011, it could change to 00000001 00000014 or grow to 00000001 00000014 00000002. In the example above, if the 00000002 selection was no longer desired, the list should be changed to 00000001 00000014 00000014, essentially repeating the last device ID. Device ids must be listed in bootDeviceInfoTable.
What is bootSequenceInfoBootSequence?
This writable octet string holds a blank-delimited list of device IDs (e.g. '00000001 00000002 00000005') defining the actual boot order for a topology node, with the documented rule that the sequence can be rearranged or extended but never shortened below its current length. It's the object an admin actually edits to change which device boots first, second, and so on for a given component. An admin wanting network boot to be tried before local disk would reorder bootSequenceInfoBootSequence so the NIC's device ID appears before the disk's device ID in the string, while being careful not to drop any existing entries since the sequence can't be reduced.
Examples
Walk all instances (SNMPv2c):
snmpwalk -v2c -c public <target> 1.3.6.1.4.1.2.3.51.2.22.1.16.1.3 snmpwalk -v2c -c public <target> CME-MIB::bootSequenceInfoBootSequence
Get a specific instance (index 1):
snmpget -v2c -c public <target> 1.3.6.1.4.1.2.3.51.2.22.1.16.1.3.1 snmpget -v2c -c public <target> CME-MIB::bootSequenceInfoBootSequence.1
Set instance 1 (SNMPv2c):
snmpset -v2c -c private <target> 1.3.6.1.4.1.2.3.51.2.22.1.16.1.3.1 s <value>
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::bootSequenceInfoBootSequence 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 OID | Name | Module |
|---|---|---|
| 1 | iso | LANART-AGENT |
| 1.3 | org | AirPair-MIB |
| 1.3.6 | dod | AirPair-MIB |
| 1.3.6.1 | internet | AirPair-MIB |
| 1.3.6.1.4 | private | AirPair-MIB |
| 1.3.6.1.4.1 | enterprises | AirPair-MIB |
| 1.3.6.1.4.1.2 | ibm | BLADE-MIB |
| 1.3.6.1.4.1.2.3 | ibmAgents | BLADE-MIB |
| 1.3.6.1.4.1.2.3.51 | netfinitySupportProcessorAgent | BLADE-MIB |
| 1.3.6.1.4.1.2.3.51.2 | bladeCenterSnmpMIB | BLADE-MIB |
| 1.3.6.1.4.1.2.3.51.2.22 | bladeCenter | BLADE-MIB |
| 1.3.6.1.4.1.2.3.51.2.22.1 | processorBlade | BLADE-MIB |
| Numeric OID | Name | Module |
|---|---|---|
| 1.3.6.1.4.1.2.3.51.2.22.1.16 | bootSequenceInfoTable | CME-MIB |
| 1.3.6.1.4.1.2.3.51.2.22.1.16.1 | bootSequenceInfoEntry | CME-MIB |
| 1.3.6.1.4.1.2.3.51.2.22.1.16.1.3 | bootSequenceInfoBootSequence | CME-MIB |