Alcatel-Lucent 5620 - Page 109

3 — Troubleshooting using network alarms
Alcatel-Lucent 5620 Service Aware Manager, Release 3-67
3HE 05723 TQZZA Edition 01 Troubleshooting Guide
Name: LspPathDown
Type: pathAlarm (12)
Probable cause: lspPathDown (20)
Severity: Major
Object Type (class): LspPath
Domain: mpls
Implicitly cleared (self-clearing): Yes
The alarm is raised when an LSP path
is operationally down.
Name: MissingHopConfiguration
Type: configurationAlarm (11)
Probable cause: MissingHopConfiguration
(252)
Severity: Warning
Object Type (class): StaticLsp
Domain: mpls
Implicitly cleared (self-clearing): Yes
The alarm is raised when a static LSP
is created without hops.
Name: MplsDown
Type: ProtocolAlarm (1)
Probable cause: protocolDown (1)
Severity: Critical
Object Type (class): Site
Domain: mpls
Implicitly cleared (self-clearing): Yes
The alarm is raised when an MPLS
site has an Operational State other
than Up, and the Administrative
State is Up.
Name: MplsPathUpdateFailed
Type: pathAlarm (12)
Probable causes:
• mbbRetryExceeded (804)
• lspPathGoingDown (805)
• startingHighPriMbb (806)
• restartingMbb (807)
• highPriMbbInProg (808)
Severity: Major
Object Type (class): LspPath
Domain: mpls
Implicitly cleared (self-clearing): Yes
The alarm is raised when an MPLS
path update fails because of an MBB
problem. The alarm clears when the
MBB status changes to Successful.
Name: MplsResignalTimerExpired
Type: ProtocolAlarm (1)
Probable cause: resignalTimerExpired (833)
Severity: Info
Object Type (class): Site
Domain: mpls
Implicitly cleared (self-clearing): No
The alarm is raised when an MPLS
instance resignal timer expires.
Name: PathReoptimized
Type: pathAlarm (12)
Probable cause: pathReoptimized (21)
Severity: Warning
Object Type (class): Tunnel
Domain: mpls
Implicitly cleared (self-clearing): No
The alarm is raised when an MPLS
path generates an
mplsTunnelReoptimized trap.
Name: PathRerouted
Type: pathAlarm (12)
Probable cause: pathRerouted (22)
Severity: Warning
Object Type (class): Tunnel
Domain: mpls
Implicitly cleared (self-clearing): No
The alarm is raised when an MPLS
path generates an
mplsTunnelRerouted trap.
Name: S2LPathBypassTunnelActive
Type: pathAlarm (12)
Probable cause:
S2LPathReroutedToBypassTunnel (552)
Severity: Warning
Object Type (class): S2LPath
Domain: mpls
Implicitly cleared (self-clearing): Yes
The alarm is raised when the bypass
tunnel in an S2L path becomes
active.The alarm clears when the
bypass tunnel is no longer active, for
example, because a primary tunnel
failure is resolved or a new path is
established.
Name: S2LPathDown
Type: pathAlarm (12)
Probable cause: S2LPathDown (553)
Severity: Major
Object Type (class): S2LPath
Domain: mpls
Implicitly cleared (self-clearing): Yes
The alarm is raised when the S2L
path Administrative State is Up and
the Operational State is not Up.The
alarm clears when the S2L path
Operational State changes to Up or
the Administrative State changes to
Down.
Alarm Attributes Additional information
(2 of 3)
Aug 2010
AAAD
8.0 R4