Complete this prerequisite when a System Platform upgrade can be performed at the customer site. In this case, 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 (or servers, in the case of High Availability configurations) that you must upgrade.
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.
| 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.
Note that use of the term “target server” in this procedure refers to the System Platform server you must upgrade.
Saving the change you just made to the Cdom IP address configuration temporarily severs your secure connection to Cdom on 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.)