OtmOpenAlarm :: otmSeverity

MIB Reference — IPNetwork Monitor · Updated October 06, 2026

All MIBs › OtmOpenAlarm › otmSeverity

otmSeverity

Module: OtmOpenAlarm

OID (symbolic): OtmOpenAlarm::otmSeverity

OID (numeric): 1.3.6.1.4.1.562.50.1.2.3

Node type: OBJECT-TYPE

Type: INTEGER

Access: read-only

Description: The severity of the alarm.

What is otmSeverity?

This value classifies the alarm's severity as one of critical(1), major(2), minor(3), warning(4), info(5), or clear(6). Admins use it to triage incoming alarms, prioritizing critical and major conditions for immediate response while treating info and clear as lower-priority or resolution notices. For example, a NOC dashboard highlights any alarm with otmSeverity of critical(1) in red for immediate escalation.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.562.50.1.2.3
snmpwalk -v2c -c public <target> OtmOpenAlarm::otmSeverity

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.562.50.1.2.3.1
snmpget -v2c -c public <target> OtmOpenAlarm::otmSeverity.1

Start monitoring NMS platforms integrating with the Optivity/OTM alarm framework with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the OtmOpenAlarm::otmSeverity OID value, configure state conditions and alerts, and monitor any NMS platforms integrating with the Optivity/OTM alarm framework from a single console.

How to Use in IPNetwork Monitor

Select an NMS platforms integrating with the Optivity/OTM alarm framework as the target host to create a monitor — the SNMP service should be up and running on it. Click New Monitor, then check SNMP Custom on the Favorites tab, click Next, and confirm the host. On the next page, click Select... to open the built-in SNMP MIB Browser and type otmSeverity into the Find box to locate it in the OID tree, then select it and click OK. The severity of the alarm. On the monitor's Main parameters page you can set the target's SNMP port (default 161), credentials, polling interval, and other settings — see the SNMP Monitor help for details. On the State conditions and Alerting tabs, configure when the monitor should change state and trigger an alert; since this is an INTEGER-type OID, Value bounds is the most useful condition here — trigger an alert if the value is anything other than 'clear', since that indicates the condition this object reports has changed to one worth investigating. Click Finish to create the monitor; you can adjust any parameter later.

OID Breakdown

Upper-level ancestors (7 from the standard OID tree / other modules)
Numeric OIDNameModule
1isoLANART-AGENT
1.3orgAirPair-MIB
1.3.6dodAirPair-MIB
1.3.6.1internetAirPair-MIB
1.3.6.1.4privateAirPair-MIB
1.3.6.1.4.1enterprisesAirPair-MIB
1.3.6.1.4.1.562nortelCPM-NORTEL-MIB
Numeric OIDNameModule
1.3.6.1.4.1.562.50otmOtmOpenAlarm
1.3.6.1.4.1.562.50.1otmOpenAlarmOtmOpenAlarm
1.3.6.1.4.1.562.50.1.2otmOpenAlarmObjectsOtmOpenAlarm
1.3.6.1.4.1.562.50.1.2.3otmSeverityOtmOpenAlarm