Lucent Technologies R5SI Computer Hardware User Manual


  Open as PDF
of 2643
 
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-156download update-file
8
In a High or Critical Reliability System, the connection to the INADS host
computer may be dropped (by the INADS side) but the process of copying the
patch file to the standby processor continues. The standby is placed in
maintenance mode and a call placed between active and standby via the data
channels. The file is transmitted in the same way for both tape and flash based
systems. The same checks are made on the receiving side as were made during
and after the original download. If no errors are found, the file is marked valid.
There is no feedback to the user on the status of the standby copy. If an error is
encountered during the copy or validation process on the standby, an error is
logged in the software error log. The data consistency audit will discover that the
two patch files are inconsistent and the user must manually copy the valid file on
the active processor to the standby processor.
The software does not indicate when the copy has completed, so scripts run by
the TSC must not issue an immediate reset on High or Critical Reliability Systems.
This will interrupt the copy and guarantee that the field update files on the two
processors are inconsistent. This problem can be avoided by using one of the
following techniques:
Use two scripts: the first to apply the patch and a second, to be run later,
to issue the reset that applies the patch. This requires two calls to each
duplicated switch.
Put a delay into the scripts which causes the scripts to wait a period of
time after downloading the file and before issuing the reset. This requires
only one call, but the amount of delay time required is not well defined as it
depends on system load.
Use a manual means of detecting when the copy has completed: either a
"PASS" on the data consistency audit or a match on the
"list configuration
software"
form. This requires only one call and introduces less delay in
requesting the reset.
Help Messages
There is no associated help message as the command has no options.
Error Messages
If the vintage of the standby SPE doesn’t match the vintage of the active SPE, the
following message is displayed:
Update file vintage does not match standby SPE core vintage
If the patch identifier in the update file does not match the patch identifier in
memory, the following message is displayed:
Update file patch identifier does not match SPE patch identifier