3.5.1 Matrix Server Upgrade Guide

Chapter 2: Single Rolling Upgrades 9

• For best results while the matrix includes a mix of servers running

3.5.1 and the older release, all UI operations (either via the

Management Console or the mx command-line utility) should be

connected to a server running the older release.

• Before performing an upgrade from 3.1.2, you will need to obtain a

new license file from your MatrixLink account. You can install the

license file during the upgrade. If the new file is not in place when you

start Matrix Server, license violations will be reported on the

Management Console and in the matrix log, and the product will shut

down after one hour and 45 minutes.

• You do not need to run mxconfig when upgrading to 3.5.1. If you

want to change any of the parameters that you originally specified

with mxconfig, first upgrade all servers to 3.5.1. After the upgrade is

complete, stop Matrix Server on each server (use /etc/init.d/pmxs

stop), and then rerun mxconfig.

Rolling Upgrade Procedures

The following procedures are available:

• Install a new operating system and upgrade Matrix Server and

optionally MxFS-Linux. See “Upgrade Matrix Software and Install a

New OS” on page 10.

• Upgrade Matrix Server and MxFS-Linux without reinstalling the

operating system. See “Upgrade with MxFS-Linux” on page 14.

• Upgrade Matrix Server without reinstalling the operating system.

“Upgrade Without MxFS-Linux” on page 17.