Before you begin
Carefully review all topics listed as Prerequisites, and be sure to complete a system backup.
Capture all current configuration settings from the Server Management > System Configuration page of the Web Console. You will need this information later to verify that all configuration settings carried forward during the upgrade process are correct and complete.
Note the method of date/time configuration set prior to the platform upgrade (manually set or configured to synchronize with an NTP server at a specific IP address).
Unless your System Platform 6.0.3.x configuration incorporates a standalone SAL Gateway server, reassign the IP addresses for Cdom and the SAL Gateway on your System Platform server according to the platform upgrade Prerequisites.) The platform upgrade software automatically checks your current SAL Gateway deployment (embedded versus standalone gateway). If the check reveals use of a standalone SAL Gateway, the upgrade software installs the System Platform 6.2.x Services Virtual Machine in a disabled state. This action prevents the embedded SAL Gateway from running on the Services VM on the local server.
- If you are upgrading two servers supporting a System Platform 6.0.x High Availability configuration, Stop HA and then Remove HA on the Primary server. System Platform does not support platform upgrades while High Availability is running. If you attempt an upgrade while High Availability is running, a warning message appears and the system prevents you from performing the upgrade.
Important If you are upgrading within a System Platform High Availability configuration using the embedded SAL Gateway, complete Cdom and SAL Gateway IP address reassignments on the primary server alone, and only after stopping High Availability operation. (See platform upgrade Prerequisites .) If you later have a High Availability failover event (triggered manually or automatically), the High Availability subsystem enables the Services VM on the standby server and the HA data replication software automatically propagates the new Cdom and SAL Gateway IP addresses to the standby server.
Procedure
- Log in to the Web Console for the primary (if HA) or standalone (if non-HA) System Platform server.
- Click Server Management > Platform Upgrade in the navigation pane.
The Server Management Platform Upgrade page appears.
- In the Upgrade Platform From field, select the location of the software to be installed.
Note If the software is located on a different server (for example, Avaya PLDS or HTTP), and depending on your specific network environment, configure a proxy if necessary to access the software. See Configuring a proxy.
- If you selected HTTP or SP Server in the Upgrade Platform From field, enter the complete URL or path of the platform upgrade files.
- Click Search.
The system searches the location that you specified for an upgrade description file that has an .ovf extension.
- Select the VSP description file for the platform upgrade, and then click Select.
The system displays the version and additional information for the current and the new platform on the Platform Upgrade Details page.
- On the Platform Upgrade Details page, click Upgrade. Important
As part of the upgrade process, the System Domain (Domain-0) and Console Domain virtual machines will reboot.
- Click OK when prompted to confirm that the template has been qualified for the platform version to which you are upgrading, and that both the System Platform Web Console and Console Domain will reboot upon completion of the upgrade .
- Click OK when prompted to confirm the upgrade.
At this stage, the upgrade process starts and the system displays the Platform Upgrade workflow status page.
Note The System Domain (Domain-0) and Console Domain reboot at this stage. For this reason, the Platform Upgrade workflow status page does not show any updates until it reboots in the new Console Domain. After the Web Console is up, the system automatically redirects you to the login page. This routine can take approximately 20 minutes.
- Log in to the System Platform Web Console. Note
You are allowed a 4-hour period to log in to the System Platform Web Console. If you do not login during this period, the system will reboot using the previous release of System Platform. If a user logs in to System Platform Web Console within the 4-hour period, it is assumed that System Platform is reachable and the timer is cancelled.
- Before electing to commit or roll back the platform upgrade, complete the procedure for Verifying an upgrade.
- On the Commit or Rollback platform upgrade page, do one of the following:
Click Commit to finalize the upgrade process by committing to the new version of System Platform. See Committing an upgrade
Click Rollback to cancel the upgrade process and go back to the previous version of the software. See Rolling back an upgrade.
- If you elected to commit the upgrade and the system finishes rebooting automatically, log on to the upgraded server's Web Console.
- Select SAL Gateway Management. Note
If your network includes a standalone SAL gateway, the platform upgrade leaves the embedded SAL Gateway disabled on the local Services Virtual Machine. You must administratively configure the details of the standalone server and then enable the SAL gateway to run on that server.
- Click Enable SAL Gateway.
- Click Launch SAL Gateway Management Portal.
The Avaya SAL Gateway user interface appears.
- Log on to the SAL Gateway user interface.
The default username is admin; the default password is admin01.
- Click Administration > Service Control & Status.
The Gateway Service Control window opens.
- Click Check Health for the Gateway on the Gateway Service Control page.
This action displays results of a final check for proper SAL Gateway operation and communication with Avaya remote servers.
This completes the System Platform upgrade procedure.