Different SAN switch models can be combined in a cluster configuration. However, if you experience difficulty establishing communication between different switch models, perform the following steps:
1. Disable the SAN switches.
2. On the SAN switches, set the following parameter:
vcencode mode = 1 3. Re-enable the SAN switches.
Installing the Software
The following sections provide information on installing the software components used in a ProLiant Fibre Channel cluster.
Installing the Linux OS and Associated Communications Packages
Before attempting to install the LifeKeeper for Linux software, be sure that the Linux operating system is successfully installed and operational on one server in the cluster.
Perform a system shutdown after the server reboots following the completion of the operating system installation. Refer to the Linux installation instructions for details.
Refer to Appendix A for operating system installation tips.
The LifeKeeper for Linux Installation Support CD provides a set of installation scripts designed to perform user-interactive system setup tasks that are necessary before LifeKeeper for Linux can be installed on the system.
Configuring Shared Storage
Perform the following tasks before creating disk-based application resource hierarchies that enable LifeKeeper for Linux to provide failover protection:
1. Power on one server.
2. Partition the disks and configure the LUNs using the Array Configuration Utility.
Refer to the storage system documentation for detailed instructions.
NOTE: If you are using the SteelEye arrayscan utility to probe all LUNs (the default on Red Hat), and there is only one LUN available on the shared disk array, then that particular vendor and model of disk array may not be included in the arrayscan utility templates file. Remember that LifeKeeper for Linux locks the disks at the LUN level. One LUN may be adequate in an active/standby configuration, but if you are using an active/active configuration, then you must configure at least two separate LUNs so that each server uses a different LUN for its normal storage device.
3. Verify that both servers recognize the shared disks (for example, by using the fdisk command). If Linux does not recognize the LUNs that were created, then LifeKeeper for Linux will not recognize the LUNs.
4. Set up the file systems. The location in which you set up the file systems depends upon the LifeKeeper for Linux configuration:
— Simple pairs or groups—Set up the file systems residing on shared disks from the system you plan to use as the primary server in the LifeKeeper for Linux hierarchy.
— N+1 configurations—For configurations where the standby server supports a number of active servers, create the file systems on the standby server. Be sure that the file systems are mounted on their respective primary servers before configuring LifeKeeper for Linux resource hierarchies.
Refer to the Linux documentation for complete instructions on the administration of file systems.
ProLiant Cluster HA/L100—LifeKeeper® for Linux Installation Guide 3-7
COMPAQ CONFIDENTIAL
Writer: Woody Jernigan File Name: d-ch3 Installing LifeKeeper-Fibre Channel Codename: Tiger Shark Part Number: 304985-001 Last Saved On: 11/8/02 9:28 AM
Installing LifeKeeper for Linux on a Fibre Channel Cluster
Verifying the Network Configuration
Be sure that the network is configured and working properly before installing LifeKeeper for Linux. To verify network operation:
1. From each server, ping the local server and ping the other servers in the cluster.
If the ping fails, then do the necessary troubleshooting and perform corrective actions before continuing.
2. From each server, telnet to the other servers in the cluster. If the telnet fails, then do the necessary troubleshooting and perform corrective actions before
continuing.
3. If the server has more than one network adapter, configure the adapters to be on different subnets. If the adapters are on the same subnet, TCP/IP cannot
effectively use the second adapter.
4. Be sure that localhost is resolvable by each server in the cluster. If DNS is not implemented, edit the /etc/hosts file and add an entry for the localhost name. This entry can list either the IP address for the local server, or it can list the default entry (127.0.0.1). Ping the local server by server name, and ping the other servers in the cluster by server name. If localhost is not resolvable, the LifeKeeper for Linux GUI may not work.
5. If DNS is implemented, verify the configuration to be sure that the servers in the LifeKeeper for Linux cluster can be resolved using DNS.
6. Be sure that the host name of each server is correct and will not change after LifeKeeper for Linux is installed. If you later decide to change the host name of a LifeKeeper for Linux system, follow these steps on all servers in the cluster:
a. Stop LifeKeeper for Linux on all servers in the cluster by entering the command:
$LKROOT/bin/lkstop
b. Change the server host name by entering the Linux hostname command.
c. Before continuing, be sure that the new host name is resolvable by each server in the cluster. Ping the local server by server name, and ping the other servers in the cluster by server name.
d. Run the following command on every server in the cluster to update the LifeKeeper for Linux host name. (Refer to lk_chg_value(1M) for details.)
$LKROOT/bin/lk_chg_value -o oldhostname -n newhostname e. Start LifeKeeper for Linux using the command:
$LKROOT/bin/lkstart
Creating a Switchable IP Address
A switchable IP address is a virtual IP address that can be switched between servers.
It is separate from the IP address associated with the network interface card (NIC) of each server. Applications under LifeKeeper for Linux protection are associated with the switchable IP address so that if there is a failure on the primary server, that IP address switches to the backup server.
If you plan to configure resource hierarchies for switchable IP addresses, you must perform the following tasks on each server in the cluster:
•
•
•
Verify that the computer name is correct and will not be changed.
Verify that the switchable IP addresses are unique by using the ping command.
Edit the /etc/hosts file to add an entry for each switchable IP address.
Refer to the LifeKeeper for Linux IP recovery kit documentation for additional information.
ProLiant Cluster HA/L100—LifeKeeper® for Linux Installation Guide 3-9
COMPAQ CONFIDENTIAL
Writer: Woody Jernigan File Name: d-ch3 Installing LifeKeeper-Fibre Channel Codename: Tiger Shark Part Number: 304985-001 Last Saved On: 11/8/02 9:28 AM
Installing LifeKeeper for Linux on a Fibre Channel Cluster
Installing and Setting Up Database Applications
If the environment includes a protected database application such as Oracle,
Informix, DB2, or MySQL, install the application using the documentation provided with the database. Be sure that the database is on a shared file system and that the configuration files are on a shared file system. The executables may either be on each local or a shared file system.
Although it is possible to install the application after LifeKeeper for Linux is
installed, you should test the application to be sure that it is configured and operating properly before placing it under LifeKeeper for Linux protection. Refer to the specific LifeKeeper for Linux database recovery kit administration guides for additional installation and setup considerations.
Installing LifeKeeper for Linux
The following sections provide information for installing LifeKeeper for Linux on servers with a Red Hat or a SuSE Linux operating system.
Using the LifeKeeper for Linux Installation Support CD
The LifeKeeper for Linux Installation Support CD provides a set of installation scripts designed to perform user-interactive system setup tasks that are necessary before LifeKeeper for Linux can be installed on the system. The Installation Support CD identifies what Linux distribution you are running and, through a series of questions that you answer, installs various packages required to ensure a successful LifeKeeper for Linux installation. It also installs a licensing utilities package that provides utilities for obtaining and displaying the host ID of the server. Host IDs are used to obtain a valid license key for running LifeKeeper for Linux.
Refer to the Installation Support CD README file and the LifeKeeper for Linux release notes for additional information.
IMPORTANT: Be sure that you have installed the public domain korn shell (pdksh) package before inserting the Installation Support CD.
1. Insert the Installation Support CD into the CD-ROM drive.
2. Change to the CD-ROM directory and enter sh setup. The CD-ROM directory to mount varies by Linux distribution. On Red Hat it is usually /mnt/cdrom. On SuSE it is usually /cdrom.
Use one of the following commands if the server is not set up to automatically mount the CD-ROM drive:
mount /mnt/cdrom (Red Hat) or mount /cdrom (SuSE) or
mount /dev/cdrom
3. Text is displayed explaining what is going to occur during the installation procedure. Answer the series of questions asked by the system by entering y for yes or n for no. The type and sequence of the questions are dependent on the Linux distribution.
Read each question carefully to be sure of a proper response. It is recommended that you answer yes to each question in order to complete all the steps required for a successful LifeKeeper for Linux installation.
IMPORTANT: The Installation Support CD may install kernel modules to support shared storage devices or the optional Data Replication and NFS Recovery Kits. If the kernel module installation does not complete properly, refer to the “Troubleshooting” chapter.
4. The last item in the setup script is the installation of the LifeKeeper for Linux licensing utilities. Refer to the section “Obtaining and Installing the License Key” in this chapter for details.
After you have answered all the questions presented by the setup script, it will inform you that the installation was successful.
5. You will be required to reboot the system in order to boot the new kernel that was just installed before installing the LifeKeeper for Linux rpm packages from the LifeKeeper for Linux Core CD.
NOTE: Trace information for execution of the setup scripts is saved in /var/log/LK_install.log.
ProLiant Cluster HA/L100—LifeKeeper® for Linux Installation Guide 3-11
COMPAQ CONFIDENTIAL
Writer: Woody Jernigan File Name: d-ch3 Installing LifeKeeper-Fibre Channel Codename: Tiger Shark Part Number: 304985-001 Last Saved On: 11/8/02 9:28 AM
Installing LifeKeeper for Linux on a Fibre Channel Cluster
Obtaining and Installing the License Key
IMPORTANT: The LifeKeeper CDs in the HA/L100 cluster kit are for a 30-day evaluation period. Go to the SteelEye website at http://licensing.steeleye.com/download/index/php for the evaluation license key. Follow the on-screen instructions
LifeKeeper for Linux requires a unique license key for each server. The license key is a run-time license, which means that you can install LifeKeeper for Linux without it, but the license must be installed before you can successfully start and run LifeKeeper for Linux. An evaluation key is available for a 30-day evaluation period. A
permanent license key is available after LifeKeeper for Linux is purchased from SteelEye.
The Installation Support script installs the Licensing Utilities package that obtains and displays the host ID of the server. The host ID is used to obtain an evaluation or permanent license key. If you are installing a permanent license key, you will also need the authorization code, which is provided after purchasing LifeKeeper for Linux.
To obtain and install the license key for each server in the LifeKeeper for Linux cluster:
1. Obtain the host ID. Make note of the host ID displayed by the licensing utility in the Installation Support setup script. (If you need to obtain the host ID again at a later time, use the command $LKROOT/bin/lmhostid.)
2. The setup script asks if you want to install the license key now.
— Answer yes to start the lkkeyins utility. You will be prompted for the license key, which must be obtained by following steps 3 and 4.
— Answer no to end the setup script. You can install the license key later by running the command $LKROOT/bin/lkkeyins. (Do this after completing steps 3 and 4.)
3. If you are installing an evaluation license, go to
http://licensing.steeleye.com/download/index.php and log in under “To Obtain an Evaluation License.” After logging in, you will be prompted to enter the host ID.
Immediately after providing the necessary information, the license key will be emailed to you.
4. If you are installing a permanent license, go to
http://licensing.steeleye.com/download/index.php and click the License Key link.
Create an account if you do not already have one. After logging in you will be prompted to enter the host ID and authorization code that was provided when you purchased LifeKeeper for Linux. Immediately after providing the necessary information, the license key will be emailed to you.
NOTE: The license key may be a long string. Therefore, if you receive the email on the LifeKeeper for Linux server, you may Edit-Copy the license key and then paste it when prompted by the license key utility (refer to the following step). Otherwise, it is
recommended that you save the license key in a text file and copy the file to the LifeKeeper for Linux server. The license key can be read directly from the file by the lkkeyins utility.
5. Install the license key. If you answered yes in step 2, the lkkeyins utility starts automatically. If you answered no in step 2, then run $LKROOT/bin/lkkeyins. Enter the license key by using one of the following methods:
— Enter a file name containing the license key obtained by email.
— Cut and paste the string from the email file.
— Type the string manually (least desirable option).
6. After entering the license key, press the Enter key a second time. The following message is displayed:
LifeKeeper license key installation was successful!
7. Repeat steps 1 through 6 on the other servers in the cluster.
ProLiant Cluster HA/L100—LifeKeeper® for Linux Installation Guide 3-13
COMPAQ CONFIDENTIAL
Writer: Woody Jernigan File Name: d-ch3 Installing LifeKeeper-Fibre Channel Codename: Tiger Shark Part Number: 304985-001 Last Saved On: 11/8/02 9:28 AM
Installing LifeKeeper for Linux on a Fibre Channel Cluster
Primary Network Interface Changes and New License Key
The host ID used by the license key utility is obtained from the LifeKeeper for Linux server primary NIC. LifeKeeper for Linux checks for a valid license key each time it starts. If the LifeKeeper for Linux server requires a NIC replacement that causes the host ID to change, then the next time LifeKeeper for Linux is stopped, you must obtain a new license key before starting LifeKeeper for Linux again. In this case, contact SteelEye customer support at 1-877-457-5113, or outside of U.S. call international+1-803-461-3970 to obtain a new license key.
Installing the LifeKeeper for Linux Software
Install the LifeKeeper for Linux software on each server in the LifeKeeper for Linux cluster configuration. Each LifeKeeper for Linux server must have the packages necessary to support the configuration requirements, including any optional LifeKeeper for Linux Recovery Kit packages. The LifeKeeper for Linux Core is installed first, followed by the optional recovery software.
You can install LifeKeeper for Linux using any rpm-supported graphical interface or through the command line. This section provides detailed instructions on installing the core package cluster using:
•
•
GnoRPM or kpackage graphical interfaces
The rpm command from the command line—refer to the rpm(8) man page for complete instructions on using the rpm command.
For more information on rpm software, go to www.rpm.org.
NOTE: These installation instructions assume that you are familiar with the Linux operating system installed on the servers.
LifeKeeper for Linux installation considerations include:
Installing LifeKeeper for Linux on the shared storage is not supported. Each server should have its own copy installed on its local disk.
By default, LifeKeeper for Linux packages are installed in the directory /opt/LifeKeeper. Using this default directory is recommended. However, if you must relocate LifeKeeper for Linux, refer to the rpm(8) man page for detailed information on RPM relocation.
If you relocate the LifeKeeper for Linux core package, you must relocate all LifeKeeper for Linux packages, including the distribution enabling packages and recovery kits, into the same directory as the core package. To relocate the distribution enabling packages use the sh setup -d <dir> command.
NOTE: If the setup script has already been run, the distribution enabling package is installed and needs to be removed and reinstalled by entering the
sh setup -d <dir> command to relocate the package.
If you are reinstalling the existing version of LifeKeeper for Linux, remove the old LifeKeeper for Linux packages first. A standard LifeKeeper for Linux installation requires that you redefine any existing resource hierarchies. If you want to retain the current resource hierarchy definitions, refer to the LifeKeeper for Linux release notes.
If you receive the following error message when you are installing LifeKeeper for Linux, you should install/reinstall the LifeKeeper for Linux Installation Support CD:
ERROR:
Cannot find the $LKROOT/config/postinstall-hook file.
Have you installed the LifeKeeper Distribution Enabling package?
ProLiant Cluster HA/L100—LifeKeeper® for Linux Installation Guide 3-15
COMPAQ CONFIDENTIAL
Writer: Woody Jernigan File Name: d-ch3 Installing LifeKeeper-Fibre Channel Codename: Tiger Shark Part Number: 304985-001 Last Saved On: 11/8/02 9:28 AM
Installing LifeKeeper for Linux on a Fibre Channel Cluster
Installing with GnoRPM or kpackage
To install the LifeKeeper for Linux software using GnoRPM or kpackage:
1. Insert the LifeKeeper for Linux CD into the CD-ROM drive. If auto-run is not turned on, open it manually or use the command line options.
— The GnoRPM window will display if auto-run is turned on.
— If you are using kpackage, go to the KDE menu and click the kpackage icon, or run kpackage at the command prompt.
2. Select only the steeleye-lk package and install it first. The LifeKeeper for Linux Core package is required to be installed before the other packages.
— Be sure the Check Dependencies box is checked if you are using kpackage.
— For SuSE users, if you are using a version of kpackage prior to 2.0.1, you should uncheck the Use Scripts box due to a problem with the Use Scripts option that was fixed in 2.0.1.
3. Select the remaining LifeKeeper for Linux packages to install.
— steeleye-lkGUI-<LifeKeeper Version>
— steeleye-lkHLP-<LifeKeeper Version>
— steeleye-lkIP-<LifeKeeper Version>
— steeleye-lkMAN-<LifeKeeper Version>
— steeleye-lkRAW-<LifeKeeper Version> (Optional for applications using raw I/O)
4. Install any LifeKeeper for Linux Recovery Kits and optional software packages from their individual CDs using the preceding steps.
— Do not select the translation table file. RPM will not allow you to highlight or add this file as part of the installation.
— Be sure the Check Dependencies box is checked if you are using kpackage.
5. Repeat steps 1 through 4 for the other servers in the cluster.