General preparation

Obtain license and authentication files for all servers in the network.

Obtain a PLDS license and an authentication file for the main server.

License and authentication files are generated using PLDS.

Survivable core servers

Upgrade each server to later version of Communication Manager.

All survivable core servers must be upgraded to the current release of Communication Manager before upgrading the main server.

For instructions on how to upgrade a server to a Communication Manager Release 5.2 or later, see Upgrading Avaya Aura® Communication Manager.

Configure the survivable core server.

Use the server System Management Interface to configure the server

Restart the server.

Verify that the survivable core server administration feature is turned on.

To verify that the survivable core server Administration and Enterprise Survivable Server feature is turned on, see Checking the license file.

Attach the survivable core server to the network and verify communication with the customer’s LAN interface.

The IP address of the Procr that you entered when configuring the survivable core server is used when the survivable core server registers with the main server for the first time and it may be used for subsequent registrations.

On the survivable core server, run the ping command with the IP address of the Procr.

Verify the communication to the main server over the IP network.

On the survivable core server, use the ping command with the IP address of the main server.

Main Server

Upgrade the server.

Upgrade the main server to later version of Communication Manager.

A main server should never run a release of Communication Manager that is later than that of the survivable core server.

If the existing server is running an earlier release of Communication Manager, upgrade to the latest version.

To use the standard process to upgrade the main server to Communication Manager, see Upgrading Avaya Aura® Communication Manager.

Configure the main server.

Use the System Management Interface of the server to configure the main server.

To configure a server for Survivable core server that is already running Communication Manager Release 5.2 or later, see Converting the existing survivable core server to main server.

Restart the server.

Verify that the survivable core server administration feature is turned on.

To verify that the survivable core server Administration feature is turned on, see Checking the license file.

Verify open ports in the customer’s network.

Certain ports must be open for survivable core server to work properly.

To obtain a list of ports that must be open for survivable core server, see Network port considerations.

Verify LAN/WAN connectivity.

For each of the survivable core servers, run the ping command on the main server with the IP address of the survivable core server.

Administer Survivable core server.

On the main server, administer each survivable core server, media gateway communities, and no service timer.

To administer the main server see Survivable core server administration.

Verify that each survivable core server registers with the main server.

Use the status ess clusters command to verify survivable core server registration.

A configured survivable core server automatically registers with the main server when the survivable core server administration completes. After registration, the survivable core server receives a translation download from the main server. The survivable core server resets to load the translations and then re-registers with the main server.

For more information on the status ess clusters command, see Maintenance Commands for Avaya Aura® Communication Manager, Branch Gateways and Servers.

Distribute the translations to the survivable core servers.

To synchronize translations between the main and newly added survivable core server for the first time, run the save translations all or the save translations ess command.

For more information, see Translations.

Acceptance testing.

Test the survivable core server configuration.

For more information on testing a survivable core server configuration, see Survivable core server acceptance testing.