Verifying an upgrade

These are manual steps you can perform to help verify a successful upgrade of your System Platform software to the latest version (6.2 or later).

Before you begin

You have performed all of the platform upgrade steps leading up to – but not including – the commit/rollback step. Before returning to commit/rollback and then finishing the procedure for Upgrading a System Platform server, you must first complete all of the checks in the following procedure successfully.

About this task

This procedure helps to verify certain key indications of a successful platform upgrade, for example:

the new System Platform version running on the server
the presence and versions of virtual machines required for your Avaya Aura^® solution
networking and user configuration capabilities
Network Time Protocol (NTP) configuration

Procedure

Log on to the Web Console as admin.
You should see the Commit/Rollback page, which verifies:
- The server successfully booted up to the new platform version.
- No image or kernel faults occurred during the upgrade. Otherwise, System Plarform automatically rolls back into its prior version and the Rollback Acknowledge page appears.
- No problems occurred in LDAP storage.
Go to Server Management > System Configuration in the Web Console and verify that all the system configuration information is accurate before committing the upgrade.
This action performs a quick check for accuracy of system configuration information carried forward during the platform upgrade.
On the Virtual Machine Management page, verify that the Domain–0 and Console Domain (cdom) versions are identical to the version of your System Platform upgrade (6.2 or later).
Use SSH to log on to Dom0 and Cdom as an advanced administrator (admin) and run the swversion command.
The command output should verify the new System Platform version (6.2 or later).
If an administrator installed a solution template before performing the System Platform upgrade, use the Web Console to verify that all virtual machines for the installed template are visible and accessible. (Click on the virtual machine links and verify their version labels.)
Go to Server Management > Date/Time Configuration in the Web Console and verify that the Date and time are correct as configured prior to the upgrade (manual date/time setting or configured to synchronize with an NTP server at a specific IP address).
This action performs a quick sanity check on the NTP protocol, date, and time configuration.
Go to Server Management > Backup/Restore > Restore in the Web Console and note the latest backup information.
A successful backup during platform upgrade should result in a file visible at this location. As such, this action performs a quick sanity check on System Platform backup/restore functionality.
Go to Server Management > Network Configuration in the Web Console and verify that all network configuration values are correct as configured.
This action performs a quick validation of the System Platform networking setup.
If possible at this time, go to User Administration > Local Management in the Web Console, and then click Create User to create a test user.
Delete the test user.
The last two steps together perform a quick check for user administration functionality.
Go to Server Management > SAL Gateway Management in the Web Console.
If you chose Enable Services VM during the platform upgrade procedure, the SAL Gateway should be running. Otherwise (if you deploy the SAL Gateway on a separate stand alone server), the embedded SAL Gateway should be stopped. This action verifies availability of the SAL gateway running on the Services Virtual Machine.
Go to Server Management > SNMP Trap Receiver Configuration in the Web Console and verify that all the SNMP trap receivers configured before the platform upgrade have been carried forward into the new version of System Platform.
The upgrade process automatically adds a trap receiver of 127.0.0.1 if the Services Virtual Machine is, by default, still enabled. Otherwise, you must add trap receiver destinations corresponding to Network Management Systems in your own network, including one for an external SAL gateway.
Trigger a test alarm from the Cdom Command Line Interface (CLI) and verify that all configured SNMP trap receivers did receive the alarm.
The last two steps together perform a quick check for SNMP trap receiver functionality.
Go to Server Management > License Management in the Web Console and launch the WebLM License Manager.
Login to WebLM portal to verify that all template virtual machine license files are still valid.
The last two steps together perform a quick check on WebLM functionality in the new version of System Platform.
Return to step 12 of Upgrading a System Platform server