Arista: SNMP MIB browser (OID list)
Download Arista MIB files or View SNMP OID List
MIB files with the search keyword "22.214.171.124.4.1.30065." in their Object ID's (OID)
Arista Networks, Inc.is a prominent player in the computer networking and data center technology sector. Founded in 2004 by Andy Bechtolsheim, David Cheriton, and Ken Duda, Arista has swiftly emerged as a leader in the development and provision of cloud networking solutions. The company specializes in designing and manufacturing high-performance Ethernet switches used in data centers, cloud computing environments, and other critical networking applications. Arista`s switches are renowned for their speed, scalability, and reliability, making them a preferred choice for organizations seeking robust and efficient network infrastructure. Arista`s commitment to innovation and its pioneering use of open-source software have contributed to its success in delivering networking solutions tailored to the demands of modern cloud computing and data center environments. With a focus on software-driven networking, Arista continues to shape the landscape of network technologies and remains a key player in the ever-evolving world of data communications and cloud computing.
What is SNMP, MIB, and OID?
SNMP stands for Simple Network Management Protocol. It is a standard protocol used for monitoring and managing network devices, such as routers, switches, and servers. SNMP MIB (Management Information Base) files contain information about the parameters and variables that can be monitored or managed on a network device. They provide a structured way to access and control device settings. An OID is a unique identifier assigned to each object in a MIB. OIDs are represented as a sequence of numbers separated by dots (e.g., 126.96.36.199.188.8.131.52). They serve as a way to locate and reference specific data points within a MIB. OIDs are used to request and retrieve information from network devices via SNMP. Learn more about SNMP protocol in this step-by-step tutorial.
How to access Arista MIBs or OIDs online?
Yes, you can search, browse, download or view any Arista MIBs or OIDs online without downloading anything or using third-party applications.
How to download Arista SNMP MIB files?
To download Arista MIB files, click on the MIB file you need from the list above. Then, select the format in which you want to download the MIB file (.mib, .csv, .json, .yml) by clicking on the corresponding icon.
What is the purpose of these Arista MIB files?
Below, you can find a list of Arista MIB files along with their descriptions:
- ARISTA-BGP4V2-MIB (aristaBgp4V2 - 184.108.40.206.4.1.30065.4.1): The MIB module for the BGP-4 protocol. This version was published in draft-ietf-idr-bgp4-mibv2-13, and modified to be homed inside the Arista enterprise. There were no other modifications. Copyright (C) The IETF Trust (2012). This version of this MIB module is part of draft-ietf-idr-bgp4-mibv2-13.txt; see the draft itself for full legal notices.
- ARISTA-VRF-MIB (aristaVrfMIB - 220.127.116.11.4.1.30065.3.18): This MIB contains information related to Virtual Routing and Forwarding (VRF). VRF is a mechanism by which a single device can provide independent routing instances. This allows customers to virtually isolate network traffic, and also use overlapping IP addresses. Layer3 or routed interfaces in the system will belong to one VRF at a time. The datapath forwarding logic uses the VRF membership of the input interface to determine a specific forwarding table to use for routing the traffic. VRF can also be used to isolate management traffic from the rest of the data plane traffic. This MIB module provides the following pieces of information: * A table of all VRFs configured in the system * A table that contains the VRF membership information for all routed interfaces in the system by sparsely augmenting the ifTable.
- ARISTA-DAEMON-MIB (aristaDaemonMIB - 18.104.22.168.4.1.30065.3.17): The MIB module for managing the state of custom agents for Arista EOS.
- ARISTA-QUEUE-MIB (aristaQueueMIB - 22.214.171.124.4.1.30065.3.6): The MIB module is for managing interface queuing on Arista devices. Arista Networks has a number of products. This MIB generalizes ingress and egress queue counters supported on all Arista products. Therefore, a platform may not support all table indices and counters listed in this MIB. For example, ingressQueueIndex in aristaIngressQueueTable, aristaEgressQueuePktsDroppedQFull, aristaEgressQueuePktsDroppedNoBuffer, and aristaEgressQueueDropPrec in aristaEgressQueueTable are not supported in 7050 series switches.
- ARISTA-ENTITY-SENSOR-MIB (aristaEntSensorMIB - 126.96.36.199.4.1.30065.3.12): This MIB module augments the entPhySensorTable of ENTITY-SENSOR-MIB to provide threshold information for various sensors in the system. For example, a given device may have several voltage sensors as well as temperature sensors each with appropriate threshold support to help NMS systems detect and alert appropriately. In addition, on systems where it is supported, if the sensor value crosses the supported threshold value the system can generate appropriate notification as well.
- ARISTA-HARDWARE-UTILIZATION-MIB (aristaHardwareUtilizationMIB - 188.8.131.52.4.1.30065.3.22): 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.
- ARISTA-SW-IP-FORWARDING-MIB (aristaSwIpForwardingMIB - 184.108.40.206.4.1.30065.3.1): This MIB contains counters for software-forwarded packets.
- ARISTA-CONFIG-MAN-MIB (aristaConfigManMIB - 220.127.116.11.4.1.30065.3.9): This MIB provides notifications in case of configuration events. Notification to the managing device are sent (aristaConfigManEvent) in case of the occurence of a config event. The config events can take place from any of the following sources: cli commands issued via CLI snmp snmpsets via SNMP aristaConfigManEvent would provide information about command source config source, config destination, config source URL (for instance flash, ftp, http and so on) and config destination URL.
- ARISTA-TEST-MIB (aristaTestMIB - 18.104.22.168.4.1.30065.3.3): Arista Test MIB.
- ARISTA-ACL-MIB (aristaAclMIB - 22.214.171.124.4.1.30065.3.5): The MIB module for managing Access Control Lists (ACLs) on Arista devices.
- ARISTA-XGS-MIB (aristaXgsMIB - 126.96.36.199.4.1.30065.3.26): The MIB module for XGS chipset status and configuration on Arista devices.
- ARISTA-REDUNDANCY-MIB (aristaRedundancyMIB - 188.8.131.52.4.1.30065.3.8): This MIB module provides configuration and status information pertaining to high availability or redundancy infrastructure on Arista devices. As such, this MIB module is aimed at providing relevant information on 'Modular Systems' which support dual supervisors for control plane redundancy. Each of the dual supervisors are referred to as 'unit' in the module.
- ARISTA-SNMP-TRANSPORTS-MIB (aristaSnmpTransportMIB - 184.108.40.206.4.1.30065.3.10): The Arista Networks specific SNMP transport domains.
- ARISTA-EXTERNAL-ALARM-MIB (aristaExternalAlarmMIB - 220.127.116.11.4.1.30065.3.25): The MIB module for reporting the configuration and status of all external alarms present on an Arista device.
- ARISTA-IF-MIB (aristaIfMIB - 18.104.22.168.4.1.30065.3.15): The MIB module for reporting additional interface statistics on Arista devices.
- ARISTA-FIB-STATS-MIB (aristaFIBStatsMIB - 22.214.171.124.4.1.30065.3.23): Arista devices that function as a router support various dynamic routing protocols like BGP, OSPF. Customers can configure local or static routes as well. The routing subsystem is responsible for creating the forwarding information base (FIB) from routing information received by customer configuration or dynamic routing protocols. The FIB has the complete details about all the routes that are active in the system and will be used for data forwarding. In the context of this MIB, we specifically refer to the unicast FIB. This MIB provides useful statistics about the FIB. Arista devices support routing function for IPv4 and IPv6 address families. Arista devices also support the concept of virtual routing and forwarding (VRF), with a single device providing multiple routing instances. This allows customers to isolate network traffic and use overlapping addresses. A VRF instance is identified by a customer configured string. Arista devices maintain independent FIB for each address family and VRF instance. This MIB provides access to FIB summary of all address families within a specific VRF instance. Network Management Stations can obtain FIB summary for every VRF instance by specifying the VRF instance as a context, when using SNMPv3; or by including the VRF instance in the community string (format is @) when using SNMPv2.
- ARISTA-XCVR-DWDM-MIB (aristaXcvrDwdmMIB - 126.96.36.199.4.1.30065.3.19): The MIB module for DWDM interface status and configuration on Arista devices.
- ARISTA-IP-MIB (aristaIpMIB - 188.8.131.52.4.1.30065.3.27): This MIB module provides additional IP statistics on Arista devices.
- ARISTA-VXLAN-MIB (aristaVxlanMIB - 184.108.40.206.4.1.30065.3.28): The MIB module for VXLAN counters and status information on Arista devices.
- ARISTA-PFC-MIB (aristaPfcMIB - 220.127.116.11.4.1.30065.3.11): Extensions for managing IEEE 802.1Qbb Priority-based Flow Control on Arista devices. This module extends IEEE8021-PFC-MIB by providing per class-of-service information for the supported Arista platforms.
- ARISTA-BRIDGE-EXT-MIB (aristaBridgeExtMIB - 18.104.22.168.4.1.30065.3.2): This MIB contains extensions to the BRIDGE-MIB.
- ARISTA-TAPAGG-MIB (aristaTapaggMIB - 22.214.171.124.4.1.30065.3.31): This MIB contains information related to the tapagg feature that is implemented on specific Arista switches running EOS. On specific Arista devices, EOS offers a powerful solution for network performance monitoring. These devices have significant bandwidth capacity and different port or interface speed options for a non-blocking monitoring solution. This specific EOS feature is called 'TAP aggregation' or 'tapagg'. These devices are typically capable of performing packet classification in hardware as well, and that can be used to steer the monitored traffic as desired, directly to the right set of external tools. With the tapagg feature, the Arista switching device is first put into an exclusive mode to do the desired packet replication. In this mode, normal switching functions like bridging, routing etc. are disabled. Interfaces are categorized into 'tap' (they receive the traffic that is required to be replicated) and 'tool' (they transmit the replicated packet out and are in the path towards the monitoring tool). Furthermore, the tapagg feature allows users to configure classification rules via the policy-map construct so that the mirrored traffic can be steered appropriately. Another layer of indirection that is provided is called aggregation-groups. Tap and tool interfaces can be part of a specific aggregation group, and that allows for a powerful way to express replication or mirroring rules. Policies can change the aggregation group for specific set of packets, and that can be used to steer traffic out of desired tool interfaces as appropriate. This MIB provides information related to the tapagg feature.
- ARISTA-QOS-MIB (aristaQosMib - 126.96.36.199.4.1.30065.3.13): This MIB provides read access to Quality of Service (QoS) configuration and statistics information for Arista platforms. Configuration information available through this MIB includes all class-map, policy-map, and service-policy parameters. The definitions of these object types are given below. Statistics available through this MIB include dropped, sent and matched packet counters per traffic class after any configured QoS policies are applied and per chip ECN counters if supported. Definitions: Class map - A data structure that uses access-control lists to define a data stream. Policy map - A data structure that associates class maps identifying specific data streams with actions that control its transmission. Action - A traffic-management action that is applied to traffic classified as belonging to a particular class. Actions may include modifying CoS or DSCP fields, assigning to traffic-class queues, shaping, or filtering.
- ARISTA-CONFIG-COPY-MIB (aristaConfigCopyMIB - 188.8.131.52.4.1.30065.3.7): This MIB is for copying a source URI to a destination URI. A URI specifies the location of a local file, network file, running-config or startup-config. The resources specified by the URIs are copied from/to Arista devices. Currently supported URI schemes include: file, flash, extension, system, ftp, http, https and tftp.
- ARISTA-BGP4V2-TC-MIB (aristaBgp4V2TC - 184.108.40.206.4.1.30065.4.2): Textual conventions for BGP-4. This version was published in draft-ietf-idr-bgp4-mibv2-13, and modified to be homed inside the Arista enterprise. There were no other modifications. Copyright (C) The IETF Trust (2011). This version of this MIB module is part of draft-ietf-idr-bgp4-mibv2-13.txt; see the draft itself for full legal notices.
- ARISTA-NEXTHOP-GROUP-MIB (aristaNexthopGroupMIB - 220.127.116.11.4.1.30065.3.21): This MIB contains information about NextHop Groups (NHG). General L3 routing creates routing table entries, each of which are associated with a nexthop. If multiple paths exist for a specific route, the route points to a set of nexthops (commonly referred as ECMP or Equal Cost MultiPath). Arista devices support a feature which allows customers to manually create a nexthop list, and use this list to route packets to the specified set of nexthop addresses. Customers can associate a tunnel type (GRE, for example) with the nexthop group, allowing relevant packets to be tunneled as well. The packet forwarding or routing decision happens in hardware. Nexthop group feature gives customers full control of how a route should be forwarded (tunneled or otherwise). The number of entries in the nexthop group is also determined by the user, and directly translates to the number of nexthop entries in the hardware for the specified route. Let's provide an example, looking at EOS CLI example. nexthop-group foo type ip-in-ip ttl 64 entry 0 tunnel-destination 10.1.1.1 entry 1 tunnel-destination 18.104.22.168 ! ip route 22.214.171.124/24 Nexthop-Group foo In the above configuration, any packet destined to 126.96.36.199/24 will be forwarded by the nexthop group 'foo'. Each entry inside the nexthop group specifies a particular nexthop ('tunnel destination') chosen by the customer. In this example, packets can be forwarded via either of the nexthop (traffic split equally between the 2 entries). This MIB module provides information relevant to the nexthop group feature, specifically the status of various nexthop groups configured, and traffic statistics.
- ARISTA-SMI-MIB (arista - 188.8.131.52.4.1.30065): The Structure of Management Information for the Arista Networks enterprise.
- ARISTA-GENERAL-MIB (aristaGeneralMib - 184.108.40.206.4.1.30065.3.24): First draft.
- ARISTA-ASIC-COUNTERS-MIB (aristaAsicCountersMIB - 220.127.116.11.4.1.30065.3.29): The MIB module for various counters on Arista devices.