Alcatel-Lucent 5620 Troubleshooting Manual page 129

Alarm
Name: OspfIfTxRetransmit
Type: communicationsAlarm (4)
Probable causes:
•
hello (47)
•
dbDescript (48)
•
lsReq (49)
•
lsUpdate (50)
•
lsAck (51)
•
nullPacket (52)
Name: OspfInterfaceDown
Type: OspfInterfaceDown (24)
Probable cause: OspfInterfaceDown (112)
Name: ShamLinkDbDescriptAuthFailure
Type: authenticationAlarm (14)
Probable causes:
•
authTypeMismatch (45)
•
authFailure (46)
Name: ShamLinkDbDescriptConfig
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)
Name: ShamLinkDown
Type: ShamLinkAlarm (57)
Probable cause: ShamLinkDown (492)
Name: ShamLinkHelloAuthFailure
Type: authenticationAlarm (14)
Probable causes:
•
authTypeMismatch (45)
•
authFailure (46)
(5 of 12)
Alcatel-Lucent 5620 Service Aware Manager, Release
3HE 05723 AAAD TQZZA Edition 01
Attributes
Severity: Warning
Object Type (class): Interface
Domain: ospf
Implicitly cleared (self-clearing): No
Severity: Warning
Object Type (class): Interface
Domain: ospf
Implicitly cleared (self-clearing): Yes
Severity: Warning
Object Type (class): ShamLink
Domain: ospf
Implicitly cleared (self-clearing): No
Severity: Warning
Object Type (class): ShamLink
Domain: ospf
Implicitly cleared (self-clearing): No
Severity: Critical
Object Type (class): ShamLink
Domain: ospf
Implicitly cleared (self-clearing): Yes
Severity: Warning
Object Type (class): ShamLink
Domain: ospf
Implicitly cleared (self-clearing): No
8.0 R4 Aug 2010
Troubleshooting Guide
3 — Troubleshooting using network alarms
Additional information
The alarm is raised when an NE
retransmits an OSPF packet. The
alarm information includes the NE ID
of the OSPF neighbor.The alarm is
not raised against a Release 4.0 or
later NE.
The alarm is raised when an OSPF
interface is operationally down.
The alarm is raised when an NE
receives a dbDescript packet on a
sham link from an NE whose
authentication key or authentication
type conflicts with the local NE
authentication key or authentication
type.
The alarm is raised when an NE
receives a dbDescript packet on a
sham link from an NE whose
configuration parameters conflict
with the local NE configuration
parameters.
The alarm is raised when a sham link
is operationally down.
The alarm is raised when an NE
receives a hello packet on a sham
link from an NE whose authentication
key or authentication type conflicts
with the local NE authentication key
or authentication type.
3-87