Filter
Top Products
DEFINITY ECS Release 8.2 Maintenance for R8.2csi
555-233-119 Issue 1
April 2000
Maintenance Commands
2-94download update-file
2
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.
Error on Application of the Patch
A patch may not have been applied for the following reasons:
1. The memory card is write-protected. Remove this protection and issue a
reset system x
command
2. The patch identifiers are inconsistent. Run
list configuration software
and compare the old_patch identifier with the values in the update file.
3. The LMM encountered a problem with the patch file. This is unlikely
because the same checks (and more) were performed when the file was
downloaded, prior to marking the file valid. This implies that the memory
that stored the update file was corrupted.
a. Apply the back out file immediately to back out the changes.
b. Run the flash checksum test to make sure the system is back to its
prepatch state.
c. Check the validity of the file again
d. Try redownloading and applying the patch immediately.
4. The LMM reports a hard error. Symptoms of this are an entry in the
hardware error log for the processor/memory board (if you’re lucky), or
extremely odd switch behavior followed by SPE down mode (if you’re not).
The problem is that the LMM cannot complete the programming of
memory with the result that memory is in a corrupted state. The only
recovery is to get or order new software and processor/ memory circuit
packs.
Good application - bad patch
This error is not caused by a failure in the download or application, but by a fault
in the patch file itself. To recover from this type of problem, the back out file that
backs out the patch should be downloaded and applied. This requires that the
system be sane enough to receive the file correctly and be able to apply it.