Upgrading Linux Based IP Office Servers to IP Office R11.1

Summary of the upgrade process

Last Updated : Aug 09, 2024 |

Prolog information

Metadata

Keywords:

The following is a summary of the upgrade process:

Step	Action	Notes
1.	Understand and plan for the upgrade	Read this document in full and understand all the requirements before taking any other actions. For IP Office systems hosting Media Manager, see Media Manager considerations. IP Office R11.1 does not use Windows servers to host its services. If using any such servers, for example for Avaya one-X® Portal for IP Office or Voicemail Pro, they must be replaced with Linux-based servers. See Windows Server migration
2.	Back up the server(s)	Before upgrading to R11.0.4.8, back up the IP Office servers and services.
3.	Upgrade to the latest R11.0.4 service pack	Upgrade the Linux-based IP Office server(s) to R11.0.4.8 using the standard ISO file transfer methods.
4.	Verify Correct Operation	After upgrading to R11.0.4.8, verify the operation of all services.
5.	Backup the server(s)	Before upgrading to R11.1.3, back up all the IP Office servers and services.
	Upgrade to the latest R11.1 service or feature pack	Proceed with the upgrade from R11.0.4.8 to R11.1.3 using the special one-off upgrade processes in this document.
	Physical Linux-based IP Office Servers including IP Office Application Servers	This process uses a USB memory key created using the R11.1.3 ISO file. See Upgrading physical Linux-based IP Office servers.
	Unified Communications Module	This process uses a USB memory key created using the R11.1.3 ISO file. See Upgrading a Unified Communications Module.
	VMware Virtual Machines	This process uses a virtual hard disk (vmdk) file downloaded from Avaya. You can use the file to reboot and upgrade the server. See Upgrading VMware virtual machines.
	Hyper-V Virtual Machines	This process uses a virtual hard disk (vhd) file downloaded from Avaya. You can use the file to reboot and upgrade the server. See Upgrading Hyper-V virtual machines.
	AWS Instances	This process uses a virtual hard disk (vmdk) file downloaded from Avaya. You can use the file to reboot and upgrade the server. See Upgrading AWS instances.
6.	Verify the upgrade	After upgrading to R11.1.3, verify the operation of all services except Media Manager. If issues are found, see Known upgrade issues.
7.	Restart Media Manager	If the server needs to supports Media Manager, restart the service. This starts the database encryption process. You must let Media Manager complete this one-time encryption process. The time required depends on the number of recordings and the server resources and can take several hours.
8.	Update any other servers

Send Feedback