Alcatel-Lucent 5620 Troubleshooting Manual page 95

Alarm name, ID, type, and probable
cause(s)
Alarm name: PollerProblem
Alarm ID: 31
Type: communicationsAlarm (4)
Probable cause: resyncFailed (24)
Alarm name: RamFreeSpaceExceeded
Alarm ID: 359
Type: thresholdCrossed (6)
Probable cause: thresholdCrossed (12)
Alarm name: RedAlarmThresholdReached
Alarm ID: 241
Type: communicationsAlarm (4)
Probable cause: tooManyAlarms (182)
Alarm name: RedundancySwitchover
Alarm ID: 181
Type: equipmentAlarm (3)
Probable cause: redundancySwitchover
(143)
Alarm name: SnmpAuthenticationFailure
Alarm ID: 176
Type: authenticationAlarm (14)
Probable cause: authFailure (46)
Alarm name: SnmpDaemonProblem
Alarm ID: 175
Type: communicationsAlarm (4)
Probable cause: snmpDaemonError (138)
Alarm name: SnmpDown
Alarm ID: 410
Type: communicationsAlarm (4)
Probable cause: snmpDown (306)
(5 of 8)
Alcatel-Lucent 5620 Service Aware Manager, Release 6.1 R3
3HE 04244 AAAB Ed. 01
Alarm severity, object type,
domain, and self-clearing attribute
Severity: Warning
Object Type (class):
NetworkElement
Domain: netw
Self-clearing alarm raised: Yes
Severity: Warning
Object Type (class):
NetworkElement
Domain: netw
Self-clearing alarm raised: No
Severity: Critical
Object Type (class): NmsSystem
Domain: netw
Self-clearing alarm raised: No
Severity: Warning
Object Type (class):
NetworkElement
Domain: netw
Self-clearing alarm raised: No
Severity: Warning
Object Type (class):
NetworkElement
Domain: netw
Self-clearing alarm raised: No
Severity: Critical
Object Type (class):
NetworkElement
Domain: netw
Self-clearing alarm raised: No
Severity: Critical
Object Type (class):
NetworkElement
Domain: netw
Self-clearing alarm raised: No
Troubleshooting Guide
3 — Troubleshooting network alarms
Additional information
Unable to poll a network object.
Possible causes include: intermittent
or no IP connectivity to the network
object, incorrect SNMP security
parameters, or SNMP is disabled on
the router.
Non-5620 SAM related polling
problems may include physical
cabling from the NMS domain to the
managed devices, and NIC card
issues.
The alarm is raised when a 7250 SAS
device sends the following trap:
BATM-SYS-MON-MIB.ramFreeSpaceEx
ceeded
A RAM utilization threshold is
configurable on the device.
The number of outstanding alarms
has reached the critical threshold,
and alarms are being discarded to
keep below system limits.
—
—
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 device sends the wrong
object in response to an SMNP
get or get-next request.
•
The 5620 SAM receives the
following trap from a managed
device:
TIMETRA-SYSTEM-MIB.tmnxSnmp
dError
—
November 2008 3-57