Alcatel-Lucent 5620 - Page 101

3 — Troubleshooting using network alarms
Alcatel-Lucent 5620 Service Aware Manager, Release 3-59
3HE 05723 TQZZA Edition 01 Troubleshooting Guide
Name: IncompleteConfig
Type: configurationAlarm (11)
Probable cause: incompleteConfig (225)
Severity: Major
Object Type (class): MultiChassisLag
Domain: lag
Implicitly cleared (self-clearing): Yes
The alarm is raised when an MC LAG
has fewer than two members.
Name: LagDown
Type: equipmentAlarm (3)
Probable cause: lagDown (17)
Severity: Critical
Object Type (class): Interface
Domain: lag
Implicitly cleared (self-clearing): Yes
The alarm is raised when all ports in
a LAG are operationally down.
Name: LinkAggMemberMisconfigured
Type: lnkaggAlarm (56)
Probable cause: lagMemberMisconfigured
(483)
Severity: Critical
Object Type (class): Interface
Domain: lag
Implicitly cleared (self-clearing): Yes
The alarm is raised when one or more
misconfigured LAG members are
detected, for example, when some
LAG members are in access mode and
some are in network mode.
Name: LinkAggModeMisconfigured
Type: lnkaggAlarm (56)
Probable cause: lagModeMisconfigured
(484)
Severity: Critical
Object Type (class): Interface
Domain: lag
Implicitly cleared (self-clearing): Yes
The alarm is raised when the LAG
mode differs from the mode of one
or more LAG members, for example,
when the LAG mode is access and the
LAG members are in network mode.
Name: LinkAggPortJoin
Type: lnkaggAlarm (56)
Probable cause: lagPortJoin (485)
Severity: Info
Object Type (class): Interface
Domain: lag
Implicitly cleared (self-clearing): No
The alarm is raised when a LAG port
joins a LAG by entering the attached
state.
Name: LinkAggPortLeave
Type: lnkaggAlarm (56)
Probable cause: lagPortLeave (486)
Severity: Info
Object Type (class): Interface
Domain: lag
Implicitly cleared (self-clearing): No
The alarm is raised when a LAG port
leaves a LAG by exiting the attached
state.
Name: LinkAggPortRemove
Type: lnkaggAlarm (56)
Probable cause: lagPortRemove (487)
Severity: Warning
Object Type (class): Interface
Domain: lag
Implicitly cleared (self-clearing): No
The alarm is raised when a LAG port
is removed from a LAG because of an
invalid configuration.
Name: MCLagDown
Type: equipmentAlarm (3)
Probable cause: mcLagDown (295)
Severity: Critical
Object Type (class):
MultiChassisLagSpecifics
Domain: lag
Implicitly cleared (self-clearing): Yes
The alarm is raised when all ports in
an MC LAG are operationally down.
Name: McLagSourceBMacLsbMisconfigured
Type: configurationAlarm (11)
Probable cause:
McLagSourceBMacLsbMisconfigured (551)
Severity: Major
Object Type (class): MultiChassisLag
Domain: lag
Implicitly cleared (self-clearing): Yes
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.
Alarm Attributes Additional information
(2 of 2)
Aug 2010
AAAD
8.0 R4