Alcatel-Lucent 5620 Troubleshooting Manual page 107

Alarm
Name: liSourceSapChange
Type: ConfigurationAlarm (15)
Probable cause: tMirrorSourceSapChange
(430)
Name: liSourceSubscriberChange
Type: ConfigurationAlarm (15)
Probable cause: tMirrorSourceSubChange
(431)
(3 of 3)
Alarm
Name: MldDown
Type: ProtocolAlarm (1)
Probable cause: protocolDown (1)
Alarm
Name: BidirIpPathMonitorPathsDiverge
Type: topologyAlarm (34)
Probable cause: ipPathsDiverge (449)
(1 of 2)
Alcatel-Lucent 5620 Service Aware Manager, Release
3HE 05723 AAAD TQZZA Edition 01
Attributes
Severity: Warning
Object Type (class):
LISourceInterface
Domain: mirrorli
Implicitly cleared (self-clearing): No
Severity: Warning
Object Type (class):
LISourceSubscriberHost
Domain: mirrorli
Implicitly cleared (self-clearing): No
Table 3-39 Domain: mld
Attributes
Severity: Critical
Object Type (class): Site
Domain: mld
Implicitly cleared (self-clearing): Yes
Table 3-40 Domain: monpath
Attributes
Severity: Minor
Object Type (class):
BidirMonitoredIpPath
Domain: monpath
Implicitly cleared (self-clearing): Yes
8.0 R4 Aug 2010
Troubleshooting Guide
3 — Troubleshooting using network alarms
Additional information
The alarm is raised when a SAP that
is associated with LI is modified or
deleted.
The alarm is raised when a subscriber
that is associated with LI is modified
or deleted.
Additional information
The alarm is raised when an MLD site
has an Operational State other than
Up, and the Administrative State is
Up.
Additional information
The alarm is raised when the
5650 CPAM detects that the IP paths
of a bidirectional IP path monitor
diverge. The alarm clears when the
paths converge.This may occur 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 file.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.
3-65