CISCO-UNIFIED-COMPUTING-COMPUTE-MIB :: cucsComputePCIeFatalProtocolStatsFlowControlErrors1DayH

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsCISCO-UNIFIED-COMPUTING-COMPUTE-MIBcucsComputePCIeFatalProtocolStatsFlowControlErrors1DayH

cucsComputePCIeFatalProtocolStatsFlowControlErrors1DayH

Module: CISCO-UNIFIED-COMPUTING-COMPUTE-MIB

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

OID (numeric): 1.3.6.1.4.1.9.9.719.1.9.20.1.17

Node type: OBJECT-TYPE

Type: Gauge32

Access: read-only

Description: Cisco UCS compute:PCIeFatalProtocolStats:flowControlErrors1DayH managed object property

What is cucsComputePCIeFatalProtocolStatsFlowControlErrors1DayH?

This Gauge32 holds the highest single-sample count of PCIe flow-control protocol errors that UCS Manager observed during any one collection interval within the last day, i.e. the link's credit-based flow-control bookkeeping between the two ends of the PCIe link became inconsistent, captured at its worst moment. Unlike the plain (non-H) gauge for this window, this high-water value stays latched at the worst reading for the rest of the window even if the fault stops recurring, which is what lets an admin catch a brief PCIe error burst that a simple end-of-window snapshot would have missed. For example, if a marginal riser produced a spike of 11 PCIe flow-control protocol errors in one polling cycle and then went quiet, this field would hold 11 until the last day window rolls forward, even though the plain gauge has since dropped to 0.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.9.9.719.1.9.20.1.17
snmpwalk -v2c -c public <target> CISCO-UNIFIED-COMPUTING-COMPUTE-MIB::cucsComputePCIeFatalProtocolStatsFlowControlErrors1DayH

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.9.9.719.1.9.20.1.17.1
snmpget -v2c -c public <target> CISCO-UNIFIED-COMPUTING-COMPUTE-MIB::cucsComputePCIeFatalProtocolStatsFlowControlErrors1DayH.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::cucsComputePCIeFatalProtocolStatsFlowControlErrors1DayH 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.20cucsComputePCIeFatalProtocolStatsTableCISCO-UNIFIED-COMPUTING-COMPUTE-MIB
1.3.6.1.4.1.9.9.719.1.9.20.1cucsComputePCIeFatalProtocolStatsEntryCISCO-UNIFIED-COMPUTING-COMPUTE-MIB
1.3.6.1.4.1.9.9.719.1.9.20.1.17cucsComputePCIeFatalProtocolStatsFlowControlErrors1DayHCISCO-UNIFIED-COMPUTING-COMPUTE-MIB