All MIBs › CISCO-UNIFIED-COMPUTING-COMPUTE-MIB › cucsComputePCIeFatalStatsAcsViolationErrors1DayH
cucsComputePCIeFatalStatsAcsViolationErrors1DayH
Module: CISCO-UNIFIED-COMPUTING-COMPUTE-MIB
OID (symbolic): CISCO-UNIFIED-COMPUTING-COMPUTE-MIB::cucsComputePCIeFatalStatsAcsViolationErrors1DayH
OID (numeric): 1.3.6.1.4.1.9.9.719.1.9.22.1.8
Node type: OBJECT-TYPE
Type: Gauge32
Access: read-only
Description: Cisco UCS compute:PCIeFatalStats:acsViolationErrors1DayH managed object property
What is cucsComputePCIeFatalStatsAcsViolationErrors1DayH?
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 1-day 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-day burst. For example, if this counter shows 5 while the live 1Day 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 1-day 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.8 snmpwalk -v2c -c public <target> CISCO-UNIFIED-COMPUTING-COMPUTE-MIB::cucsComputePCIeFatalStatsAcsViolationErrors1DayH
Get a specific instance (index 1):
snmpget -v2c -c public <target> 1.3.6.1.4.1.9.9.719.1.9.22.1.8.1 snmpget -v2c -c public <target> CISCO-UNIFIED-COMPUTING-COMPUTE-MIB::cucsComputePCIeFatalStatsAcsViolationErrors1DayH.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::cucsComputePCIeFatalStatsAcsViolationErrors1DayH 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.8 | cucsComputePCIeFatalStatsAcsViolationErrors1DayH | CISCO-UNIFIED-COMPUTING-COMPUTE-MIB |