Upgrading the Pexip Infinity platform
This topic describes how to upgrade your Pexip Infinity platform to the latest software version. It covers:
When you initiate an upgrade of the Pexip Infinity software, the following steps occur automatically, in order.
- The Management Node software is upgraded, after which the Management Node will automatically reboot.
- The first Conferencing Node is put into maintenance mode, meaning all further incoming calls to it will be rejected.
When all calls have cleared from the first Conferencing Node, its software is upgraded and the system is rebooted. This process should take around 2 minutes to complete, but may take longer depending on the speed of the connection between the Management Node and Conferencing Node over which the files are transferred.
If all calls have not cleared after 1 hour, the first Conferencing Node will be taken out of maintenance mode and put at the back of the queue of systems to be upgraded. A further attempt to upgrade the first Conferencing Node will be made after all other systems have been upgraded (or had upgrade attempts made).
- After the first Conferencing Node has been upgraded successfully (or has been put back in the queue for a later upgrade attempt) and is again available, the second Conferencing Node is put into maintenance mode.
The process continues with each subsequent Conferencing Node being put into maintenance mode, and, after all calls have cleared, being upgraded and then rebooted.
Any Conferencing Nodes used for dynamic cloud bursting will be automatically started up and upgraded.
- If the upgrade of the Management Node and all Conferencing Nodes has not completed successfully after 24 hours, the process will stop and all systems will be left in their existing upgrade state. This is designed to prevent situations where one Conferencing Node cannot be upgraded, which would otherwise leave the system in a permanent state of upgrading.
If the upgrade process does not complete successfully and stops after 24 hours, you may have a mix of upgraded and non-upgraded systems. You will then need to repeat the upgrade process. During a repeat upgrade, only those systems that have not already been upgraded will be included in the upgrade process.
During the 24-hour period from when an upgrade has been initiated, you cannot re-initiate an upgrade using the Administrator interface. If you must re-initiate an upgrade during this time, you must reboot the Management Node and then start the process again.
While the upgrade is in progress, some Conferencing Nodes will be running the newer version of the software and some will be running the older version. These Conferencing Nodes will be incompatible until they are all again running the same version. This means that there may be instances where two endpoints dial the same Virtual Meeting Room alias but if they are routed to different Conferencing Nodes that are running different versions of the software, the two endpoints will be in different conferences. For this reason, we recommend upgrading at a time of minimal usage.
If you need to upgrade your platform during active business hours we recommend that you put all of your Conferencing Nodes into maintenance mode prior to starting the upgrade. As each node is upgraded it will automatically come out of maintenance mode and be able to host new conferences.
During an upgrade from version 11 or earlier to version 12 or later you will not be able to host any conferences on those Conferencing Nodes that are still running the earlier software version. You will experience "No valid license available" errors should anybody try to join a conference on those nodes. Those nodes will be able to host conferences again as soon as they have been upgraded to the new software.
To upgrade Pexip Infinity software
Before upgrading an on-prem deployment, we recommend that you use your hypervisor's snapshot functionality to take a full VMware/Hyper-V snapshot of the Management Node.
If upgrading from v8, due to incompatibilities resolved in v8.1, ensure that you take a non-quiescing snapshot. This snapshot will be required should you later need to downgrade, or if the upgrade fails.You may also want to take a snapshot of each Conferencing Node, although depending on the size and complexity of your deployment it may be easier to simply redeploy these from the Management Node in the unlikely event that this is required.
Before upgrading a cloud-based deployment (AWS or Azure), you should backup the Management Node via Pexip Infinity's inbuilt mechanism ( ).
- Download the Pexip Infinity upgrade package for v14.1
- From the Pexip Infinity Administrator interface, go to .
Selectand browse to the location of the upgrade package.
Select. There will be a short delay while the upgrade package is uploaded.
After the upgrade package has been uploaded, you are presented with a confirmation page showing details of the existing software version and the upgrade version.
To proceed, select.
You are taken to the Management Node and all Conferencing Nodespage, showing the current upgrade status of the
(for a definition of each status, see Definition of upgrade statuses). This page automatically refreshes every 5 seconds.
When the upgrade completes, all systems will show a status of No upgrade in progress and have the new Installed version.
If a Conferencing Node fails to upgrade, for example if it remains on a Waiting for calls to clear status, it should be rebooted. The upgrade process will then continue as expected.
No additional actions are required to upgrade the Management Node or Conferencing Nodes individually.
We recommend that you take a fresh backup of your system after upgrading.
Error messages during upgrade
The following Error-level messages are expected during an upgrade and do not require any action:
2014-03-03T12:12:01.924+00:00 <manager_hostname> 2014-03-03 12:12:01,924 Level="ERROR" Name="administrator.system.configuration" Message="Node configuration failed." Node="<worker_hostname>" Resource="File[/etc/certs/privatekey.pem]"
2014-03-03T12:12:01.924+00:00 <manager_hostname> 2014-03-03 12:12:01,924 Level="ERROR" Name="administrator.system.configuration" Message="Node configuration failed." Node=""<worker_hostname>" Resource="File[/etc/certs/server.pem]"
2014-03-03T12:12:02.400+00:00 <manager_hostname> 2014-03-03 12:12:02,399 Level="ERROR" Name="administrator.system.connectivity" Message="Unable to contact node." Node="<node_ip_fqdn>"
If you are running a Pexip Infinity software version between v3 and v7 inclusive, to upgrade to the latest version, you must first upgrade to version 8. To do this:
- Download the Pexip Infinity v8 upgrade file (contact your Pexip authorized support representative for the link to this file).
- Follow the steps outlined in Upgrading from version 8 or later to version 14.1, but when asked to browse to the location of the v8 upgrade file.
- Verify that the upgrade has completed successfully.
- Download the Pexip Infinity v14.1 upgrade file.
- Follow the steps outlined in Upgrading from version 8 or later to version 14.1, and when asked to browse to the location of the v14.1 upgrade file.
The automatic upgrade process described above will update the Management Node and all Conferencing Nodes, including Conferencing Nodes that have been created using the configuration only deployment type.
However, if after the upgrade you wish to deploy new configuration-only Conferencing Nodes, you must download and use a version of the Conferencing Node VM template that matches the version of the Management Node that you have upgraded to. Creating a new Conferencing Node from a VM template containing a different version of the Pexip Infinity software than that which is running on the Management Node is not supported and will not work. For more information, see Deploying a Conferencing Node using a generic VM template and configuration file
During an upgrade, the Conferencing Node as follows:page will report the status of each
|No upgrade in progress||During a platform upgrade, this is the default state that occurs before a Conferencing Node is upgraded, or after the node has rebooted .|
|Upgrade pending||An upgrade of the platform is in progress and this Conferencing Node is in the queue to be upgraded.|
|Preparing to upgrade||The Conferencing Node is preparing to upgrade. During this time the node will be put into maintenance mode, and other services will be stopped.|
|Waiting for calls to clear||The Conferencing Node is in maintenance mode and is waiting for existing conferences to complete.|
|Timeout waiting for calls to clear||Not all conferences had cleared after 1 hour. This Conferencing Node has been removed from maintenance mode and the upgrade will be attempted again later.|
|Upgrade in progress||The new software is being unpackaged and installed on the Conferencing Node. During this time the Conferencing Node will not synchronize configuration with the Management Node.|
|Rebooting||The upgrade has completed and the Conferencing Node is rebooting.|
|Could not communicate with conferencing node||This error will be reported if the Conferencing Node cannot be contacted.|
To downgrade your system to the previous version, or to recover your system after a failed upgrade:
- Restore the Management Node from the VMware snapshot that you took using your hypervisor at the start of the upgrade process.
- Restore the individual Conferencing Nodes by either:
- redeploying each Conferencing Node manually from the Management Node - see Deploying new Conferencing Nodes, or
- restoring the hypervisor snapshot of each Conferencing Node that was taken at the start of the upgrade process.
To view which software version is running on the Management Node, click on the link at the top right corner of the Pexip Infinity Administrator interface.
To view which software version is running on individual Conferencing Nodes, go to . The software version number will be shown in the Installed version column.