CISCO-UNIFIED-COMPUTING-COMPUTE-MIB :: cucsComputePCIeFatalStatsAcsViolationErrors1Week

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsCISCO-UNIFIED-COMPUTING-COMPUTE-MIBcucsComputePCIeFatalStatsAcsViolationErrors1Week

cucsComputePCIeFatalStatsAcsViolationErrors1Week

Module: CISCO-UNIFIED-COMPUTING-COMPUTE-MIB

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

OID (numeric): 1.3.6.1.4.1.9.9.719.1.9.22.1.11

Node type: OBJECT-TYPE

Type: Gauge32

Access: read-only

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

What is cucsComputePCIeFatalStatsAcsViolationErrors1Week?

This field is part of the PCIeFatalStats table's tally of ACS (Access Control Services) violation errors on this compute node's PCIe fabric — ACS is the PCIe feature that isolates and redirects peer-to-peer traffic between devices, and a violation means some device attempted a peer-to-peer transfer that broke that isolation policy. This is the count of this specific error type accumulated during the most recently completed 1-week collection window for this compute node, which is what lets an admin tell whether the fault is a one-off blip or actively recurring at that timescale. For example, a jump from 0 to 2 in this 1-week window would point to something like e.g. a non-compliant mezzanine card attempting direct peer-to-peer DMA that the platform's ACS policy blocks and flags happening twice during that period specifically, rather than a single lingering old error.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.9.9.719.1.9.22.1.11
snmpwalk -v2c -c public <target> CISCO-UNIFIED-COMPUTING-COMPUTE-MIB::cucsComputePCIeFatalStatsAcsViolationErrors1Week

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.9.9.719.1.9.22.1.11.1
snmpget -v2c -c public <target> CISCO-UNIFIED-COMPUTING-COMPUTE-MIB::cucsComputePCIeFatalStatsAcsViolationErrors1Week.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::cucsComputePCIeFatalStatsAcsViolationErrors1Week 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.11cucsComputePCIeFatalStatsAcsViolationErrors1WeekCISCO-UNIFIED-COMPUTING-COMPUTE-MIB