Filter
Top Products
DEFINITY Enterprise Communications Server Release 5
Maintenance and Test for R5vs/si
555-230-123
Issue 1
April 1997
Maintenance Commands and Trouble-Clearing Aids
Page 8-157download update-file
8
If an update file which is created for a different system (i.e.,. a patch file is
created for a tape system and downloaded to a flash system), the following
message is displayed:
Update file designed for a different configuration, file will not be used
If the update file is too large to fit in the remaining space, the following message
is displayed:
Update file is too large to fit on device
If the calculated file checksum is incorrect, the following message will be
displayed:
File checksum failed; file will not be used
If an invalid update file block was found, the following message will be displayed:
Found a bad file block; file will not be used
If the total number of blocks listed in the header block of the update file did not
match the number of blocks received by the SPE, the following message is
displayed:
Received an invalid number of blocks; file will be ignored
The total number of subpatches listed in the header of the update file did not
match the number of subpatches received by the switch
Received wrong number of subpatches for update file
Output
None
Feature Interactions
The form displayed for the list configuration software-vintage command has been
modified to reflect the changes imposed by the flash architecture. The list
configuration software command should allow INADS to determine, with one
query, the hardware configuration, software vintage and patch identifier.
There is no interaction with routine periodic or scheduled maintenance because
patches are only applied on restarts before the system is in normal operation.
The flash checksum test acts as a backup check to make sure the entire field
update file was applied correctly. It can fail because of a bad checksum update
from a poorly constructed update file or because the patching operation has
aborted. When the flash Checksum Test fails, a MAJOR on-board alarm is raised
on the processor/memory circuit pack. Maintenance runs a data consistency test
on a daily basis to check that copies of translations, announcements and
software files are consistent across both processors in a High or Critical