Managing Serviceguard Extension for SAP Version B.05.10, December 2012

Several of the following steps must be repeated on each node. Record the steps completed for
each node as you complete them. This helps identify errors in the event of a malfunction later in
the integration process. The HP-UX configuration task is split into the following sections:
• Directory Structure Configuration—this section adds implementation practices to the architectural
decisions made in the chapter "Storage Layout Considerations." It gives some guidance on
how to achieve the differences in directory structure layout for a clustered SAP system as
compared to a standard installation. Most of these steps in this section are only performed
once on the primary host.
• The primary host is where the SAP Instance was installed. If your database is currently running
on a machine different from this, the database vendor dependent steps will have to be done
on the host where the database was installed.
• Cluster Node Synchronization—there are a couple of changes to the operating system
configuration that were performed during SAP installation on the primary node. To allow the
system to run on other nodes, these changes need to be incorporated in the other cluster
nodes. This section also includes steps to distribute the changes of the directory structure
configuration performed in the section above. Repeat the cluster node synchronization steps
for each node of the cluster that is different than the primary.
• Cluster Node Configuration—this section consists of steps performed on all the cluster nodes,
regardless if the node is a primary node or a backup node. Repeat the cluster node
configuration steps for each node of the cluster.
• External Application Server Host Configuration—this section consists of steps performed on
any host outside of the cluster that runs another ABAP instance of the SAP system. Repeat this
section for each host that has an external application server installed.
Performing some of the iterations in parallel is acceptable. Use caution in any complex setup
situation.
Rather than using the cut and paste mechanism, you can fill out the tables provided by first analyzing
the primary host(s). Afterwards, you can use the tables to synchronize all nodes.
Directory Structure Configuration
This section adds implementation practices to the architectural decisions made in the chapter
"Storage Layout Considerations." If layout option 1 or option 2 is used, then the non-CFS directory
structure conversion must be performed. An implementation based on HP LVM is described in this
document. VxVM can similarly be used. Option 3 maps to the CFS configuration for SAP. In this
case, usage of VxVM and CVM are mandatory.
Cluster Filesystem Configuration
Logon as root to the system where the SAP Central Instance is installed. If the database is installed
on a different host, also open a shell as root on the database machine. Make sure that all SAP
instances and the database were stopped manually.
NOTE: These steps are only required if HP Serviceguard Cluster File System is used for the SAP
instances.
Installation Step: IS009
Verify that the existing disk group layout is compliant with the needs of the Serviceguard package(s)
as specified in the tables for option 3 of chapter “Designing SGeSAP Cluster Scenarios” (page 8) .
All directories that are labeled shared in these tables need to reside on logical volumes on a shared
external storage system. The volume management needs to be VxVM based. The volumes can be
converted using vxvmconvert(1m), if the SAP System was originally installed on HP LVM volumes
instead.
HP-UX Configuration 57