AGG-TRAP-MIB
18 objects
The MIB module for entities implementing the xxxx protocol.
Imported Objects
| OID | Name | Access | Status | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.1751 | Nodelucent | |||
| 1.3.6.1.4.1.1751.1 | Nodeproducts | |||
| 1.3.6.1.4.1.1751.1.1198 | NodemantraDevice | |||
| 1.3.6.1.4.1.1751.1.1198.0 | IdentitymantraTraps | The MIB module for entities implementing the xxxx protocol. | ||
| 1.3.6.1.4.1.1751.1.1198.0.5 | NotificationunParsedEvent | current | An event is sent up as unParsedEvent, if there is an error in formatting, and event construction does not succeed. The variables are: 1) unknownDeviceTrapConte… | |
| 1.3.6.1.4.1.1751.1.1198.0.6 | NotificationstyxProducerConnect | current | 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… | |
| 1.3.6.1.4.1.1751.1.1198.0.7 | NotificationstyxProducerUnReadable | current | 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 t… | |
| 1.3.6.1.4.1.1751.1.1198.0.8 | NotificationstyxProducerDisconnect | current | 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… | |
| 1.3.6.1.4.1.1751.1.1198.0.9 | NotificationstyxProducerUnReachable | current | 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 … | |
| 1.3.6.1.4.1.1751.1.1198.0.10 | NotificationlogFileChanged | current | 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)… | |
| 1.3.6.1.4.1.1751.1.1198.0.11 | NotificationstyxFTMateConnect | current | 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 m… | |
| 1.3.6.1.4.1.1751.1.1198.0.12 | NotificationstyxFTMateDisconnect | current | 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 mat… | |
| 1.3.6.1.4.1.1751.1.1198.0.13 | NotificationsBProducerUnreachable | current | 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 Enfo… | |
| 1.3.6.1.4.1.1751.1.1198.0.14 | NotificationsBProducerConnected | current | 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 E… | |
| 1.3.6.1.4.1.1751.1.1198.0.15 | NotificationsBProducerRegistered | current | 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 Polic… | |
| 1.3.6.1.4.1.1751.1.1198.0.16 | NotificationsBProducerDisconnected | current | 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 Pol… | |
| 1.3.6.1.4.1.1751.1.1198.0.17 | NotificationsBProducerCannotRegister | current | 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… | |
| 1.3.6.1.4.1.1751.1.1198.0.18 | NotificationsBProducerCannotDisconnect | current | 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 Po… |