Alcatel-Lucent 5620 Troubleshooting Manual page 121

Alarm name, ID, type, and probable
cause(s)
Alarm name: AccessInterfaceDown
Alarm ID: 249
Type: AccessInterfaceAlarm (32)
Probable cause: interfaceDown (32)
Alarm name: AddressMisconfiguration
Alarm ID: 591
Type: configurationAlarm (11)
Probable causes:
•
EpipeBackboneMacAddressMismatch
(444)
•
BVplsSourceMacAddressDuplicate (445)
Alarm name: BfdSessionDown
Alarm ID: 439
Type: bfdSessionAlarm (46)
Probable cause: bfdSessionDown (346)
Alarm name: BfdSessionMissing
Alarm ID: 438
Type: bfdSessionAlarm (46)
Probable cause: bfdSessionMissing (345)
Alarm name: EndpointActiveObjectChanged
Alarm ID: 437
Type: RedudancyAlarm (42)
Probable causes:
•
RedundancySwitchover (317)
•
ForceSwitchover (318)
Alarm name: FrameSizeProblem
Alarm ID: 37
Type: configurationAlarm (11)
Probable cause: frameSizeProblem (33)
Alarm name: GroupInterfaceDown
Alarm ID: 441
Type: GroupInterfaceAlarm (44)
Probable cause: interfaceDown (32)
(1 of 3)
Alcatel-Lucent 5620 Service Aware Manager, Release 6.1 R3
3HE 04244 AAAB Ed. 01
Table 3-51 Domain: service
Alarm severity, object type,
domain, and self-clearing attribute
Severity: Critical
Object Type (class): AccessInterface
Domain: service
Self-clearing alarm raised: Yes
Severity: Major
Object Type (class): Service
Domain: service
Self-clearing alarm raised: Yes
Severity: Warning
Object Type (class):
L3AccessInterface
Domain: service
Self-clearing alarm raised: Yes
Severity: Warning
Object Type (class):
L3AccessInterface
Domain: service
Self-clearing alarm raised: Yes
Severity: Warning
Object Type (class): Endpoint
Domain: service
Self-clearing alarm raised: No
Severity: Warning
Object Type (class): Service
Domain: service
Self-clearing alarm raised: Yes
Severity: Critical
Object Type (class): GroupInterface
Domain: service
Self-clearing alarm raised: Yes
Troubleshooting Guide
3 — Troubleshooting network alarms
Additional information
The alarm is raised when an L2 or L3
interface operational state is down
and the administrative state of the
site for the interface is up.
This alarm is not raised against an L2
access interface that is in
multi-chassis ring standby state.
This alarm is issued when addresses
are misconfigured for the service.
The probable cause of
EpipeBackboneMacAddressMismatch
happens when backbone destination
MAC address are misconfigured on
EPIPE services. The backbone
destination MAC address should be
same as the backbone source MAC
address of BVPLS site on the
destination node. The probable
cause of
BVplsSourceMacAddressDuplicate
happens when there are duplicated
backbone source MAC address
configured in one B-VPLS service.
—
—
The alarm is raised when a
switchover occurs on an endpoint
because of a failure or because of a
manually forced switchover.
The alarm is raised when the
provisioned MTU value is greater
than the actual MTU value.
The alarm is raised when a group
interface becomes operationally
down. The alarm is cleared when the
group interface becomes
operationally up.
November 2008 3-83