PolyServe® Upgrade Guide PolyServe Matrix Server 3.5.1 File Serving Utility™ 3.5.1 for Red Hat Enterprise Linux AS/ES 4.
Copyright © 2006-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 Supported Operating System and Kernels. . . . . . . . . . . . . . . . . . . . . . RHEL4 Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SLES9 Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MxFS-Linux Upgrade Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . Third-Party MPIO Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents iv 4 “All-at-Once” Upgrades Upgrade Matrix Software and Install a New OS . . . . . . . . . . . . . . . . 35 Upgrade Matrix Software Without Reinstalling the OS . . . . . . . . . . 39 Upgrade the Management Console on Clients . . . . . . . . . . . . . . . . . 42 A Install the RHEL4 Operating System Installation Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installation Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1 Overview Upgrades to Matrix Server 3.5.1 are supported from Matrix Server 3.1.2 and 3.5.0. If you are running a different version of Matrix Server, you will first need to upgrade to Matrix Server 3.1.2 or 3.5.0 and then upgrade to 3.5.1. CAUTION: Do not deviate from the upgrade procedures in this document. It is important to complete the upgrade steps exactly as described. Supported Operating System and Kernels Matrix Server 3.5.1 is supported on both RHEL4 and SLES9.
Chapter 1: Overview 2 Linux. The PolyServe kernels are available on MatrixLink in the following binary and source formats: kernel-..rpm For uniprocessor systems kernel-largesmp-..rpm For multiprocessor systems with more than 16 GB of RAM kernel-smp-..rpm For multiprocessor systems kernel-.src.rpm The kernel sources PolyServe also supplies devel packages for these kernels.
Chapter 1: Overview 3 MxFS-Linux sets the parameters in the /etc/sysconfig/nfs file. The original /etc/sysconfig/nfs file is saved as /etc/sysconfig/nfs.pre_mxfs. If the /etc/ sysconfig/nfs file does not exist, it will be created. Third-Party MPIO Software If you are using third-party MPIO software and are upgrading the operating system, reinstall the MPIO software according to the product documentation. Also check the PolyServe Knowledge Base on the PolyServe Web site for articles regarding the product.
Chapter 1: Overview 4 Changes for SanPulse Start Options The names of the SanPulse start options were changed in the Matrix Server 3.5 release. If the sanpulse_start_options line in your mxinit.conf file includes any of the following options, be sure to rename them after upgrading to 3.5.1.
Chapter 1: Overview 5 To restore the Export Group configuration, copy the saved dump file to a directory in the Matrix Server directory structure. Then run the following command in that directory. $ mx --continue --file dump__ NLM State You should also save the state of the Network Lock Manager (NLM), which will be either enabled or disabled.
Chapter 1: Overview 6 server is removed from the matrix, upgraded, and then returned to the matrix. No matrix downtime is required. See Chapter 3. • All-at-once upgrade. This procedure upgrades all servers at once. The matrix must be down during the upgrade procedure. See Chapter 4. Copyright © 1999-2007 PolyServe, Inc. All rights reserved.
2 Single Rolling Upgrades The single rolling upgrade procedures do not require any matrix downtime. Each server is removed from the matrix, upgraded, and then returned to the matrix. If the Management Console is installed on client machines, you will also need to upgrade that software. Rolling upgrades to Matrix Server 3.5.1 are supported only from Matrix Server 3.1.2 and 3.5.0. Rolling Upgrade Considerations You should be aware of the following when upgrading to the Matrix Server 3.5.1 release.
Chapter 2: Single Rolling Upgrades 8 For example, the servers could have the following network interfaces: server srv1: network interfaces 10.10.1.1 and 10.10.2.3 server srv2: network interfaces 10.10.1.2 and 10.10.2.2 server srv3: network interfaces 10.10.1.3 and 10.10.2.1 Run the command mx --numeric server status to determine the IP addresses known to the matrix. In our example, the output is as follows and indicates that srv3 (IP address 10.10.1.3) should be upgraded first. 10.10.1.1 10.10.1.2 10.10.
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.
Chapter 2: Single Rolling Upgrades 10 Upgrade Matrix Software and Install a New OS This procedure is intended for sites that will be doing a fresh installation of the operating system during the upgrade to the 3.5.1 version of Matrix Server and related products. Note the following: • The operating system architecture must be the same before and after the upgrade (either 32-bit or 64-bit).
Chapter 2: Single Rolling Upgrades 11 Ensure that the new kernel is set as the default in the /boot/grub/ menu.lst file. If you need to build a custom kernel, see Appendix C for more information. • SLES9 systems: Follow the steps in Appendix B to install the operating system and kernel. If you will be using MxFS-Linux, you will need to compile a kernel from source. 5. Install Matrix Server 3.5.1 from the Matrix Server product CD or the location where you have downloaded the software.
Chapter 2: Single Rolling Upgrades 12 Next, run the following command to see a list of devices. # cat /proc/partitions Review the output to verify that the SAN is configured as you expect. 12. Reboot the server. 13. Restore the Matrix Server configuration files that you saved in step 3. Also restore the MxFS-Linux configuration files if that product was originally installed. See “Back Up and Restore the Matrix Configuration” on page 3 for more information. NOTE: If your mxinit.
Chapter 2: Single Rolling Upgrades 13 16. If you installed an HBA driver in the previous step, run the following command to load the driver: # /etc/init.d/pmxs load 17. Verify that the server has access to the SAN storage. Run the following command to see a list of devices and review the output to verify that the SAN is configured as you expect. # cat /proc/partitions 18. Check the mount points for the PSFS filesystems on the server, and recreate them if necessary to match the other servers. 19.
Chapter 2: Single Rolling Upgrades 14 Upgrade Matrix Software Without Reinstalling the OS If you are currently running Matrix Server 3.1.2 or 3.5.0 and you will not be installing a new operating system, use these procedures to upgrade to the 3.5.1 release. The procedures include steps to upgrade to a later RHEL4 Update or SLES9 Service Pack and to install a new kernel. Upgrade with MxFS-Linux If your servers are currently running both Matrix Server and MxFS-Linux, use this procedure to upgrade to the 3.
Chapter 2: Single Rolling Upgrades 15 7. If any Matrix Server patches are installed, uninstall them: # rpm -e pmxs-patch 8. 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).
Chapter 2: Single Rolling Upgrades 16 Ensure that the new kernel is set as the default in the /boot/grub/ menu.lst file. If you need to build a custom kernel, see Appendix C for more information. • SLES9 systems: If necessary, upgrade to a supported SLES9 release. Next, install the Matrix Server 3.5.1 Support RPM and the MxFSLinux kernel patches RPM and compile the kernel. See Appendix B for more information. 12. Reboot the server. 13. Edit operating system files if necessary.
Chapter 2: Single Rolling Upgrades 17 17. Install MxFS-Linux from the product CD or the location where you have downloaded the software. # rpm -i /mxfs-3.5.1-..rpm 18. Install the Management Console and mx utility provided in the Matrix Server distribution: # rpm -i /mxconsole-3.5.1-..rpm 19. Install the quota tools RPM. (This RPM is optional). # rpm -i /pmxs-quota-tools-3.13-..rpm 20. If you are upgrading from 3.1.
Chapter 2: Single Rolling Upgrades 18 4. If any Matrix Server patches are installed, uninstall them: # rpm -e pmxs-patch 5. 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).
Chapter 2: Single Rolling Upgrades 19 Ensure that the new kernel is set as the default in the /boot/grub/ menu.lst file. If you need to build a custom kernel, see Appendix C for more information. • SLES9 systems: If necessary, upgrade to a supported SLES9 release and the appropriate kernel. See Appendix B for more information. 9. Reboot the server. 10. Edit operating system files if necessary.
Chapter 2: Single Rolling Upgrades 20 15. Copy your new license file to /etc/opt/polyserve/licenses/license on the server. 16. Start Matrix Server on the server. Run the following command: # /etc/init.d/pmxs start 17. Repeat this procedure on the server with the next-highest IP address. If the PolyServe Management Console software (versions earlier than 3.5.0) is installed on client machines, the software must be upgraded to the 3.5.1 version. See “Upgrade the Management Console on Clients,” below.
3 Double Rolling Upgrades 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 3.1.2. The rolling upgrade does not require any matrix downtime. Each server is removed from the matrix, upgraded, and then returned to the matrix.
Chapter 3: Double Rolling Upgrades 22 For example, the servers could have the following network interfaces: server srv1: network interfaces 10.10.1.1 and 10.10.2.3 server srv2: network interfaces 10.10.1.2 and 10.10.2.2 server srv3: network interfaces 10.10.1.3 and 10.10.2.1 Run the command mx --numeric server status to determine the IP addresses known to the matrix. In our example, the output is as follows and indicates that srv3 (IP address 10.10.1.3) should be upgraded first. 10.10.1.1 10.10.1.2 10.10.
Chapter 3: Double Rolling Upgrades 23 mixed-version cluster is not supported. All servers should be upgraded to 3.5.1 as quickly as possible. • During the upgrade, a mix of servers running 3.5.1 and the older release may have a PSFS filesystem mounted. After the PSFS filesystem has been unmounted on the last node running the older release, the filesystem cannot be mounted on a node running the older release unless it is first unmounted on the nodes running 3.5.1.
Chapter 3: Double Rolling Upgrades 24 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. Disable the server to cause any active Virtual NFS Services to migrate to another server. (Right-click on the server and select Disable). 2. Stop Matrix Server on the server: # /etc/init.d/pmxs stop 3.
Chapter 3: Double Rolling Upgrades 25 The following message then appears: Stopping PolyServe Matrix Server This server needs to be rebooted before Matrix Server can be removed. After the server has been rebooted, execute the 'rpm -e' command. Configuring Matrix Server not to start on boot: ..done '/etc/init.d/pmxs autostart off' has been called to prevent Matrix Server from starting automatically on boot. Reboot the server and run the rpm -e command again. Matrix Server will now be uninstalled.
Chapter 3: Double Rolling Upgrades 26 14. Edit operating system files if necessary. Check the list of files specified in Appendix A (for RHEL4) or Appendix B (for SLES9) and update them if they have not already been modified. 15. 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 32-bit version of the RPM. # rpm -i /pmxs-3.5.1-.i586.rpm 16.
Chapter 3: Double Rolling Upgrades 27 21. Disable the server to be upgraded (start with the server with the highest IP address). Right-click on the server and select Disable. 22. 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. 23. Stop Matrix Server on the server: # /etc/init.d/pmxs stop 24. If you will be doing a fresh installation of the 64-bit operating system, skip to step 27.
Chapter 3: Double Rolling Upgrades 28 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. 27. Uninstall the Management Console: # rpm -e mxconsole 28. Upgrade to the 64-bit version of SLES9 SP3 or RHEL4 Update 3. (For RHEL4, see Appendix A for information about files that need to be modified. For SLES9, see Appendix B.) 29. Install the kernel: • For SLES9 systems, install the Matrix Server 3.5.
Chapter 3: Double Rolling Upgrades 29 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.
Chapter 3: Double Rolling Upgrades 30 Double Upgrade Without MxFS-Linux This procedure should be used only if you are running Matrix Server 3.1.2 on a 32-bit operating system and want to move to Matrix Server 3.5.1 on a 64-bit operating system. The procedure is a double upgrade. The first upgrade installs Matrix Server 3.5.1 on the 32-bit operating system. When all servers are running Matrix Server 3.5.1, the second upgrade is done to take the operating system to 64-bit mode.
Chapter 3: Double Rolling Upgrades 31 7. Uninstall Matrix Server 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). 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 Matrix Server can be removed.
Chapter 3: Double Rolling Upgrades 32 Ensure that the new kernel is set as the default in /boot/grub/ menu.lst file. If you need to build a custom kernel, see Appendix C for more information. • SLES9 systems: Follow the steps in Appendix B to install the operating system and kernel. 11. Reboot the server. 12. 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. 13. Install Matrix Server 3.5.
Chapter 3: Double Rolling Upgrades 33 18. Back up the Matrix Server configuration again. Use tar -cv to create tar files of the /etc/opt/polyserve and /var/opt/polyserve directories. 19. Stop Matrix Server on the server to be upgraded (start with the server with the highest IP address): # /etc/init.d/pmxs stop 20. If you will be doing a fresh installation of the 64-bit operating system, skip to step 23. Otherwise, continue with the following steps. 21. Uninstall Matrix Server 3.5.1 from the server.
Chapter 3: Double Rolling Upgrades 34 24. If you did a fresh installation of the operating system, extract the backup tar files saved in step 16 to /etc/opt/polyserve and /var/opt/ polyserve. 25. Install the kernel: • For SLES9 systems, install the Matrix Server 3.5.1 Support RPM (use the 32-bit version) and the MxFS-Linux kernel patches RPM and then compile the kernel. See Appendix B for more information. • For RHEL4 systems, install the appropriate PolyServe binary kernel.
Chapter 3: Double Rolling Upgrades 35 29. Install the Management Console: # rpm -i /mxconsole-3.5.1-..rpm 30. Install the quota tools RPM. (This RPM is optional). # rpm -i /pmxs-quota-tools-3.13-..rpm 31. If you did a fresh installation of the operating system, recreate mount points for the PSFS filesystem. 32. Start Matrix Server on the upgraded server. Run this command: # /etc/init.d/pmxs start 33. Repeat steps 18 through 31 on the remaining servers.
4 “All-at-Once” Upgrades This chapter describes how to upgrade all servers at once. The matrix will be down during the upgrade procedure. “All-at-once” upgrades are supported from Matrix Server 3.1.2 and 3.5.0. Upgrade Matrix Software and Install a New OS This procedure is intended for sites that will be doing a fresh installation of the operating system during the upgrade to the 3.5.1 version of Matrix Server and related products.
Chapter 4: “All-at-Once” Upgrades 37 3. Perform a fresh installation of the operating system: • RHEL4 systems: Install the operating system and edit system files as described in Appendix A. Then install the appropriate PolyServe binary kernel. Run the following command: # rpm -ihv .rpm Ensure that the new kernel is set as the default in /boot/grub/ menu.lst file. If you need to build a custom kernel, see Appendix C for more information.
Chapter 4: “All-at-Once” Upgrades 38 7. Install the Management Console and mx utility: # rpm -i /mxconsole-3.5.1-..rpm 8. Install the quota tools RPM. (This RPM is optional). # rpm -i /pmxs-quota-tools-3.13-..rpm 9. Verify that the server has access to the SAN storage. If an HBA driver has not already been loaded, run the following command to load the driver: # /etc/init.d/pmxs load Next, run the following command to see a list of devices.
Chapter 4: “All-at-Once” Upgrades 39 If your system configuration requires a different driver version (either a version included with Matrix Server or a version from another source), you can install that driver version in place of the Matrix Server default version. For more information, see the article “HBA Driver Procedures” in MatrixLink on the PolyServe Web site. Do not start Matrix Server after installing the driver.
Chapter 4: “All-at-Once” Upgrades 40 Upgrade Matrix Software Without Reinstalling the OS This procedure is intended for sites that will not be reinstalling the operating system during the upgrade. The procedure includes steps to update the operating system to a later RHEL4 update or SLES9 service pack and to install a new kernel. Complete the following steps on all servers in the matrix: 1. Stop Matrix Server: # /etc/init.d/pmxs stop 2.
Chapter 4: “All-at-Once” Upgrades 41 7. 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 Matrix Server can be removed. After the server has been rebooted, execute the 'rpm -e' command.
Chapter 4: “All-at-Once” Upgrades 42 • 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.
Chapter 4: “All-at-Once” Upgrades 43 b. Install MxFS-Linux 3.5.1 from the same location. Be sure to install the RPM that corresponds to your architecture (i586 for 32-bit or x86_64 for 64-bit). # rpm -i /mxfs-3.5.1-..rpm 16. Install the quota tools RPM. (This RPM is optional). # rpm -i /pmxs-quota-tools-3.13-..rpm 17. If you are upgrading from 3.1.2, copy your new license file to /etc/opt/ polyserve/licenses/license. 18. Start Matrix Server.
A Install the RHEL4 Operating System Installation Steps Before installing Matrix Server, you will need to complete these steps: 1. Install Red Hat Enterprise Linux AS/ES 4, Update 3 or 4. 2. Determine whether the HBA driver should be loaded either during the initial booting of the kernel or when Matrix Server is started. 3. Modify system files. 4. If necessary, run mkinitrd to build a new initrd image containing the correct driver modules. Installation Procedure 1.
Appendix A: Install the RHEL4 Operating System 45 NOTE: The default Red Hat installation configures firewall rules that prevent the correct operation of Matrix Server. PolyServe recommends that you either select the “No firewall rules” option, or select “Custom” and then ensure that the service ports required by Matrix Server are open. See the Administration Guide for more information about these ports.
Appendix A: Install the RHEL4 Operating System 46 2. 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 47 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 48 To avoid this problem, you will need to modify the mount command specified in the script to enable the root filesystem to be remounted via its device path. Locate the following line in the /etc/init.d/halt script: mount | awk '{ print $3 }' | while read line; do On this line, change $3 to $1. mount | awk '{ print $1 }' | while read line; do • /etc/modprobe.conf file.
Appendix A: Install the RHEL4 Operating System 49 behavior is not desired, the blacklist file can be edited; however, doing this is not recommended. 4. 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 your kernel. Remove the image if it exists in the directory. 2.
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. For iSCSI configurations, build and install the iscsi kernel modules. 4.
Appendix B: Install the SLES9 Operating System and Kernel 51 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 52 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 patches. Matrix Server includes patches that fix problems with the SLES9 kernel. (For a description of the patches, see the section “PolyServe Kernel Patches” in the PolyServe Release Notes.
Appendix B: Install the SLES9 Operating System and Kernel 53 The installation creates a subdirectory in /usr/src/polyserve for each kernel provided in the RPM. Each kernel subdirectory contains the following: • A configs subdirectory containing the sample configuration files for that kernel. • A patches subdirectory containing any PolyServe kernel patches for that kernel. These patches are automatically applied when the RPM is installed.
Appendix B: Install the SLES9 Operating System and Kernel 54 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.bigsmp. Kernel with support for SMP and large memory. • ps_config.debug. Debug version of the kernel. The files for the 64-bit kernel are as follows: • ps_config.default. The standard kernel. • ps_config.smp. Kernel with multiprocessor support. • ps_config.debug. Debug version of the kernel.
Appendix B: Install the SLES9 Operating System and Kernel 55 Now run the following command to patch the .config file: # ./patch_config mxfs_patchlist /usr/src/linux/.config 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 56 make: Leaving directory '/usr/src/linux-2.6.5-7.252' Refer to the linux-iscsi RPM for the user-side control daemon and configuration. 4. 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.
Appendix B: Install the SLES9 Operating System and Kernel 57 to load its own HBA driver. (You may need to take steps to ensure that the appropriate HBA driver is loaded. See your vendor documentation for more information.) 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.
Appendix B: Install the SLES9 Operating System and Kernel 58 hostnames include the hostnames of all servers in the matrix and the hostnames of all FibreChannel switches being used with the matrix. One easy way to ensure reliable hostname lookups is to put all critical hostnames and their IP addresses in /etc/hosts on each of the servers (see the hosts(5) man page.) After you have done this, ensure that the host lookup order in /etc/nsswitch.
Appendix B: Install the SLES9 Operating System and Kernel 59 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 directory: # mkinitrd For more information about this command, see the mkinitrd(8) man page. 7. Reboot and Verify the Kernel Configuration Reboot the operating system and then verify that the kernel is built and configured correctly.
C Build a RHEL4 Kernel from PolyServe Sources This appendix describes how to install and compile a RHEL4 kernel using a PolyServe source kernel. NOTE: If you will be using Oracle, the name of the kernel cannot be longer than 29 characters. This restriction is caused by an issue with the Oracle installer. Install the Kernel PolyServe provides 2.6.9-based source kernels on Matrix Link. These kernels include the PolyServe kernel patches.
Appendix C: Build a RHEL4 Kernel from PolyServe Sources 61 3. Run the following command on the spec file: # rpmbuild -bp --target= kernel-2.6.spec 4. Copy the kernel source tree to /usr/src: # cp -a /usr/src/redhat/BUILD/kernel-2.6.9/linux-2.6.9 /usr/src 5. Create a symbolic link to the kernel source tree for the “linux” common name. # ln -s /usr/src/linux-2.6.9 /usr/src/linux 6.
Appendix C: Build a RHEL4 Kernel from PolyServe Sources 62 1. Go to the /usr/src/linux- directory on the server and run the make mrproper command. # cd /usr/src/linux- # make mrproper 2. Patch the kernel as necessary for your site. 3. The patched Matrix Server kernel includes sample configuration files that are recommended for use with the Linux kernel and Matrix Server.
Appendix C: Build a RHEL4 Kernel from PolyServe Sources 63 5. If you are using grub, the make install step should have updated the grub file. Verify that the correct kernel version is selected as the default. 6. If you are using LILO, you will need to take these steps: a. Set the new kernel to be the default in the /etc/lilo.conf file. You can assign any name to the kernel. b. Add a section for the new kernel to the /etc/lilo.conf file. The “image” line specifies the location of the kernel.
