HP Serviceguard Toolkit for NFS manual FILELOCKMIGRATION1

Page 26

This IP address is the relocatable IP address for the package. NFS clients that mount the file systems in the package use this IP address to identify the server. You must configure a name for this address in the DNS, NIS, or LDAP database, or in the /etc/hosts file.

b)Set the exported directory in nfs1.conf as follows: For nfs1.conf generated on HP Serviceguard A.11.18:

XFS“/cfs1”

For nfs1.conf generated on HP Serviceguard A.11.19:

nfs/hanfs_export/XFS“/cfs1”

In nfs2.conf, set the exported directory to “/cfs2”.

c)By default the service_name is enabled and is set to nfs.monitor. If you want to monitor NFS services by running the NFS monitor script, then change nfs.monitor to a unique name for each package.

service_name

nfs1.monitor

service_cmd

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

service_restart

none

service_fail_fast_enabled

no

service_halt_timeout

0

In nfs2.conf, set the service_name variable to nfs2.monitor. If you do not want to monitor NFS services, comment out the service_name, service_cmd, service_restart, service_fail_fast_enabled and service_halt_timeout variables.

d)To enable File Lock Migration, set the FILE_LOCK_MIGRATION variable to 1: For nfs1.conf generated on HP Serviceguard A.11.18:

FILE_LOCK_MIGRATION1

For nfs1.conf generated on HP Serviceguard A.11.19:

nfs/hanfs_export/FILE_LOCK_MIGRATION1

e)The FLM_HOLDING_DIR variable defines the holding directory associated with the package. Specify the FLM_HOLDING_DIR as below:

For nfs1.conf generated on HP Serviceguard A.11.18:

FLM_HOLDING_DIR"/cfs1/sm"

For nfs1.conf generated on HP Serviceguard A.11.19:

nfs/hanfs_flm/FLM_HOLDING_DIR"/cfs1/sm"

In nfs2.conf, set the variable to “/cfs2/sm”.

f) Specify the package name:

26

Image 26
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