Reassigning Cdom and SAL Gateway IP addresses remotely

Complete this prerequisite when a System Platform upgrade must be performed from a location remote from the customer site. In this case, no Avaya or Avaya Partner Support Engineering personnel are available on-site to assist with local (customer network) login to the Web Console for the server that you must upgrade. A Support Engineer at Avaya or an Avaya Partner site must complete this task entirely by means of communication established between an Avaya Remote Server and the server you must upgrade.

Before you begin

You must be an Avaya (or Avaya Partner) Support Engineer to perform this procedure. If you are a customer of Avaya or an Avaya Partner and must complete a server software upgrade to System Platform version 6.2 (or later), find a support contact at http://support.avaya.com > Support Contact Options > Maintenance Support.

Complete the blank fields in the following table. Procedural steps below reference either address “A” or “B”, as appropriate.

Table 1. Cdom IP address assignments (remote procedure)
Current Cdom (avpublic) IP Address:	A.
New customer-provided IP address for Cdom: (The new address for the cdom virtual machine must be on the same IP subnet used by the System Platform Domain 0 virtual machine. Verify using Linux `ipcalc` or similar tool.)	B.

If you have not already done so, download all necessary platform upgrade files from DVD media, a USB storage device, or an HTTP server, or use File Manager to copy it to the target System Platform server's local /vsp-template directory.
If you have not already done so, perform a full backup of your current Avaya Aura solution before changing any configuration settings or applying new upgrade software.
If you are an Avaya or Avaya Partner Support Engineer, have your eToken (SecureID) USB device available for the additional authentication required for you to complete this prerequisite, and the upgrade process, overall.
Note that use of the term “target server” in this procedure refers to the System Platform server you must upgrade.

Procedure

Open a Web browser and log on to the SAL Remote Server at https://tech1.sal.avaya.com
Using the SE ID of VSPU (cdom), open a remote HTTPS SAL session with the Cdom virtual machine on the target server.
Log on to the System Platform Web Console and authenticate as admin.
Select Server Management > Network Configuration.
From the Domain Network Interface panel, under the Console Domain, note the avpublic IP address from Cdom IP address assignments (remote procedure), field “A”.
Enter the new, customer-provided cdom IP address (from Cdom IP address assignments (remote procedure), field ”B”) into the Console Domain avpublic IP field.
Click Save.
Saving the change you just made to the Cdom IP address configuration temporarily severs your secure connection to the target server. However, the server continues to have connectivity and communication with the remote Avaya servers. (Your existing SAL Gateway 1.8 gracefully manages changes to the server's IP address configuration.)
From the SAL Remote Server at https://tech1.sal.avaya.com, request an HTTPS session with the SAL Gateway on the target server.
Log on to the SAL Gateway user interface using the VSALGW SE ID: (https://<localhost>:7443) and update the Cdom managed element (VSPU) to match the value in Cdom IP address assignments (remote procedure), field “B”.
Click Apply.
Submit your changes to restart SAL Gateway services.
Disconnect from the SAL Gateway on the target server.
From the SAL Remote Server at https://tech1.sal.avaya.com, again request an HTTPS session with the Cdom virtual machine on the target server.
This tunnel session now terminates at the new address assigned to the Cdom virtual machine on the target server.
Using the SE ID of VSPU (Cdom), open a remote HTTPS SAL session with the Cdom virtual machine on the target server.
Log on to the target server's Web Console.

Next Steps

Upgrading a System Platform server