Alcatel-Lucent 5620 - Page 122

3 — Troubleshooting using network alarms
3-80 Alcatel-Lucent 5620 Service Aware Manager, Release
Troubleshooting Guide 3HE 05723 TQZZA Edition 01
Name: SnmpDaemonProblem
Type: communicationsAlarm (4)
Probable cause: snmpDaemonError (138)
Severity: Critical
Object Type (class):
NetworkElement
Domain: netw
Implicitly cleared (self-clearing): No
The alarm is raised when one of the
following occurs:
• The 5620 SAM receives an
unexpected response to an SNMP
request, for example, when a
managed NE sends the wrong
object in response to an SMNP
get or get-next request.
• The 5620 SAM receives the
TIMETRA-SYSTEM-MIB.tmnxSnmp
dError trap from a managed NE.
Name: SnmpDown
Type: communicationsAlarm (4)
Probable cause: snmpDown (306)
Severity: Critical
Object Type (class):
NetworkElement
Domain: netw
Implicitly cleared (self-clearing): No
The alarm is raised when the SNMP
agent is manually shut down on an NE
and the NE sends a trap to indicate
this.
Name: SnmpReachabilityProblem
Type: communicationsAlarm (4)
Probable cause:
SnmpReachabilityTestFailed (176)
Severity: Major
Object Type (class):
NetworkElement
Domain: netw
Implicitly cleared (self-clearing): Yes
The alarm is raised when an SNMP
poll of the SysUpTimeAlarm object
on an NE fails, for example, because
of network congestion or because
the NE is too busy to respond. The
probable cause is an unreachable NE
SNMP agent on the NE. By default,
the 5620 SAM polls a managed NE
every two minutes. If a poll fails, the
alarm is raised.The 5620 SAM polls
the NE two minutes after the first
failure. If successive polls fail, the
5620 SAM raises the polling interval
for the NE by two minutes after each
failure to a maximum of 12 min. The
polling interval remains at 12 min
until the 5620 SAM receives a
response from the NE.The alarm
clears when the 5620 SAM receives a
response from the NE, and the
5620 SAM GUI icon that represents
the NE turns from red to green.
Name: SnmpTrapDropped
Type: communicationsAlarm (4)
Probable cause: snmpDaemonOverloaded
(141)
Severity: Warning
Object Type (class):
NetworkElement
Domain: netw
Implicitly cleared (self-clearing): No
The alarm is raised when the
5620 SAM receives a
tmnxTrapDropped notification from
an NE to indicate that the NE has
dropped a trap. As a result, the
5620 SAM resynchronizes the table
associated with the dropped trap.
Name:
StandbyCPMManagementConnectionDown
Type: communicationsAlarm (4)
Probable cause:
managementConnectionDown (111)
Severity: Critical
Object Type (class):
NodeDiscoveryControl
Domain: netw
Implicitly cleared (self-clearing): No
The alarm is raised when the
5620 SAM cannot reach a managed
NE using the ping function.
Name: StandbyServerStatus
Type: communicationsAlarm (4)
Probable cause: systemFailed (144)
Severity: Critical
Object Type (class): NmsSystem
Domain: netw
Implicitly cleared (self-clearing): No
The alarm is raised when the primary
5620 SAM main server cannot
communicate with the 5620 SAM
standby main server. The alarm
clears when communication between
the servers is restored.
Alarm Attributes Additional information
(8 of 11)
Aug 2010
AAAD
8.0 R4