HP Serviceguard Toolkit for NFS manual Cluster Status, Node Status State, SG-CFS-DG-1, SG-CFS-MP-1

Page 8

feature functions properly in A.11.18, install the following patch on all servers that will be configured as nodes in the cluster.

PHSS_39484

1.0

Serviceguard A.11.18.00

6.Configuring Serviceguard NFS Legacy Package over CFS Packages

This section describes how to configure and start Serviceguard NFS legacy packages in a Serviceguard over CFS environment. It is assumed that you have already setup your Serviceguard cluster, and have performed the steps listed in the “Before Creating a Serviceguard NFS Legacy Package” section of the Serviceguard NFS Toolkit A.11.11.06, A.11.23.05 and A.11.31.08 Administrator’s Guide to configure the /etc/rc.config.d/nfsconf file, start the NFS server, configure the disk hardware, and setup volume groups, logical volumes, and file systems. It is assumed that you have setup CFS as documented in the Veritas Storage Foundation Cluster File System Installation and Administration Guide, and that you have already started the Serviceguard CFS multi-node packages.

In the following example, the CFS file systems are /cfs1 and /cfs2, and they correspond to Serviceguard CFS multi-node packages SG-CFS-MP-1 and SG-CFS-MP-2. The cluster ASCII configuration file is assumed to be /etc/cmcluster/cluster.conf. The cluster name is cluster1 and there are two nodes, thyme and basil. If you run the cmviewcl command after setting up the Serviceguard CFS packages, the output is similar to the following:

# cmviewcl

CLUSTER STATUS

cluster1 up

NODE STATUS

STATE

 

 

 

thyme up

running

 

 

 

NODE STATUS

STATE

 

 

 

basil up

running

 

 

 

MULTI_NODE_PACKAGES

 

 

 

PACKAGE

STATUS

STATE

AUTO_RUN

SYSTEM

SG-CFS-pkg

up

running

enabled

yes

SG-CFS-DG-1

up

running

enabled

no

SG-CFS-MP-1

up

running

enabled

no

SG-CFS-MP-2

up

running

enabled

no

Create a directory on each server in the cluster to hold all the configuration files (if this directory already exists you should save the contents before continuing):

# mkdir /etc/cmcluster/nfs

The rest of the configuration is dependent upon whether or not the cluster requires file locking (as described in the Issues and Limitations with the current CFS implementation section). If file locking is not required, follow the instructions in section “Serviceguard NFS Legacy Package over CFS Packages without File Locking”. If file

8

Image 8
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 Cluster Status Node Status StateMultinodepackages Package Status State Autorun SG-CFS-DG-1Configuring a Serviceguard NFS export package SG NFS over CFS without file locking# Failoverpolicy Configurednode # Failbackpolicy Manual Runscripttimeout NotimeoutPackagename SG-NFS-XP-1 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