AGG-TRAP-MIB

File: AGG-TRAP-MIB.mib (10344 bytes)

Imported modules

RFC1155-SMI RFC-1212 RFC1213-MIB
SNMPv2-SMI AGGREGATED-EXT-MIB SNMPv2-TC

Imported symbols

enterprises Counter OBJECT-TYPE
DisplayString NOTIFICATION-TYPE MODULE-IDENTITY
ObjectName Integer32 Counter32
snmpModules unknownDeviceTrapContents pepName
devName host port
file oldFile newFile
reason snName myHost
myPort mateHost matePort
minutes result sbProducerHost
sbProducerPort TruthValue DisplayString
TestAndIncr TimeStamp RowStatus

Defined Values

lucent 1.3.6.1.4.1.1751
OBJECT IDENTIFIER    

products 1.3.6.1.4.1.1751.1
OBJECT IDENTIFIER    

mantraDevice 1.3.6.1.4.1.1751.1.1198
OBJECT IDENTIFIER    

mantraTraps 1.3.6.1.4.1.1751.1.1198.0
The MIB module for entities implementing the xxxx protocol.
MODULE-IDENTITY    

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
NOTIFICATION-TYPE    

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
NOTIFICATION-TYPE    

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
NOTIFICATION-TYPE    

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
NOTIFICATION-TYPE    

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
NOTIFICATION-TYPE    

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
NOTIFICATION-TYPE    

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
NOTIFICATION-TYPE    

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
NOTIFICATION-TYPE    

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
NOTIFICATION-TYPE    

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
NOTIFICATION-TYPE    

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
NOTIFICATION-TYPE    

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
NOTIFICATION-TYPE    

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
NOTIFICATION-TYPE    

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
NOTIFICATION-TYPE