Lucent Technologies Release 3 Version 8 manual HA Upgrade Scenarios

Upgrading CMS to the High Availability Option	CentreVu CMS R3V8 High Availability
	Connectivity, Upgrade and Administration
HA Upgrade Scenarios	3-2

If either case a) or b) are in effect, the upgrade process is significantly simplified, since:

•the Definity switch can be administered for the correct CMS version and the dual ACD links prior to the arrival of the new HA server onsite (the unused C-LAN link is busied out until the new HA server is installed)

•the original server either does not require a software upgrade or only needs a base load upgrade to match the installation on the new HA server.

In either case, when a new HA server is added to a system in which the original server is already installed with the correct CMS version, achievement of a “synchronized” system requires minimal or no software installation, followed by one or two maintenance backups and restores between the two servers (the servers are never truly synchronized due to operational differences between the primary and secondary servers).

Due to the simplified logistics associated with creation of a new HA system when the original server is already installed with the correct CMS version, this document does not describe upgrade scenarios in which a full CMS version upgrade is not required.

In contrast, when the original server is installed with a pre-R3V8 version of the CMS software, the HA upgrade process entails a specific sequence of installation and administration activities, as well as various maintenance backups, data migrations and restores. These activities must be executed in an ordered sequence that minimizes system downtime and the overall provisioning effort. The procedures required to perform an HA upgrade under this scenario are presented in the following sections.