Alcatel-Lucent 5620 Troubleshooting Manual page 129

Alarm name, ID, type, and probable
cause(s)
Alarm name:
IgmpSnpgGrpDroppedLimitExceeded
Alarm ID: 392
Type: SdpBindingAlarm (30)
Probable cause:
igmpSnpgGrpMaxNbrGrpsReached (292)
Alarm name: KeepAliveProblem
Alarm ID: 100
Type: oamAlarm (18)
Probable cause: keepAliveFailed (86)
Alarm name: LabelProblem
Alarm ID: 98
Type: CircuitAlarm (17)
Probable cause: labelProblem (84)
Alarm name: SdpBindingDown
Alarm ID: 221
Type: SdpBindingAlarm (30)
Probable cause: SdpBindingNotReady (166)
Alarm name: SdpBindingMisconfigured
Alarm ID: 293
Type: SdpBindingAlarm (30)
Probable cause:
returnSdpBindingTypeMismatch (224)
Alarm name: SdpBindingTunnelDown
Alarm ID: 222
Type: CircuitAlarm (17)
Probable cause: SdpTunnelNotReady (167)
Alarm name: TunnelOverbooked
Alarm ID: 590
Type: resourceAlarm (28)
Probable cause: tunnelOverbooked (442)
Alcatel-Lucent 5620 Service Aware Manager, Release 6.1 R3
3HE 04244 AAAB Ed. 01
Table 3-57 Domain: svt
Alarm severity, object type,
domain, and self-clearing attribute
Severity: Warning
Object Type (class):
SdpBindingIgmpSnpgCfg
Domain: svt
Self-clearing alarm raised: No
Severity: Warning
Object Type (class): Tunnel
Domain: svt
Self-clearing alarm raised: Yes
Severity: Critical
Object Type (class): SdpBinding
Domain: svt
Self-clearing alarm raised: Yes
Severity: Critical
Object Type (class): SdpBinding
Domain: svt
Self-clearing alarm raised: Yes
Severity: Critical
Object Type (class): SdpBinding
Domain: svt
Self-clearing alarm raised: Yes
Severity: Critical
Object Type (class): SdpBinding
Domain: svt
Self-clearing alarm raised: Yes
Severity: Warning
Object Type (class): Tunnel
Domain: svt
Self-clearing alarm raised: No
Troubleshooting Guide
3 — Troubleshooting network alarms
Additional information
The alarm is raised when an IGMP
group is removed from an SDP
binding because a configurable
maximum number of IGMP groups is
reached.
—
The alarm is raised when either an
ingress or an egress label is missing.
The alarm is raised when the SDP
binding administrative state is up
and the SDP binding operational
state is not up.
The alarm is raised when the return
SDP binding type does not match the
type of the originating SDP binding,
for example, when the return SDP
binding is spoke and the originating
SDP binding is mesh.
The alarm is raised when the
operational state of the SDP binding
is sdpNotReady (the SDP signaling
session is down) or sdpDown (the SDP
is not operationally up). Possible
causes are:
•
The underlying LSP is
operationally down.
•
The LDP sessions are down.
The alarm was formerly called
CircuitDown.
The alarm is raised when the
bandwidth that has been allocated to
the SDP bindings indicated by
sdpBookedBandwidth exceeds
sdpMaxBookableBandwidth.
November 2008 3-91