CISCO-UNIFIED-COMPUTING-COMPUTE-MIB :: cucsComputePCIeFatalStatsIntervals

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsCISCO-UNIFIED-COMPUTING-COMPUTE-MIBcucsComputePCIeFatalStatsIntervals

cucsComputePCIeFatalStatsIntervals

Module: CISCO-UNIFIED-COMPUTING-COMPUTE-MIB

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

OID (numeric): 1.3.6.1.4.1.9.9.719.1.9.22.1.13

Node type: OBJECT-TYPE

Type: Gauge32

Access: read-only

Description: Cisco UCS compute:PCIeFatalStats:intervals managed object property

What is cucsComputePCIeFatalStatsIntervals?

The desc ties this to the 'intervals' property of this compute node's PCIeFatalStats table — it is the count of statistics-collection intervals actually represented in this stats object's current sample history. Operationally, this tells you how many sampling cycles of history the 15-minute/hourly/daily/weekly/2-week figures above genuinely reflect, so if intervals is still low right after a server was added, the longer-window peak fields haven't filled in yet and shouldn't be read as proof of a clean multi-week history. For example, cucsComputePCIeFatalStatsIntervals reading 4 shortly after a blade is inserted means only four sampling cycles of PCIe fatal-error data exist yet, so the 2Weeks/2WeeksH fields are effectively still empty rather than confirming two genuinely quiet weeks.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.9.9.719.1.9.22.1.13
snmpwalk -v2c -c public <target> CISCO-UNIFIED-COMPUTING-COMPUTE-MIB::cucsComputePCIeFatalStatsIntervals

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.9.9.719.1.9.22.1.13.1
snmpget -v2c -c public <target> CISCO-UNIFIED-COMPUTING-COMPUTE-MIB::cucsComputePCIeFatalStatsIntervals.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::cucsComputePCIeFatalStatsIntervals 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.22cucsComputePCIeFatalStatsTableCISCO-UNIFIED-COMPUTING-COMPUTE-MIB
1.3.6.1.4.1.9.9.719.1.9.22.1cucsComputePCIeFatalStatsEntryCISCO-UNIFIED-COMPUTING-COMPUTE-MIB
1.3.6.1.4.1.9.9.719.1.9.22.1.13cucsComputePCIeFatalStatsIntervalsCISCO-UNIFIED-COMPUTING-COMPUTE-MIB