CISCO-UNIFIED-COMPUTING-COMPUTE-MIB :: cucsComputeServerDiscPolicyFsmStageName

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsCISCO-UNIFIED-COMPUTING-COMPUTE-MIBcucsComputeServerDiscPolicyFsmStageName

cucsComputeServerDiscPolicyFsmStageName

Module: CISCO-UNIFIED-COMPUTING-COMPUTE-MIB

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

OID (numeric): 1.3.6.1.4.1.9.9.719.1.9.55.1.6

Node type: OBJECT-TYPE

Type: CucsComputeServerDiscPolicyFsmStageName

Access: read-only

Description: Cisco UCS compute:ServerDiscPolicyFsmStage:name managed object property

What is cucsComputeServerDiscPolicyFsmStageName?

This holds the name of this specific stage within the discovery policy's workflow, for example the internal step name UCS Manager uses when applying a configuration change. The stage name is what an admin actually recognizes when reading FSM history, since it names the concrete action being performed rather than an abstract sequence number. A stage might be named `ConfigureLocal`, identifying it as the step that applies settings locally before any remote propagation occurs.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.9.9.719.1.9.55.1.6
snmpwalk -v2c -c public <target> CISCO-UNIFIED-COMPUTING-COMPUTE-MIB::cucsComputeServerDiscPolicyFsmStageName

Get a specific instance (index 1):

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

SNMPv3 example:

snmpget -v3 -l authPriv -u snmpv3-user -a SHA -A "AuthPassword1" -x AES -X "PrivPassword1" <target> cucsComputeServerDiscPolicyFsmStageName.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::cucsComputeServerDiscPolicyFsmStageName 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.55cucsComputeServerDiscPolicyFsmStageTableCISCO-UNIFIED-COMPUTING-COMPUTE-MIB
1.3.6.1.4.1.9.9.719.1.9.55.1cucsComputeServerDiscPolicyFsmStageEntryCISCO-UNIFIED-COMPUTING-COMPUTE-MIB
1.3.6.1.4.1.9.9.719.1.9.55.1.6cucsComputeServerDiscPolicyFsmStageNameCISCO-UNIFIED-COMPUTING-COMPUTE-MIB