CISCO-UNIFIED-COMPUTING-COMPUTE-MIB :: cucsComputePCIeFatalProtocolStatsThresholded

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsCISCO-UNIFIED-COMPUTING-COMPUTE-MIBcucsComputePCIeFatalProtocolStatsThresholded

cucsComputePCIeFatalProtocolStatsThresholded

Module: CISCO-UNIFIED-COMPUTING-COMPUTE-MIB

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

OID (numeric): 1.3.6.1.4.1.9.9.719.1.9.20.1.24

Node type: OBJECT-TYPE

Type: CucsComputePCIeFatalProtocolStatsThresholded

Access: read-only

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

What is cucsComputePCIeFatalProtocolStatsThresholded?

This enumerated field records which, if any, of the configured alarm thresholds for the PCIe protocol-error values in this row have been crossed — for instance a configured maximum-errors-per-interval threshold on one of the PCIe error counters in this row — and is what actually drives a UCS Manager fault or SNMP trap rather than the raw value alone. An admin watching this field can tell at a glance whether a number that looks high is still within the configured normal range or has already tripped a minor/major/critical threshold that needs a service ticket. For example, this field flipping from a normal state to an upper-critical indication is what would actually page an on-call engineer, even before they look at the raw measurement.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.9.9.719.1.9.20.1.24
snmpwalk -v2c -c public <target> CISCO-UNIFIED-COMPUTING-COMPUTE-MIB::cucsComputePCIeFatalProtocolStatsThresholded

Get a specific instance (index 1):

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

SNMPv3 example:

snmpget -v3 -l authPriv -u snmpv3-user -a SHA -A "AuthPassword1" -x AES -X "PrivPassword1" <target> cucsComputePCIeFatalProtocolStatsThresholded.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::cucsComputePCIeFatalProtocolStatsThresholded 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.24cucsComputePCIeFatalProtocolStatsThresholdedCISCO-UNIFIED-COMPUTING-COMPUTE-MIB