Managing Serviceguard NFS for Linux, March 2009

3 Sample Configurations
This chapter gives sample cluster configuration files, package configuration files, package control
script, and NFS control script for configurations supporting the following failover options:
• Failover between multiple active nodes. The sample configuration has three servers and
three Serviceguard NFS packages and supports a three-server mutual takeover. Each server
is the primary node for one package and an adoptive node for the other two packages.
• One adoptive node for two packages. The sample configuration has two packages, each
owned by a different server. A third server is the adoptive node for both packages. This
sample configuration uses the package control option, which prevents the adoptive node
from adopting more than one package at a time.
• Multiple node cascading failover. The sample configuration has three servers and two
packages. One server is the primary node for both packages, and the other two servers are
adoptive nodes for both packages.
• One adoptive node for an NFS package with File Lock Migration. The sample configuration
has two servers and one Serviceguard NFS package. One server is the primary node and
the other server is the adoptive node for the NFS package. This sample configuration enables
the File Lock Migration Feature.
NOTE: Examples in this chapter are Red Hat specific.
The sample configuration files in this chapter show only the configured values. Most of the
comments have been omitted.
Configuring Multiple Nodes to Support Failover of Multiple Packages
This configuration has three servers and three Serviceguard NFS packages. Each server is the
primary node for one package and an adoptive node for the other two packages. Figure 3-1
illustrates this configuration. Dotted lines indicate which servers are adoptive nodes for the
packages. Figure 3-2 illustrates the configuration after host basil fails.
Configuring Multiple Nodes to Support Failover of Multiple Packages 33