LEFTHAND-NETWORKS-NUS-COMMON-NOTIFICATION-MIB: View SNMP OID List / Download MIB

VENDOR: LEFTHAND NETWORKS


 Home MIB: LEFTHAND-NETWORKS-NUS-COMMON-NOTIFICATION-MIB
Download as:   

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
 lhnNusCommonNotificationModule 1.3.6.1.4.1.9804.1.1.15
Notification (Trap) items for NUS Devices
             lhnNusCommonEventGroup 1.3.6.1.4.1.9804.3.1.1.1.1.2
Events defined for NUS devices
               notificationMessageCount 1.3.6.1.4.1.9804.3.1.1.2.13.1 integer read-only
number of notification messages
               notificationMessageTable 1.3.6.1.4.1.9804.3.1.1.2.13.2 no-access
A table of notification messages for the NUS. The number of entries is given by notificationMessageCount.
                   notificationMessageEntry 1.3.6.1.4.1.9804.3.1.1.2.13.2.1 no-access
A row of notification messages for the NUS.
                       notificationIndex 1.3.6.1.4.1.9804.3.1.1.2.13.2.1.1 integer read-only
notification message index
                       notificationMessage 1.3.6.1.4.1.9804.3.1.1.2.13.2.1.2 octet string read-only
notification message contents
                       notificationTime 1.3.6.1.4.1.9804.3.1.1.2.13.2.1.3 dateandtime read-only
time notification occurred
         userNotification 1.3.6.1.4.1.9804.3.1.1.3.1
A system variable being monitored reached a threshold. The user chose to be notified of this condition via SNMP. A table of messages exists which stores all the notifications issued. This trap will carry the OID referring to the corresponding message stored in this table.