OPENNMS-MIB

File: OPENNMS-MIB.mib (18485 bytes)

Imported modules

SNMPv2-SMI SNMPv2-TC SNMPv2-CONF

Imported symbols

MODULE-IDENTITY OBJECT-TYPE NOTIFICATION-TYPE
enterprises DisplayString MODULE-COMPLIANCE
OBJECT-GROUP NOTIFICATION-GROUP

Defined Values

openNMS 1.3.6.1.4.1.5813
The MIB module for OpenNMS, the world's first enterprise-grade open-source network management application platform
MODULE-IDENTITY    

onmsLegacyTraps 1.3.6.1.4.1.5813.1
OBJECT IDENTIFIER    

groups 1.3.6.1.4.1.5813.4
OBJECT IDENTIFIER    

data 1.3.6.1.4.1.5813.20
OBJECT IDENTIFIER    

events 1.3.6.1.4.1.5813.20.1
OBJECT IDENTIFIER    

eventsSpecific 1.3.6.1.4.1.5813.20.2
OBJECT IDENTIFIER    

tl1AutonomousMessage 1.3.6.1.4.1.5813.20.2.1
OBJECT IDENTIFIER    

syslogMessageObjects 1.3.6.1.4.1.5813.20.2.2
OBJECT IDENTIFIER    

correlatedEventObjects 1.3.6.1.4.1.5813.20.2.3
OBJECT IDENTIFIER    

eventsAlarms 1.3.6.1.4.1.5813.20.3
OBJECT IDENTIFIER    

dbid 1.3.6.1.4.1.5813.20.1.1
This is the database ID for the event. Each event in OpenNMS is assigned a unique, sequential eventid. Unless the database is cleared, the sequence should never repeat.
Status: current Access: read-only
OBJECT-TYPE    
  DisplayString  

distPoller 1.3.6.1.4.1.5813.20.1.2
This is the distributed poller name for the event.
Status: current Access: read-only
OBJECT-TYPE    
  DisplayString  

create-time 1.3.6.1.4.1.5813.20.1.3
This is the time the event was created in the database.
Status: current Access: read-only
OBJECT-TYPE    
  DisplayString  

master-station 1.3.6.1.4.1.5813.20.1.4
This is the name of the master station for the event.
Status: current Access: read-only
OBJECT-TYPE    
  DisplayString  

uei 1.3.6.1.4.1.5813.20.1.6
This is the Unique Event Identifier (UEI) for the event. The UEI is a string that should be descriptive and unique for each event type that OpenNMS handles.
Status: current Access: read-only
OBJECT-TYPE    
  DisplayString  

source 1.3.6.1.4.1.5813.20.1.7
This is the source of the event, usually the OpenNMS process name, such as Capsd or Trapd.
Status: current Access: read-only
OBJECT-TYPE    
  DisplayString  

nodeid 1.3.6.1.4.1.5813.20.1.8
This is the Node ID for the event. Node IDs are simply a handle that OpenNMS uses to group interfaces and services together, and each node should represent an actual device.
Status: current Access: read-only
OBJECT-TYPE    
  DisplayString  

time 1.3.6.1.4.1.5813.20.1.9
This is the time the event occurred.
Status: current Access: read-only
OBJECT-TYPE    
  DisplayString  

host 1.3.6.1.4.1.5813.20.1.10
This is the host for the event. In most cases it will represent the OpenNMS instance that generated it.
Status: current Access: read-only
OBJECT-TYPE    
  DisplayString  

interface 1.3.6.1.4.1.5813.20.1.11
This is the interface for the event. It should contain the IP address of the interface that caused the event.
Status: current Access: read-only
OBJECT-TYPE    
  DisplayString  

snmphost 1.3.6.1.4.1.5813.20.1.12
This is the SNMP host for the event. In the case of an SNMP Trap that was received by OpenNMS, it will reflect the device that generated the trap. In the case of a trap generated by OpenNMS, such as forwarding a nodeLostService event to another system, it will reflect the OpenNMS server.
Status: current Access: read-only
OBJECT-TYPE    
  DisplayString  

service 1.3.6.1.4.1.5813.20.1.13
This is the name of the service (ICMP, SSH, HTTP, etc.) that is associated with the event. For example, a failed web server may generate a nodeLostService event. In that case this field would most likely read HTTP.
Status: current Access: read-only
OBJECT-TYPE    
  DisplayString  

descr 1.3.6.1.4.1.5813.20.1.16
This is the verbose description of the event.
Status: current Access: read-only
OBJECT-TYPE    
  DisplayString  

logmsg 1.3.6.1.4.1.5813.20.1.17
The log message is a short, usually one sentence, description of the event suitable for displaying in a log or table.
Status: current Access: read-only
OBJECT-TYPE    
  DisplayString  

severity 1.3.6.1.4.1.5813.20.1.18
This is the severity of the event, one of CLEARED, INDETERMINATE, NORMAL, WARNING, MINOR, MAJOR or CRITICAL.
Status: current Access: read-only
OBJECT-TYPE    
  DisplayString  

pathoutage 1.3.6.1.4.1.5813.20.1.19
The pathoutage field in the event has yet to be implemented, but it will be stored here when available.
Status: current Access: read-only
OBJECT-TYPE    
  DisplayString  

operinst 1.3.6.1.4.1.5813.20.1.20
It is possible to associate operator instructions with events in OpenNMS. If this information is available, it will be stored here.
Status: current Access: read-only
OBJECT-TYPE    
  DisplayString  

ifresolve 1.3.6.1.4.1.5813.20.1.21
An attempt will be made to resolve the FQDN of the IP address in OpenNMS-event-interface and if successful, the value returned will be stored here.
Status: current Access: read-only
OBJECT-TYPE    
  DisplayString  

nodelabel 1.3.6.1.4.1.5813.20.1.22
This will contain the name of the node as known by OpenNMS. This is based solely on OpenNMS-event-nodeid and can be considered an authoritative way to identify the device from the perspective of OpenNMS. This name is automatically assigned in the following order: 1) DNS Name: The reverse-resolved name of the primary interface for the node. 2) NetBIOS Name: If available on a Windows or SMB system. 3) SNMP sysName: If SNMP is available, the sysName. 4) IP Address All of these methods can be overridden by an end user via the webUI, and thus the value can change over time, although the OpenNMS-event-nodeid will not.
Status: current Access: read-only
OBJECT-TYPE    
  DisplayString  

tl1amRawMessage 1.3.6.1.4.1.5813.20.2.1.1
The raw TL1 autonomous message in its entirety.
Status: current Access: read-only
OBJECT-TYPE    
  DisplayString  

tl1amAlarmCode 1.3.6.1.4.1.5813.20.2.1.2
The ASCII alarm-code for this TL1 autonomous message.
Status: current Access: read-only
OBJECT-TYPE    
  DisplayString  

tl1amAutonomousTag 1.3.6.1.4.1.5813.20.2.1.3
The ASCII autonomous-tag for this TL1 autonomous message.
Status: current Access: read-only
OBJECT-TYPE    
  DisplayString  

tl1amVerb 1.3.6.1.4.1.5813.20.2.1.4
The ASCII verb for this TL1 autonomous message. Should always be REPT.
Status: current Access: read-only
OBJECT-TYPE    
  DisplayString  

tl1amAutoBlock 1.3.6.1.4.1.5813.20.2.1.5
The ASCII auto-block for this TL1 autonomous message.
Status: current Access: read-only
OBJECT-TYPE    
  DisplayString  

tl1amAID 1.3.6.1.4.1.5813.20.2.1.6
The ASCII AID (access identifier) for this TL1 autonomous message, as parsed from the auto-block.
Status: current Access: read-only
OBJECT-TYPE    
  DisplayString  

tl1amAdditionalParams 1.3.6.1.4.1.5813.20.2.1.7
The additional parameters for this TL1 autonomous message, as parsed from the auto-block.
Status: current Access: read-only
OBJECT-TYPE    
  DisplayString  

syslogFacilityName 1.3.6.1.4.1.5813.20.2.2.1
The name of the facility from which this syslog message originated, e.g.: kernel, auth, mail...
Status: current Access: read-only
OBJECT-TYPE    
  DisplayString  

syslogSeverityName 1.3.6.1.4.1.5813.20.2.2.2
The name of the severity of this syslog message, e.g.: Debug, Info, Error...
Status: current Access: read-only
OBJECT-TYPE    
  DisplayString  

syslogTimestamp 1.3.6.1.4.1.5813.20.2.2.3
The timestamp of this syslog message from the originating sender, if provided, in format: MMM dd HH:mm:ss
Status: current Access: read-only
OBJECT-TYPE    
  DisplayString  

syslogProcessName 1.3.6.1.4.1.5813.20.2.2.4
The process that sent this syslog message from the originating sender, if provided, e.g.: init, named, sendmail...
Status: current Access: read-only
OBJECT-TYPE    
  DisplayString  

syslogProcessID 1.3.6.1.4.1.5813.20.2.2.5
The numeric PID of the process that sent this syslog message from the originating sender, if provided.
Status: current Access: read-only
OBJECT-TYPE    
  INTEGER  

syslogMessageBody 1.3.6.1.4.1.5813.20.2.2.6
The body of this syslog message with protocol metadata (timestamp, severity, priority, process name and PID) removed.
Status: current Access: read-only
OBJECT-TYPE    
  DisplayString  

correlationEngineName 1.3.6.1.4.1.5813.20.2.3.1
The name of the OpenNMS correlation engine responsible for the correlation that led to the event corresponding to this trap, e.g. Drools
Status: current Access: read-only
OBJECT-TYPE    
  DisplayString  

correlationRuleSetName 1.3.6.1.4.1.5813.20.2.3.2
The name of the correlation rule set responsible for the correlation that led to the event corresponding to this trap. In combination with correlationEngineName, identifies the specific rule set that led to the creation of the event corresponding to this trap.
Status: current Access: read-only
OBJECT-TYPE    
  DisplayString  

correlationComments 1.3.6.1.4.1.5813.20.2.3.3
Contains optional comments from the correlation rule set to aid the operator in interpreting the event corresponding to this trap.
Status: current Access: read-only
OBJECT-TYPE    
  DisplayString  

alarmId 1.3.6.1.4.1.5813.20.3.1
The unique alarm identifier.
Status: current Access: read-only
OBJECT-TYPE    
  DisplayString  

synchronizing 1.3.6.1.4.1.5813.20.3.2
flag indicating if the alarm is due to a synchronization session (SYNC) or not (null)
Status: current Access: read-only
OBJECT-TYPE    
  DisplayString  

eventTrap 1.3.6.1.4.1.5813.1.1
This is the definition of the generic OpenNMS trap sent from the scriptd process. Key variables are uei (which tells what type of OpenNMS event this was), interface (the IP address of the interface that caused the event) and severity.
Status: current Access: read-only
NOTIFICATION-TYPE    

tl1AutonomousMessageTrap 1.3.6.1.4.1.5813.1.2
This trap is used to convey the contents of a TL1 autonomous message received from a TL1 NE or a north-bound TL1 EMS. Managers receiving this trap may need to perform additional analysis of its varbinds in order to realize value from this trap.
Status: current Access: read-only
NOTIFICATION-TYPE    

alarmTrap 1.3.6.1.4.1.5813.1.3
The OpenNMS alarm SNMP Trap
Status: current Access: read-only
NOTIFICATION-TYPE    

heartbeatTrap 1.3.6.1.4.1.5813.1.4
Trap sent periodically by OpenNMS to keep alive external SNMP Manager
Status: current Access: read-only
NOTIFICATION-TYPE    

startSyncTrap 1.3.6.1.4.1.5813.1.5
OpenNMS Synchronization Process is starting
Status: current Access: read-only
NOTIFICATION-TYPE    

endSyncTrap 1.3.6.1.4.1.5813.1.6
OpenNMS Synchronization Process is successfully ended
Status: current Access: read-only
NOTIFICATION-TYPE    

syncRequestTrap 1.3.6.1.4.1.5813.1.7
OpenNMS synchronization request
Status: current Access: read-only
NOTIFICATION-TYPE    

syslogMessageTrap 1.3.6.1.4.1.5813.1.8
This trap is used to convey the contents of a syslog message received from a remote system. Managers receiving should be able to reconstruct all information present in the original syslog message based on the values of the trap's varbinds.
Status: current Access: read-only
NOTIFICATION-TYPE    

correlatedEventTrap 1.3.6.1.4.1.5813.1.9
This trap is used to convey the contents of an OpenNMS event that was created as the output of a correlation rule set.
Status: current Access: read-only
NOTIFICATION-TYPE    

events-Group 1.3.6.1.4.1.5813.4.1
Conformance Group for OpenNMS Events
Status: current Access: read-only
OBJECT-GROUP    

tl1AutonomousMessage-Group 1.3.6.1.4.1.5813.4.2
Conformance Group for TL1 autonomous message
Status: current Access: read-only
OBJECT-GROUP    

eventsAlarms-Group 1.3.6.1.4.1.5813.4.3
Conformance Group for OpenNMS Events related to Alarms
Status: current Access: read-only
OBJECT-GROUP    

traps-Group 1.3.6.1.4.1.5813.4.4
OpenNMS Notification Group
Status: current Access: read-only
NOTIFICATION-GROUP    

syslogMessageGroup 1.3.6.1.4.1.5813.4.5
Notification group for syslog message-derived traps
Status: current Access: read-only
OBJECT-GROUP    

correlatedEventsGroup 1.3.6.1.4.1.5813.4.6
Notification group for correlated event-based traps
Status: current Access: read-only
OBJECT-GROUP