OtmOpenAlarm

All MIBs › OtmOpenAlarm

Description: MIB for Nortel OTM (Optivity Telephony Manager) open alarm traps, reporting severity-graded alarms from call servers, signaling servers, and media cards

Start monitoring vendor-neutral, standards-based MIB, any SNMPv3-capable network device (SNMP engine identity/boot/clock status) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

What Is OtmOpenAlarm?

OtmOpenAlarm is a legacy proprietary MIB (enterprise OID 562) defining the OTM (Open Trap Management) Open Alarm trap format used to internationalize alarm text across vendor NMS integrations. Its trap-varbind objects cover sequence number, date/time, severity, namespace, type, site, system, system component, originating agent, an Optivity-specific trap type, associated user, and up to three free-form problem-isolation data fields. As a notification MIB it lets an NMS receive a language-neutral, severity-coded alarm that can be localized for display regardless of the receiving operator's locale. It is used by network management systems integrating with the Optivity/OTM alarm framework. Engineers can download the OtmOpenAlarm file directly to load it into their MIB browser.

IPNetwork Monitor allows you to monitor SNMP objects defined in OtmOpenAlarm. Use the built-in SNMP Monitoring Browser to explore available variables, view their current values and descriptions, and select the objects you want to monitor. You can then create SNMP monitors, configure thresholds, and receive alerts when monitored values change.

Supported Devices

NMS platforms integrating with the Optivity/OTM alarm framework

Monitoring Examples

An NMS decodes otmSeverity and otmProblemIsolationData1 from a received OtmOpenAlarm trap to render a localized, severity-coded alarm in the operator's own language.

What Can Be Monitored

language-neutral alarm severity and problem-isolation data

Imported Objects

From RFC-1215

TRAP-TYPE

From SNMPv2-SMI

OBJECT-TYPE
enterprises

From SNMPv2-TC

DisplayString

How to Use in IPNetwork Monitor

Example using otmSeverity OID:

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.

OIDs

OID symbolic	OID numeric	Type	Access	Description
nt	1.3.6.1.4.1.562
otm	1.3.6.1.4.1.562.50
otmOpenAlarm	1.3.6.1.4.1.562.50.1
otmOpenAlarmEp	1.3.6.1.4.1.562.50.1.1
NTF otmOpenAlarmCritical	1.3.6.1.4.1.562.50.1.1.0.1			The OTM Open Alarm Trap with an otmSeverity of critical(1). This trap is intended to be internationalizable, hence, it contains no natural language text.
NTF otmOpenAlarmMajor	1.3.6.1.4.1.562.50.1.1.0.2			The OTM Open Alarm Trap with a severity of major(2). This trap is intended to be internationalizable, hence, it contains no natural language text.
NTF otmOpenAlarmMinor	1.3.6.1.4.1.562.50.1.1.0.3			The OTM Open Alarm Trap with an otmSeverity of minor(3). This trap is intended to be internationalizable, hence, it contains no natural language text.
NTF otmOpenAlarmWarning	1.3.6.1.4.1.562.50.1.1.0.4			The OTM Open Alarm Trap with an otmSeverity of warning(4). This trap is intended to be internationalizable, hence, it contains no natural language text.
NTF otmOpenAlarmInfo	1.3.6.1.4.1.562.50.1.1.0.5			The OTM Open Alarm Trap with an otmSeverity of info(5). This trap is intended to be internationalizable, hence, it contains no natural language text.
NTF otmOpenAlarmClear	1.3.6.1.4.1.562.50.1.1.0.6			The OTM Open Alarm Trap with a severity of clear(6). This trap is intended to be internationalizable, hence, it contains no natural language text.
otmOpenAlarmObjects	1.3.6.1.4.1.562.50.1.2
INT otmSeqNumber	1.3.6.1.4.1.562.50.1.2.1	INTEGER	read-only	Sequence number of the alarm; starts at 1 and increments by 1; must be unique for all alarms received from otmSource.
STR otmDateAndTime	1.3.6.1.4.1.562.50.1.2.2	DisplayString	read-only	Time at which the alarm occurred. Its format is YYYY MM DD HH MM SS hh; hh may equal 00.
INT otmSeverityEx	1.3.6.1.4.1.562.50.1.2.3	INTEGER	read-only	The severity of the alarm.
INT otmNameSpace	1.3.6.1.4.1.562.50.1.2.4	INTEGER	read-only	This field, plus otmAlarmType, assigns a universally unique name to the trap. Values of this field are allocated by personnel at Nortel Networks, MPK.
STR otmType	1.3.6.1.4.1.562.50.1.2.5	DisplayString	read-only	The type of the alarm. The value of this field is unique within the name space defined by otmAlarmNameSpace. The format of this object is device-dependent. The Meridian 1 format is AAAA9999, where the numeric portion is unique within the alpha portion. The SL-100 format is AAAAA99999, where the numeric portion is unique within the alpha portion.
STR otmSite	1.3.6.1.4.1.562.50.1.2.6	DisplayString	read-only	The site associated with otmSystem. This site may contain or be a grouping of several systems. The format of this object is device-dependent.
STR otmSystem	1.3.6.1.4.1.562.50.1.2.7	DisplayString	read-only	The alarm's source - the name of the largest containing object to be identified as the alarm's emitter. The format of this object is device-dependent.
STR otmSystemComponent	1.3.6.1.4.1.562.50.1.2.8	DisplayString	read-only	A component within otmSystem emitting the alarm. The format of this object is device-dependent.
STR otmOriginatingAgent	1.3.6.1.4.1.562.50.1.2.9	DisplayString	read-only	The IP address of the SNMP agent that originated the trap.
INT otmOptivityTrapType	1.3.6.1.4.1.562.50.1.2.10	INTEGER	read-only	Indicates this trap fits the definition of a specific Optivity-defined trap type.
STR otmAssocUser	1.3.6.1.4.1.562.50.1.2.11	DisplayString	read-only	Name of the user most closely associated with the alarm (e.g., the user of the application that emits the alarm). The format of this object is device-dependent.
OCT otmProblemIsolationData1	1.3.6.1.4.1.562.50.1.2.12	OCTET STRING	read-only	Data useful in isolating the problem represented by the alarm. The format of this object is device-dependent.
OCT otmProblemIsolationData2	1.3.6.1.4.1.562.50.1.2.13	OCTET STRING	read-only	Data useful in isolating the problem represented by the alarm. An extension to otmProblemIsolationData1. The format of this object is device-dependent.
OCT otmProblemIsolationData3	1.3.6.1.4.1.562.50.1.2.14	OCTET STRING	read-only	Data useful in isolating the problem represented by the alarm. An extension to otmProblemIsolationData2. The format of this object is device-dependent.

RFC description

Defines OTM open alarm trap types and varbinds for device-independent alarm reporting at multiple severity levels.

Start monitoring NMS platforms integrating with the Optivity/OTM alarm framework with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

Download OtmOpenAlarm