Alcatel-Lucent 5620 - Page 108

3 — Troubleshooting using network alarms
3-66 Alcatel-Lucent 5620 Service Aware Manager, Release
Troubleshooting Guide 3HE 05723 TQZZA Edition 01
Table 3-41 Domain: mpls
Name:
IpPathMonitorFailedRetryThresholdCrossed
Type: topologyAlarm (34)
Probable cause:
ipPathCouldNotBeDetermined (299)
Severity: Major
Object Type (class): MonitoredIpPath
Domain: monpath
Implicitly cleared (self-clearing): Yes
The alarm is raised when the
5650 CPAM cannot set up an IP path
monitor 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.
Name:
IpPathMonitorRetryAttemptsExhausted
Type: topologyAlarm (34)
Probable cause:
ipPathCouldNotBeDetermined (299)
Severity: Major
Object Type (class): MonitoredIpPath
Domain: monpath
Implicitly cleared (self-clearing): No
The alarm is raised when the
5650 CPAM 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 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.
Alarm Attributes Additional information
Name: LastHopIncorrectLabelAction
Type: configurationAlarm (11)
Probable cause:
LabelActionIsNotPopOnLastHop (254)
Severity: Warning
Object Type (class): StaticLsp
Domain: mpls
Implicitly cleared (self-clearing): Yes
The alarm is raised when the label
action specified for the last hop in a
static LSP is not a pop action.
Name: LastHopNotMatchingDestination
Type: configurationAlarm (11)
Probable cause:
LastHopNotMatchingDestination (253)
Severity: Warning
Object Type (class): StaticLsp
Domain: mpls
Implicitly cleared (self-clearing): Yes
The alarm is raised when the last hop
in a static LSP is not the destination.
Name: LspDown
Type: pathAlarm (12)
Probable cause: lspDown (19)
Severity: Critical
Object Type (class): Lsp
Domain: mpls
Implicitly cleared (self-clearing): Yes
The alarm is raised when the
Operational State of an LSP is Down,
but the Administrative State is Up.
Name: LspPathBypassTunnelActive
Type: pathAlarm (12)
Probable cause:
LspPathReroutedToBypassTunnel (197)
Severity: Warning
Object Type (class): LspPath
Domain: mpls
Implicitly cleared (self-clearing): Yes
The alarm is raised when an LSP
primary path is rerouted to the
bypass tunnel. The alarm clears
when the primary path returns to the
original tunnel and the actual hop
returns to the primary path.
(1 of 3)
Alarm Attributes Additional information
(2 of 2)
Aug 2010
AAAD
8.0 R4