No upgrade license needed. Check this link. The process is different if you're upgrading from 11.0 FP4 SP3 to 11.1 versus upgrading from 11.0 FP4 SP4 to 11.1. Apparently with 11.0 FP4 SP3, you have to use a replacement virtual server for data migration purposes. If you go to 11.0 FP4 SP4, then upgrade to 11.1, it removes the need for the separate server for data migration purposes.
Link - [URL unfurl="true"]https://ipofficekb.avaya.com/upgrade [/url]
Upgrading to R11.1 SP1
Prev
Up
Next
More
For existing Linux-based IP Office servers, in order to upgrade to IP Office Release 11.1 SP1, the previous standard upgrade methods cannot be used. This is due to a required change of the Linux operating system to CentOS 7 as CentOS 6 is now end-of-life.
•Upgrading Using an ISO File
Attempting to upgrade a server using the standard methods, for example uploading the R11.1 ISO, will not proceed beyond the initial start of the upgrade process before halting with an error.
•Upgrade Process Changes
This document covers the process of upgrading to R11.1 SP1 via R11.0.4.4. The process is different from that originally used for upgrading to R11.1 from R11.0.4.3. For those familiar with the previous process, a summary of the changes are available. See Changes to the Upgrade Process.
•11.1GA and Future Upgrades
This is a one-off process for upgrading existing pre-R11.1 system. Upgrades of systems already on R11.1 can use the traditional ISO upgrade methods to upgrade to R11.1 SP1.
Process Summary
1.Upgrade to R11.0.4.4
The first stage is to upgrade all IP Office servers to R11.0.4.4 using the standard upgrade methods (upgrade by ISO file transfer for Linux-based servers, upgrade using IP Office Manager for IP500 V2 control units).
•This is absolutely essential. R11.0.4.4 contains changes which are used by the process of upgrading to R11.1 SP1.
•Attempting to upgrade to R11.1 SP1 from any other release other than R11.1 will cause the lose of data.
2.Verify Operation
Once upgraded to R11.0.4.4, verify the operation of all services (local and remote phones, voicemail, one-X Portal for IP Office, Media Manager, etc).
•! WARNING: Even if the customer no longer uses Media Manager, if there are any stored call recordings on the server's additional hard disk, then the service needs to be running correctly on R11.0.4.4 before the server is upgraded to R11.1 SP1. Once the server is upgraded to R11.1 SP1, the Media Manager service can be stopped again if not required.
3.Backup the Servers
Once satisfied with operation at R11.0.4.4, take a full backup of all servers. The backup is not used as part of the R11.1 SP1 upgrade processes in this document but is recommended for system recovery should that become necessary.
4.Upgrade to R11.1 SP1
Finally, proceed with the upgrade from R11.0.4.4 to R11.1 SP1. The upgrade process required varies depending on the type of server being upgraded:
•IP500 V2 Control Unit
These can be upgraded using the normal IP Office Manager based upgrade processes and are not covered in this document.
•Unified Communications Module
This process uses a 32GB USB memory key created using Avaya USB Creator and the 11.1 SP1 ISO file. The Unified Communications Module is rebooted from the USB memory key. The USB memory key then runs the upgrade process and is used to temporarily store existing data during the module's upgrade.
•Physical Linux-based IP Office Servers (including IP Office Application Server)
This process use a 256GB USB memory key created using Rufus and the 11.1 SP1 ISO file. The USB memory key is used to run the upgrade process and to temporarily store existing data during the modules upgrade.
•VVMware Virtual Machines
This process uses a virtual machine hard-disk (VMDK) file downloaded from Avaya. The virtual hard-disk is mounted onto the existing server and the server then rebooted using that disk. The upgrade hard-disk runs the upgrade process and is used to temporarily store data during the server's upgrade.
