Alcatel-Lucent 5620 Troubleshooting Manual page 122

3 — Troubleshooting network alarms
Alarm name, ID, type, and probable
cause(s)
Alarm name: InterfaceDown
Alarm ID: 36
Type: configurationAlarm (11)
Probable cause: interfaceDown (32)
Alarm name:
SapDHCPLeaseEntriesExceeded
Alarm ID: 386
Type: communicationsAlarm (4)
Probable cause:
sapDHCPLeaseEntriesExceeded (290)
Alarm name: sapDHCPProxyServerError
Alarm ID: 387
Type: communicationsAlarm (4)
Probable cause: UnableProxyDHCPRequest
(291)
Alarm name: ServiceCustomerInconsistent
Alarm ID: 242
Type: configurationAlarm (11)
Probable cause:
ServiceCustomerInconsistent (175)
Alarm name: ServiceSiteDown
Alarm ID: 97
Type: serviceAlarm (16)
Probable cause: siteDown (83)
Alarm name: SubscriberInterfaceDown
Alarm ID: 440
Type: SubscriberInterfaceAlarm (43)
Probable cause: interfaceDown (32)
Alarm name: TodSuiteAssignmentFailure
Alarm ID: 312
Type: todSuiteAlarm (35)
Probable cause:
configConflictOrResourceFull (274)
(2 of 3)
3-84
Alarm severity, object type,
domain, and self-clearing attribute
Severity: Major
Object Type (class):
RedundantInterface
Domain: service
Self-clearing alarm raised: Yes
Severity: Major
Object Type (class): AccessInterface
Domain: service
Self-clearing alarm raised: No
Severity: Major
Object Type (class): AccessInterface
Domain: service
Self-clearing alarm raised: No
Severity: Critical
Object Type (class): Service
Domain: service
Self-clearing alarm raised: Yes
Severity: Critical
Object Type (class): Site
Domain: service
Self-clearing alarm raised: Yes
Severity: Critical
Object Type (class):
SubscriberInterface
Domain: service
Self-clearing alarm raised: Yes
Severity: Minor
Object Type (class): AccessInterface
Domain: service
Self-clearing alarm raised: No
November 2008 Alcatel-Lucent 5620 Service Aware Manager, Release 6.1 R3
Additional information
—
The alarm is raised when the number
of DHCP lease-state entries on a SAP
reaches the configured maximum
value.
The alarm is raised when the
5620 SAM is unable to proxy a DHCP
request.
—
All SAPs on the site are operationally
down, or the service tunnels to the
site are operationally down.
The alarm is raised when a subscriber
interface becomes operationally
down. The alarm is cleared when the
subscriber interface becomes
operationally up.
The alarm is raised when a Time of
Day suite cannot be assigned to an
aggregation scheduler, or an L2 or L3
access interface, because of a
configuration conflict or a lack of
resources.
The alarm does not apply to SAPs.
Troubleshooting Guide 3HE 04244 AAAB Ed. 01