CISCO-UNIFIED-COMPUTING-COMPUTE-MIB :: cucsComputeCartridgeOperQualifierReason

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsCISCO-UNIFIED-COMPUTING-COMPUTE-MIBcucsComputeCartridgeOperQualifierReason

cucsComputeCartridgeOperQualifierReason

Module: CISCO-UNIFIED-COMPUTING-COMPUTE-MIB

OID (symbolic): CISCO-UNIFIED-COMPUTING-COMPUTE-MIB::cucsComputeCartridgeOperQualifierReason

OID (numeric): 1.3.6.1.4.1.9.9.719.1.9.71.1.11

Node type: OBJECT-TYPE

Type: SnmpAdminString

Access: read-only

Description: Cisco UCS compute:Cartridge:operQualifierReason managed object property

What is cucsComputeCartridgeOperQualifierReason?

This SnmpAdminString property holds the human-readable text explaining why this cartridge's operational state is currently what it is, the cartridge-level counterpart to cucsComputeBoardControllerOperQualifierReason. An admin seeing a cartridge reported as degraded or inoperable would read this qualifier text to get the actual diagnostic detail, such as a specific failed component or fault condition, rather than just the bare numeric status. This is typically the first place an admin looks after an alarm to understand what specifically is wrong before opening a hardware case.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.9.9.719.1.9.71.1.11
snmpwalk -v2c -c public <target> CISCO-UNIFIED-COMPUTING-COMPUTE-MIB::cucsComputeCartridgeOperQualifierReason

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.9.9.719.1.9.71.1.11.1
snmpget -v2c -c public <target> CISCO-UNIFIED-COMPUTING-COMPUTE-MIB::cucsComputeCartridgeOperQualifierReason.1

SNMPv3 example:

snmpget -v3 -l authPriv -u snmpv3-user -a SHA -A "AuthPassword1" -x AES -X "PrivPassword1" <target> cucsComputeCartridgeOperQualifierReason.1

Start monitoring Cisco UCS blade servers and chassis with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the CISCO-UNIFIED-COMPUTING-COMPUTE-MIB::cucsComputeCartridgeOperQualifierReason OID value, configure state conditions and alerts, and monitor any Cisco UCS blade servers and chassis 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.9cucsComputeObjectsCISCO-UNIFIED-COMPUTING-COMPUTE-MIB
1.3.6.1.4.1.9.9.719.1.9.71cucsComputeCartridgeTableCISCO-UNIFIED-COMPUTING-COMPUTE-MIB
1.3.6.1.4.1.9.9.719.1.9.71.1cucsComputeCartridgeEntryCISCO-UNIFIED-COMPUTING-COMPUTE-MIB
1.3.6.1.4.1.9.9.719.1.9.71.1.11cucsComputeCartridgeOperQualifierReasonCISCO-UNIFIED-COMPUTING-COMPUTE-MIB