EXTREME-ENTITY-MIB: View SNMP OID List / Download MIB

VENDOR: EXTREME NETWORKS

Home	MIB: EXTREME-ENTITY-MIB
Download as:		SNMPv2-CONF, ENTITY-MIB, SNMPv2-SMI, EXTREME-BASE-MIB, SNMPv2-TC		Download standard MIB format if you are planning to load a MIB file into some system (OS, Zabbix, PRTG ...) or view it with a MIB browser. CSV is more suitable for analyzing and viewing OID' and other MIB objects in excel. JSON and YAML formats are usually used in programing even though some systems can use MIB in YAML format (like Logstash). Keep in mind that standard MIB files can be successfully loaded by systems and programs only if all the required MIB's from the "Imports" section are already loaded. The tree-like SNMP object navigator requires no explanations because it is very simple to use. And if you stumbled on this MIB from Google note that you can always go back to the home page if you need to perform another MIB or OID lookup.

Object Name	OID	Type	Access	Info
extremeEntity	1.3.6.1.4.1.1916.1.31			Extreme FRU Odometer objects
extremeEntityFRUTable	1.3.6.1.4.1.1916.1.31.1		no-access	A table containing information about each FRU in the chassis based on Entity MIB
extremeEntityFRUEntry	1.3.6.1.4.1.1916.1.31.1.1		no-access	Entry in the table for a FRU Entity
extremeEntityFRUStartTime	1.3.6.1.4.1.1916.1.31.1.1.1	unsigned32	read-only	First Recorded Start Date/Time. The units are represented as the standard time_t value of the start Date/Time
extremeEntityFRUOdometer	1.3.6.1.4.1.1916.1.31.1.1.2	unsigned32	read-only	Number of time units in service.
extremeEntityFRUOdometerUnit	1.3.6.1.4.1.1916.1.31.1.1.3	integer	read-only	Time unit used to represent value reported by extremeEntityFRUOdometer. Depending on the underlying hardware capability, the agent implementation can choose the time-unit used to represent the Odometer value. Enumeration: 'seconds': 2, 'days': 1.