Managing Serviceguard Extension for SAP Version A.06.00 for Linux, December 2012

1. Check if the package will start up on each cluster node, where it is configured.
2. Run showmount –e <sapnfs package ip_address> and verify if name resolution
works.
3. Run showmount –e <virtual NFS hostname> on an external system (or a cluster node
currently not running the sapnfs package) and check the exported file systems are shown.
On each NFS client in the cluster check the following:
• Run cd /usr/sap/trans command to check the read access of the NFS server
directories.
• Run touch /sapmnt/C11/abc; rm /sapmnt/C11/abc command to check the
write access.
NOTE:
• For more information on synchronization with the other cluster nodes, see “NFS and
automount synchronization” (page 63) section.
• For information on the final synchronization of the other cluster nodes with the automount
configuration, see “Post SAP installation tasks and final node synchronization (Phase 3a)”
(page 59) section.
Infrastructure Setup - SAP base package setup (Phase 1b)
This step will finally make the basic infrastructure available to start the SAP installation afterwards,
which includes the instance and database file systems as well as the IP addresses of the virtual
hostnames used for the installation. While there are other manual ways to provide that basic
infrastructure, setting up a Serviceguard package is the recommended way.
SAP base package setup enables the available basic infrastructure to start the SAP installation.
This includes the instance and database file systems as well as the IP addresses of the virtual
hostnames used for the installation. Setting up a Serviceguard package is another recommended
method to set up the basic infrastructure.
There are two ways to set up the initial SAP base package:
1. Set up the package with both Serviceguard and SGeSAP modules.
2. Set up the package with only Serviceguard modules.
Intermediate synchronization and verification of mount points
The procedure for synchronizing mount points are as follows:
• Ensure that all the file system mount points for this package are created on all the cluster nodes
as specified in the prerequisites.
For example:
mkdir /usr/sap/C11/SCS40
Verification step(s):
Invoke cd /usr/sap/C11/SCS40 on all the nodes and test for availability.
SAP base package with Serviceguard and SGeSAP modules
At this stage any SGeSAP modules relevant to the SAP instance can be included into the base
package configuration.
Creating the package with the Serviceguard Manager
NOTE: To create a package you can use either Serviceguard Manager GUI or the CLI. This
section describes the GUI steps and the CLI steps are described in the “Creating the package
configuration file with the CLI” (page 55) section.
Infrastructure setup, pre-installation preparation (Phase 1) 53