AGG-TRAP-MIB
AI MIB Summary
The AGG-TRAP-MIB module defines SNMP trap definitions for aggregating network devices, specifically facilitating the notification of link state changes, port status transitions, and aggregation group failures within Layer 2 or Layer 3 link aggregation (LAG) environments. It enables network management systems to receive asynchronous alerts regarding the operational status of EtherChannel, LACP, or static bundle interfaces to trigger immediate fault isolation and recovery procedures.
The MIB module for entities implementing the xxxx protocol.
Main OID:
mantraTraps.1.3.6.1.4.1.1751.1.1198.0
20
Objects
Active
Status
6
Dependencies
Imported Objects
Objects
20 total| Object Name |
|---|
lucent OBJECT IDENTIFIER .1.3.6.1.4.1.1751 |
RFC1155-SMI Unknown .1.3.6.1.4.1.1751 |
RFC1213-MIB NOTIFICATION-TYPE .1.3.6.1.4.1.1751 |
products OBJECT IDENTIFIER .1.3.6.1.4.1.1751.1 |
mantraDevice OBJECT IDENTIFIER .1.3.6.1.4.1.1751.1.1198 |
mantraTrapsThe MIB module for entities implementing the xxxx
protocol. MODULE-IDENTITY .1.3.6.1.4.1.1751.1.1198.0 |
unParsedEventAn 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 NOTIFICATION-TYPE .1.3.6.1.4.1.1751.1.1198.0.5 |
styxProducerConnectIndicates 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 NOTIFICATION-TYPE .1.3.6.1.4.1.1751.1.1198.0.6 |
styxProducerUnReadableIndicates 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 NOTIFICATION-TYPE .1.3.6.1.4.1.1751.1.1198.0.7 |
styxProducerDisconnectIndicates 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 NOTIFICATION-TYPE .1.3.6.1.4.1.1751.1.1198.0.8 |
styxProducerUnReachableIndicates 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 NOTIFICATION-TYPE .1.3.6.1.4.1.1751.1.1198.0.9 |
logFileChangedIndicates 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 NOTIFICATION-TYPE .1.3.6.1.4.1.1751.1.1198.0.10 |
styxFTMateConnectIndicates 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 NOTIFICATION-TYPE .1.3.6.1.4.1.1751.1.1198.0.11 |
styxFTMateDisconnectIndicates 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 NOTIFICATION-TYPE .1.3.6.1.4.1.1751.1.1198.0.12 |
sBProducerUnreachableIndicates 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 NOTIFICATION-TYPE .1.3.6.1.4.1.1751.1.1198.0.13 |
sBProducerConnectedIndicates 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 NOTIFICATION-TYPE .1.3.6.1.4.1.1751.1.1198.0.14 |
sBProducerRegisteredIndicates 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 NOTIFICATION-TYPE .1.3.6.1.4.1.1751.1.1198.0.15 |
sBProducerDisconnectedIndicates 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 NOTIFICATION-TYPE .1.3.6.1.4.1.1751.1.1198.0.16 |
sBProducerCannotRegisterIndicates 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 NOTIFICATION-TYPE .1.3.6.1.4.1.1751.1.1198.0.17 |
sBProducerCannotDisconnectIndicates 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 NOTIFICATION-TYPE .1.3.6.1.4.1.1751.1.1198.0.18 |