Please enable JavaScript to view this site.

R11.1 Linux-Based System Upgrade Notes

> » No topics above this. «

Upgrading Pre-R11.1 SP1 Systems to R11.1

Scroll Prev Up Next More

For existing pre-11.1 Linux-based IP Office servers to upgrade to R11.1, the previous standard ISO file upgrade methods cannot be used. This is due to a change in the underlying Linux operating system from CentOS 6 to CentOS 7.

The non-standard upgrade process required is covered in this document. This is a one-off process. Once upgraded to R11.1 SP1 or higher, subsequent upgrades can use the traditional ISO file transfer methods.

Quick Summary of the Upgrade Path

A quick summary of the upgrade path follows. For a more detailed summary, see Upgrade Process Summary

 

Action

Description

1.

Upgrade to the latest R11.0.4 service pack

The server should first be upgraded to R11.0.4.5 using the standard ISO transfer methods.

This is essential as the service pack contains changes that are used as part of the subsequent upgrade process.

2.

Upgrade from R11.0.4 to R11.1

Once running the R11.0.4.5 service pack, the server can then be upgraded to R11.1 SP2 or R11.1 FP2 using the processes covered in this document.

Hyper-V virtual machines can only be upgraded to R11.1 FP1. There is no Hyper-V upgrade file for R11.1 service packs or R11.1 FP2.

Software Versions

This document uses the latest versions of the software available at the time of writing. However, if later versions are available at the time of upgrading, they should be used instead as they may contain changes relating specifically to the upgrade process. That is, the latest R11.0.4.x service pack and the latest R11.1 or R11.1 FP1 service packs.

Future Upgrades

The processes in this documentation are a one-time process. Once upgraded to R11.1 or R11.1 FP1, future upgrades can return to using the standard ISO transfer methods.

IP500 V2 Control Units

The processes in this document are only necessary for Linux-based servers, including IP Office Application Servers and UCM modules. They are not needed for IP500 V2 control units. However, it is expected that any such units in the same network as the Linux-based servers are upgraded in parallel.  

 

 

Performance figures, data and operation quoted in this document are typical and must be specifically confirmed in writing by Avaya before they become applicable to any particular order or contract. The company reserves the right to make alterations or amendments at its own discretion. The publication of information in this document does not imply freedom from patent or any other protective rights of Avaya or others. All trademarks identified by ™, ® or © are registered trademarks or trademarks respectively are the property of their respective owners.

Use of this site indicates acceptance of its cookies and analytics, and acceptance of the Avaya privacy policy.

© 2021 AVAYA
Issue 03.b.-
Friday, November 5, 2021