All MIBs › TROPIC-ABSNODE-NOTIFICATION-MIB
Organization: Alcatel-Lucent
Last Updated: 2016-02-26
Category: Nokia Optical Transport
Description: Defines Alcatel-Lucent Tropic abstract node SNMP notifications and alarm traps for optical transport.
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 TROPIC-ABSNODE-NOTIFICATION-MIB?
TROPIC-ABSNODE-NOTIFICATION-MIB is a private vendor MIB, originally from Alcatel-Lucent and now under Nokia's Tropic optical transport product line, that defines SNMP notifications and alarm traps for the 'abstract node' -- a generalized representation of a managed network element in the Tropic WDM/optical transport system. It exposes fault-category data exclusively: trap definitions used to signal alarms and state changes at the network-element level rather than routine performance counters. In monitoring terms this module is squarely about fault/status notification for the overall network element -- surfacing conditions like configuration changes, alarm raise/clear events, or communication state changes so an NMS can react to abstract-node-level faults, distinct from the more granular hardware alarms defined in companion Tropic MIBs (e.g., card or shelf level). It works alongside other TROPIC-*-MIB modules (card, shelf, optical card, PHM) which define the alarm conditions this notification framework reports on. It is deployed in Nokia/Alcatel-Lucent optical transport (WDM) network deployments as part of the overall element management alarm surfacing pipeline. Engineers can download the TROPIC-ABSNODE-NOTIFICATION-MIB file directly to load it into their MIB browser.
IPNetwork Monitor allows you to monitor SNMP objects defined in TROPIC-ABSNODE-NOTIFICATION-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
- Nokia (formerly Alcatel-Lucent) Tropic optical transport network element
Monitoring Examples
No sample object names were provided for this module, so a concrete object-level scenario cannot be given; consistent with its stated purpose as an abstract-node notification MIB, an NMS would subscribe to its traps to receive alarm raise/clear events at the network-element level, using them to trigger investigation of underlying card, shelf, or optical hardware faults reported by companion Tropic MIBs.
What Can Be Monitored
- network-element alarm raise/clear events
- abstract-node state change notifications
Imported Objects
From SNMPv2-SMI
| MODULE-IDENTITY | |
| NOTIFICATION-TYPE |
From TROPIC-GLOBAL-REG
| tnAbsNodeMIBModules | OBJECT-IDENTITY |
| tnNotificationObjs | OBJECT-IDENTITY |
| tnTrapCategory | OBJECT-TYPE |
| tnTrapCondition | OBJECT-TYPE |
| tnTrapData | OBJECT-TYPE |
| tnTrapDescr | OBJECT-TYPE |
| tnTrapEntityType | OBJECT-TYPE |
| tnTrapObjectID | OBJECT-TYPE |
| tnTrapObjectIDType | OBJECT-TYPE |
| tnTrapServiceAffecting | OBJECT-TYPE |
| tnTrapTime | OBJECT-TYPE |
OIDs
RFC description
Alcatel-Lucent abstract node notifications for alarm and event generation on network elements, extending GMPLS object management.
Start monitoring Nokia (formerly Alcatel-Lucent) Tropic optical transport network element (abstract-node fault notification 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.