Alcatel-Lucent 5620 Troubleshooting Manual page 114

3 — Troubleshooting using network alarms
Alarm
Name: McLagSourceBMacLsbMisconfigured
Type: configurationAlarm (11)
Probable cause:
McLagSourceBMacLsbMisconfigured (551)
Name: MCPeerEPDown
Type: equipmentAlarm (3)
Probable cause: MCPeerEPDown (811)
Name: MultiChassisRingDown
Type: redundancyAlarm (52)
Probable cause: ringDown (395)
Name: NoPeerMcRingFound
Type: configurationAlarm (11)
Probable cause: IncompleteConfig (557)
Name: RemoteRncvOperDown
Type: redundancyAlarm (52)
Probable cause: remoteRncvDisconnected
(397)
Name: tmnxMcSyncClientAlarm
Type: communicationsAlarm (4)
Probable cause:
locallyDeletedEntryInMCSyncDatabase (407)
(2 of 2)
Alarm
Name: NatIsaMemberSessionUsageHigh
Type: equipmentAlarm (3)
Probable cause: resourceFull (53)
Name: NatPlL2AwBlockUsageHigh
Type: equipmentAlarm (3)
Probable cause: resourceFull (53)
(1 of 2)
3-72
Attributes
Severity: Major
Object Type (class): MultiChassisLag
Domain: multichassis
Implicitly cleared (self-clearing): Yes
Severity: Critical
Object Type (class):
MultiChassisEndpoint
Domain: multichassis
Implicitly cleared (self-clearing): Yes
Severity: Major
Object Type (class): MultiChassisRing
Domain: multichassis
Implicitly cleared (self-clearing): Yes
Severity: Major
Object Type (class): MultiChassisRing
Domain: multichassis
Implicitly cleared (self-clearing): Yes
Severity: Major
Object Type (class):
MultiChassisRingNode
Domain: multichassis
Implicitly cleared (self-clearing): Yes
Severity: Warning
Object Type (class):
PeerSynchronizationProtocol
Domain: multichassis
Implicitly cleared (self-clearing): Yes
Table 3-45 Domain: nat
Attributes
Severity: Major
Object Type (class): IsaMda
Domain: nat
Implicitly cleared (self-clearing): Yes
Severity: Major
Object Type (class): NatPool
Domain: nat
Implicitly cleared (self-clearing): Yes
Alcatel-Lucent 5620 Service Aware Manager, Release
Aug 2010
Troubleshooting Guide
Additional information
The alarm is raised when the
5620 SAM detects a mismatch in the
last 16 bits of the source backbone
MAC address on the peer device.This
mismatch prevents PBB access dual
homing from operating.
The alarm is raised when an MC
endpoint is operationally down.
The alarm is raised when a MC ring
group Operational State is not in the
Connected state. The alarm is
cleared when the ring group enters
the Connected state.
The alarm is raised when the
5620 SAM cannot find the peer MC
ring.
The alarm is raised when the remote
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 a MC
synchronization database entry is
deleted locally.
Additional information
The alarm is raised when the session
usage of an ISA-NAT group member
reaches the high watermark. The
alarm clears when the session usage
reaches the low watermark.
The alarm is raised when the block
usage of an L2-aware NAT address
pool reaches the high watermark.
The alarm clears when the block
usage reaches the low watermark.
3HE 05723 AAAD TQZZA Edition 01
8.0 R4