Alcatel-Lucent 5620 Troubleshooting Manual page 87

Alarm name, ID, type, and probable
cause(s)
Alarm name:
BidirIpPathMonitorPathsDiverge
Alarm ID: 603
Type: topologyAlarm (34)
Probable cause: ipPathsDiverge (449)
Alarm name:
IpPathMonitorFailedRetryThresholdCrossed
Alarm ID: 400
Type: topologyAlarm (34)
Probable cause:
ipPathCouldNotBeDetermined (299)
Alarm name:
IpPathMonitorRetryAttemptsExhausted
Alarm ID: 401
Type: topologyAlarm (34)
Probable cause:
ipPathCouldNotBeDetermined (299)
Alcatel-Lucent 5620 Service Aware Manager, Release 6.1 R3
3HE 04244 AAAB Ed. 01
Table 3-31 Domain: monpath
Alarm severity, object type,
domain, and self-clearing attribute
Severity: Minor
Object Type (class):
BidirMonitoredIpPath
Domain: monpath
Self-clearing alarm raised: Yes
Severity: Major
Object Type (class): MonitoredIpPath
Domain: monpath
Self-clearing alarm raised: Yes
Severity: Major
Object Type (class): MonitoredIpPath
Domain: monpath
Self-clearing alarm raised: No
Troubleshooting Guide
3 — Troubleshooting network alarms
Additional information
The alarm is raised by the 5650 CPAM
when an IP path monitor cannot be
set up after the number of attempts
specified by the cpamManagedRoute
problematicThresholdAlarmAfter
value in the nms-server.xml tile.
The alarm is raised if the
cpamManagedRoute
problematicRetryStrategy value in
nms-server.xml is set to countdown.
The default
problematicRetryStrategy value of
reactive prevents the alarm from
being raised.
The alarm is raised by the 5650 CPAM
when an IP path monitor cannot be
set up after the number of attempts
specified by the cpamManagedRoute
problematicThresholdAlarmAfter
value in the nms-server.xml tile.
The alarm is raised if the
cpamManagedRoute
problematicRetryStrategy value in
nms-server.xml is set to countdown.
The default
problematicRetryStrategy value of
reactive prevents the alarm from
being raised.
The alarm is raised by the 5650 CPAM
when it stops trying to set up an IP
path monitor after the number of
attempts specified by the
cpamManagedRoute
problematicDeadAfter value in the
nms-server.xml tile.
The alarm is raised if the
cpamManagedRoute
problematicRetryStrategy value in
nms-server.xml is set to countdown.
The default
problematicRetryStrategy value of
reactive prevents the alarm from
being raised.
November 2008 3-49