PolyServe® Matrix Server Upgrade Guide PolyServe® Matrix Server 3.1.
Copyright © 2007 PolyServe, Inc. Use, reproduction and distribution of this document and the software it describes are subject to the terms of the software license agreement distributed with the product (“License Agreement”). Any use, reproduction, or distribution of this document or the described software not explicitly permitted pursuant to the License Agreement is strictly prohibited unless prior written permission from PolyServe has been received.
Contents 1 Overview Matrix Software Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Supported Operating System and Kernels. . . . . . . . . . . . . . . . . . . . . . Back Up the Existing Matrix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Upgrade Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Rolling Upgrade for 32-Bit OS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Rolling Upgrade for 64-Bit OS .
Contents iv Matrix Server 2.7.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51 A Install the RHEL4 Operating System and Kernel Install the Operating System and Kernel . . . . . . . . . . . . . . . . . . . . . . 1. Install the Operating System. . . . . . . . . . . . . . . . . . . . . . . . . . . . 2. Compile a New Kernel or Install a Binary Kernel . . . . . . . . . . 3. HBA Drivers and Matrix Server. . . . . . . . . . . . . . . . . . . . . . . . . 4.
1 Overview The following upgrades to Matrix Server 3.1.2 are supported: • Matrix Server 3.1.0 or 3.1.1 running RHEL4 or SLES9. • Matrix Server 3.0.1 running SLES9. • Matrix Server 2.7.2 running RHEL3 or SLES8. If you are running a different version of Matrix Server, you will first need to upgrade to Matrix Server 2.7.2 or 3.0.1 and then upgrade to 3.1.2. CAUTION: Do not deviate from the upgrade procedures in this document. It is important to complete the upgrade steps exactly as described.
Chapter 1: Overview 2 • The servers in the matrix can be running different versions of the same operating system type (for example, SLES9 SP2 and SP3), as long as the above rules are met. • If you will be using a Matrix Server Solution Pack, it must be installed on all nodes in the matrix. Supported Operating System and Kernels The supported operating systems and kernels are as follows. See the PolyServe Hardware and Software Compatibility Guide for any updates to the list of supported kernels. .
Chapter 1: Overview 3 If you choose to perform a fresh install of the operating system, extract the contents of the tar files to /etc/polyserve and /var/polyserve (or /etc/ opt/polyserve and /var/opt/polyserve if upgrading from 3.1.0 or 3.1.1) before installing Matrix Server 3.1.2. • Back up all PSFS filesystems for disaster recovery purposes. Upgrade Scenarios You can use either of these methods for the upgrade: • All at once.
Chapter 1: Overview 4 Current OS Matrix Server MxFSLinux 3.x? SLES9 3.0.1 Yes “Matrix Server 3.0.1 With MxFS-Linux” on page 21 RHEL3/ SLES8 2.7.2 NA “Matrix Server 2.7.2” on page 26 Upgrade Procedure If you are planning to add 64-bit servers to the matrix, perform the upgrade first and then add the servers. Rolling Upgrade for 64-Bit OS If you are currently using 64-bit servers that are running in 32-bit mode, you can upgrade the servers to 64-bit mode during the Matrix Server upgrade.
Chapter 1: Overview Upgrade Notes When upgrading to Matrix Server 3.1.2 from a release earlier than 3.1.0, you should be aware of the following: • The contents of the /etc/polyserve directory will be moved to /etc/opt/polyserve. • The contents of the /var/polyserve directory will be moved to /var/opt/polyserve. Copyright © 1999-2007 PolyServe, Inc. All rights reserved.
2 “All-at-Once” Upgrades This chapter describes how to upgrade all servers at once. The matrix will be down during the upgrade procedure. Upgrades Without MxFS-Linux Complete the following steps on all servers in the matrix: 1. Back up the Matrix Server configuration as described under “Back Up the Existing Matrix” on page 2. 2. Stop Matrix Server: # /etc/init.d/pmxs stop 3. If the following Matrix Server configuration files have been modified at your site, save copies of the files. (For Matrix Server 3.
Chapter 2: “All-at-Once” Upgrades 7 6. Uninstall Matrix Server. This step does not remove your existing matrix configuration or log files. The matrix software must be uninstalled from a location outside of the matrix directory structure (/opt/polyserve). Run this command on the server: # rpm -e pmxs The following message then appears: Stopping PolyServe Matrix Server This server needs to be rebooted before the product removal can proceed. /etc/init.d/pmxs has been moved to /etc/init.
Chapter 2: “All-at-Once” Upgrades 8 12. Install Matrix Server 3.1.2 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 /pmxs-3.1.2-..rpm 13. If you saved any Matrix Server configuration files in step 3, compare the saved files with the new versions of the files that were installed with Matrix Server 3.1.
Chapter 2: “All-at-Once” Upgrades 9 4. If you are upgrading from MxFS-Linux 3.1.0, uninstall the MxFSLinux fastpatch: # rpm -e mxfs-fastpatch 5. Uninstall MxFS-Linux. (When you uninstall MxFS-Linux, you may see an error message stating that a failure occurred. You can ignore this message; the uninstall was successful.) For upgrades from MxFS-Linux 3.1.0 or later, use these commands. # rpm -e mxfs-sles9-support # rpm -e mxfs # rpm -e mxfs-patches For upgrades from MxFS-Linux 3.0.
Chapter 2: “All-at-Once” Upgrades 10 Reboot the server and run the rpm -e command again. Matrix Server will now be uninstalled. NOTE: When the uninstall is complete, you will see a message listing files and directories that could not be removed. Do not manually remove any of these files. 9. Uninstall the Management Console: # rpm -e mxconsole 10. If necessary, upgrade to SLES9 SP2 or do a fresh installation of the operating system. See Appendix B for information about files that need to be modified. 11.
Chapter 2: “All-at-Once” Upgrades 11 17. Install the MxFS-Linux support RPM from the MxFS-Linux product CD or the location where you have downloaded the software. Be sure to install the RPM that corresponds to your architecture (i386 for 32-bit or x86_64 for 64-bit). # rpm -i /mxfs--sles9-support-3.1.2-..rpm Then install MxFS-Linux 3.1.2 from the product CD or the location where you have downloaded the software.
3 Single Upgrade Procedures This chapter describes how to upgrade Matrix Server in a single rolling upgrade. For upgrades from Matrix Server 2.7.2 and 3.0.1, all servers must be running a 32-bit operating system. The procedures do not require any matrix downtime. Each server is removed from the matrix, upgraded, and then returned to the matrix. Rolling Upgrade Considerations You should be aware of the following when upgrading to the Matrix Server 3.1.
Chapter 3: Single Upgrade Procedures 13 • During the rolling upgrade, the matrix will include a mix of servers running 3.1.2 and the earlier release (2.7/3.x). As long as the matrix includes at least one active server running 2.7/3.x, other servers running that version will be able to join the matrix (for example, following a reboot). However, after the last server running 2.7/3.x has left the matrix, only servers running 3.1.2 can join the matrix.
Chapter 3: Single Upgrade Procedures 14 • If you are using MxFS-Linux, you will need to perform an extra step to unmount PSFS filesystems. See “Unmount Filesystems on Clusters With MxFS-Linux” on page 25 for details. Matrix Server 3.1.x Without MxFS-Linux Complete the following steps to upgrade to Matrix Server 3.1.2. NOTE: Upgrade the server with the highest IP address first. Then continue to upgrade the servers in descending order of IP address, with the lowest numbered server being upgraded last. 1.
Chapter 3: Single Upgrade Procedures 15 The following message then appears: Stopping PolyServe Matrix Server This server needs to be rebooted before the product removal can proceed. /etc/init.d/pmxs has been moved to /etc/init.d/Pmxs to avoid PolyServe Matrix Server from starting automatically on boot. error: %preun(pmxs--release) scriptlet failed, exit status 1 Reboot the server and run the rpm -e command again. Matrix Server will now be uninstalled.
Chapter 3: Single Upgrade Procedures 16 14. If you did a fresh installation of the operating system, recreate mount points for the PSFS filesystems. 15. Start Matrix Server on the upgraded server. Run the following command: # /etc/init.d/pmxs start 16. Repeat this procedure on each server in the matrix. The upgrade is now complete. Matrix Server 3.1.x With MxFS-Linux Complete the following steps to upgrade to Matrix Server 3.1.2. NOTE: Upgrade the server with the highest IP address first.
Chapter 3: Single Upgrade Procedures 17 6. Uninstall MxFS-Linux 3.1.x from the server. Run the following commands. (When you uninstall MxFS-Linux, you may see an error message stating that a failure occurred. You can ignore this message; the uninstall was successful.) # rpm -e mxfs # rpm -e mxfs-sles9-support # rpm -e mxfs-patches 7. If the Matrix Server Support RPM is installed, uninstall it: # rpm -e pmxs-sles9-support 8.
Chapter 3: Single Upgrade Procedures 18 11. Install the Matrix Server 3.1.2 Support RPM and the MxFS-Linux kernel patches RPM and then compile the kernel and reboot. Be sure to verify that the kernel is patched correctly for MxFS-Linux. See Appendix B for more information. 12. Install Matrix Server 3.1.2 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).
Chapter 3: Single Upgrade Procedures 19 Matrix Server 3.0.1 Without MxFS-Linux Complete the following steps to upgrade to Matrix Server 3.1.2. NOTE: Upgrade the server with the highest IP address first. Then continue to upgrade the servers in descending order of IP address, with the lowest numbered server being upgraded last. 1. Back up the Matrix Server configuration as described under “Back Up the Existing Matrix” on page 2. 2. Stop Matrix Server on the server: # /etc/init.d/pmxs stop 3.
Chapter 3: Single Upgrade Procedures 20 The following message then appears: Stopping PolyServe Matrix Server This server needs to be rebooted before the product removal can proceed. /etc/init.d/pmxs has been moved to /etc/init.d/Pmxs to avoid PolyServe Matrix Server from starting automatically on boot. error: %preun(pmxs--release) scriptlet failed, exit status 1 Reboot the server and run the rpm -e command again. Matrix Server will now be uninstalled.
Chapter 3: Single Upgrade Procedures 21 15. Copy your new license file to /etc/opt/polyserve/licenses/license on the server. 16. If you did a fresh installation of the operating system, recreate the mount points for PSFS filesystems. 17. Start Matrix Server on the upgraded server. Run the following command: # /etc/init.d/pmxs start 18. Repeat this procedure on each server in the matrix. The upgrade is now complete.
Chapter 3: Single Upgrade Procedures 22 4. If the following Matrix Server configuration files have been modified at your site, save copies of the files. After installing Matrix Server, you can merge your local changes into the new versions of the files. /etc/polyserve/mxinit.conf /etc/polyserve/scl.conf /etc/polyserve/fc_pcitable /etc/polyserve/san_snmp.conf 5. If you will be doing a fresh installation of the operating system, skip to step 11. Otherwise, continue with the following steps. 6.
Chapter 3: Single Upgrade Procedures 23 Reboot the server and run the rpm -e command again. Matrix Server will now be uninstalled. NOTE: When the uninstall is complete, you will see a message listing files and directories that could not be removed. Do not manually remove any of these files. 10. Uninstall the Management Console: # rpm -e mxconsole 11. Upgrade the operating system to SLES9 SP2 or do a fresh installation. (See Appendix B for information about files that need to be modified.) 12.
Chapter 3: Single Upgrade Procedures 24 # rpm -i /mxfs-sles9-support-3.1.2-..rpm Then install MxFS-Linux 3.1.2 from the product CD or the location where you have downloaded the software. Be sure to install the RPM that corresponds to your architecture (i386 for 32-bit or x86_64 for 64bit). # rpm -i /mxfs-3.1.2-..rpm 18. Copy your new license file to /etc/opt/polyserve/licenses/license on the server. 19.
Chapter 3: Single Upgrade Procedures 25 27. Repeat steps 24 through 26 until all of the nodes have been upgraded. 28. On the node that was upgraded first, run the following command: # ./mxfsmigrate.sh --end The upgrade is now complete. If you want to enable filesystem quotas on your PSFS filesystems, you will need to unmount the filesystems one-at-a-time (or one export group at-a-time) and then perform the upgrade. Use the following procedure to unmount the filesystems.
Chapter 3: Single Upgrade Procedures 26 Matrix Server 2.7.2 Complete the following steps to upgrade the matrix to the 3.1.2 release. NOTE: Upgrade the server with the highest IP address first. Then continue to upgrade the servers in descending order of IP address, with the lowest numbered server being upgraded last. 1. Back up the Matrix Server configuration as described under “Back Up the Existing Matrix” on page 2. 2. Stop Matrix Server on the server to be upgraded.
Chapter 3: Single Upgrade Procedures 27 The following message then appears: Stopping PolyServe Matrix Server This server needs to be rebooted before the product removal can proceed. /etc/init.d/pmxs has been moved to /etc/init.d/Pmxs to avoid PolyServe Matrix Server from starting automatically on boot. error: %preun(pmxs--release) scriptlet failed, exit status 1 Reboot the server and run the rpm -e command again. Matrix Server will now be uninstalled.
Chapter 3: Single Upgrade Procedures 28 14. Install the Management Console: # rpm -i /mxconsole-3.1.2-.i586.rpm 15. If you did a fresh installation of the operation system, recreate mount points for the PSFS filesystems. 16. Copy your new license file to /etc/opt/polyserve/licenses/license on the server. 17. Start Matrix Server: # /etc/init/d/pmxs start Repeat this procedure on the remaining nodes in the matrix.
4 Double Upgrade Procedures This chapter describes how to upgrade Matrix Server on clusters that meet these conditions: • The nodes have 64-bit CPUs and are currently running in 32-bit mode, but will upgrade to 64-bit mode. • The nodes are currently running Matrix Server 2.7.2, 3.0.1, 3.1.0, or 3.1.1. The rolling upgrade does not require any matrix downtime. Each server is removed from the matrix, upgraded, and then returned to the matrix.
Chapter 4: Double Upgrade Procedures 30 Server on the node that was upgraded out of order. Continue upgrading the other nodes before starting Matrix Server on that node. • To ensure that applications can acquire fcntl(2) locks throughout the upgrade, you will need to perform the rolling upgrade twice. The first upgrade takes the servers to a supported operating system running Matrix Server 3.1.2 in 32-bit mode.
Chapter 4: Double Upgrade Procedures 31 license file can be installed 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.1.2. If you want to change any of the parameters that you originally specified with mxconfig, first upgrade all servers to 3.1.2.
Chapter 4: Double Upgrade Procedures 32 /etc/opt/polyserve/mxinit.conf /etc/opt/polyserve/scl.conf /etc/opt/polyserve/fc_pcitable /etc/opt/polyserve/san_snmp.conf 4. If you will be performing a fresh installation of the operating system, skip to step 9. Otherwise, continue with the following steps. 5. If the Matrix Server Support RPM is installed, uninstall it: # rpm -e pmxs--support 6. Uninstall any Matrix Server patches installed on the server: # rpm -e pmxs-patch 7. Uninstall Matrix Server 3.1.
Chapter 4: Double Upgrade Procedures 33 9. If desired, perform a fresh installation of the operating system or upgrade the kernel. See Appendix A (RHEL4) or B (SLES9) for information about the necessary steps. 10. If you did a fresh installation of the operating system, extract the backup tar files saved in step 1 to /etc/opt/polyserve and /var/opt/ polyserve. 11. Install Matrix Server 3.1.2 from the Matrix Server product CD or the location where you have downloaded the software.
Chapter 4: Double Upgrade Procedures 34 The following message then appears: Stopping PolyServe Matrix Server This server needs to be rebooted before the product removal can proceed. /etc/init.d/pmxs has been moved to /etc/init.d/Pmxs to avoid PolyServe Matrix Server from starting automatically on boot. error: %preun(pmxs--release) scriptlet failed, exit status 1 Reboot the server and run the rpm -e command again. Matrix Server will now be uninstalled.
Chapter 4: Double Upgrade Procedures 35 25. Install the Management Console: # rpm -i /mxconsole-3.1.2-.i586.rpm 26. If you did a fresh installation of the operating system, recreate mount points for the PSFS filesystem. 27. Start Matrix Server on the upgraded server. Run this command: # /etc/init.d/pmxs start 28. Repeat steps 15 through 27 on the remaining servers. All servers are now running Matrix Server 3.1.2 in 64-bit mode. Matrix Server 3.1.
Chapter 4: Double Upgrade Procedures 36 4. If the following Matrix Server configuration files have been modified at your site, save copies of the files. After the second installation of Matrix Server, you can merge your local changes into the new versions of the files. /etc/opt/polyserve/mxinit.conf /etc/opt/polyserve/scl.conf /etc/opt/polyserve/fc_pcitable /etc/opt/polyserve/san_snmp.conf 5. Remove any MxFS-Linux patches: # rpm -e mxfs-fastpatch 6. Uninstall MxFS-Linux 3.1.x from the server.
Chapter 4: Double Upgrade Procedures 37 /etc/init.d/pmxs has been moved to /etc/init.d/Pmxs to avoid PolyServe Matrix Server from starting automatically on boot. error: %preun(pmxs--release) scriptlet failed, exit status 1 Reboot the server and run the rpm -e command again. Matrix Server will now be uninstalled. NOTE: When the uninstall is complete, you will see a message listing files and directories that could not be removed. Do not manually remove any of these files. 10.
Chapter 4: Double Upgrade Procedures 38 17. Disable the server to be upgraded (start with the server with the highest IP address). Right-click on the server and select Disable. 18. Back up the Matrix Server configuration again on the server being upgraded. Use tar -cv to create tar files of the /etc/opt/polyserve and /var/opt/polyserve directories. 19. Stop Matrix Server on the server: # /etc/init.d/pmxs stop 20. If you will be doing a fresh installation of the 64-bit operating system, skip to step 24.
Chapter 4: Double Upgrade Procedures 39 23. Uninstall the Management Console: # rpm -e mxconsole 24. Upgrade the operating system to 64-bit mode SLES9 SP2 or do a fresh installation. (See Appendix B for information about files that need to be modified.) 25. Install the Matrix Server Support RPM (use the 64-bit version) and the MxFS-Linux kernel patches RPM and then compile the kernel and reboot. Be sure to verify that the kernel is patched correctly for MxFSLinux. See Appendix B for more information. 26.
Chapter 4: Double Upgrade Procedures 40 32. Start Matrix Server on the upgraded server. Run the following command: # /etc/init.d/pmxs start 33. Re-enable the server (right-click on the server and select Enable). 34. Repeat steps 17 through 33 on each remaining server. All servers are now running Matrix Server 3.1.2 in 64-bit mode. Matrix Server 3.0.1 Without MxFS-Linux This procedure is a double upgrade. The first upgrade takes the operating system to SLES9 SP2 in 32-bit mode and installs Matrix Server.
Chapter 4: Double Upgrade Procedures 41 5. If the Matrix Server Support RPM is installed, uninstall it: # rpm -e pmxs-sles9-support 6. Uninstall any Matrix Server patches installed on the server: # rpm -e pmxs-patch 7. Uninstall Matrix Server 3.0.1 from the server. This step does not remove your existing matrix configuration or log files. The matrix software must be uninstalled from a location outside of the matrix directory structure (/opt/polyserve).
Chapter 4: Double Upgrade Procedures 42 11. If you did a fresh installation of the operating system, extract the backup tar files saved in step 1 to /etc/opt/polyserve and /var/opt/ polyserve. 12. Install Matrix Server 3.1.2 from the Matrix Server product CD or the location where you have downloaded the software. Be sure to install the RPM for the 32-bit architecture. # rpm -i /pmxs-3.1.2-.i586.rpm 13. Install the Management Console: # rpm -i /mxconsole-3.1.2-.i586.
Chapter 4: Double Upgrade Procedures 43 The following message then appears: Stopping PolyServe Matrix Server This server needs to be rebooted before the product removal can proceed. /etc/init.d/pmxs has been moved to /etc/init.d/Pmxs to avoid PolyServe Matrix Server from starting automatically on boot. error: %preun(pmxs--release) scriptlet failed, exit status 1 Reboot the server and run the rpm -e command again. Matrix Server will now be uninstalled.
Chapter 4: Double Upgrade Procedures 44 27. Install the Management Console: # rpm -i /mxconsole-3.1.2-.i586.rpm 28. Copy your new license file to /etc/opt/polyserve/licenses/license on the server. 29. If you did a fresh installation of the operating system, recreate mount points for the PSFS filesystem. 30. Start Matrix Server on the upgraded server. Run the following command: # /etc/init.d/pmxs start 31. Repeat steps 17 through 30 on the remaining servers.
Chapter 4: Double Upgrade Procedures 45 2. Back up the Matrix Server configuration on the node being upgraded as described under “Back Up the Existing Matrix” on page 2. 3. Stop Matrix Server on the server: # /etc/init.d/pmxs stop 4. If the following Matrix Server configuration files have been modified at your site, save copies of the files. After the second installation of Matrix Server, you can merge your local changes into the new versions of the files. /etc/polyserve/mxinit.conf /etc/polyserve/scl.
Chapter 4: Double Upgrade Procedures 46 The following message then appears: Stopping PolyServe Matrix Server This server needs to be rebooted before the product removal can proceed. /etc/init.d/pmxs has been moved to /etc/init.d/Pmxs to avoid PolyServe Matrix Server from starting automatically on boot. error: %preun(pmxs--release) scriptlet failed, exit status 1 Reboot the server and run the rpm -e command again. Matrix Server will now be uninstalled.
Chapter 4: Double Upgrade Procedures 47 16. Install the MxFS-Linux support RPM from the MxFS-Linux product CD or the location where you have downloaded the software. # rpm -i /mxfs-sles9-support-3.1.2-.i386.rpm Then install MxFS-Linux 3.1.2 from the product CD or the location where you have downloaded the software. # rpm -i /mxfs-3.1.2-.i386.rpm 17. Copy your new license file to /etc/polyserve/licenses/license on the server. 18.
Chapter 4: Double Upgrade Procedures 48 26. Repeat steps 23 through 25 until all of the nodes have been upgraded. 27. On the node that was upgraded first, run the following command: # ./mxfsmigrate.sh --end All servers in the matrix are now running Matrix Server 3.1.2 in 32-bit mode. Next, repeat the rolling upgrade as described in the following steps. 28. Disable the server to be upgraded (start with the server with the highest IP address). Right-click on the server and select Disable. 29.
Chapter 4: Double Upgrade Procedures 49 PolyServe Matrix Server from starting automatically on boot. error: %preun(pmxs--release) scriptlet failed, exit status 1 Reboot the server and run the rpm -e command again. Matrix Server will now be uninstalled. NOTE: When the uninstall is complete, you will see a message listing files and directories that could not be removed. Do not manually remove any of these files. 34. Uninstall the Management Console: # rpm -e mxconsole 35.
Chapter 4: Double Upgrade Procedures 50 Then install MxFS-Linux 3.1.2 from the product CD or the location where you have downloaded the software. # rpm -i /mxfs-3.1.2-.x86_64.rpm 42. Copy your new license file to /etc/polyserve/licenses/license on the server. 43. If you did a fresh installation of the operating system, recreate mount points for the PSFS filesystems. 44. Start Matrix Server on the upgraded server. Run the following command: # /etc/init.d/pmxs start 45.
Chapter 4: Double Upgrade Procedures 51 2. Run the command exportfs -ua on each server where the filesystem will be unmounted. 3. Unmount the filesystem from the servers. If you see a “device busy” message, run the exportfs -ua command again and then repeat the unmount operation. Matrix Server 2.7.2 This procedure is a double upgrade. The first upgrade takes the operating system to RHEL4 or SLES9 SP2 in 32-bit mode and takes Matrix Server to 3.1.2. When all servers are running Matrix Server 3.1.
Chapter 4: Double Upgrade Procedures 52 6. Uninstall any Matrix Server software patches from the server. The Matrix Server 2.7.2 product updates contained patches to the Matrix Server software. If a 2.7.2 patch is currently installed, use the following command to remove it. # rpm -e pmxs-patch 7. Uninstall PolyServe Matrix Server. This step does not remove your existing matrix configuration or log files.
Chapter 4: Double Upgrade Procedures 53 12. Install Matrix Server 3.1.2 from the Matrix Server product CD or the location where you have downloaded the software. Be sure to install the 32-bit version of the RPM. # rpm -i /pmxs-3.1.2-.i586.rpm 13. Install the Management Console: # rpm -i /mxconsole-3.1.2-.i586.rpm 14. If you did a fresh installation of the operating system, recreate mount points for the PSFS filesystems. 15.
Chapter 4: Double Upgrade Procedures 54 Stopping PolyServe Matrix Server This server needs to be rebooted before the product removal can proceed. /etc/init.d/pmxs has been moved to /etc/init.d/Pmxs to avoid PolyServe Matrix Server from starting automatically on boot. error: %preun(pmxs--release) scriptlet failed, exit status 1 Reboot the server and run the rpm -e command again. Matrix Server will now be uninstalled.
Chapter 4: Double Upgrade Procedures 55 28. Install the Management Console: # rpm -i /mxconsole-3.1.2-.i586.rpm 29. Copy your new license file to /etc/opt/polyserve/licenses/license on the server. 30. If you did a fresh installation of the operating system, recreate mount points for the PSFS filesystems. 31. Start Matrix Server on the upgraded server. Run this command: # /etc/init.d/pmxs start 32. Repeat steps 18 through 31 on the remaining servers.
A Install the RHEL4 Operating System and Kernel Install the Operating System and Kernel Before installing Matrix Server, you will need to complete these steps: 1. Install Red Hat Enterprise Linux AS/ES 4. 2. Either compile a new kernel from source or install a binary kernel. If you want to use the kernel patches provided with Matrix Server, you will need to compile the kernel. 3.
Appendix A: Install the RHEL4 Operating System and Kernel 57 1. Install the Operating System The operating system must be installed on each server that will be in a matrix. When you perform the installation, do not place any operatingsystem files on the SAN disks. To ensure that files are not installed on these disks, you can either unplug the HBA card from the FC switch or unplug the SAN connection before starting the installation.
Appendix A: Install the RHEL4 Operating System and Kernel 58 2. Compile a New Kernel or Install a Binary Kernel Matrix Server requires a supported Red Hat Linux kernel. See “Supported Operating Systems” on page 5 for a list of the supported RHEL4 kernels. You will need to determine whether to compile a new kernel from source or to install a binary kernel. Matrix Server includes patches that fix problems with the RHEL4 kernel.
Appendix A: Install the RHEL4 Operating System and Kernel 59 4. Modify the EXTRAVERSION variable to identify the patched Matrix Server kernel. The variable is located in the Makefile in the directory / usr/src/linux-. The variable specifies the portion of the kernel name that follows the kernel version number (2.6.9 in our example). The variable must be set to the name used by the binary RHEL4 kernel. This is typically the build number.
Appendix A: Install the RHEL4 Operating System and Kernel 60 /usr/src/polyserve directory contains the version of the kernel that you are building. To install the PolyServe kernel patches, complete these steps: 1. Run the following command: # /usr/src/polyserve/mxpatch -i A message stating that the kernel patches are being applied should now appear. 2.
Appendix A: Install the RHEL4 Operating System and Kernel 61 • ps_config.athlon. Uniprocessor systems using an Athlon chip. • ps_config.athlon-smp. SMP systems using the Athlon chip. The files provided for the 64-bit kernel are: • ps_config.x86_64. Uniprocessor systems using a 64-bit processor. • ps_config.x86_64-smp. SMP systems using a 64-bit processor. Copy the configuration that is appropriate for your server: # cp /usr/src/polyserve//configs/ .
Appendix A: Install the RHEL4 Operating System and Kernel 62 3. HBA Drivers and Matrix Server When configuring the operating system, you will need to consider whether the HBA driver should be loaded either during the initial booting of the kernel or when Matrix Server is started. The following scenarios describe the appropriate action for common Matrix Server configurations. You may need to take certain steps to ensure that the HBA driver is booted at the correct point.
Appendix A: Install the RHEL4 Operating System and Kernel 63 SAN Boot Disk With certain storage arrays, the boot disk can be on the SAN. In this case, the HBA driver must be loaded with the kernel so that the boot disk can be located. (You may need to take steps to ensure that the appropriate HBA driver is loaded. See your vendor documentation for more information.) You will need to use non-fabric fencing with this configuration.
Appendix A: Install the RHEL4 Operating System and Kernel 64 4. Modify System Files You may need to modify the following files on each server: • /etc/hosts file. Red Hat Linux places both localhost and the server name on the 127.0.0.1 entry in the /etc/hosts file: 127.0.0.1 localhost servername Matrix Server requires that the server name appear on a separate line with its real IP address, as in the following example. Be sure to move the server name to its own line in the /etc/hosts file on each server.
Appendix A: Install the RHEL4 Operating System and Kernel 65 – If you want Matrix Server to load the HBA driver, you may need to modify the /etc/modprobe.conf file. In the file, look for entries such as the following for scsi_hostadapter. alias scsi_hostadapter qla2x00 alias scsi_hostadapter1 aic7xxx alias scsi_hostadapter2 ...
Appendix A: Install the RHEL4 Operating System and Kernel 66 5. Run mkinitrd If Necessary If you edited the /etc/modprobe.conf file in the previous step, you will need to run mkinitrd to create a new initrd image with the appropriate drivers. 1. Check the /boot directory for an initrd image for the kernel you just installed. Remove the image if it exists in the directory. 2. Run the following command from the /usr/src/linux-2.
Appendix A: Install the RHEL4 Operating System and Kernel 67 When Matrix Server is uninstalled, it takes these actions to remove the psfs policy information: 1. Removes the psfs policy line from the following file: /etc/selinux/targeted/source/policy/genfs_contexts 2. Rebuilds the binary policy file and installs it in: /etc/selinux/targeted/policy/policy.* 3. Reloads the kernel with the new policy information. Build a Debug Kernel For a normal installation, you should build the standard kernel.
B Install the SLES9 Operating System and Kernel Install the Operating System and Kernel Before installing Matrix Server, you will need to perform the following steps: 1. Install SuSE Linux Enterprise Server Version 9. 2. Either compile a new kernel from source or install a binary kernel. If you will be using MxFS-Linux or you want to use the kernel patch provided with Matrix Server, you will need to compile the kernel. 3.
Appendix B: Install the SLES9 Operating System and Kernel 69 1. Install SuSE Linux Enterprise Server Version 9 SuSE Linux Enterprise Server Version 9 must be installed on each server in the matrix. Following are some considerations for the installation. • Do not place any operating-system files on the SAN disks. To ensure that files are not installed on these disks, you can either unplug the HBA card from the FC switch or unplug the SAN connection before starting the installation.
Appendix B: Install the SLES9 Operating System and Kernel 70 2. Install a Supported Kernel See “Supported Operating Systems” on page 5 for a list of the supported SLES9 kernels. To check your current kernel version, run the following command: # uname -rv You will need to determine whether to compile a new kernel from source or to install a binary kernel. You will need to compile the kernel if you will be installing either (or both) of the following: • The MxFS-Linux product. • The PolyServe kernel patch.
Appendix B: Install the SLES9 Operating System and Kernel 71 To install the Support RPM, mount the Matrix Server CD or go to the location where you downloaded the software and then run the following command. Be sure to use the version of the RPM that corresponds to your architecture (i586 for 32-bit or x86_64 for 64-bit). # rpm -i /pmxs-sles9-support-3.1.2-..rpm The installation creates a subdirectory in /usr/src/polyserve for each kernel provided in the RPM.
Appendix B: Install the SLES9 Operating System and Kernel 72 2. The Matrix Server Support RPM includes sample configuration files that are recommended for use with the Linux kernel and Matrix Server. The files are based on the configuration files included with the SLES9 binary kernel and are placed in the directory /usr/src/polyserve/ /configs. The files for the 32-bit kernel are as follows: • ps_config.default. The standard kernel. • ps_config.smp. Kernel with multiprocessor support. • ps_config.
Appendix B: Install the SLES9 Operating System and Kernel 73 NOTE: Do not attempt to apply the 90_mxfs.patch file. This patch file was already applied when you installed the MxFS-Linux patches RPM earlier in this procedure. 4. Complete the kernel configuration and install the kernel.
Appendix B: Install the SLES9 Operating System and Kernel 74 3. HBA Drivers and Matrix Server When configuring the operating system, you will need to consider whether the HBA driver should be loaded either during the initial booting of the kernel or when Matrix Server is started. The following scenarios describe the appropriate action for common Matrix Server configurations. You may need to take certain steps to ensure that the HBA driver is booted at the correct point.
Appendix B: Install the SLES9 Operating System and Kernel 75 SAN Boot Disk With certain storage arrays, the boot disk can be on the SAN. In this case, the HBA driver must be loaded with the kernel so that the boot disk can be located. (You may need to take steps to ensure that the correct HBA driver is loaded. See the vendor documentation for more information.) You will need to use non-fabric fencing with this configuration.
Appendix B: Install the SLES9 Operating System and Kernel 76 4. Modify System Files You may need to modify the following files on each server: • /etc/hosts file. SuSE Linux places both localhost and the server name on the 127.0.0.1 entry in the /etc/hosts file: 127.0.0.1 localhost servername Matrix Server requires that the server name appear on a separate line with its real IP address, as in the following example. Be sure to move the server name to its own line in the /etc/hosts file on each server.
Appendix B: Install the SLES9 Operating System and Kernel 77 • /etc/sysconfig/kernel file. If the following modules are present in the INITRD_MODULES directive, remove them. lpfc qla2100 qla2200 qla2300 qla2322 qla2xxx qla2xxx_conf qla6312 qla6322 qlogicfc Matrix Server appends these modules to the /etc/hotplug/blacklist file, which specifies modules that should not be automatically loaded by the kernel.
Appendix B: Install the SLES9 Operating System and Kernel 78 5. Run mkinitrd If Necessary If you edited the /etc/sysconfig/kernel file in the previous step, you will need to run mkinitrd to create a new initrd image with the appropriate drivers. 1. Check the /boot directory for an initrd image for the kernel you just installed. Remove the image if it exists in the directory. 2.
