All MIBs › ITU-ALARM-TC-MIB
Organization: IETF Distributed Management Working Group
Last Updated: 2004-09-09
Category: Alarm and Event Management, Textual Conventions and Registries
Description:
Defines textual conventions for ITU alarm management based on ITU Recommendations M.3100, X.733, and X.736.
Imported Objects
From SNMPv2-SMI
| MODULE-IDENTITY | |
| mib-2 |
From SNMPv2-TC
| TEXTUAL-CONVENTION |
What Is ITU-ALARM-TC-MIB?
ITU-ALARM-TC-MIB, published as IETF RFC 3877, is a vendor-neutral textual-conventions module defining a standardized alarm severity/type convention based on ITU-T Recommendations M.3100 (generic network information model), X.733 (alarm reporting function), and X.736 (security alarm reporting function). It defines no scalars or tables itself, only the ItuAlarmPerceivedSeverity-style textual conventions that other alarm-reporting MIBs import to classify fault notifications consistently (e.g. critical, major, minor, warning, cleared). Its value for hardware/software status monitoring is entirely indirect: it underpins consistent severity classification for fault and alarm traps raised elsewhere in a device's MIB suite, letting an NMS triage incoming alarms by standardized severity rather than vendor-specific codes. It explicitly derives its conventions from ITU-T M.3100, X.733, and X.736, and is designed to be imported by other alarm-model MIBs (such as the IETF Alarm MIB). It is deployed as a dependency wherever telecom or carrier-grade equipment implements standards-based alarm reporting compliant with the ITU alarm model, and an engineer reviewing an ITU-ALARM-TC-MIB OID list will find only these severity/type conventions rather than concrete alarm instance objects, since actual alarm data resides in the importing MIBs.
IPNetwork Monitor allows you to monitor SNMP objects defined in ITU-ALARM-TC-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/carrier-grade network equipment implementing ITU alarm model
Monitoring Examples
No sample objects were extracted, consistent with this being a pure textual-conventions module with no runtime data of its own. An admin would never poll ITU-ALARM-TC-MIB directly; instead, its severity/type conventions are imported by other alarm-reporting MIBs so that fault traps across different vendors' equipment can be triaged using a common, ITU-standardized severity scale (critical/major/minor/warning/cleared). Its practical value shows up whenever an NMS normalizes alarms from multiple device types into one severity taxonomy.
OIDs
| OID symbolic | OID numeric | Type | Access | Description |
|---|---|---|---|---|
| ituAlarmTc | 1.3.6.1.2.1.120 | This MIB module defines the ITU Alarm textual convention for objects not expected to require regular extension. Copyright (C) The Internet Society (2004). The initial version of this MIB module was published in RFC 3877. For full legal notices see the RFC itself. Supplementary information may be available on: http://www.ietf.org/copyrights/ianamib.html |
RFC description
ITU-T alarm textual conventions MIB defining standard SNMP data types and conventions for alarm management, severity levels, and alarm notification handling in telecommunications systems.
Start monitoring Vendor-neutral IETF/ITU-T standard (telecom/carrier-grade equipment implementing ITU 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.