Indicates a certain domain:group:process cannot be
started even after several attempts. Variables are:
1) deviceType - this is either CC, H323, SS7 or
EBGen (the various modules in SARAS)
2-4) domain:group:name - these three variables comprise
the fully qualified name of the process (for start/
stop snmp-commands)
5) host - the hostname on which this process was to be
run.
6) port - the port on which this process was exposing
its health information.
7) runStatus - the current run-state in which the
process is (likely to be 1). See moduleSummary for
more explanation of runStatus.
Severity: CRITICAL
Parsed from file mantraTraps.MIB.txt
Company: None
Module: MANTRA-TRAP-MIB
Indicates a certain domain:group:process cannot be
started even after several attempts. Variables are:
1) deviceType - this is either CC, H323, SS7 or
EBGen (the various modules in SARAS)
2-4) domain:group:name - these three variables comprise
the fully qualified name of the process (for start/
stop snmp-commands)
5) host - the hostname on which this process was to be
run.
6) port - the port on which this process was exposing
its health information.
7) runStatus - the current run-state in which the
process is (likely to be 1). See moduleSummary for
more explanation of runStatus.
Severity: CRITICAL
Parsed from file MANTRA-TRAP-MIB.mib
Module: MANTRA-TRAP-MIB
Vendor: Lucent Technologies
Module: MANTRA-TRAP-MIB
[Automatically extracted from oidview.com]
lssProcessUnstartable NOTIFICATION-TYPE OBJECTS { deviceType, domain, group, name, host, port, runStatus } STATUS current DESCRIPTION "Indicates a certain domain:group:process cannot be started even after several attempts. Variables are: 1) deviceType - this is either CC, H323, SS7 or EBGen (the various modules in SARAS) 2-4) domain:group:name - these three variables comprise the fully qualified name of the process (for start/ stop snmp-commands) 5) host - the hostname on which this process was to be run. 6) port - the port on which this process was exposing its health information. 7) runStatus - the current run-state in which the process is (likely to be 1). See moduleSummary for more explanation of runStatus. Severity: CRITICAL" ::= { mantraTraps 0 }
lssProcessUnstartable NOTIFICATION-TYPE OBJECTS { deviceType, domain, group, name, host, port, runStatus } STATUS current DESCRIPTION "Indicates a certain domain:group:process cannot be started even after several attempts. Variables are: 1) deviceType - this is either CC, H323, SS7 or EBGen (the various modules in SARAS) 2-4) domain:group:name - these three variables comprise the fully qualified name of the process (for start/ stop snmp-commands) 5) host - the hostname on which this process was to be run. 6) port - the port on which this process was exposing its health information. 7) runStatus - the current run-state in which the process is (likely to be 1). See moduleSummary for more explanation of runStatus. Severity: CRITICAL" ::= { mantraTraps 0 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.1751.1.1198.0.1 | lssProcessCreated | 0 | 0 | Indicates a certain domain:group:process was successfully created/re-started. Variables are same as the above trap: 1) deviceTy… |
| 1.3.6.1.4.1.1751.1.1198.0.2 | lssProcessDied | 0 | 0 | Indicates a certain domain:group:process died. 1) deviceType - this is either CC, H323, SS7 or EBGen (the various modules in SA… |
| 1.3.6.1.4.1.1751.1.1198.0.3 | lssProcessKilled | 0 | 0 | Indicates a certain domain:group:process was taken down manually in response to an snmp-set on mantraReboot, or processStop varia… |
| 1.3.6.1.4.1.1751.1.1198.0.4 | lssProcessStateChange | 0 | 0 | Indicates a change of status in a process. Usually sent to indicate if a process that was inactive, took over for an earlier act… |
| 1.3.6.1.4.1.1751.1.1198.0.5 | unParsedEvent, lssInternalError | 0 | 0 | An event is sent up as unParsedEvent, if there is an error in formatting, and event construction does not succeed. The variables a… |
| 1.3.6.1.4.1.1751.1.1198.0.6 | styxProducerConnect, lssElementSuccessfulConnection | 0 | 0 | Indicates that the pep was sucessfully able to connect to the source of events specified in its config. The variables are: 1) pep… |
| 1.3.6.1.4.1.1751.1.1198.0.7 | styxProducerUnReadable, lssElementFileUnReadable | 0 | 0 | Indicates that the pep's connection exists to the device, but the file named in the trap is not readable. The variables are: 1) p… |
| 1.3.6.1.4.1.1751.1.1198.0.8 | styxProducerDisconnect, lssElementDisconnect | 0 | 0 | Indicates that the pep's connection to the source of events was severed. This could either be because device process died, or be… |
| 1.3.6.1.4.1.1751.1.1198.0.9 | styxProducerUnReachable, lssElementUnReachable | 0 | 0 | Indicates that the pep's connection to the device has not been up for some time now, indicated in minutes. The variables are: 1) … |
| 1.3.6.1.4.1.1751.1.1198.0.10 | logFileChanged | 0 | 0 | Indicates that a log-file-change attempt is successful or failure. The variables are: 1) oldFile - this is the name of the old f… |
| 1.3.6.1.4.1.1751.1.1198.0.11 | styxFTMateConnect, lssFTMateConnect | 0 | 0 | Indicates that this ServiceNode was sucessfully able to connect to its redundant mate. This event is usually raised by the Backup… |
| 1.3.6.1.4.1.1751.1.1198.0.12 | styxFTMateDisconnect, lssFTMateDisconnect | 0 | 0 | Indicates that this ServiceNode has lost connection to its redundant mate due to either process or host failure. This event is us… |
| 1.3.6.1.4.1.1751.1.1198.0.13 | sbProducerUnreachable | 0 | 0 | SBProducerUnreachable |
| 1.3.6.1.4.1.1751.1.1198.0.14 | sbProducerConnected | 0 | 0 | SBProducerConnected |
| 1.3.6.1.4.1.1751.1.1198.0.15 | sbProducerRegistered | 0 | 0 | SBProducerRegistered |
| 1.3.6.1.4.1.1751.1.1198.0.16 | sbProducerDisconnected | 0 | 0 | SBProducerDisconnected |
| 1.3.6.1.4.1.1751.1.1198.0.17 | sbProducerCannotRegister | 0 | 0 | SBProducerCannotRegister |
| 1.3.6.1.4.1.1751.1.1198.0.18 | sbProducerCannotDisconnect | 0 | 0 | SBProducerCannotDisconnect |