Alcatel-Lucent 5620 - Page 166

3 — Troubleshooting using network alarms
3-124 Alcatel-Lucent 5620 Service Aware Manager, Release
Troubleshooting Guide 3HE 05723 TQZZA Edition 01
Name: DataLossAlarm
Type: storageAlarm (25)
Probable cause: dataLoss (122)
Severity: Major
Object Type (class):
AccountingStatsRetrievalManager
Domain: sw
Implicitly cleared (self-clearing): No
The alarm is raised when the
5620 SAM receives the
tmnxLogAccountingDataLoss trap,
which is sent when a statistics
collection interval ends while an NE
is writing data to an accounting file.
The statistics collection for the
interval stops immediately, and
collection for the next interval
begins. The accounting statistics file
for the interrupted collection
contains an incomplete data set as a
result.
Name: HardwareBootFailure
Type: softwareAlarm (19)
Probable cause:
softwareBootProblemDueToHardwareIssues
(92)
Severity: Critical
Object Type (class): CardSoftware
Domain: sw
Implicitly cleared (self-clearing): Yes
The alarm is raised when an NE fails
to boot because of a hardware
problem.
Name: PrimaryImageBootFailure
Type: configurationAlarm (11)
Probable cause:
bootOptionFileMisconfigured (150)
Severity: Warning
Object Type (class): CardSoftware
Domain: sw
Implicitly cleared (self-clearing): Yes
The alarm is raised when the primary
software image specified in an NE
BOF is unusable.
Name: restoreFailureAlarm
Type: softwareAlarm (19)
Probable cause: restoreFailureAlarm (404)
Severity: Major
Object Type (class):
SoftwareControlModule
Domain: sw
Implicitly cleared (self-clearing): No
The alarm is raised when the
software restore process on an NE
fails.
Name: SaveConfigFailed
Type: configurationAlarm (11)
Probable cause: fileAccessError (90)
Severity: Major
Object Type (class):
BackupRestoreManager
Domain: sw
Implicitly cleared (self-clearing): Yes
The alarm is raised when the admin
save command on an NE fails.
Name: SoftwareBootFailure
Type: softwareAlarm (19)
Probable cause: softwareBootProblem (91)
Severity: Major
Object Type (class): CardSoftware
Domain: sw
Implicitly cleared (self-clearing): Yes
The alarm is raised when an NE fails
to boot because of a software
problem.
Name: SoftwareDownloading
Type: softwareAlarm (19)
Probable cause: softwareDownloading (93)
Severity: Warning
Object Type (class): CardSoftware
Domain: sw
Implicitly cleared (self-clearing): Yes
The alarm is raised when an NE
begins to download software to a IOM
or CPM card.
Name: SoftwareInitialized
Type: softwareAlarm (19)
Probable cause: softwareInitialized (95)
Severity: Warning
Object Type (class): CardSoftware
Domain: sw
Implicitly cleared (self-clearing): Yes
The alarm is raised when software
initialization on an IOM or CPM card
completes.
Name: SoftwareInitializing
Type: softwareAlarm (19)
Probable cause: softwareInitializing (94)
Severity: Warning
Object Type (class): CardSoftware
Domain: sw
Implicitly cleared (self-clearing): Yes
The alarm is raised when software
initialization on an IOM or CPM card
begins.
Alarm Attributes Additional information
(2 of 3)
Aug 2010
AAAD
8.0 R4