Avaya Definity SI Maintenance Manual page 378

Maintenance Commands and Trouble-Clearing Aids
The flash checksum test acts as a backup check to ensure that 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 Reliability System. If the test
detects a difference, a minor, off-board alarm is generated.
When checking the software, the test compares the memory resident
software version and patch identifier. It also checks for the presence of a
field update file and, if found, compares the old and new patch identifiers to
make sure the same patch file id loaded on each processor. If the software
or update files are inconsistent, the list configuration software command
can be used to display the status of the patch file.
Recovery procedures
In the event of a failure encountered during the download and application of the
update file, follow the recommended recovery procedures. The instructions apply
to both simplex and duplex switches; additional detail is given when needed.
Error on the download transmission
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
configuration 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.
8-128 Issue 4 May 2002 555-233-123