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

VENDOR: EXTREME NETWORKS


 Home MIB: EXTREME-UPM-MIB
Download as:   
SNMPv2-CONF, EXTREME-BASE-MIB, SNMPv2-TC, SNMPv2-SMI

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
 extremeUpm 1.3.6.1.4.1.1916.1.35
Extreme universal port management mib
       upmNotificationTrap 1.3.6.1.4.1.1916.1.35.1
           upmProfileEventExecution 1.3.6.1.4.1.1916.1.35.1.1
This trap will be generated, when a profile is executed.
       upmConfig 1.3.6.1.4.1.1916.1.35.2
           upmProfileName 1.3.6.1.4.1.1916.1.35.2.1 displaystring no-access
The textual string identifying the name of the profile.
           upmExecutionId 1.3.6.1.4.1.1916.1.35.2.2 unsigned32 no-access
The value uniquely identifies the execution of a UPM profile. Switch stores history of 100 last run executions.
           upmEventType 1.3.6.1.4.1.1916.1.35.2.3 integer no-access
The type of the event that triggered the profile execution. Enumeration: 'upmTimer': 5, 'devicedetect': 1, 'deviceundetect': 2, 'userauthenticated': 3, 'userunauthenticated': 4, 'userrequest': 7.
           upmExecutionStatus 1.3.6.1.4.1.1916.1.35.2.4 integer no-access
The state of the profile execution. Enumeration: 'failure': 2, 'success': 1.
           upmPort 1.3.6.1.4.1.1916.1.35.2.5 integer no-access
The ifIndex of the port on which the profile was run. Is non-zero only when there is a valid port associated when the profile was run with the event. For ex: When a timer fires, the port may not be valid parameter
           upmProfileExecVars 1.3.6.1.4.1.1916.1.35.2.6 displaystring no-access
The textual string identifying the variables that were set when executing the profile.
           upmTimerName 1.3.6.1.4.1.1916.1.35.2.7 displaystring no-access
The textual string identifying the timer fired when executing the profile.