HP Serviceguard Toolkit for NFS manual Starting a Serviceguard NFS export package

Page 22

e)Set the dependency_name, dependency_condition, and dependency_location variables so that the export package will only run if the Serviceguard CFS multi-node packages are already running. Since there are two CFS file systems in this example, there are also two CFS multi-node packages:

dependency_name dependency_condition dependency_location

dependency_name dependency_condition dependency_location

SG-CFS-MP-1-dep SG-CFS-MP-1=up same_node

SG-CFS-MP-2-dep SG-CFS-MP-2=up same_node

f)Comment out the service_name, service_cmd, service_restart, service_fail_fast_enabled and service_halt_timeout variables.

# service_name

nfs.monitor

# service_cmd

"$SGCONF/scripts/nfs/nfs_upcc.mon"

# service_restart

none

# service_fail_fast_enabled

no

# service_halt_timeout

0

Note: The NFS export multi-node package does not monitor exported file systems (for example if a file system becomes unexported or inaccessible). It checks if the CFS dependent packages have access to the file systems. If the NFS failover package loses access and cannot read or write to the disk, it will fail (the exportfs multi-node package will not fail).

Starting a Serviceguard NFS export package

1. Verify the cluster and package configuration files on each server:

#cmcheckconf -k -v –C /etc/cmcluster/cluster.conf –P\ /etc/cmcluster/nfs_modular/nfs-export.conf

2. Verify and apply the cluster package configuration files on a single server:

#cmapplyconf –v –C /etc/cmcluster/cluster.conf –P /etc/cmcluster/nfs_modular/\ nfs-export.conf

3.Run the export package on a single server with the command:

# cmrunpkg –v SG-NFS-XP-1

4.You can verify if the export package is running with the cmviewcl command. The output is similar to the following:

# cmviewcl

CLUSTER STATUS

cluster1 up

22

Image 22
Contents Serviceguard NFS Toolkit Support for Cluster File System Starting a Serviceguard NFS failover package Integrating Support for CFS into Serviceguard NFS Toolkit Non-CFS Implementation with Package FailoverCurrent SG-NFS over VxFS Support CFS vs. Non-CFS ImplementationSG NFS Servers over VxFS High Availability Issues and Limitations with the Current CFS Implementation Prerequisites Multinodepackages Package Status State Autorun Cluster StatusNode Status State SG-CFS-DG-1Configuring a Serviceguard NFS export package SG NFS over CFS without file lockingPackagename SG-NFS-XP-1 # Failoverpolicy Configurednode # Failbackpolicy ManualRunscripttimeout Notimeout Packagetype MultinodeStarting a Serviceguard NFS export package Haltscripttimeout NotimeoutSG-NFS-XP-1 Configuring a Serviceguard NFS failover package Packagename SG-NFS1Starting a Serviceguard NFS failover package DEPENDENCYCONDITIONSG-NFS-XP-1=UP DependencylocationsamenodePackage Status State Autorun Node SG-NFS1 Package Status State Autorun Node SG-NFS2SG NFS over CFS with file locking NFSFILELOCKMIGRATION=1 Nfs2.conf file set these variables to Starting a Serviceguard NFS failover package Cluster1 up XFS Starting a Serviceguard NFS export package Configuring a Serviceguard NFS failover package Starting a Serviceguard NFS failover package Package Status State Autorun Node SG-NFS1 FILELOCKMIGRATION1 Starting a Serviceguard NFS failover package Thyme Running
Related manuals
Manual 93 pages 19.37 Kb Manual 93 pages 21.07 Kb