CISCO-UNIFIED-COMPUTING-COMPUTE-MIB :: cucsComputePCIeFatalProtocolStatsFlowControlErrors2Weeks

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsCISCO-UNIFIED-COMPUTING-COMPUTE-MIBcucsComputePCIeFatalProtocolStatsFlowControlErrors2Weeks

cucsComputePCIeFatalProtocolStatsFlowControlErrors2Weeks

Module: CISCO-UNIFIED-COMPUTING-COMPUTE-MIB

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

OID (numeric): 1.3.6.1.4.1.9.9.719.1.9.20.1.29

Node type: OBJECT-TYPE

Type: Gauge32

Access: read-only

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

What is cucsComputePCIeFatalProtocolStatsFlowControlErrors2Weeks?

This Gauge32 reports the count of PCIe flow-control protocol errors accumulated specifically within the last 14 days — that is, the link's credit-based flow-control bookkeeping between the two ends of the PCIe link became inconsistent — and rolls forward on that period rather than accumulating forever like the base Counter32 for this error type. A rising value here (rather than a flat one inherited from months ago) is what tells an admin that this specific PCIe error is happening right now and worth an immediate look, not just a historical scar. For example, seeing this climb from 22 to 25 across two SNMP polls during the last 14 days window would point to an active, ongoing PCIe fault on this component rather than a one-time event from long ago.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.9.9.719.1.9.20.1.29
snmpwalk -v2c -c public <target> CISCO-UNIFIED-COMPUTING-COMPUTE-MIB::cucsComputePCIeFatalProtocolStatsFlowControlErrors2Weeks

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.9.9.719.1.9.20.1.29.1
snmpget -v2c -c public <target> CISCO-UNIFIED-COMPUTING-COMPUTE-MIB::cucsComputePCIeFatalProtocolStatsFlowControlErrors2Weeks.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::cucsComputePCIeFatalProtocolStatsFlowControlErrors2Weeks 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.29cucsComputePCIeFatalProtocolStatsFlowControlErrors2WeeksCISCO-UNIFIED-COMPUTING-COMPUTE-MIB