CISCO-UNIFIED-COMPUTING-COMPUTE-MIB :: cucsComputePCIeFatalStatsAcsViolationErrors15MinH

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsCISCO-UNIFIED-COMPUTING-COMPUTE-MIBcucsComputePCIeFatalStatsAcsViolationErrors15MinH

cucsComputePCIeFatalStatsAcsViolationErrors15MinH

Module: CISCO-UNIFIED-COMPUTING-COMPUTE-MIB

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

OID (numeric): 1.3.6.1.4.1.9.9.719.1.9.22.1.6

Node type: OBJECT-TYPE

Type: Gauge32

Access: read-only

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

What is cucsComputePCIeFatalStatsAcsViolationErrors15MinH?

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 historical high-water mark: the highest count of this error type ever recorded in a single 15-minute 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 15-minute burst. For example, if this counter shows 5 while the live 15Min bucket currently reads 0, it means five such errors (e.g. a non-compliant mezzanine card attempting direct peer-to-peer DMA that the platform's ACS policy blocks and flags) occurred together at some point in an earlier 15-minute 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.6
snmpwalk -v2c -c public <target> CISCO-UNIFIED-COMPUTING-COMPUTE-MIB::cucsComputePCIeFatalStatsAcsViolationErrors15MinH

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.9.9.719.1.9.22.1.6.1
snmpget -v2c -c public <target> CISCO-UNIFIED-COMPUTING-COMPUTE-MIB::cucsComputePCIeFatalStatsAcsViolationErrors15MinH.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::cucsComputePCIeFatalStatsAcsViolationErrors15MinH 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.6cucsComputePCIeFatalStatsAcsViolationErrors15MinHCISCO-UNIFIED-COMPUTING-COMPUTE-MIB