Posted on November 1, 2017 11:20 am
 |  Asked by Abhijeet Bhapkar
Print Friendly, PDF & Email

Required specific OIDs and MIBs for Arista switches

Posted by Alexandru
Answered on November 1, 2017 11:48 am

Hi Abhijeet,


You can find the MIBs supported by Arista switches using the following link

If you wish to get specific details from a switch you can walk the ENTITY-MIB, more specifically the ENTITY-MIB::entPhysicalDescr and get the description of the physical entities and relevant sensors.

For example the following command will list all entities:

show snmp mib walk ENTITY-MIB::entPhysicalDescr

ENTITY-MIB::entPhysicalDescr[1] = STRING: 48x10GbE (SFP+) & 6x40GbE (2xMXP)

ENTITY-MIB::entPhysicalDescr[100004002] = STRING: Scd Chip 2

ENTITY-MIB::entPhysicalDescr[100004196] = STRING: Standby Cpld Chip 196

ENTITY-MIB::entPhysicalDescr[100006001] = STRING: Cpu temp sensor



Next lets say we are interested in the CPU TEMP sensor. We get its ID 100006001 and check the ENTITY-SENSOR-MIB::entPhySensorTable

show snmp mib walk ENTITY-SENSOR-MIB::entPhySensorTable | grep 100006001

ENTITY-SENSOR-MIB::entPhySensorType[100006001] = INTEGER: celsius(8)

ENTITY-SENSOR-MIB::entPhySensorScale[100006001] = INTEGER: units(9)

ENTITY-SENSOR-MIB::entPhySensorPrecision[100006001] = INTEGER: 1

ENTITY-SENSOR-MIB::entPhySensorValue[100006001] = INTEGER: 414

ENTITY-SENSOR-MIB::entPhySensorOperStatus[100006001] = INTEGER: ok(1)

ENTITY-SENSOR-MIB::entPhySensorUnitsDisplay[100006001] = STRING: Celsius

ENTITY-SENSOR-MIB::entPhySensorValueTimeStamp[100006001] = Timeticks: (199094459) 23 days, 1:02:24.59

ENTITY-SENSOR-MIB::entPhySensorValueUpdateRate[100006001] = Gauge32: 5000 milliseconds

This tells us that the returned value is in celsius, its status is OK and the value is 414 which is 41.4 degrees.

If we wish to poll a specific OID remotely we need to translate the text values to numbers using the translate command:

show snmp mib translate ENTITY-SENSOR-MIB::entPhySensorValue.100006001


Most modern NMS should be able to discover the all the entities automatically just by doing a full walk on the relevant trees and deriving the OIDs and their meaning.

I recommend checking the NMS for autodiscovery features and make sure to load all the MIBs supported by Arista as detailed in the link provided initially, as the number of sensors is fairly large and they change depending on platform and switch load-out, for example there are 325 OIDs returned on a fairly empty DCS-7050SX-72-F

cz153#show snmp mib walk ENTITY-MIB::entPhysicalDescr | wc -l


I hope this addresses your question.


Post your Answer

You must be logged in to post an answer.