CISCO-UNIFIED-COMPUTING-EQUIPMENT-MIB :: cucsEquipmentBootDeviceConstraintsDn

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsCISCO-UNIFIED-COMPUTING-EQUIPMENT-MIBcucsEquipmentBootDeviceConstraintsDn

cucsEquipmentBootDeviceConstraintsDn

Module: CISCO-UNIFIED-COMPUTING-EQUIPMENT-MIB

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

OID (numeric): 1.3.6.1.4.1.9.9.719.1.15.204.1.2

Node type: OBJECT-TYPE

Type: CucsManagedObjectDn

Access: read-only

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

What is cucsEquipmentBootDeviceConstraintsDn?

This holds the distinguished name (DN) -- the full path in the UCS Manager information tree -- that uniquely identifies 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. Because every boot device constraint is addressed by its DN rather than a simple index, this value is what lets a management station pull SNMP data for one exact boot device constraint out of the many similar instances that can exist across a single UCS domain. On a live system this object would return a path such as 'sys/chassis-2/blade-5/boot-device-constraints', pinpointing that one instance rather than a generic template.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.9.9.719.1.15.204.1.2
snmpwalk -v2c -c public <target> CISCO-UNIFIED-COMPUTING-EQUIPMENT-MIB::cucsEquipmentBootDeviceConstraintsDn

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.9.9.719.1.15.204.1.2.1
snmpget -v2c -c public <target> CISCO-UNIFIED-COMPUTING-EQUIPMENT-MIB::cucsEquipmentBootDeviceConstraintsDn.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::cucsEquipmentBootDeviceConstraintsDn 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.2cucsEquipmentBootDeviceConstraintsDnCISCO-UNIFIED-COMPUTING-EQUIPMENT-MIB