Lucent Technologies Medical Alarms Release 3 Version 8 User Manual

3

The steps required to perform an HA upgrade when the original server 
requires a full CMS version upgrade are described below and depicted in 
the accompanying figure

1. Upgrade the Definity Switches to Release 8.1 (or later) and 

administer the switches to run with the current (pre-R3V8) version of 
CMS installed on the original server.

2. Since backup tapes will be exchanged between the two servers,  

verify that the tape drive on the original server is compatible with the 
tape drive on the new HA server. For example, if a Sun Enterprise 
3500 server is purchased for incorporation with an existing 
Enterprise 3000 server, the tape drive on the 3000 system must be 
replaced with a new Exabyte Mammoth 20-40 Gbyte 8mm (EXB-
8900) tape drive. Old tapes should be discarded so that they are 
not mistakenly used in the new tape drive.

If replacement of the tape drive on the original server is 
required, provisioning will dispatch a Sun

*

 technician. For 24/7 

call center operations, this activity will incur some loss of CMS 
data. 

3. Coordinate with the customer to:

a. determine which CMS server will be designated as the 

primary server and which will be designated as the 
secondary server (for details, see 

)

b. establish a cut-off time on the day of the HA upgrade, after 

which time CMS users will not make changes to the system 
administration until the upgrade is completed.

4. Perform a CMS full maintenance backup and a CMSADM backup 

on the original server approximately 24 hours before the HA 
upgrade begins. 

*

Sun is a registered trademark of Sun Microsystems, Inc.