3 — Troubleshooting using network alarms
3-90 Alcatel-Lucent 5620 Service Aware Manager, Release
Troubleshooting Guide 3HE 05723 TQZZA Edition 01
Name: ShamLinkNullPacketConfig
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 a null packet on a sham link
from an NE whose configuration
parameters conflict with the local NE
configuration parameters.
Name: ShamLinkRxBadPacket
Type: communicationsAlarm (4)
Probable causes:
• hello (47)
• dbDescript (48)
• lsReq (49)
• lsUpdate (50)
• lsAck (51)
• nullPacket (52)
Severity: Warning
Object Type (class): ShamLink
Domain: ospf
Implicitly cleared (self-clearing): No
The alarm is raised when an NE
cannot parse an OSPF packet that it
receives on a sham link.
Name: TxRetransmit
Type: communicationsAlarm (4)
Probable causes:
• hello (47)
• dbDescript (48)
• lsReq (49)
• lsUpdate (50)
• lsAck (51)
• nullPacket (52)
Severity: Warning
Object Type (class): ShamLink,
VirtualLink
Domain: ospf
Implicitly cleared (self-clearing): No
The alarm is raised when an NE
retransmits an OSPF packet on a
non-virtual interface. The alarm
information includes the NE ID of the
OSPF neighbor.
Name: VirtualLinkDbDescriptAuthFailure
Type: authenticationAlarm (14)
Probable causes:
• authTypeMismatch (45)
• authFailure (46)
Severity: Warning
Object Type (class): VirtualLink
Domain: ospf
Implicitly cleared (self-clearing): No
The alarm is raised when an NE
receives a dbDescript packet on a
virtual link from an NE whose
authentication key or authentication
type conflicts with the local NE
authentication key or authentication
type.
Alarm Attributes Additional information
(8 of 12)