Run the /opt/Avaya/InstallAgent/bin/DownloadPK.bash<EPM_Hostname, or EPM IP address> command on the MPPs to authorize the software upgrades through EPM.
For more information, see the Authorizing the EPM to upgrade the MPP section in the Implementing Avaya Experience Portal on multiple servers guide.
Procedure
Log on to the EPM web interface.
If Avaya Services is maintaining this system and you are an Avaya Services representative, log on to EPM by using the init EPM account that is created during the EPM software installation.
Otherwise, log on to EPM by using an account with the Administrator user role.
On the EPM navigation pane, click System Management > Software Upgrade.
In the MPP server table, select the check box in the header row of the first column to select all MPP servers.
Note:
The upgrade process skips an MPP if:
You do not have permission to upgrade an MPP.
There is no .iso image or .tar.gz patch file available in the $AVAYA_IA_HOME/download directory.
An MPP is already being upgraded.
The MPP version is not Experience Portal 6.0 or higher.
The MPP is on the same server as the primary EPM.
In the New Version field, select the required upgrade version.
Note:
Only those versions that have the .iso image or .tar.gz patch file available in the directory $AVAYA_IA_HOME/download (default = /opt/Avaya/InstallAgent/download) are available for selection.
In the Upgrade Commands group, click Upgrade and confirm your selection when prompted.
Experience Portal upgrades the MPP servers. This process can take several minutes depending on how many servers are there in your system.
Note:
The selection boxes are greyed out and you cannot start another upgrade until the current one completes.
After a few minutes, click Refresh and verify the following states for all MPP servers:
Mode is Online.
State is Running.
Config is OK.
Note:
If there is an error, you can view the details in the Log Viewer page.
Check that the version numbers are correctly allocated to the MPP servers by verifying the Current Version column.
