Alcatel-Lucent 5620 Troubleshooting Manual page 91

Alarm name, ID, type, and probable
cause(s)
Alarm name: ActivitySwitch
Alarm ID: 182
Type: communicationsAlarm (4)
Probable cause: systemFailed (144)
Alarm name:
BootConfigFailScriptNotAccesible
Alarm ID: 543
Type: configurationAlarm (11)
Probable cause:
bootConfigFailScriptNotAccesible (416)
Alarm name:
BootConfigOKScriptNotAccesible
Alarm ID: 544
Type: configurationAlarm (11)
Probable cause:
bootConfigOKScriptNotAccesible (417)
Alarm name: BootParametersMisconfigured
Alarm ID: 35
Type: configurationAlarm (11)
Probable causes:
•
persistentIndexFailure (30)
•
configFileBootFailure (31)
Alarm name: CliCommandFailure
Alarm ID: 402
Type: communicationsAlarm (4)
Probable cause: cliCommandFailure (300)
Alarm name: CliConnectionProblem
Alarm ID: 299
Type: communicationsAlarm (4)
Probable cause: cliConnectionProblem (230)
Alarm name: CliLoginFailed
Alarm ID: 298
Type: communicationsAlarm (4)
Probable cause: cliLoginFailed (229)
Alarm name: CpuUtilizationExceeded
Alarm ID: 358
Type: thresholdCrossed (6)
Probable cause: thresholdCrossed (12)
(1 of 8)
Alcatel-Lucent 5620 Service Aware Manager, Release 6.1 R3
3HE 04244 AAAB Ed. 01
Table 3-35 Domain: netw
Alarm severity, object type,
domain, and self-clearing attribute
Severity: Critical
Object Type (class): NmsSystem
Domain: netw
Self-clearing alarm raised: No
Severity: Major
Object Type (class):
NetworkElement
Domain: netw
Self-clearing alarm raised: No
Severity: Major
Object Type (class):
NetworkElement
Domain: netw
Self-clearing alarm raised: No
Severity: Critical
Object Type (class):
NetworkElement
Domain: netw
Self-clearing alarm raised: Yes
Severity: Warning
Object Type (class):
NetworkElement
Domain: netw
Self-clearing alarm raised: No
Severity: Warning
Object Type (class):
NetworkElement
Domain: netw
Self-clearing alarm raised: No
Severity: Warning
Object Type (class):
NetworkElement
Domain: netw
Self-clearing alarm raised: No
Severity: Warning
Object Type (class):
NetworkElement
Domain: netw
Self-clearing alarm raised: No
Troubleshooting Guide
3 — Troubleshooting network alarms
Additional information
This a redundant 5620SAM
switchover alarm.
—
—
The SNMP Index Boot Status is not
configured to be persistent on the
router. See the router CLI menu
"show system info" for the current
setting.
The alarm is raised when a command
sent via CLI failed on the node.
—
—
The alarm is raised when a 7250 SAS
device sends the following trap:
BATM-SYS-MON-MIB.cpuUtilizationEx
ceeded
A CPU utilization threshold is
configurable on the device.
November 2008 3-53