Alcatel-Lucent 5620 Troubleshooting Manual page 157

Alarm
Name: BfdSessionDown
Type: bfdSessionAlarm (46)
Probable cause: bfdSessionDown (346)
Name: BfdSessionMissing
Type: bfdSessionAlarm (46)
Probable cause: bfdSessionMissing (345)
Name: EndpointActiveObjectChanged
Type: redundancyAlarm (52)
Probable causes:
•
RedundancySwitchover (317)
•
ForceSwitchover (318)
Name: FrameSizeProblem
Type: configurationAlarm (11)
Probable cause: frameSizeProblem (33)
Name: GroupInterfaceDown
Type: GroupInterfaceAlarm (44)
Probable cause: interfaceDown (32)
Name: InterfaceDown
Type: configurationAlarm (11)
Probable cause: interfaceDown (32)
Name: SapDHCPLeaseEntriesExceeded
Type: communicationsAlarm (4)
Probable cause:
sapDHCPLeaseEntriesExceeded (290)
Name: sapDHCPProxyServerError
Type: communicationsAlarm (4)
Probable cause: UnableProxyDHCPRequest
(291)
Name: ServiceSiteDown
Type: serviceAlarm (16)
Probable cause: siteDown (83)
Name: SubscriberInterfaceDown
Type: SubscriberInterfaceAlarm (43)
Probable cause: interfaceDown (32)
(2 of 3)
Alcatel-Lucent 5620 Service Aware Manager, Release
3HE 05723 AAAD TQZZA Edition 01
Attributes
Severity: Warning
Object Type (class):
L3AccessInterface
Domain: service
Implicitly cleared (self-clearing): Yes
Severity: Warning
Object Type (class):
L3AccessInterface
Domain: service
Implicitly cleared (self-clearing): Yes
Severity: Warning
Object Type (class): Endpoint
Domain: service
Implicitly cleared (self-clearing): No
Severity: Warning
Object Type (class): Service
Domain: service
Implicitly cleared (self-clearing): Yes
Severity: Critical
Object Type (class): GroupInterface
Domain: service
Implicitly cleared (self-clearing): Yes
Severity: Major
Object Type (class):
RedundantInterface
Domain: service
Implicitly cleared (self-clearing): Yes
Severity: Major
Object Type (class): AccessInterface
Domain: service
Implicitly cleared (self-clearing): No
Severity: Major
Object Type (class): AccessInterface
Domain: service
Implicitly cleared (self-clearing): No
Severity: Critical
Object Type (class): Site
Domain: service
Implicitly cleared (self-clearing): Yes
Severity: Critical
Object Type (class):
SubscriberInterface
Domain: service
Implicitly cleared (self-clearing): Yes
8.0 R4 Aug 2010
Troubleshooting Guide
3 — Troubleshooting using network alarms
Additional information
The alarm is raised when a BFD
session is operationally down.
The alarm is raised when a previously
present BFD session is absent.
The alarm is raised when an
automatic or manual endpoint
switchover occurs.
The alarm is raised when a
provisioned MTU size value is greater
than the supported MTU size value.
The alarm is raised when the
5620 SAM detects that a group
interface is operationally down. The
alarm clears when the group
interface is operationally up.
The alarm is raised when the
5620 SAM detects that a redundant
interface is operationally down.
The alarm is raised when the number
of DHCP lease-state entries on a SAP
reaches the configured maximum
value. This value is defined by
sapTlsDhcpLeasePopulate for a TLS
VLAN service, and by
vRtrIfDHCPLeasePopulate for an IES
or VPRN service.
The alarm is raised when the
5620 SAM is unable to proxy a DHCP
request.
The alarm is raised when all SAPs on
a site are operationally down, or
when the service tunnels for the site
are operationally down.
The alarm is raised when a subscriber
interface is operationally down. The
alarm clears when the subscriber
interface is operationally up.
3-115