All MIBs › CISCO-UNIFIED-COMPUTING-COMPUTE-MIB › cucsComputePCIeFatalStatsAcsViolationErrors1Day
cucsComputePCIeFatalStatsAcsViolationErrors1Day
Module: CISCO-UNIFIED-COMPUTING-COMPUTE-MIB
OID (symbolic): CISCO-UNIFIED-COMPUTING-COMPUTE-MIB::cucsComputePCIeFatalStatsAcsViolationErrors1Day
OID (numeric): 1.3.6.1.4.1.9.9.719.1.9.22.1.7
Node type: OBJECT-TYPE
Type: Gauge32
Access: read-only
Description: Cisco UCS compute:PCIeFatalStats:acsViolationErrors1Day managed object property
What is cucsComputePCIeFatalStatsAcsViolationErrors1Day?
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-day 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-day 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.7 snmpwalk -v2c -c public <target> CISCO-UNIFIED-COMPUTING-COMPUTE-MIB::cucsComputePCIeFatalStatsAcsViolationErrors1Day
Get a specific instance (index 1):
snmpget -v2c -c public <target> 1.3.6.1.4.1.9.9.719.1.9.22.1.7.1 snmpget -v2c -c public <target> CISCO-UNIFIED-COMPUTING-COMPUTE-MIB::cucsComputePCIeFatalStatsAcsViolationErrors1Day.1
SNMPv3 example:
snmpget -v3 -l authPriv -u snmpv3-user -a SHA -A "AuthPassword1" -x AES -X "PrivPassword1" <target> cucsComputePCIeFatalStatsAcsViolationErrors1Day.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::cucsComputePCIeFatalStatsAcsViolationErrors1Day 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.7 | cucsComputePCIeFatalStatsAcsViolationErrors1Day | CISCO-UNIFIED-COMPUTING-COMPUTE-MIB |