Alcatel-Lucent 5620 Troubleshooting Manual page 109

Alarm
Name: LspPathDown
Type: pathAlarm (12)
Probable cause: lspPathDown (20)
Name: MissingHopConfiguration
Type: configurationAlarm (11)
Probable cause: MissingHopConfiguration
(252)
Name: MplsDown
Type: ProtocolAlarm (1)
Probable cause: protocolDown (1)
Name: MplsPathUpdateFailed
Type: pathAlarm (12)
Probable causes:
•
mbbRetryExceeded (804)
•
lspPathGoingDown (805)
•
startingHighPriMbb (806)
•
restartingMbb (807)
•
highPriMbbInProg (808)
Name: MplsResignalTimerExpired
Type: ProtocolAlarm (1)
Probable cause: resignalTimerExpired (833)
Name: PathReoptimized
Type: pathAlarm (12)
Probable cause: pathReoptimized (21)
Name: PathRerouted
Type: pathAlarm (12)
Probable cause: pathRerouted (22)
Name: S2LPathBypassTunnelActive
Type: pathAlarm (12)
Probable cause:
S2LPathReroutedToBypassTunnel (552)
Name: S2LPathDown
Type: pathAlarm (12)
Probable cause: S2LPathDown (553)
(2 of 3)
Alcatel-Lucent 5620 Service Aware Manager, Release
3HE 05723 AAAD TQZZA Edition 01
Attributes
Severity: Major
Object Type (class): LspPath
Domain: mpls
Implicitly cleared (self-clearing): Yes
Severity: Warning
Object Type (class): StaticLsp
Domain: mpls
Implicitly cleared (self-clearing): Yes
Severity: Critical
Object Type (class): Site
Domain: mpls
Implicitly cleared (self-clearing): Yes
Severity: Major
Object Type (class): LspPath
Domain: mpls
Implicitly cleared (self-clearing): Yes
Severity: Info
Object Type (class): Site
Domain: mpls
Implicitly cleared (self-clearing): No
Severity: Warning
Object Type (class): Tunnel
Domain: mpls
Implicitly cleared (self-clearing): No
Severity: Warning
Object Type (class): Tunnel
Domain: mpls
Implicitly cleared (self-clearing): No
Severity: Warning
Object Type (class): S2LPath
Domain: mpls
Implicitly cleared (self-clearing): Yes
Severity: Major
Object Type (class): S2LPath
Domain: mpls
Implicitly cleared (self-clearing): Yes
8.0 R4 Aug 2010
Troubleshooting Guide
3 — Troubleshooting using network alarms
Additional information
The alarm is raised when an LSP path
is operationally down.
The alarm is raised when a static LSP
is created without hops.
The alarm is raised when an MPLS
site has an Operational State other
than Up, and the Administrative
State is Up.
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.
The alarm is raised when an MPLS
instance resignal timer expires.
The alarm is raised when an MPLS
path generates an
mplsTunnelReoptimized trap.
The alarm is raised when an MPLS
path generates an
mplsTunnelRerouted trap.
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.
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.
3-67