Alcatel-Lucent 5620 - Page 165

3 — Troubleshooting using network alarms
Alcatel-Lucent 5620 Service Aware Manager, Release 3-123
3HE 05723 TQZZA Edition 01 Troubleshooting Guide
Table 3-73 Domain: sw
Name: TunnelDown
Type: pathAlarm (12)
Probable cause: tunnelDown (23)
Severity: Critical
Object Type (class): Tunnel
Domain: svt
Implicitly cleared (self-clearing): Yes
The alarm is raised when the
5620 SAM detects that a service
tunnel is operationally down.
Name: TunnelOverbooked
Type: resourceAlarm (28)
Probable cause: tunnelOverbooked (442)
Severity: Warning
Object Type (class): Tunnel
Domain: svt
Implicitly cleared (self-clearing): No
The alarm is raised when the
allocated SDP binding bandwidth
specified by sdpBookedBandwidth
exceeds the
sdpMaxBookableBandwidth value.
Alarm Attributes Additional information
Name: BootableConfigBackupFailed
Type: configurationAlarm (11)
Probable cause: fileTransferFailure (89)
Severity: Major
Object Type (class):
BackupRestoreManager
Domain: sw
Implicitly cleared (self-clearing): Yes
The alarm is raised when the
5620 SAM fails to back up a set of NE
configuration files.
Name: BootableConfigRestoreFailed
Type: configurationAlarm (11)
Probable cause: fileTransferFailure (89)
Severity: Major
Object Type (class):
BackupRestoreManager
Domain: sw
Implicitly cleared (self-clearing): Yes
The alarm is raised when the
5620 SAM fails to restore a set of NE
configuration files.
Name: BootEnvironmentSyncFailed
Type: equipmentAlarm (3)
Probable cause:
bootEnvironmentSyncFailed (87)
Severity: Critical
Object Type (class):
SoftwareUpgradeManager
Domain: sw
Implicitly cleared (self-clearing): Yes
The alarm is raised when the
synchronization of one or more
system initialization files between
the active and standby CPM cards
fails. See the 7750 SR OS System
Guide for more information.
Name: certifyFailureAlarm
Type: softwareAlarm (19)
Probable cause: certifyFailureAlarm (402)
Severity: Major
Object Type (class):
SoftwareControlModule
Domain: sw
Implicitly cleared (self-clearing): No
The alarm is raised when the
software certification process on an
NE fails.
Name: ConfigFileSyncFailed
Type: equipmentAlarm (3)
Probable cause: configFileSyncFailed (88)
Severity: Critical
Object Type (class):
SoftwareUpgradeManager
Domain: sw
Implicitly cleared (self-clearing): Yes
The alarm is raised when the
configuration file synchronization
between the active and standby CPM
cards fails.
(1 of 3)
Alarm Attributes Additional information
(3 of 3)
Aug 2010
AAAD
8.0 R4