All MIBs › ITU-ALARM-MIB
Organization: IETF Distributed Management Working Group
Last Updated: 2004-09-09
Category: Alarm and Event Management
Description: Defines managed objects for ITU alarm modelling based on ITU-T M.3100 standards, supplementing the generic IETF Alarm MIB.
IPNetwork Monitor uses several OIDs from this MIB in network discovery and polling the applicable devices. Start monitoring ITU-ALARM-MIB with a free 30-day trial of IPNetwork Monitor.
What Is ITU-ALARM-MIB?
ITU-ALARM-MIB is an IETF standards-track MIB (RFC 3877 companion) that models telecom alarms per ITU-T Recommendations M.3100, X.733, and X.736, supplementing the generic IETF Alarm MIB with ITU-specific alarm semantics. It exposes alarm records including perceived severity, event type, probable cause, and free-text detail, plus an 'active alarms' table tracking currently outstanding conditions. It is squarely a faults/traps-oriented MIB used for monitoring software/hardware status indirectly: it reports the alarm/fault state of managed elements (severity trending, detecting entity, service provider context) rather than raw performance counters. It explicitly builds on and extends RFC 3877's generic Alarm MIB and ITU-T M.3100/X.733/X.736 alarm models, and network engineers new to telecom fault management often use the ITU-ALARM-MIB guide provided with these RFCs to understand how perceived severity and probable cause map onto ITU-T alarm semantics. Deployment context is telecom network elements and NMS/EMS systems in carrier and service-provider networks requiring standardized alarm reporting.
IPNetwork Monitor allows you to monitor SNMP objects defined in ITU-ALARM-MIB. 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
- vendor-neutral, standards-based MIB, not tied to a specific manufacturer
- telecom network element (managed per ITU-T M.3100 alarm model)
Monitoring Examples
An NMS would poll ituAlarmActiveTable/ituAlarmActiveEntry to enumerate all currently active alarms, reading ituAlarmActiveTrendIndication to see if a condition is worsening, improving, or stable, and ituAlarmActiveDetector/ituAlarmActiveServiceProvider to identify which subsystem raised it. The historical ituAlarmTable/ituAlarmEntry would be queried for ituAlarmPerceivedSeverity, ituAlarmEventType, ituAlarmProbableCause, and ituAlarmAdditionalText to diagnose a specific fault event, e.g. a critical-severity communications alarm with a probable cause of loss-of-signal.
What Can Be Monitored
- active alarm list and severity trend
- alarm perceived severity
- alarm event type and probable cause
- alarm detecting entity/service provider
- additional alarm free-text detail
Imported Objects
From ALARM-MIB
| alarmActiveDateAndTime | OBJECT-TYPE |
| alarmActiveIndex | OBJECT-TYPE |
| alarmListName | OBJECT-TYPE |
| alarmModelIndex | OBJECT-TYPE |
| IANAItuEventType | |
| IANAItuProbableCause |
From ITU-ALARM-TC-MIB
| ItuPerceivedSeverity | |
| ItuTrendIndication |
From RMON2-MIB
| ZeroBasedCounter32 |
From SNMP-FRAMEWORK-MIB
| SnmpAdminString |
From SNMPv2-CONF
| MODULE-COMPLIANCE | |
| OBJECT-GROUP |
From SNMPv2-SMI
| Gauge32 | |
| MODULE-IDENTITY | |
| OBJECT-TYPE | |
| mib-2 |
From SNMPv2-TC
| AutonomousType | |
| RowPointer |
OIDs
FAQ
How would a carrier NMS use ITU-ALARM-MIB to track faults on a telecom network element?
It exposes an active-alarms table plus alarm records with perceived severity, event type, probable cause, and free-text detail, letting an NMS report and trend the fault state of managed elements per the ITU-T M.3100/X.733/X.736 alarm model.
Does ITU-ALARM-MIB replace the generic IETF Alarm MIB?
No — it supplements RFC 3877's generic Alarm MIB, extending it with ITU-specific alarm semantics rather than replacing it.
RFC description
Defines management objects for ITU-T alarm monitoring and handling in telecommunications equipment (RFC 3877).
Start monitoring Vendor-neutral IETF standard, RFC 3877 (telecom network element, ITU-T M.3100 alarm model) 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.