Alcatel-Lucent 5620 Troubleshooting Manual page 84

3 — Troubleshooting network alarms
Alarm name, ID, type, and probable
cause(s)
Alarm name: CorruptImageFile
Alarm ID: 171
Type: configurationAlarm (11)
Probable cause: invalidOrCorruptImageFile
(134)
Alarm name, ID, type, and probable
cause(s)
Alarm name:
MirrorDestinationMisconfigured
Alarm ID: 209
Type: configurationAlarm (11)
Probable cause:
mirrorDestinationMisconfigured (162)
Alarm name:
MirrorEncapsulationTypeInconsistent
Alarm ID: 217
Type: configurationAlarm (11)
Probable cause:
mirrorEncapsulationTypeInconsistent (171)
3-46
Table 3-27 Domain: mediation
Alarm severity, object type,
domain, and self-clearing attribute
Severity: Critical
Object Type (class):
AbstractSoftwareFolderDescriptor
Domain: mediation
Self-clearing alarm raised: Yes
Table 3-28 Domain: mirror
Alarm severity, object type,
domain, and self-clearing attribute
Severity: Major
Object Type (class): Mirror
Domain: mirror
Self-clearing alarm raised: Yes
Severity: Major
Object Type (class): Mirror
Domain: mirror
Self-clearing alarm raised: Yes
November 2008 Alcatel-Lucent 5620 Service Aware Manager, Release 6.1 R3
Additional information
The alarm is raised when one or more
files in the 5620 SAM software image
specified for a device software
upgrade is invalid, corrupt or absent.
The 5620 SAM validates a device
software file set before it imports
the file set and distributes it to an
NE. Ensure that the file set
downloads properly to the NE and is
not tampered with before you
re-attempt the upgrade.
The alarm is cleared when a valid file
set is on the NE and the 5620 SAM
activates the software image in the
file set.
Additional information
More than one destination SAP is
configured for a service mirror.
The encapsulation type is
inconsistent among the mirroring
sites of a service.
Troubleshooting Guide 3HE 04244 AAAB Ed. 01