MIB Viewer

MANTRA-TRAP-MIB

23 objects
The MIB module for entities implementing the xxxx protocol.
Imported Objects
AGGREGATED-EXT-MIBdeviceType devName domain file group host mateHost matePort minutes myHost myPort name newFile oldFile pepName port reason result runStatus sbProducerHost sbProducerPort snName unknownDeviceTrapContents
RFC-1212OBJECT-TYPE
RFC1155-SMICounter enterprises
SNMPv2-SMICounter32 Integer32 MODULE-IDENTITY NOTIFICATION-TYPE ObjectName snmpModules
SNMPv2-TCDisplayString RowStatus TestAndIncr TimeStamp TruthValue
OIDNameAccessStatusDescription
1.3.6.1.4.1.1751Nodelucent
1.3.6.1.4.1.1751.1Nodeproducts
1.3.6.1.4.1.1751.1.1198NodesoftSwitch
1.3.6.1.4.1.1751.1.1198.0IdentitymantraTrapsThe MIB module for entities implementing the xxxx protocol.
1.3.6.1.4.1.1751.1.1198.0.0NotificationlssProcessUnstartablecurrentIndicates a certain domain:group:process cannot be started even after several attempts. Variables are: 1) deviceType - this is either CC, H323, SS7 or EBGen (t…
1.3.6.1.4.1.1751.1.1198.0.1NotificationlssProcessCreatedcurrentIndicates a certain domain:group:process was successfully created/re-started. Variables are same as the above trap: 1) deviceType - this is either CC, H323, SS…
1.3.6.1.4.1.1751.1.1198.0.2NotificationlssProcessDiedcurrentIndicates a certain domain:group:process died. 1) deviceType - this is either CC, H323, SS7 or EBGen (the various modules in SARAS) 2-4) domain:group:name - th…
1.3.6.1.4.1.1751.1.1198.0.3NotificationlssProcessKilledcurrentIndicates a certain domain:group:process was taken down manually in response to an snmp-set on mantraReboot, or processStop variable. Variables are exactly sam…
1.3.6.1.4.1.1751.1.1198.0.4NotificationlssProcessStateChangecurrentIndicates a change of status in a process. Usually sent to indicate if a process that was inactive, took over for an earlier active process that died. Variable…
1.3.6.1.4.1.1751.1.1198.0.5NotificationlssInternalErrorcurrentAn event is sent up as lssInternalError, if there is an error in formatting, and event construction does not succeed. The variables are: 1) unknownDeviceTrapCo…
1.3.6.1.4.1.1751.1.1198.0.6NotificationlssElementSuccessfulConnectioncurrentIndicates 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.7NotificationlssElementFileUnReadablecurrentIndicates 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.8NotificationlssElementDisconnectcurrentIndicates 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.9NotificationlssElementUnReachablecurrentIndicates 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.10NotificationlogFileChangedcurrentIndicates 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.11NotificationlssFTMateConnectcurrentIndicates 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.12NotificationlssFTMateDisconnectcurrentIndicates 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.13NotificationsbProducerUnreachablecurrentIndicates 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.14NotificationsbProducerConnectedcurrentIndicates 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.15NotificationsbProducerRegisteredcurrentIndicates 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.16NotificationsbProducerDisconnectedcurrentIndicates 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.17NotificationsbProducerCannotRegistercurrentIndicates 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.18NotificationsbProducerCannotDisconnectcurrentIndicates 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…