Alcatel-Lucent 5620 Troubleshooting Manual page 128

3 — Troubleshooting network alarms
Alarm name, ID, type, and probable
cause(s)
Alarm name: SapMismatch
Alarm ID: 417
Type: configurationAlarm (11)
Probable cause: remoteSapMismatch (310)
Alarm name: SapTagMismatch
Alarm ID: 418
Type: configurationAlarm (11)
Probable cause: remoteSyncTagMismatch
(311)
Alarm name: SubnetMismatch
Alarm ID: 415
Type: configurationAlarm (11)
Probable cause: ipAddressListMismatch
(308)
(2 of 2)
Alarm name, ID, type, and probable
cause(s)
Alarm name: backupScriptInUse
Alarm ID: 274
Type: configurationAlarm (11)
Probable cause: backupInUse (206)
Alarm name: noFunctioningScript
Alarm ID: 275
Type: configurationAlarm (11)
Probable cause: primaryBackupDown (207)
Alarm name: scriptBackupLost
Alarm ID: 273
Type: configurationAlarm (11)
Probable cause: backupDown (205)
3-90
Alarm severity, object type,
domain, and self-clearing attribute
Severity: Major
Object Type (class): Instance
Domain: srrp
Self-clearing alarm raised: No
Severity: Major
Object Type (class): Instance
Domain: srrp
Self-clearing alarm raised: No
Severity: Major
Object Type (class): Instance
Domain: srrp
Self-clearing alarm raised: Yes
Table 3-56 Domain: subscrident
Alarm severity, object type,
domain, and self-clearing attribute
Severity: Major
Object Type (class): Policy
Domain: subscrident
Self-clearing alarm raised: Yes
Severity: Critical
Object Type (class): Policy
Domain: subscrident
Self-clearing alarm raised: Yes
Severity: Warning
Object Type (class): Policy
Domain: subscrident
Self-clearing alarm raised: Yes
November 2008 Alcatel-Lucent 5620 Service Aware Manager, Release 6.1 R3
Additional information
—
—
—
Additional information
The primary script is operationally
down, but one of the other scripts is
operationally up.
All scripts are operationally down.
The primary script URL is
operationally up but a lower-priority
script or URL is operationally down.
Troubleshooting Guide 3HE 04244 AAAB Ed. 01