The preferred method for upgrading servers and server applications is to use the Web Manager menus. However, you can use the previous web control methods for legacy installations.
You can upgrade individual application services without having to reinstall or upgrade the whole server. This is done using either an .rpm file or a .zip file of multiple .rpm's uploaded to the server (local) or downloaded by the server from an HTTP folder (remote repository), see File Repositories.
Once an .rpm file or files are available, the Unified Communications Module web configuration pages will list the available versions and allow switching between versions or simple upgrading to the latest version.
•! WARNING - Not Supported for Upgrades from Pre-R12.0
This method of upgrading is not supported for upgrading from pre-R12.0 releases. For example, from R11.1 to R12.0. The sever must be upgraded using the processes in the Upgrading Linux-Based IP Office Systems to R12.0 manual.
•! Upgrade Warning
Upgrading shows a summary of the supported upgrade paths and methods. Before using any upgrade, refer to the IP Office Technical Bulletin for the IP Office release to confirm that Avaya supports the upgrade path and for any additional information that may not be in this manual.
•! Backup Application Data
In all cases, always backup all application data to a separate location before upgrading. You can do this using the Web Manager menus.
•! Disable one-X Portal for IP Office Logging before upgrading
You must disable one-X Portal for IP Office logging prior to upgrading. If you do not do this, one-X Portal for IP Office admin is very slow to respond after the upgrade. You can disable one-X Portal for IP Office logging through the one-X Portal for IP Office administrator menus by setting the Master Logging Level (Diagnostics | Logging Configuration) to OFF.
The options in this section cover the upgrading of individual components of the operating system and applications supported by the Unified Communications Module.