Maintenance Commands and Trouble-Clearing Aids
555-233-123
8-130 Issue 4 May 2002
Inconsistent software versions on a duplicated
switch
As indicated by a failure in the data consistency test, inconsistent software can be
caused by problems in copying the update file to the standby or validation test
failures on the standby. Unlike the tape or MIPS systems which revert to the same
version of software as a result of a refresh, a flash system remains inconsistent
until some manual intervention occurs:
1. Use the list config software command to determine the status of the
vintages, patch identifiers, and patch file data on both the active and
standby processors.
2. If one processor looks as if it has been patched (updated patch identifier
and no update file) and the other looks as if the patch file is still present (no
patch identifier and valid update file), the application of the patch can be
forced by making that processor active and requesting the system restart
indicated in the accompanying documentation.
3. If one processor has a copy of the update file and the other doesn’t (neither
has been patched), the file can be copied using the copy update-file
command.
4. If patch identifiers disagree but neither side has a valid update file, the
missing patch should be redownloaded to the system. During the download
process, the file should pass the vintage test and then be copied to the
standby processor. Validation tests are then be run on both processors.
The patch is applied to memory on the next restart. This procedure is less
disruptive to the customer if the unpatched processor is the standby at the
time of the restart.
To Next Page
Loading...
