All MIBs › CISCO-UNIFIED-COMPUTING-EQUIPMENT-MIB › cucsEquipmentBootDeviceConstraintsIsSupported
cucsEquipmentBootDeviceConstraintsIsSupported
Module: CISCO-UNIFIED-COMPUTING-EQUIPMENT-MIB
OID (symbolic): CISCO-UNIFIED-COMPUTING-EQUIPMENT-MIB::cucsEquipmentBootDeviceConstraintsIsSupported
OID (numeric): 1.3.6.1.4.1.9.9.719.1.15.204.1.7
Node type: OBJECT-TYPE
Type: TruthValue
Access: read-only
Description: Cisco UCS equipment:BootDeviceConstraints:isSupported managed object property
What is cucsEquipmentBootDeviceConstraintsIsSupported?
This is a true/false flag stating whether the boot-device type named in this constraint entry is actually supported on the associated hardware model. This is the flag UCS Manager's boot-policy validator checks before it will let an admin save a boot policy referencing that device type for that specific model, so a 'false' here is the direct cause of a rejected boot-policy assignment. A value of 'false' for an SD-card constraint entry would mean that particular server model has no supported SD boot device.
Examples
Walk all instances (SNMPv2c):
snmpwalk -v2c -c public <target> 1.3.6.1.4.1.9.9.719.1.15.204.1.7 snmpwalk -v2c -c public <target> CISCO-UNIFIED-COMPUTING-EQUIPMENT-MIB::cucsEquipmentBootDeviceConstraintsIsSupported
Get a specific instance (index 1):
snmpget -v2c -c public <target> 1.3.6.1.4.1.9.9.719.1.15.204.1.7.1 snmpget -v2c -c public <target> CISCO-UNIFIED-COMPUTING-EQUIPMENT-MIB::cucsEquipmentBootDeviceConstraintsIsSupported.1
SNMPv3 example:
snmpget -v3 -l authPriv -u snmpv3-user -a SHA -A "AuthPassword1" -x AES -X "PrivPassword1" <target> cucsEquipmentBootDeviceConstraintsIsSupported.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::cucsEquipmentBootDeviceConstraintsIsSupported 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 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.9 | cisco | CAT2600-MIB |
| 1.3.6.1.4.1.9.9 | ciscoMgmt | CISCO-SMI |
| 1.3.6.1.4.1.9.9.719 | ciscoUnifiedComputingMIB | CISCO-UNIFIED-COMPUTING-MIB |
| 1.3.6.1.4.1.9.9.719.1 | ciscoUnifiedComputingMIBObjects | CISCO-UNIFIED-COMPUTING-MIB |
| Numeric OID | Name | Module |
|---|---|---|
| 1.3.6.1.4.1.9.9.719.1.15 | cucsEquipmentObjects | CISCO-UNIFIED-COMPUTING-EQUIPMENT-MIB |
| 1.3.6.1.4.1.9.9.719.1.15.204 | cucsEquipmentBootDeviceConstraintsTable | CISCO-UNIFIED-COMPUTING-EQUIPMENT-MIB |
| 1.3.6.1.4.1.9.9.719.1.15.204.1 | cucsEquipmentBootDeviceConstraintsEntry | CISCO-UNIFIED-COMPUTING-EQUIPMENT-MIB |
| 1.3.6.1.4.1.9.9.719.1.15.204.1.7 | cucsEquipmentBootDeviceConstraintsIsSupported | CISCO-UNIFIED-COMPUTING-EQUIPMENT-MIB |