This procedure is used when you have an existing server that you are converting to a survivable core server.
Procedure
Back up the translations on the server to be converted.
If the existing server is still in operation, perform a complete backup. If the existing main server is not in operation, determine the location of the last known good backup.
Verify that the server to be converted is disconnected from the LAN/WAN.
Caution:
Be careful to never have two main servers connected to the LAN/WAN at the same time.
Connect the laptop to the services port on the server.
Confirm that the server to be converted is running the latest version of Communication Manager.
On the System Management Interface, click Administration > Server (Maintenance).
The Server Administration Interface is displayed.
Click Software Version under Server.
If the server is not running on the latest version of Communication Manager, upgrade the server. For the procedure to upgrade the server, see Upgrading Avaya Aura® Communication Manager.
If the server is a duplex pair busy out the standby server.
Perform this step for simplex and active servers of duplex pair. In the System Management Interface, click Server Configuration > Network Configuration.
For duplex servers, perform the same configuration activities as step 6 for the standby server.
Enter a unique Server ID (SVID) in the Server ID field.
A single SVID is required for a simplex server and two unique SVIDs are required for a duplex server pair. This ID must be between 1 and 256. Usually the main servers are set to SVID 1 and 2. Gaps in the numbering are allowed (10, 20, 30, . . .) but servers may also be consecutively numbered.
Click Continue, and verify the IP Addresses.
Go to Server Configuration and click the Server Role option.
Select the main server.
Configuring the server causes a reset to be executed. It is not sufficient to notify all of the non Communication Manager processes of the new server configuration including the Cluster ID.
From the active server command line interface use the command line interface to run the following commands to inform all processes of the new server configuration and Module ID.:
stop -caf
start -ca
For the duplex servers, release the busy out of the standby server using the Release Server command on the System Management Interface.
Use the command line interface to perform the following commands to inform all processes of the new server configuration and Module ID:
stop -caf
start -ca
Verify that the main server has the latest translations available.
Translate the new survivable core server on the main server: From the main server execute the change survivable-processor command.
For more information on administering the survivable core server, see Survivable core server administration.
Connect the new survivable core server to the LAN/WAN.
Verify that the survivable core servers register with the main server and that the translations are updated on the survivable core server.
Use the status ess clusters command to verify that the main (this server) is shown and that all the survivable core servers register and translations are updated. Periodically repeat the status ess clusters command until all the survivable core servers are registered and updated.
Note:
A active main server knows its own state and that of any survivable core server that registers with it. For some period of time (minutes), after all servers are installed and configured, there may be a discrepancy between the state displayed by the main server and the survivable core servers.
To synchronize translations between the main server, the survivable remote servers, and the survivable core server, run save translation all on the main server.
