Alcatel-Lucent 5620 Troubleshooting Manual page 101

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