Alcatel-Lucent 5620 - Page 131

3 — Troubleshooting using network alarms
Alcatel-Lucent 5620 Service Aware Manager, Release 3-89
3HE 05723 TQZZA Edition 01 Troubleshooting Guide
Name: ShamLinkLsReqConfig
Type: configurationAlarm (11)
Probable causes:
• badVersion (35)
• areaMismatch (36)
• unknownNbmaNbr (37)
• unknownVirtualNbr (38)
• netMaskMismatch (39)
• helloIntervalMismatch (40)
• deadIntervalMismatch (41)
• optionMismatch (42)
• mtuMismatch (43)
• noError (44)
• duplicateRouterId (168)
• ifAdminDown (834)
• ifPassive (835)
Severity: Warning
Object Type (class): ShamLink
Domain: ospf
Implicitly cleared (self-clearing): No
The alarm is raised when an NE
receives an lsReq packet on a sham
link from an NE whose configuration
parameters conflict with the local NE
configuration parameters.
Name: ShamLinkLsUpdateAuthFailure
Type: authenticationAlarm (14)
Probable causes:
• authTypeMismatch (45)
• authFailure (46)
Severity: Warning
Object Type (class): ShamLink
Domain: ospf
Implicitly cleared (self-clearing): No
The alarm is raised when an NE
receives an lsUpdate packet on a
sham link from an NE whose
authentication key or authentication
type conflicts with the local NE
authentication key or authentication
type.
Name: ShamLinkLsUpdateConfig
Type: configurationAlarm (11)
Probable causes:
• badVersion (35)
• areaMismatch (36)
• unknownNbmaNbr (37)
• unknownVirtualNbr (38)
• netMaskMismatch (39)
• helloIntervalMismatch (40)
• deadIntervalMismatch (41)
• optionMismatch (42)
• mtuMismatch (43)
• noError (44)
• duplicateRouterId (168)
• ifAdminDown (834)
• ifPassive (835)
Severity: Warning
Object Type (class): ShamLink
Domain: ospf
Implicitly cleared (self-clearing): No
The alarm is raised when an NE
receives an lsUpdate packet on a
sham link from an NE whose
configuration parameters conflict
with the local NE configuration
parameters.
Name: ShamLinkNullPacketAuthFailure
Type: authenticationAlarm (14)
Probable causes:
• authTypeMismatch (45)
• authFailure (46)
Severity: Warning
Object Type (class): ShamLink
Domain: ospf
Implicitly cleared (self-clearing): No
The alarm is raised when an NE
receives a null packet on a sham link
from an NE whose authentication key
or authentication type conflicts with
the local NE authentication key or
authentication type.
Alarm Attributes Additional information
(7 of 12)
Aug 2010
AAAD
8.0 R4