CISCO-UNIFIED-COMPUTING-COMPUTE-MIB :: cucsComputePCIeFatalReceiveStatsErrFatalErrors

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsCISCO-UNIFIED-COMPUTING-COMPUTE-MIBcucsComputePCIeFatalReceiveStatsErrFatalErrors

cucsComputePCIeFatalReceiveStatsErrFatalErrors

Module: CISCO-UNIFIED-COMPUTING-COMPUTE-MIB

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

OID (numeric): 1.3.6.1.4.1.9.9.719.1.9.21.1.13

Node type: OBJECT-TYPE

Type: Counter32

Access: read-only

Description: Cisco UCS compute:PCIeFatalReceiveStats:errFatalErrors managed object property

What is cucsComputePCIeFatalReceiveStatsErrFatalErrors?

This Counter32 is a free-running, cumulative tally of PCIe ERR_FATAL messages recorded against this PCIe endpoint's receive path since the counter was last reset by a reboot or reseat; concretely, the link partner signalled an unrecoverable (fatal) PCIe error condition over the ERR_FATAL sideband message. Because it never wraps back to zero on its own, an admin uses it as the lifetime baseline against which the 15-minute/hourly/daily/weekly gauges on this same row are compared to spot fresh activity. A blade that shipped with this counter at 0 and now reads 187 has accumulated 187 such faults since it was last powered up, which on a healthy riser should stay at 0.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.9.9.719.1.9.21.1.13
snmpwalk -v2c -c public <target> CISCO-UNIFIED-COMPUTING-COMPUTE-MIB::cucsComputePCIeFatalReceiveStatsErrFatalErrors

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.9.9.719.1.9.21.1.13.1
snmpget -v2c -c public <target> CISCO-UNIFIED-COMPUTING-COMPUTE-MIB::cucsComputePCIeFatalReceiveStatsErrFatalErrors.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::cucsComputePCIeFatalReceiveStatsErrFatalErrors 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.21cucsComputePCIeFatalReceiveStatsTableCISCO-UNIFIED-COMPUTING-COMPUTE-MIB
1.3.6.1.4.1.9.9.719.1.9.21.1cucsComputePCIeFatalReceiveStatsEntryCISCO-UNIFIED-COMPUTING-COMPUTE-MIB
1.3.6.1.4.1.9.9.719.1.9.21.1.13cucsComputePCIeFatalReceiveStatsErrFatalErrorsCISCO-UNIFIED-COMPUTING-COMPUTE-MIB