Lucent Technologies lucent ユーザーズマニュアル

ページ / 2392
DEFINITY Enterprise Communications Server  Release 6
Maintenance for R6vs/si  
555-230-127   
Issue 1
August 1997
Error Messages 
Page A-36
download update-file 
A
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
RECOVERY PROCEDURES
This sections describes the procedures to be followed to recover from failures 
encountered during the download and application of the update file. The instructions 
apply to both simplex and duplex switches; additional detail is given when needed.
Error on the Transmission of the Download
If the error displayed on the terminal indicates that the download step in the process 
failed, there are several culprits:
1. The transmission line could have been noisy. Retry after making all the following 
checks. Failed attempts take up room in the hard patch file and may require a 
warm start to clear the file.
2. The user may have downloaded the tape/MIPS version of the patch instead of the 
flash version.
3. The vintage of the update file may not match the vintage of software currently 
running in the system. Check the customer’s vintage using "list config software" 
and patch vintage provided in the documentation.
4. The switch may have had difficulty in writing to the hard patch file. Check the 
hardware error log for processor/memory board failures.
5. The hard patch file may be full. Issue a "reset system 1". This should cause valid 
files to be applied and invalid ones to be erased.