Managing HP Serviceguard Extension for SAP for Linux, December 2013

Table 18 SGeSAP use cases for easy package deployment (continued)
ScenarioUse case
For example:
A newly installed ASCS must be part of the existing SCS package.
Easy deployment will add such an ASCS into the existing package,
if it is configured to the same virtual host as the SCS or if option
"combined" is selected.
Add a new SAP instance to an already configured
package
For example:
A new volume group related to a SAP instance must be added.
IPv6 is enabled and the virtual hostname now also has an IPv6
address which must be added. Easy deployment discovers these
new attributes and add them to the appropriate existing SGeSAP
packages.
Update existing package with additionally
required resources
5.2 Infrastructure setup, pre-installation preparation (Phase 1)
This section describes the infrastructure that is provided with the setup of a NFS toolkit package
and a base package for the upcoming SAP Netweaver installation. It also describes the prerequisites
and some selected verification steps.
There is a one to one or one to many relationship between a Serviceguard package and SAP
instances and a one to one relationship between a Serviceguard package and a SAP database.
A package can only serve a maximum of one SAP SID and one DB SID at a time, but SAP SID and
DB SID are not required to be identical.
Common resources on which SAP instances depend must go into a single package and (unless
Serviceguard package dependencies are going to be used) instances depending on these resources
must be configured into the same package later.
5.2.1 Prerequisites
• Volume groups, logical volumes, and file system (with their appropriate sizes) must be setup
according to the storage layout described in Chapter 4“SAP Netweaver cluster storage layout
planning” (page 37).
• Volume groups must be accessible from all cluster nodes.
• The file system mount points must be created on all the cluster nodes.
• Virtual hostnames (and their IP addresses) required for the SAP installation must exist, and
must resolve on all the cluster nodes. This is mandatory for the NFS toolkit package setup. If
the NFS toolkit setup is not used, continue to Infrastructure Setup - SAP base package setup
(Phase 1b).
After completing the steps in this section everything is ready for starting the SAP installation. This
infrastructure consists of:
• A running sapnfs package exporting the relevant file systems (it depends upon the setup
chosen, as NFS may also be part of a SGeSAP package instead of a separate NFS toolkit
package).
• A working automount configuration on all the hosts that will run the SAP instance.
• One or more SGeSAP “base packages” providing the environment for the subsequent SAP
installation.
54 Clustering SAP Netweaver using SGeSAP packages