Alcatel-Lucent 5620 Troubleshooting Manual page 113

Alarm
Name: AsymmetricalConfig
Type: configurationAlarm (11)
Probable cause: asymmetricalConfig (226)
Name: IncompleteConfig
Type: configurationAlarm (11)
Probable cause: incompleteConfig (225)
Name: IncorrectEndPointPeerConfig
Type: configurationAlarm (11)
Probable cause: incompleteEPPeerConfig
(810)
Name: IncorrectPeerConfig
Type: configurationAlarm (11)
Probable cause: IncorrectPeerConfig (554)
Name:
IncorrectPeerSynchronizationPortConfig
Type: configurationAlarm (11)
Probable cause:
IncorrectPeerSynchronizationPortConfig
(555)
Name:
IncorrectPeerSynchronizationPortEncapRan
geConfig
Type: configurationAlarm (11)
Probable cause:
IncorrectPeerSynchronizationPortEncapRan
geConfig (556)
Name: LocalRncvOperDown
Type: redundancyAlarm (52)
Probable cause: localRncvDisconnected
(396)
Name: MCLagDown
Type: equipmentAlarm (3)
Probable cause: mcLagDown (295)
(1 of 2)
Alcatel-Lucent 5620 Service Aware Manager, Release
3HE 05723 AAAD TQZZA Edition 01
Table 3-44 Domain: multichassis
Attributes
Severity: Major
Object Type (class):
MultiChassisPeer,
MultiChassisLagMember,
MultiChassisLag
Domain: multichassis
Implicitly cleared (self-clearing): Yes
Severity: Major
Object Type (class):
MultiChassisSync,
MultiChassisLagMember
Domain: multichassis
Implicitly cleared (self-clearing): Yes
Severity: Major
Object Type (class):
MultiChassisEndpoint
Domain: multichassis
Implicitly cleared (self-clearing): Yes
Severity: Major
Object Type (class): Peer
Domain: multichassis
Implicitly cleared (self-clearing): Yes
Severity: Major
Object Type (class):
PeerSynchronizationPort
Domain: multichassis
Implicitly cleared (self-clearing): Yes
Severity: Major
Object Type (class):
PeerSynchronizationPortEncapRange
Domain: multichassis
Implicitly cleared (self-clearing): Yes
Severity: Major
Object Type (class):
MultiChassisRingNode
Domain: multichassis
Implicitly cleared (self-clearing): Yes
Severity: Critical
Object Type (class):
MultiChassisLagPeerSpecifics
Domain: multichassis
Implicitly cleared (self-clearing): Yes
8.0 R4 Aug 2010
Troubleshooting Guide
3 — Troubleshooting using network alarms
Additional information
The alarm is raised when there is a
peer configuration mismatch that
prevents MC operation.
The alarm is raised when a peer
configuration cannot be found on the
peer NE.
The alarm is raised when a peer
configuration cannot be found on the
peer NE.
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.
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.
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.
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.
The alarm is raised when all ports in
an MC LAG are operationally down.
3-71