Managing HP Serviceguard Extension for SAP for Linux, December 2013

…
tkit/nfs/nfs/XFS "-o rw,no_root_squash,fsid=102 *:/export/sapmnt/C11"
…
NOTE: Change the service_name attribute, if it is not unique within the cluster.
3. Run the cmapplyconf –P sapnfs.config command to apply the package.
4. Run the cmrunpkg sapnfs command to start the package.
5.2.5.3 Automount setup
On each NFS client, add a direct map entry /- /etc/auto.direct to the /etc/auto.master
automounter configuration file.
On each NFS client that will mount the /sapmnt/C11 from the NFS server, edit and add the
following to /etc/auto.direct:
/sapmnt/C11 -fstype=nfs,nfsvers=3,udp,nosymlink 192.168.100.99:/export/sapmnt/C11
This is also valid if both the NFS server and the NFS client are on the same cluster node.
NOTE: You can specify the virtual host name nfsreloc, instead of the IP address.
Reload the autofs changes with:
/etc/init.d/autofs reload
For more information about how to specify options and the NFS export string, see HP Serviceguard
Toolkit for NFS version A.03.03.01 for Linux User Guide at http://www.hp.com/go/
linux-serviceguard-docs.
NOTE: If a common sapnfs package already exists it can be extended by the new volume
groups, file systems, and exports instead.
5.2.5.4 Solutionmanager diagnostic agent file system preparations related to NFS toolkit
If a dialog instance with a virtual hostname is installed initially and clustering the instance is done
later, then some steps related to the file system layout must be performed before the SAP installation
starts.
These steps are optional if:
• It is planned to keep all the diagnostic agent installations on the “local” file system or
• The agent is not configured to move with the related dialog instance.
The SAP installation installs a separate diagnostic agent instance for each host of a dialog instance
installation (physical and virtual). Therefore, diagnostic agent and dialog instances are “linked”
via the virtual hostname and shares the same IP address. As a result of this “link”, an agent instance
must move with the related (clustered) dialog instances, if the dialog instances fail over. As described
in chapter 4 “SAP Netweaver cluster storage layout planning” (page 37), the logical volume of
the diagnostic agent also has to fail over.
There is also a SYS directory underneath /usr/sap/DASID. Compared to other SAP installations
this does not contain links to /sapmnt. To have the same diagnostic agent SYS available on all
the cluster nodes, these links must be created and subsequently the /sapmnt/DASID must be
mapped to a NFS-exported directory.
The steps to install file system layout are as follows:
1. Create directory /sapmnt/DASID.
2. Create a link from /usr/sap/DASID/SYS to /sapmnt/DASID.
3. Create a logical volume and filesystem for the files on /sapmnt/DASID.
5.2 Infrastructure setup, pre-installation preparation (Phase 1) 59