3.5.1 Matrix Server Upgrade Guide

Chapter 4: “All-at-Once” Upgrades 42
Copyright © 1999-2007 PolyServe, Inc. All rights reserved.
SLES9 systems: If necessary, upgrade to a supported SLES9 release
and the appropriate kernel. If you will be running MxFS-Linux,
you will need to compile the kernel from source. See Appendix B
for more information.
11. If you updated the operating system or kernel, reboot the server.
12. Install Matrix Server 3.5.1 from the Matrix Server product CD or the
location where you have downloaded the software. Be sure to install
the RPM that corresponds to your architecture (i586 for 32-bit or
x86_64 for 64-bit).
# rpm -i <mountpoint>/pmxs-3.5.1-<xxxx>.<arch>.rpm
13. When you removed the previous version of Matrix Server, the
uninstall process saved all Matrix Server configuration files that had
been modified at your site. The old files were saved with the suffix
.rpmsave.
After Matrix Server 3.5.1 is installed, the installation process runs the
mxcheck utility, which will report errors for the saved files. Review
the mxcheck report to locate the saved files and then compare them
with the new versions of the files that have been installed. You will
need to migrate your customized values from the old files to the new
files as necessary. You can then delete the .rpmsave files.
NOTE: If your mxinit.conf file includes SanPulse start options, be sure
to rename the options as described under “Changes for
SanPulse Start Options” on page 4.
14. Install the Management Console:
# rpm -i <mountpoint>/mxconsole-3.5.1-<xxxx>.<arch>.rpm
15. If you will be using MxFS-Linux, complete these steps:
a. Install the MxFS-Linux support RPM from the product CD or the
location where you have downloaded the software. Be sure to
install the RPM that corresponds to your architecture (i586 for 32-
bit or x86_64 for 64-bit).
# rpm -i <mountpoint>/mxfs--sles9-support-3.5.1-<xxxx>.<arch>.rpm