| OID symbolic | OID numeric | Type | Access | Description |
|---|
| lucent | 1.3.6.1.4.1.1751 | | | |
| products | 1.3.6.1.4.1.1751.1 | | | |
| softSwitch | 1.3.6.1.4.1.1751.1.1198 | | | |
| mantraTraps | 1.3.6.1.4.1.1751.1.1198.0 | | | The MIB module for entities implementing the xxxx
protocol. |
| NTF lssProcessUnstartable | 1.3.6.1.4.1.1751.1.1198.0.0 | | | 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 |
| NTF lssProcessCreated | 1.3.6.1.4.1.1751.1.1198.0.1 | | | Indicates a certain domain:group:process was
successfully created/re-started. Variables are same
as the above trap:
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. See moduleSummary for more explanation
of runStatus.
Severity: INFO |
| NTF lssProcessDied | 1.3.6.1.4.1.1751.1.1198.0.2 | | | Indicates 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 - 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. See moduleSummary for more explanation
of runStatus.
Severity: MAJOR |
| NTF lssProcessKilled | 1.3.6.1.4.1.1751.1.1198.0.3 | | | Indicates a certain domain:group:process was taken
down manually in response to an snmp-set on mantraReboot,
or processStop variable. Variables are exactly same as
in the processDied trap:
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. See moduleSummary for more explanation
of runStatus.
Severity: MAJOR |
| NTF lssProcessStateChange | 1.3.6.1.4.1.1751.1.1198.0.4 | | | Indicates 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.
Variables are exactly same as all other traps:
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. See moduleSummary for more explanation
of runStatus.
Severity: MAJOR |
| NTF lssInternalError | 1.3.6.1.4.1.1751.1.1198.0.5 | | | An event is sent up as lssInternalError,
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 |
| NTF lssElementSuccessfulConnection | 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 |
| NTF lssElementFileUnReadable | 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 |
| NTF lssElementDisconnect | 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 |
| NTF lssElementUnReachable | 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 |
| NTF 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 |
| NTF lssFTMateConnect | 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 |
| NTF lssFTMateDisconnect | 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 |
| NTF 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 |
| NTF 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 |
| NTF 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 |
| NTF 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 |
| NTF 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 |
| NTF 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 |
