ARISTA-HARDWARE-UTILIZATION-MIB

        This MIB contains information about the capacity and
utilization of hardware resources on Arista devices.
        
Arista ships and supports devices which perform packet
forwarding decisions in hardware. To make these forwarding
decisions (L2 bridging, input and output access list, L3
forwarding based on IP destination etc.), the devices use
information programmed in various hardware
resources. Examples of such hardware resources are the
hash table used for MAC address lookup, TCAM for
destination IP lookup etc. 
        
Each of Arista's devices have different hardware resource
capacity or size limits. It is extremely useful for a
Network Management system to be able to query and monitor
the utilization of these hardware resources. Due to
unxpected network event or configuration change, it is
possible that a specific hardware resource is over
utilized and there is no room to program additional
entries. For example, a routing mis-configuration can
result in overflowing the L3 forwarding TCAM. This may
be detrimental to the network operation. So it's extremely
useful to monitor the utilization of the various hardware
resources of a specific device.
        
On some devices, due to hardware design considerations,
several features may have to share a single hardware
resource. If one feature ends up using more of the same
resource, it can affect the functionality of another
feature. This is another reason to have visibility into
the hardware resource usage.
        
The hardware element that makes the forwarding decision is
frequently referred to as the 'Forwarding ASIC' or
'Forwarding Chip'. In this MIB document we refer to this
hardware element as 'Forwarding Element'. Even though a
device can have multiple forwarding elements, the information
programmed in each of the forwarding element is typically
the same. But there are some cases, where this is not the
case. In such instances, the utilization of relevant
hardware resource(s) may not be the same across all the
forwarding elements.
        
This MIB module provides the hardware capacity and
utilization information for various resources in a generic
manner, that's applicable to all Arista devices.
    
Source file
ARISTA-HARDWARE-UTILIZATION-MIB
Last revised
Identity
aristaHardwareUtilizationMIB
Base OID
1.3.6.1.4.1.30065.3.22
Imported Objects
ARISTA-SMI-MIB aristaMibs
SNMPv2-CONF MODULE-COMPLIANCE (no object page) NOTIFICATION-GROUP (no object page) OBJECT-GROUP (no object page)
SNMPv2-SMI Counter32 MODULE-IDENTITY (no object page) NOTIFICATION-TYPE (no object page) OBJECT-TYPE (no object page)
SNMPv2-TC DisplayString TimeStamp
Net-SNMP examples using the arista MIB directory Show commands

These commands use the standard Observium installation path and load the selected MIB variant before the RFC and Net-SNMP directories.

Translate the module identity
/usr/bin/snmptranslate -Pud -Ir -On -m 'ARISTA-HARDWARE-UTILIZATION-MIB' -M '/opt/observium/mibs/arista:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'ARISTA-HARDWARE-UTILIZATION-MIB::aristaHardwareUtilizationMIB'
Walk the MIB subtree
/usr/bin/snmpbulkwalk -v2c -c '<community>' -Pud -Ir -OQUs -m 'ARISTA-HARDWARE-UTILIZATION-MIB' -M '/opt/observium/mibs/arista:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'ARISTA-HARDWARE-UTILIZATION-MIB::aristaHardwareUtilizationMIB'
How SNMP, Net-SNMP, MIB paths, and variants work
Objects (18)
.1.3.6.1.4.1.30065.3.22
.1.3.6.1.4.1.30065.3.22.0
.1.3.6.1.4.1.30065.3.22.1
.1.3.6.1.4.1.30065.3.22.1.1
.1.3.6.1.4.1.30065.3.22.1.1.1
OctetString
.1.3.6.1.4.1.30065.3.22.1.1.1.1
OctetString
.1.3.6.1.4.1.30065.3.22.1.1.1.10
OctetString
.1.3.6.1.4.1.30065.3.22.1.1.1.2
OctetString
.1.3.6.1.4.1.30065.3.22.1.1.1.3
.1.3.6.1.4.1.30065.3.22.1.1.1.4
.1.3.6.1.4.1.30065.3.22.1.1.1.5
.1.3.6.1.4.1.30065.3.22.1.1.1.6
.1.3.6.1.4.1.30065.3.22.1.1.1.7
.1.3.6.1.4.1.30065.3.22.1.1.1.8
.1.3.6.1.4.1.30065.3.22.1.1.1.9
.1.3.6.1.4.1.30065.3.22.2
.1.3.6.1.4.1.30065.3.22.2.1
.1.3.6.1.4.1.30065.3.22.2.2
Dependencies (4) 4 direct Show tree and compile order Hide dependency details

Each imported module is resolved in the importing module's source directory first, then through the normal default-variant rules.

Dependency tree
Dependency-first compile order
  1. SNMPv2-SMIrfc
  2. ARISTA-SMI-MIBarista
  3. SNMPv2-CONFrfc
  4. SNMPv2-TCrfc
  5. ARISTA-HARDWARE-UTILIZATION-MIBaristaselected
Conformance Groups (2)
The collection of objects that provide counter information
for hardware resource utilization.
.1.3.6.1.4.1.30065.3.22.2.2.1
The notification(s) generated by the system if the hardware
utilization of a specific resource exceeds configured
threshold.
.1.3.6.1.4.1.30065.3.22.2.2.2
Compliance Statements (1)

OID .1.3.6.1.4.1.30065.3.22.2.1.1
The compliance statement for Arista switches that implement
the ARISTA-HARDWARE-CAPACITY-MIB.
Required groups
Notifications / Traps (1)
NameOIDDescription
.1.3.6.1.4.1.30065.3.22.0.1
This notification is generated when the hardware utilization
crosses the specified threshold.