All MIBs › CISCO-UNIFIED-COMPUTING-COMPUTE-MIB › cucsComputePCIeFatalStatsPoisonedTLPErrors
cucsComputePCIeFatalStatsPoisonedTLPErrors
Module: CISCO-UNIFIED-COMPUTING-COMPUTE-MIB
OID (symbolic): CISCO-UNIFIED-COMPUTING-COMPUTE-MIB::cucsComputePCIeFatalStatsPoisonedTLPErrors
OID (numeric): 1.3.6.1.4.1.9.9.719.1.9.22.1.23
Node type: OBJECT-TYPE
Type: Counter32
Access: read-only
Description: Cisco UCS compute:PCIeFatalStats:poisonedTLPErrors managed object property
What is cucsComputePCIeFatalStatsPoisonedTLPErrors?
This field is part of the PCIeFatalStats table's tally of poisoned-TLP errors on this compute node's PCIe fabric — a poisoned TLP is one the sending device deliberately marks as carrying corrupted data (the EP/poison bit) instead of silently forwarding bad data. This is the running cumulative total of this error type counted since this counter object was created or last reset/wrapped — the base tally that the 15-minute/hourly/daily/weekly figures on this same compute node's PCIeFatalStats table are derived from. For example, a steadily climbing raw count (say from 12 to 15) while the current 15-minute window shows 0 tells an admin the errors (e.g. a memory ECC error on a network adapter causing the adapter to poison the TLP carrying that corrupted payload instead of passing it through unflagged) happened earlier in the counter's lifetime, not in the last 15 minutes.
Examples
Walk all instances (SNMPv2c):
snmpwalk -v2c -c public <target> 1.3.6.1.4.1.9.9.719.1.9.22.1.23 snmpwalk -v2c -c public <target> CISCO-UNIFIED-COMPUTING-COMPUTE-MIB::cucsComputePCIeFatalStatsPoisonedTLPErrors
Get a specific instance (index 1):
snmpget -v2c -c public <target> 1.3.6.1.4.1.9.9.719.1.9.22.1.23.1 snmpget -v2c -c public <target> CISCO-UNIFIED-COMPUTING-COMPUTE-MIB::cucsComputePCIeFatalStatsPoisonedTLPErrors.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::cucsComputePCIeFatalStatsPoisonedTLPErrors 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 OID | Name | Module |
|---|---|---|
| 1 | iso | LANART-AGENT |
| 1.3 | org | AirPair-MIB |
| 1.3.6 | dod | AirPair-MIB |
| 1.3.6.1 | internet | AirPair-MIB |
| 1.3.6.1.4 | private | AirPair-MIB |
| 1.3.6.1.4.1 | enterprises | AirPair-MIB |
| 1.3.6.1.4.1.9 | cisco | CAT2600-MIB |
| 1.3.6.1.4.1.9.9 | ciscoMgmt | CISCO-SMI |
| 1.3.6.1.4.1.9.9.719 | ciscoUnifiedComputingMIB | CISCO-UNIFIED-COMPUTING-MIB |
| 1.3.6.1.4.1.9.9.719.1 | ciscoUnifiedComputingMIBObjects | CISCO-UNIFIED-COMPUTING-MIB |
| Numeric OID | Name | Module |
|---|---|---|
| 1.3.6.1.4.1.9.9.719.1.9 | cucsComputeObjects | CISCO-UNIFIED-COMPUTING-COMPUTE-MIB |
| 1.3.6.1.4.1.9.9.719.1.9.22 | cucsComputePCIeFatalStatsTable | CISCO-UNIFIED-COMPUTING-COMPUTE-MIB |
| 1.3.6.1.4.1.9.9.719.1.9.22.1 | cucsComputePCIeFatalStatsEntry | CISCO-UNIFIED-COMPUTING-COMPUTE-MIB |
| 1.3.6.1.4.1.9.9.719.1.9.22.1.23 | cucsComputePCIeFatalStatsPoisonedTLPErrors | CISCO-UNIFIED-COMPUTING-COMPUTE-MIB |