All MIBs › NE-ALARM-MIB
Category: Alarm & Fault Management
Description: Defines network element alarm objects, severity levels, and notification types for fault management systems.
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 NE-ALARM-MIB?
NE-ALARM-MIB is a generic network element (NE) alarm MIB used in fault management systems to model alarm objects, severity levels, and notification (trap) types for a managed device. Given the sparse module description and empty sample object list, its exact vendor origin is unclear, but the naming convention is consistent with telecom/network-element fault-management MIBs common across transport and access equipment vendors. Its core purpose is monitoring device and software fault status: it typically exposes alarm tables with severity (critical, major, minor, warning), alarm type/probable cause, and raised/cleared state, feeding into an NMS/EMS alarm correlation engine. Such MIBs commonly reference or align with ITU-T alarm severity conventions and the standard SNMPv2-MIB/NOTIFICATION-TYPE framework for trap delivery, though no explicit import is confirmed here. It is typically deployed on telecom network elements (transport, access, or aggregation equipment) as the fault-reporting layer polled or trapped to a centralized alarm/EMS system. Engineers implementing or auditing this functionality typically reference the NE-ALARM-MIB RFC/standard documentation for the authoritative specification.
IPNetwork Monitor allows you to monitor SNMP objects defined in NE-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
- network element (transport/access equipment), vendor-neutral naming but likely device-specific fault MIB
Monitoring Examples
Because no sample objects were provided for this MIB, a concrete object-level monitoring scenario cannot be honestly constructed here; in general practice such a MIB would expose an alarm table (e.g., an active-alarm entry per alarm instance) with severity and probable-cause columns, and corresponding SNMP traps for alarm-raised and alarm-cleared events. Without the actual object names, further specifics would be invented rather than grounded.
What Can Be Monitored
- active alarm severity
- alarm probable cause/type
- alarm raised/cleared state
Imported Objects
From SPIDCOM-MIB
| spidcom | OBJECT-IDENTITY |
OIDs
RFC description
Network Element alarm management MIB providing standardized alarm definition, reporting, and severity classification for network devices.
Start monitoring Network element (transport/access equipment, vendor-neutral naming) 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.