
DEFINITY Enterprise Communications Server Release 7
Maintenance for R7r
555-230-126
Issue 4
June 1999
Additional Maintenance Procedures
6-9Software updates
6
The following step will
result in the service
effects described
above.
upgrade
software
to-version
10 Use the new software version number
described above. The system will reboot
the standby SPE, reload translations, and
then execute an SPE interchange. Results
of each step in the upgrade process and
initialization diagnostics will be displayed
on the terminal.
NOTE:
Be careful not to touch the G3-MT
keyboard while waiting for the
command to execute, or the result
messages may be lost.
Log in on the G3-MT.
status spe
5 Repeat this command until the states of
health of both SPEs are
functional
.
reset spe-standby 4
5 This step initiates a reboot of the standby
SPE with the new software load.
status spe
15 Repeat this command until the states of
health of both SPEs are
functional
.
change sys-par maint
2 Set the Save Translation, Alarm Origination
Activated, CPE Alarm Level, SPE
Interchange fields and Daily Scheduled
Maintenance times to the values that were
in effect before starting this procedure.
save translation both
2 This step stores the upgraded translations
on both disks.
backup disk
20 This step makes a backup copy of the new
files. The next run of scheduled
maintenance will also do this. If a
coredump from before the upgrade is on
disk, this can take up to 50 minutes.
test stored-data 10 This step verifies that all MSS files are
consistent. The next run of scheduled
maintenance will also do this.
list config soft long 5 Verify that all files are correct.
Table 6-2. Software Update—Duplicated SPE — Continued
Step
Time
(min) Remarks
Continued on next page