CISCO-UNIFIED-COMPUTING-SYSDEBUG-MIB :: cucsSysdebugLogExportPolicyFsmStageName

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsCISCO-UNIFIED-COMPUTING-SYSDEBUG-MIBcucsSysdebugLogExportPolicyFsmStageName

cucsSysdebugLogExportPolicyFsmStageName

Module: CISCO-UNIFIED-COMPUTING-SYSDEBUG-MIB

OID (symbolic): CISCO-UNIFIED-COMPUTING-SYSDEBUG-MIB::cucsSysdebugLogExportPolicyFsmStageName

OID (numeric): 1.3.6.1.4.1.9.9.719.1.47.34.1.6

Node type: OBJECT-TYPE

Type: CucsSysdebugLogExportPolicyFsmStageName

Access: read-only

Description: Cisco UCS sysdebug:LogExportPolicyFsmStage:name managed object property

What is cucsSysdebugLogExportPolicyFsmStageName?

This CucsSysdebugLogExportPolicyFsmStageName value is the name of one individual step (e.g. connect, transfer, verify) inside the FSM run for a log-export policy, drawn from a fixed list of named phases in that workflow. Because a workflow runs through several named steps in sequence, this field is how an admin identifies exactly which one this particular stage row corresponds to. For example, an admin drilling into a stalled log export to see which specific step it is stuck on, and this name field tells them which named step of that sequence they are currently looking at.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.9.9.719.1.47.34.1.6
snmpwalk -v2c -c public <target> CISCO-UNIFIED-COMPUTING-SYSDEBUG-MIB::cucsSysdebugLogExportPolicyFsmStageName

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.9.9.719.1.47.34.1.6.1
snmpget -v2c -c public <target> CISCO-UNIFIED-COMPUTING-SYSDEBUG-MIB::cucsSysdebugLogExportPolicyFsmStageName.1

Start monitoring Cisco UCS Manager-managed blade/rack servers and fabric interconnects with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the CISCO-UNIFIED-COMPUTING-SYSDEBUG-MIB::cucsSysdebugLogExportPolicyFsmStageName OID value, configure state conditions and alerts, and monitor any Cisco UCS Manager-managed blade/rack servers and 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.47cucsSysdebugObjectsCISCO-UNIFIED-COMPUTING-SYSDEBUG-MIB
1.3.6.1.4.1.9.9.719.1.47.34cucsSysdebugLogExportPolicyFsmStageTableCISCO-UNIFIED-COMPUTING-SYSDEBUG-MIB
1.3.6.1.4.1.9.9.719.1.47.34.1cucsSysdebugLogExportPolicyFsmStageEntryCISCO-UNIFIED-COMPUTING-SYSDEBUG-MIB
1.3.6.1.4.1.9.9.719.1.47.34.1.6cucsSysdebugLogExportPolicyFsmStageNameCISCO-UNIFIED-COMPUTING-SYSDEBUG-MIB