CISCO-UNIFIED-COMPUTING-EQUIPMENT-MIB :: cucsEquipmentBootDeviceConstraintsRn

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsCISCO-UNIFIED-COMPUTING-EQUIPMENT-MIBcucsEquipmentBootDeviceConstraintsRn

cucsEquipmentBootDeviceConstraintsRn

Module: CISCO-UNIFIED-COMPUTING-EQUIPMENT-MIB

OID (symbolic): CISCO-UNIFIED-COMPUTING-EQUIPMENT-MIB::cucsEquipmentBootDeviceConstraintsRn

OID (numeric): 1.3.6.1.4.1.9.9.719.1.15.204.1.3

Node type: OBJECT-TYPE

Type: SnmpAdminString

Access: read-only

Description: Cisco UCS equipment:BootDeviceConstraints:rn managed object property

What is cucsEquipmentBootDeviceConstraintsRn?

This is the relative name (RN) -- the final naming component appended to its parent's DN -- that distinguishes one boot-device constraint rule -- a catalog entry stating which boot-device types a given server or adapter model is permitted to use in a boot policy from its siblings under the same parent object. Reading the RN alongside the parent DN is how UCS Manager, and any SNMP poller querying it, reconstructs which boot device constraint a given row of data actually belongs to without repeating the full path in every field. For a boot device constraint the RN is typically the last path segment shown in 'sys/chassis-2/blade-5/boot-device-constraints', e.g. 'boot-device-constraints'.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.9.9.719.1.15.204.1.3
snmpwalk -v2c -c public <target> CISCO-UNIFIED-COMPUTING-EQUIPMENT-MIB::cucsEquipmentBootDeviceConstraintsRn

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.9.9.719.1.15.204.1.3.1
snmpget -v2c -c public <target> CISCO-UNIFIED-COMPUTING-EQUIPMENT-MIB::cucsEquipmentBootDeviceConstraintsRn.1

Start monitoring Cisco UCS chassis, blade/rack servers, fabric interconnects with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the CISCO-UNIFIED-COMPUTING-EQUIPMENT-MIB::cucsEquipmentBootDeviceConstraintsRn OID value, configure state conditions and alerts, and monitor any Cisco UCS chassis, blade/rack servers, fabric interconnects from a single console.

OID Breakdown

Upper-level ancestors (10 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.9ciscoCAT2600-MIB
1.3.6.1.4.1.9.9ciscoMgmtCISCO-SMI
1.3.6.1.4.1.9.9.719ciscoUnifiedComputingMIBCISCO-UNIFIED-COMPUTING-MIB
1.3.6.1.4.1.9.9.719.1ciscoUnifiedComputingMIBObjectsCISCO-UNIFIED-COMPUTING-MIB
Numeric OIDNameModule
1.3.6.1.4.1.9.9.719.1.15cucsEquipmentObjectsCISCO-UNIFIED-COMPUTING-EQUIPMENT-MIB
1.3.6.1.4.1.9.9.719.1.15.204cucsEquipmentBootDeviceConstraintsTableCISCO-UNIFIED-COMPUTING-EQUIPMENT-MIB
1.3.6.1.4.1.9.9.719.1.15.204.1cucsEquipmentBootDeviceConstraintsEntryCISCO-UNIFIED-COMPUTING-EQUIPMENT-MIB
1.3.6.1.4.1.9.9.719.1.15.204.1.3cucsEquipmentBootDeviceConstraintsRnCISCO-UNIFIED-COMPUTING-EQUIPMENT-MIB