Specifications

Verifying Network Configuration
1. Partition disks and LUNs. Because all disks placed under LifeKeeper protection must be
partitioned, your shared disk arrays must now be configured into logical units, or LUNs. Use
your disk array management software to perform this configuration. You should refer to your
disk array software documentation for detailed instructions.
Note:
l Remember that LifeKeeper locks its disks at the LUN level. Therefore, 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 hierarchy can
access its own unique LUN.
2. Verify that both servers recognize the shared disks (for example, using the fdisk command). If
Linux does not recognize the LUNs you have created, then LifeKeeper will not either.
3. Create file systems on your shared disks from the system you plan to use as the primary
server in your LifeKeeper hierarchy. Refer to the Linux documentation for complete
instructions on the administration of file systems.
Verifying Network Configuration
It is important to ensure that your network is configured and working properly before you install
LifeKeeper. There are several tasks you should do at this point to verify your network operation:
1. If your server installation has a firewall enabled, you will eitherneed to accommodate the
LifeKeeper ports or disable the firewall. Please refer to the topic "Running LifeKeeper With a
Firewall".
2. From each server, ping the local server, and ping the other server(s) in the cluster. If the ping
fails, then do the necessary troubleshooting and perform corrective actions before continuing.
3. If your server has more than one network adapter, you should configure the adapters to be on
different subnets. If the adapters are on the same subnet, TCP/IP cannot effectively utilize the
second adapter.
4. Ensure 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). If localhost is not
resolvable, the LifeKeeper GUI may not work.
5. If DNS is implemented, verify the configuration to ensure the servers in your LifeKeeper
cluster can be resolved using DNS.
6. Ensure each server’s hostname is correct and will not change after LifeKeeper is installed. If
you later decide to change the hostname of a LifeKeeper system, you should follow these
steps on all servers in the cluster.
a. Stop LifeKeeper on all servers in the cluster using the command:
/etc/init.d/lifekeeper stop-nofailover
26Setting Up Your LifeKeeper Environment