Alcatel-Lucent 5620 - Page 113

3 — Troubleshooting using network alarms
Alcatel-Lucent 5620 Service Aware Manager, Release 3-71
3HE 05723 TQZZA Edition 01 Troubleshooting Guide
Table 3-44 Domain: multichassis
Alarm Attributes Additional information
Name: AsymmetricalConfig
Type: configurationAlarm (11)
Probable cause: asymmetricalConfig (226)
Severity: Major
Object Type (class):
MultiChassisPeer,
MultiChassisLagMember,
MultiChassisLag
Domain: multichassis
Implicitly cleared (self-clearing): Yes
The alarm is raised when there is a
peer configuration mismatch that
prevents MC operation.
Name: IncompleteConfig
Type: configurationAlarm (11)
Probable cause: incompleteConfig (225)
Severity: Major
Object Type (class):
MultiChassisSync,
MultiChassisLagMember
Domain: multichassis
Implicitly cleared (self-clearing): Yes
The alarm is raised when a peer
configuration cannot be found on the
peer NE.
Name: IncorrectEndPointPeerConfig
Type: configurationAlarm (11)
Probable cause: incompleteEPPeerConfig
(810)
Severity: Major
Object Type (class):
MultiChassisEndpoint
Domain: multichassis
Implicitly cleared (self-clearing): Yes
The alarm is raised when a peer
configuration cannot be found on the
peer NE.
Name: IncorrectPeerConfig
Type: configurationAlarm (11)
Probable cause: IncorrectPeerConfig (554)
Severity: Major
Object Type (class): Peer
Domain: multichassis
Implicitly cleared (self-clearing): Yes
The alarm is raised when an MC peer
does not exist, or when an MC peer
exists but the peer address is not the
address of a network interface on the
peer.
Name:
IncorrectPeerSynchronizationPortConfig
Type: configurationAlarm (11)
Probable cause:
IncorrectPeerSynchronizationPortConfig
(555)
Severity: Major
Object Type (class):
PeerSynchronizationPort
Domain: multichassis
Implicitly cleared (self-clearing): Yes
The alarm is raised when the peer
port does not exist, or when the peer
port exists but the synchronization
tags of the peers do not match.
Name:
IncorrectPeerSynchronizationPortEncapRan
geConfig
Type: configurationAlarm (11)
Probable cause:
IncorrectPeerSynchronizationPortEncapRan
geConfig (556)
Severity: Major
Object Type (class):
PeerSynchronizationPortEncapRange
Domain: multichassis
Implicitly cleared (self-clearing): Yes
The alarm is raised when an MC
synchronization group does not have
a configured VLAN range, or when
the VLAN ranges on the MC
synchronization peers do not match.
Name: LocalRncvOperDown
Type: redundancyAlarm (52)
Probable cause: localRncvDisconnected
(396)
Severity: Major
Object Type (class):
MultiChassisRingNode
Domain: multichassis
Implicitly cleared (self-clearing): Yes
The alarm is raised when the local
RNCV Operational State of a ring
node is other than Connected or
NotTested, which means that the
ring node is not connected to the
local MC ring group. The alarm clears
when the ring node enters the
Connected or NotTested state.
Name: MCLagDown
Type: equipmentAlarm (3)
Probable cause: mcLagDown (295)
Severity: Critical
Object Type (class):
MultiChassisLagPeerSpecifics
Domain: multichassis
Implicitly cleared (self-clearing): Yes
The alarm is raised when all ports in
an MC LAG are operationally down.
(1 of 2)
Aug 2010
AAAD
8.0 R4