Alcatel-Lucent 5620 - Page 164

3 — Troubleshooting using network alarms
3-122 Alcatel-Lucent 5620 Service Aware Manager, Release
Troubleshooting Guide 3HE 05723 TQZZA Edition 01
Name: HashLabelMismatch
Type: configurationAlarm (11)
Probable cause: hashLabelMismatch (826)
Severity: Warning
Object Type (class): SdpBinding
Domain: svt
Implicitly cleared (self-clearing): Yes
The alarm is raised when an SDP
binding hash label is enabled and the
return SDP binding hash label is
disabled. The receiving site drops
the data packets as a result.
Name: IgmpSnpgGrpDroppedLimitExceeded
Type: SdpBindingAlarm (30)
Probable cause:
igmpSnpgGrpMaxNbrGrpsReached (292)
Severity: Warning
Object Type (class):
SdpBindingIgmpSnpgCfg
Domain: svt
Implicitly cleared (self-clearing): No
The alarm is raised when an IGMP
group is removed from an SDP
binding because the number of
allowed IGMP groups specified by
sdpBndIgmpSnpgCfgMaxNbrGrps is
reached.
Name: IgmpSnpgSrcDroppedLimitExceeded
Type: SdpBindingAlarm (30)
Probable cause:
igmpSnpgGrpMaxNbrSrcsReached (512)
Severity: Warning
Object Type (class):
SdpBindingIgmpSnpgCfg
Domain: svt
Implicitly cleared (self-clearing): No
The alarm is raised when an IGMP
source is removed from an SDP
binding because the number of
allowed IGMP sources specified by
sdpBndIgmpSnpgCfgMaxNbrSrcs is
reached.
Name: KeepAliveProblem
Type: oamAlarm (18)
Probable cause: keepAliveFailed (86)
Severity: Warning
Object Type (class): Tunnel
Domain: svt
Implicitly cleared (self-clearing): Yes
The alarm is raised when the
5620 SAM detects a keep-alive
protocol status of senderIdInvalid or
responderIdError.
Name: LabelProblem
Type: CircuitAlarm (17)
Probable cause: labelProblem (84)
Severity: Critical
Object Type (class): SdpBinding
Domain: svt
Implicitly cleared (self-clearing): Yes
The alarm is raised when an ingress
or an egress label is missing.
Name: McacPolicyDropped
Type: communicationsAlarm (4)
Probable cause:
igmpGroupOnSdpBindDropped (265)
Severity: Major
Object Type (class):
SdpBindingIgmpSnpgCfg
Domain: svt
Implicitly cleared (self-clearing): No
The alarm is raised when an IGMP
group is dropped because a multicast
CAC policy is applied to an SDP
binding.
Name: SdpBindingDown
Type: SdpBindingAlarm (30)
Probable cause: SdpBindingNotReady (166)
Severity: Critical
Object Type (class): SdpBinding
Domain: svt
Implicitly cleared (self-clearing): Yes
The alarm is raised when an SDP
binding has an Operational State
other than Up, and the
Administrative State is Up.
Name: SdpBindingMisconfigured
Type: SdpBindingAlarm (30)
Probable cause:
returnSdpBindingTypeMismatch (224)
Severity: Critical
Object Type (class): SdpBinding
Domain: svt
Implicitly cleared (self-clearing): Yes
The alarm is raised when the return
SDP binding type does not match the
originating SDP binding type, for
example, when the return SDP
binding is spoke and the originating
SDP binding is mesh.
Name: SdpBindingTunnelDown
Type: CircuitAlarm (17)
Probable cause: SdpTunnelNotReady (167)
Severity: Critical
Object Type (class): SdpBinding
Domain: svt
Implicitly cleared (self-clearing): Yes
The alarm is raised when an SDP
binding tunnel has an Operational
State other than Up, and the
Administrative State is Up.
Name: TunnelAdministrativelyDown
Type: pathAlarm (12)
Probable cause:
tunnelAdministrativelyDown (333)
Severity: Minor
Object Type (class): Tunnel
Domain: svt
Implicitly cleared (self-clearing): Yes
The alarm is raised when the
5620 SAM detects that a service
tunnel is administratively down.
Alarm Attributes Additional information
(2 of 3)
Aug 2010
AAAD
8.0 R4