Alcatel-Lucent 5620 Troubleshooting Manual page 88

3 — Troubleshooting network alarms
Alarm name, ID, type, and probable
cause(s)
Alarm name: LastHopIncorrectLabelAction
Alarm ID: 352
Type: configurationAlarm (11)
Probable cause:
LabelActionIsNotPopOnLastHop (254)
Alarm name:
LastHopNotMatchingDestination
Alarm ID: 351
Type: configurationAlarm (11)
Probable cause:
LastHopNotMatchingDestination (253)
Alarm name: LspDown
Alarm ID: 25
Type: pathAlarm (12)
Probable cause: lspDown (19)
Alarm name: LspPathBypassTunnelActive
Alarm ID: 264
Type: pathAlarm (12)
Probable cause:
LspPathReroutedToBypassTunnel (197)
Alarm name: LspPathDown
Alarm ID: 26
Type: pathAlarm (12)
Probable cause: lspPathDown (20)
Alarm name: MissingHopConfiguration
Alarm ID: 350
Type: configurationAlarm (11)
Probable cause: MissingHopConfiguration
(252)
Alarm name: MplsDown
Alarm ID: 27
Type: ProtocolAlarm (1)
Probable cause: protocolDown (1)
(1 of 2)
3-50
Table 3-32 Domain: mpls
Alarm severity, object type,
domain, and self-clearing attribute
Severity: Warning
Object Type (class): StaticLsp
Domain: mpls
Self-clearing alarm raised: Yes
Severity: Warning
Object Type (class): StaticLsp
Domain: mpls
Self-clearing alarm raised: Yes
Severity: Critical
Object Type (class): Lsp
Domain: mpls
Self-clearing alarm raised: Yes
Severity: Warning
Object Type (class): LspPath
Domain: mpls
Self-clearing alarm raised: Yes
Severity: Major
Object Type (class): LspPath
Domain: mpls
Self-clearing alarm raised: Yes
Severity: Warning
Object Type (class): StaticLsp
Domain: mpls
Self-clearing alarm raised: Yes
Severity: Critical
Object Type (class): Site
Domain: mpls
Self-clearing alarm raised: Yes
November 2008 Alcatel-Lucent 5620 Service Aware Manager, Release 6.1 R3
Additional information
—
—
The alarm is raised when the
operational state of the LSP is down,
but the administrative state is up.
Verify the status of the underlying
ports as a probable cause.
For dynamic LSP signaling, ensure
that one of the two supported
signaling protocols, either LDP or
RSVP, is enabled on the interfaces
that support the dynamic creation of
LSPs.
For static LSPs, if there is no ARP
entry for the next-hop IP address of
the LSP, the LSP is set to
operationally down.
Ensure that at least one MPLS
interface is configured on the
device. Ensure that MPLS is enabled
on all devices that are part of an LSP.
When an LSP primary path is
rerouted to the bypass tunnel, the
alarm is raised.
When the primary path is returned to
the original tunnel and the actual
hop returns to the primary path, the
alarm is cleared.
—
—
—
Troubleshooting Guide 3HE 04244 AAAB Ed. 01