CISCO-UNIFIED-COMPUTING-COMPUTE-MIB :: cucsComputePCIeFatalStatsMalformedTLPErrors1WeekH

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsCISCO-UNIFIED-COMPUTING-COMPUTE-MIBcucsComputePCIeFatalStatsMalformedTLPErrors1WeekH

cucsComputePCIeFatalStatsMalformedTLPErrors1WeekH

Module: CISCO-UNIFIED-COMPUTING-COMPUTE-MIB

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

OID (numeric): 1.3.6.1.4.1.9.9.719.1.9.22.1.22

Node type: OBJECT-TYPE

Type: Gauge32

Access: read-only

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

What is cucsComputePCIeFatalStatsMalformedTLPErrors1WeekH?

This field is part of the PCIeFatalStats table's tally of malformed-TLP (Transaction Layer Packet) errors on this compute node's PCIe fabric — a TLP is the basic packet PCIe devices use to exchange data and requests, and 'malformed' means a packet arrived that violates the PCIe framing/format rules. This is the historical high-water mark: the highest count of this error type ever recorded in a single 1-week window within the retention history UCS Manager keeps for this compute node's PCIe fatal-error stats, so a quiet current reading doesn't hide an earlier 1-week burst. For example, if this counter shows 5 while the live 1Week bucket currently reads 0, it means five such errors (e.g. a firmware bug on an adapter card generating a TLP with an invalid header field that the receiving PCIe root port rejects and counts here) occurred together at some point in an earlier 1-week window, even though none are happening right now.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.9.9.719.1.9.22.1.22
snmpwalk -v2c -c public <target> CISCO-UNIFIED-COMPUTING-COMPUTE-MIB::cucsComputePCIeFatalStatsMalformedTLPErrors1WeekH

Get a specific instance (index 1):

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

SNMPv3 example:

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