CISCO-UNIFIED-COMPUTING-COMPUTE-MIB :: cucsComputeServerDiscPolicyFsmCurrentFsm

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsCISCO-UNIFIED-COMPUTING-COMPUTE-MIBcucsComputeServerDiscPolicyFsmCurrentFsm

cucsComputeServerDiscPolicyFsmCurrentFsm

Module: CISCO-UNIFIED-COMPUTING-COMPUTE-MIB

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

OID (numeric): 1.3.6.1.4.1.9.9.719.1.9.54.1.5

Node type: OBJECT-TYPE

Type: CucsComputeServerDiscPolicyFsmCurrentFsm

Access: read-only

Description: Cisco UCS compute:ServerDiscPolicyFsm:currentFsm managed object property

What is cucsComputeServerDiscPolicyFsmCurrentFsm?

The 'currentFsm' property names the specific finite-state-machine template this workflow record is executing, for example the internal name for propagating a discovery-policy change. Knowing which named FSM is running tells an admin what kind of operation is actually in flight, since a discovery policy can trigger more than one type of internal workflow over its lifetime. This might read a value such as `ConfigDiscoveryPolicy`, identifying the specific workflow currently or most recently associated with this policy.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.9.9.719.1.9.54.1.5
snmpwalk -v2c -c public <target> CISCO-UNIFIED-COMPUTING-COMPUTE-MIB::cucsComputeServerDiscPolicyFsmCurrentFsm

Get a specific instance (index 1):

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

SNMPv3 example:

snmpget -v3 -l authPriv -u snmpv3-user -a SHA -A "AuthPassword1" -x AES -X "PrivPassword1" <target> cucsComputeServerDiscPolicyFsmCurrentFsm.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::cucsComputeServerDiscPolicyFsmCurrentFsm 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.54cucsComputeServerDiscPolicyFsmTableCISCO-UNIFIED-COMPUTING-COMPUTE-MIB
1.3.6.1.4.1.9.9.719.1.9.54.1cucsComputeServerDiscPolicyFsmEntryCISCO-UNIFIED-COMPUTING-COMPUTE-MIB
1.3.6.1.4.1.9.9.719.1.9.54.1.5cucsComputeServerDiscPolicyFsmCurrentFsmCISCO-UNIFIED-COMPUTING-COMPUTE-MIB