General prerequisites

• Download the required System Manager OVA, patch files, and data migration utility from the Avaya Support website at http://support.avaya.com/.

  For information about software details, see Software details of System Manager.

• Calculate the MD5sum of the downloaded files and ensure that it has the same value as given on the Avaya PLDS website.

• Keep the following information handy to create a backup on the remote server:

  • IP address

  • Directory

  • User Name

  • Password

• Record the number of users and custom roles in the current release of System Manager.

  After the upgrade, you require this data to verify if System Manager has successfully imported the users and custom roles from the earlier release to the latest release of System Manager.

  For more information about managing users and custom roles, see Administering Avaya Aura® System Manager.

• During the System Manager upgrade, Session Manager performance data (perfdata) is not preserved. If performance data is required after the System Manager upgrade, backup the performance data on the NFS remote server.

  For information about the performance data storage using NFS remote server, see Administering Avaya Aura® Session Manager.

System prerequisites

• Verify that the existing server is compatible with System Manager Release 10.2.x. If the existing server is incompatible, change the server.

  For information, see Supported servers.

• Verify that the ESXi version is compatible with System Manager Release 10.2.x. If the existing ESXi version is incompatible, upgrade to the supported ESXi version.

  For information, see Supported ESXi version.

Geographically redundant System Manager prerequisites

• You can update the primary and secondary System Manager servers in any order. However, you should not simultaneously update the primary and secondary System Manager servers.

  At a time, install the patch on one server.

• Activate the secondary System Manager server only after installing the patch.

  To activate the secondary System Manager server, the primary and secondary System Manager servers must be on the same release and patch version.

• Take the snapshot only after disabling the Geographic Redundancy replication.

Additional considerations

In relation to Avaya Aura® Messaging, note the following points. These points apply to Avaya Aura® Messaging only. Avaya IX™ Messaging, also known as Officelinx, is not impacted.

• Starting with 10.2.x, if AAM is managed by System Manager then before upgrading System Manager, clean the AAM data from System Manager.

• You must administer mailboxes natively in the AAM Management interface.