NLSBBN-TRAPS-MIB

MIB Reference — IPNetwork Monitor

All MIBsNLSBBN-TRAPS-MIB

Category: Network Management

Description:

Defines SNMP trap notifications for fault events and status changes on NLS BBN network devices.

Imported Objects

From NLS-BBNIDENT-MIB

bbnTrapsOBJECT-IDENTITY
giOBJECT-IDENTITY
nlsbbnOBJECT-IDENTITY

From RFC-1212

OBJECT-TYPE

From RFC-1215

TRAP-TYPE

From RFC1155-SMI

Counter
IpAddress
TimeTicks
enterprises

From RFC1213-MIB

DisplayString

From RFC1271-MIB

EntryStatus

What Is NLSBBN-TRAPS-MIB?

NLSBBN-TRAPS-MIB is a vendor-specific notification module defining SNMP trap definitions for NLS BBN network devices, a broadband networking product line. Rather than exposing pollable counters or tables, its content is entirely fault and event notification objects that a device sends asynchronously to a management station when a significant state change occurs. It is used specifically for monitoring hardware and software status changes on the device by alerting operators in near-real-time to conditions such as link failures, hardware faults, restarts, or configuration changes, rather than requiring the NMS to poll for them. As a traps-only module it typically depends on the vendor's companion identification/registration MIB (such as NLS-BBNIDENT-MIB) for the enterprise OID root and object identity definitions referenced in the trap varbinds. It is deployed in broadband access or aggregation network environments where NLS BBN equipment is installed and integrated into a fault management/NMS trap-receiver pipeline. Because the NLSBBN-TRAPS-MIB MIB contains no polled counters, its value is realized only once trap forwarding is properly configured and received traps are correlated against device inventory.

IPNetwork Monitor allows you to monitor SNMP objects defined in NLSBBN-TRAPS-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

  • NLS BBN broadband network device

Monitoring Examples

No sample objects were provided and the module description is empty in the source, so specific trap names cannot be confirmed from the available data; based on the module name, traps would plausibly correspond to fault events and status-change notifications (e.g. link up/down, hardware alarm, reboot) rather than any counters or tables. Because this is fundamentally a notification-only MIB, there are no gauge or counter objects to poll on a schedule -- its value comes from configuring the device to send these traps to a trap receiver so operators are alerted the moment a fault occurs. An admin would configure trap destinations on the NLS BBN device and correlate incoming traps against device inventory to identify which unit raised the alarm.

OIDs
OID symbolicOID numericTypeAccessDescription
bbnTrapElements1.3.6.1.4.1.1166.5.3.1
INT trapIdentifier1.3.6.1.4.1.1166.5.3.1.1INTEGERread-onlyThis object identifies the trap issued by the network element.
STR trapNetworkElemModelNumber1.3.6.1.4.1.1166.5.3.1.2DisplayStringread-onlyThe value of this object is the model number of the network element. Combination of Model # and Serial # is used as the unique identifier of the NE.
STR trapNetworkElemSerialNum1.3.6.1.4.1.1166.5.3.1.3DisplayStringread-onlyThe value of this object is the serial number of the network element. Combination of Model # and Serial # is used as the unique identifier of the NE.
INT trapPerceivedSeverity1.3.6.1.4.1.1166.5.3.1.4INTEGERread-onlyThis parameter defines five severity levels, which provide an indication of how it is perceived that the capability of the managed object has been affected. The other level is not a severity level, but indicates that an alarm has been cleared, and thus is no longer in alarm state. Note that this field has no meaning for configuration change traps.
INT trapNetworkElemOperState1.3.6.1.4.1.1166.5.3.1.5INTEGERread-onlyThe current Operational State of the Network Element which generated the trap.
INT trapNetworkElemAlarmStatus1.3.6.1.4.1.1166.5.3.1.6INTEGERread-onlyThe current Alarm Status of the Network Element Alarm Status is always equal to the highest severity level of all outstanding alarms in this NE.
INT trapNetworkElemAdminState1.3.6.1.4.1.1166.5.3.1.7INTEGERread-onlyThe current Adminsitrative state of the network element.
INT trapNetworkElemAvailStatus1.3.6.1.4.1.1166.5.3.1.8INTEGERread-onlyThe current Operational state of the network elment is defined in ISO/IEC 10164-2.
STR trapText1.3.6.1.4.1.1166.5.3.1.9DisplayStringread-onlyThis variable contains an optional trap text.
TIK trapNETrapLastTrapTimeStamp1.3.6.1.4.1.1166.5.3.1.10TimeTicksread-onlyThis OBJECT IDENTIFIER is used to hold time since NE was 'CHANGED' last time. 'CHANGE' is defined as: 1) any write operation was performed on this NE which caused a trap. 2) any alarm was generated by this NE which caused a trap. 3) any alarm was cleared on this NE which caused a trap.
OID trapChangedObjectId1.3.6.1.4.1.1166.5.3.1.11OBJECT IDENTIFIERread-onlyThis variable identifies the object that has generated the trap.
INT trapAdditionalInfoInteger11.3.6.1.4.1.1166.5.3.1.12INTEGERread-onlyThis 32 bit integer is used to hold specific information about the trap.
INT trapAdditionalInfoInteger21.3.6.1.4.1.1166.5.3.1.13INTEGERread-onlyThis 32 bit integer is used to hold specific information about the trap.
INT trapAdditionalInfoInteger31.3.6.1.4.1.1166.5.3.1.14INTEGERread-onlyThis 32 bit integer is used to hold specific information about the trap.
STR trapChangedValueDisplayString1.3.6.1.4.1.1166.5.3.1.15DisplayStringread-onlyThis DisplayString is used to hold specific information about the trap.
OID trapChangedValueOID1.3.6.1.4.1.1166.5.3.1.16OBJECT IDENTIFIERread-onlyThis OBJECT IDENTIFIER is used to hold specific information about the trap.
IP trapChangedValueIpAddress1.3.6.1.4.1.1166.5.3.1.17IpAddressread-onlyThis OBJECT IDENTIFIER is used to hold specific information about the trap.
INT trapChangedValueInteger1.3.6.1.4.1.1166.5.3.1.18INTEGERread-onlyThis 32 bit integer is used to hold specific information about the trap.
bbnTrapControl1.3.6.1.4.1.1166.5.3.2
INT numberOfTrapReceivers1.3.6.1.4.1.1166.5.3.2.1INTEGERread-onlyThe number of managers to send traps to. This number can not exceed 4
trapReceiversTable1.3.6.1.4.1.1166.5.3.2.2not-accessibleA list of managers to send traps to. The number of entries is given by the value of NumTrapReceivers. Maximum number of Trap Receivers is four.
trapReceiversTableEntry1.3.6.1.4.1.1166.5.3.2.2.1not-accessibleThe managers to send traps to.
INT trapReceiversTableIndex1.3.6.1.4.1.1166.5.3.2.2.1.1INTEGERnot-accessibleThe index to a trap receiver entry.
IP trapReceiverAddr1.3.6.1.4.1.1166.5.3.2.2.1.2IpAddressread-writeThe IP address of the manager to send a trap to. NOTE: Changing TrapReceiverAddr FROM default value to anything else is equivalent of 'creating' of a new entry. Changing TrapReceiverAddr TO default value will result in deletion of that entry.
STR trapReceiverCommunityString1.3.6.1.4.1.1166.5.3.2.2.1.3DisplayStringread-writeThe community name to use in the trap when sent to the manager.
INT trapToBeSendQueueSize1.3.6.1.4.1.1166.5.3.2.2.1.4INTEGERread-writeThe agent maintains 2 queues: TrapsToBeSendQueue and TrapsSentQueue. The SNMP agent can receive a burst of traps which need to be sent to the network manager. The SNMP agent will put them in TrapsToBeSendQueue and from there hi will send traps to the a manager at throttling rate. The traps will be kept in sequence by the time at which they came in.
INT trapSentQueueSize1.3.6.1.4.1.1166.5.3.2.2.1.5INTEGERread-writeThe agent maintains 2 queues: TrapsToBeSendQueue and TrapsSentQueue. The SNMP agent maintains Trap History (TrapsSentQueue) by saving last 'X' sent traps.
INT trapThrottlingRate1.3.6.1.4.1.1166.5.3.2.2.1.6INTEGERread-writeThe number of traps agent can send to a particular manager (trapReceiver) per second.
INT trapLastSent1.3.6.1.4.1.1166.5.3.2.2.1.7INTEGERread-onlyThis variable contains the last trapIdentifier (sequence number) agent sent to this manager. Upon startup agent will send cold-start trap and sat value of TrapLastSent to 1.
INT trapReceiversEntryOperState1.3.6.1.4.1.1166.5.3.2.2.1.8INTEGERread-writeThe current Operational State of this entry in TrapReceivers Table.
INT trapResendRequest1.3.6.1.4.1.1166.5.3.2.2.1.9INTEGERread-writeThe manager may write this object when the indicated trap (indicated via trapIdentifier) should be resent. It is not intended to be read by the manager, but is read-write for compatability with older SNMP compilers.
INT numberOfDiscriminators1.3.6.1.4.1.1166.5.3.2.3INTEGERread-onlyThe number of EFDs (filters) agent has in it's database. This number can not exceed 20
trapDiscrimTable1.3.6.1.4.1.1166.5.3.2.4not-accessibleA list of EFDs (trap filters). Before forwarding trap to a trapReceiver (manager) agent filters all traps acording to all EFDs defined for this manager.
trapDiscrimTableEntry1.3.6.1.4.1.1166.5.3.2.4.1not-accessibleThe list of discriminators (trap filters.)
INT trapDiscrimTableIndex1.3.6.1.4.1.1166.5.3.2.4.1.1INTEGERnot-accessibleThe index to a trap discriminator entry.
IP trapDiscrimReceiverAddr1.3.6.1.4.1.1166.5.3.2.4.1.2IpAddressread-writeThe IP address of the manager this Discrim belongs to. It should be equal to TrapReceiverAddr. NOTE: Changing TrapDiscrimReceiverAddr FROM default value to anything else is equivalent of 'creating' of a new entry. Changing TrapReceiverAddr TO default value will result in deletion of that entry.
INT trapDiscrimAvailabilityStatus1.3.6.1.4.1.1166.5.3.2.4.1.3INTEGERread-onlyThis object reflects the current Availability status of the Discrim (based on ISO/IEC 10164-2).
STR trapDiscrimWeeklyMask1.3.6.1.4.1.1166.5.3.2.4.1.4DisplayStringread-writeThis object represents weekly scedule for corresponding Discrim. The WeeklyMask consists of 7 numeric characters (1 for each day of the week). Each numeric character can take a value of eather '1' - enabled or '2' - disabled. For example, with WeeklyMask='1122221', an agent will aplly corresponding Disriminator only on Mondays, Tuesdays and Sundays. Any characters other than '1' and '2' will be ignored.
INT trapDiscrimDailyStartTime1.3.6.1.4.1.1166.5.3.2.4.1.5INTEGERread-writeThis object represents daily start time for corresponding Discrim. The StartTime is expressed as an offset (in minutes) from 2400 hours military time. For example, StartTime=70 represents start time of 1:10 AM.
INT trapDiscrimDailyStopTime1.3.6.1.4.1.1166.5.3.2.4.1.6INTEGERread-writeThis object represents daily stop time for corresponding Discrim. The StopTime is expressed as an offset (in minutes) from 2400 hours military time. For example, StopTime=70 represents stop time of 1:10 AM.
INT trapSeverityDiscrim1.3.6.1.4.1.1166.5.3.2.4.1.7INTEGERread-writeThe severity threshold of traps to be send to the manager. Only traps of equal or greater severity than this value are sent to the manager.
INT trapDiscrimOperationalState1.3.6.1.4.1.1166.5.3.2.4.1.8INTEGERread-writeThe current Operational State of the Discriminator.
INT trapDiscrimConfigChangeCntl1.3.6.1.4.1.1166.5.3.2.4.1.9INTEGERread-writeThis variable turns reporting of configuration changes on or off.

FAQ

What does NLSBBN-TRAPS-MIB actually monitor on an NLS BBN broadband device?
It defines the SNMP traps an NLS BBN broadband device sends when something changes state — link failures, hardware faults, restarts, or configuration changes — rather than exposing counters you poll. So instead of walking a table on a schedule, you configure the device to send these traps to your management station and get near-real-time alerts when a fault occurs.

I've pointed my trap receiver at an NLS BBN device but the alerts don't identify which object changed — what am I missing?
NLSBBN-TRAPS-MIB is a traps-only module and typically relies on a companion identification/registration MIB (such as NLS-BBNIDENT-MIB) for the enterprise OID root and object identity referenced in the trap varbinds. Make sure that companion MIB is also loaded in your trap receiver so it can resolve the varbind OIDs to meaningful device/object names instead of showing raw numeric OIDs.

RFC description

Network Laboratory Systems BBN vendor-specific MIB defining trap (notification) objects for network monitoring and alerting on BBN networking equipment.

Start monitoring NLS BBN broadband network device (SNMP trap notifications) 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 NLSBBN-TRAPS-MIB