AGG-TRAP-MIB

All MIBs › AGG-TRAP-MIB

Organization: Lucent Technologies

Last Updated: 240701

Category: Alarm and Event Management

Description: Manages aggregated SNMP trap configuration, enabling batching or consolidation of multiple notifications into aggregate events.

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 AGG-TRAP-MIB?

AGG-TRAP-MIB is a Lucent Technologies MIB, registered under the lucent.products.mantraDevice branch, intended to manage aggregated/batched SNMP trap notifications for an unspecified "Mantra" device product line. The module's own description is an unfilled vendor template ("the xxxx protocol"), and only branch/registration nodes are present in the available source, so no specific data-object names can be confirmed. Conceptually, the category of data it is meant to expose is trap-handling configuration -- controls for batching, thresholds, or enabling/disabling aggregation of repeated fault notifications. Its intended monitoring value is fault-monitoring support: consolidating repeated notifications during a fault storm so an NMS trap receiver is not flooded with duplicate alerts, which indirectly aids visibility into device fault conditions. No dependency on other MIBs is evident, and it would be deployed wherever Lucent Mantra-branded devices generate high volumes of SNMP traps that benefit from aggregation before reaching a management station. Engineers can download the AGG-TRAP-MIB file directly to load it into their MIB browser.

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

Lucent Mantra device (specific product line unspecified in source)

Monitoring Examples

Only the branch/registration nodes (lucent, products, mantraDevice) are present in the sampled objects, so the specific trap-aggregation configuration objects cannot be confirmed from the available source. Conceptually an administrator would use this module to set batching parameters so that a burst of repeated fault traps from a Mantra device is consolidated into a single aggregate notification instead of flooding the trap receiver.

Imported Objects

From AGGREGATED-EXT-MIB

devName	OBJECT-TYPE
file	OBJECT-TYPE
host	OBJECT-TYPE
mateHost	OBJECT-TYPE
matePort	OBJECT-TYPE
minutes	OBJECT-TYPE
myHost	OBJECT-TYPE
myPort	OBJECT-TYPE
newFile	OBJECT-TYPE
oldFile	OBJECT-TYPE
pepName	OBJECT-TYPE
port	OBJECT-TYPE
reason	OBJECT-TYPE
result	OBJECT-TYPE
sbProducerHost	OBJECT-TYPE
sbProducerPort	OBJECT-TYPE
snName	OBJECT-TYPE
unknownDeviceTrapContents	OBJECT-TYPE

From RFC-1212

OBJECT-TYPE

From RFC1155-SMI

Counter
enterprises

From RFC1213-MIB

DisplayString

From SNMPv2-SMI

Counter32
Integer32
MODULE-IDENTITY
NOTIFICATION-TYPE
ObjectName
snmpModules

From SNMPv2-TC

RowStatus
TestAndIncr
TimeStamp
TruthValue

OIDs

OID symbolic	OID numeric	Description
lucent	1.3.6.1.4.1.1751
products	1.3.6.1.4.1.1751.1
mantraDevice	1.3.6.1.4.1.1751.1.1198
mantraTraps	1.3.6.1.4.1.1751.1.1198.0	The MIB module for entities implementing the xxxx protocol.
NTF unParsedEvent	1.3.6.1.4.1.1751.1.1198.0.5	An event is sent up as unParsedEvent, if there is an error in formatting, and event construction does not succeed. The variables are: 1) unknownDeviceTrapContents - a string representing the event text as the pep received it. Severity: MAJOR
NTF styxProducerConnect	1.3.6.1.4.1.1751.1.1198.0.6	Indicates that the pep was sucessfully able to connect to the source of events specified in its config. The variables are: 1) pepName - this is the name of the PEP who is raising the event 2) devName - this is the logical name of the device this pep is connected to 3-4) host:port - these two identify the device that was mounted by the pep 5) file - this is the file name used internally start-up event, mainly. Severity: INFO
NTF styxProducerUnReadable	1.3.6.1.4.1.1751.1.1198.0.7	Indicates that the pep's connection exists to the device, but the file named in the trap is not readable. The variables are: 1) pepName - this is the name of the PEP who is raising the event 2) devName - this is the logical name of the device this pep is connected to 3-4) host:port - these two identify the device that was mounted by the pep 5) file - this is the file name used internally Severity: MAJOR
NTF styxProducerDisconnect	1.3.6.1.4.1.1751.1.1198.0.8	Indicates that the pep's connection to the source of events was severed. This could either be because device process died, or because there is a network outage. The variables are: 1) pepName - this is the name of the PEP who is raising the event 2) devName - this is the logical name of the device this pep is connected to 3-4) host:port - these two identify the device that was mounted by the pep 5) file - this is the file name used internally Severity: MAJOR
NTF styxProducerUnReachable	1.3.6.1.4.1.1751.1.1198.0.9	Indicates that the pep's connection to the device has not been up for some time now, indicated in minutes. The variables are: 1) pepName - this is the name of the PEP who is raising the event 2) devName - this is the logical name of the device this pep is connected to 3-4) host, port - these two identify the device that was mounted by the pep 5) file - this is the file name used internally minutes - the time in minutes for which the connection to the device has not been up. Severity: MAJOR
NTF logFileChanged	1.3.6.1.4.1.1751.1.1198.0.10	Indicates that a log-file-change attempt is successful or failure. The variables are: 1) oldFile - this is the name of the old file which was to be changed. 2) newFile - this is the new log file name 3) result - this indicates 'success' or failure of logFileChange attempt. 4) reason - this describes the reason when log file change has failed. Severity: INFO
NTF styxFTMateConnect	1.3.6.1.4.1.1751.1.1198.0.11	Indicates that this ServiceNode was sucessfully able to connect to its redundant mate. This event is usually raised by the Backup mate who is responsible for monitoring its respective Primary. The variables are: 1) snName - this is the name of the ServiceNode who is raising the event. 2-3) myHost:myPort - these identify the host and port of the ServiceNode raising the event. 4-5) mateHost:matePort - these identify the host and port of the mate to which this ServiceNode connected. Severity: INFO
NTF styxFTMateDisconnect	1.3.6.1.4.1.1751.1.1198.0.12	Indicates that this ServiceNode has lost connection to its redundant mate due to either process or host failure. This event is usually raised by the Backup mate who is monitoring its respective Primary. Connection will be established upon recovery of the mate. The variables are: 1) snName - this is the name of the ServiceNode who is raising the event 2-3) myHost:myPort - these identify the host and port of the ServiceNode raising the event. 4-5) mateHost:matePort - these identify the host and port of the mate to which this ServiceNode lost connection. Severity: MAJOR
NTF sBProducerUnreachable	1.3.6.1.4.1.1751.1.1198.0.13	Indicates that this Socket Based Producer is not reachable by the Policy Enforcement Point. The variables are: 1) pepName - this is the name of the Policy Enforcement Point (PEP) who is raising the event 2) devName: Device which is unreachable 3) sbProducerHost: Host where the Socket Based event producer is on. 4) sbProducerPort: Port where the Socket Based event producer is running on. Severity: MAJOR
NTF sBProducerConnected	1.3.6.1.4.1.1751.1.1198.0.14	Indicates that this Socket Based Producer has connected to the Policy Enforcement Point (PEP). The variables are: 1) pepName - this is the name of the Policy Enforcement Point (PEP) who is raising the event 2) devName: Device which is unreachable 3) sbProducerHost: Host where the Socket Based event producer is on. 4) sbProducerPort: Port where the Socket Based event producer is running on. Severity: MAJOR
NTF sBProducerRegistered	1.3.6.1.4.1.1751.1.1198.0.15	Indicates that this Socket Based Producer has registered with the Policy Enforcement Point (PEP). The variables are: 1) pepName - this is the name of the Policy Enforcement Point (PEP) who is raising the event 2) devName: Device which is unreachable 3) sbProducerHost: Host where the Socket Based event producer is on. 4) sbProducerPort: Port where the Socket Based event producer is running on. Severity: INFO
NTF sBProducerDisconnected	1.3.6.1.4.1.1751.1.1198.0.16	Indicates that this Socket Based Producer has disconnected from the Policy Enforcement Point (PEP). The variables are: 1) pepName - this is the name of the Policy Enforcement Point (PEP) who is raising the event 2) devName: Device which is unreachable 3) sbProducerHost: Host where the Socket Based event producer is on. 4) sbProducerPort: Port where the Socket Based event producer is running on. Severity: INFO
NTF sBProducerCannotRegister	1.3.6.1.4.1.1751.1.1198.0.17	Indicates that this Socket Based Producer cannot register to the Policy Enforcement Point (PEP). The variables are: 1) pepName - this is the name of the Policy Enforcement Point (PEP) who is raising the event 2) devName: Device which is unreachable 3) sbProducerHost: Host where the Socket Based event producer is on. 4) sbProducerPort: Port where the Socket Based event producer is running on. Severity: INFO
NTF sBProducerCannotDisconnect	1.3.6.1.4.1.1751.1.1198.0.18	Indicates that this Socket Based Producer cannot disconenct from the Policy Enforcement Point (PEP). The variables are: 1) pepName - this is the name of the Policy Enforcement Point (PEP) who is raising the event 2) devName: Device which is unreachable 3) sbProducerHost: Host where the Socket Based event producer is on. 4) sbProducerPort: Port where the Socket Based event producer is running on. Severity: INFO

RFC description

Event and trap handling for Lucent Mantra network management aggregation platform.

Start monitoring Lucent Technologies networking equipment 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 AGG-TRAP-MIB

What Is AGG-TRAP-MIB?

Supported Devices

Monitoring Examples

This MIB depends on

Related MIBs

RFC description