Managing HP Serviceguard Extension for SAP for Linux, December 2013

services of existing clusters if there are SGeSAP/LX A.03.00 legacy configurations. Thus, for the
majority of existing clusters, no additional migration tool is required to move from legacy to modular.
For other cases, like liveCache, SAP external instance and SAP infrastructure tool clusters, the
conversion of SGeSAP/LX 3.xx legacy configurations to SGeSAP/LX A.06.xx module configurations
requires manual steps. Preparatory effort lies in the range of 1 hour per package.
The cmmigratepkg(1) command can be applied to SGeSAP legacy packages. The output file
will lack SAP-specific package configurations of the sap*.config file, but the resulting configuration
file can be used to simplify the creation of a modular SGeSAP package:
cmmakepkg –i cmmigratepkg_output_file -m sgesap/all modular_sap_pkg.config
The configuration of the SGeSAP specific parameters to modular_sap_pkg.config can be
done manually. For more information on configuring modular package configuration, see “Clustering
SAP Netweaver using SGeSAP packages” (page 49).
Caution is required for clusters that have altered unofficial SGeSAP parameters not described in
the official product documentation and in clusters that use customized code as part of the SGeSAP
customer.functions hooks. In these cases, an individual analysis of the required steps is needed.
3.7 SAP HANA cluster administration
The list of administrative operations possible using SGeSAP cluster packages are:
3.7.1 Starting and stopping the primary HANA system
If the primary system is up and running, then the package will start successfully. If not start the
primary package on a node configured as the primary system. The instance and required resources
are subsequently monitored by the cluster. The SAP application servers access the primary HANA
instance through the data network.
Commands to start the package and to enable subsequent failover are:
# cmrunpkg –n <node_1> hdbp<SID>
# cmmodpkg –e hdbp<SID>
To halt the primary package on the node configured as the primary system, run the following
command. This will command stop the instance of the primary system. Once the primary system
is shut down you cannot monitor the node.
# cmhaltpkg hdbp<SID>
Stop or start the local HANA instances with standard SAP tools (HANA studio, HDB, or sapcontrol
CLI commands), even if the package is up or down. The instance monitoring for an active package
distinguishes triggered instance stops from unintended software crashes. During planned instance
downtime, an active package indicates the downtime in the package log file, and Serviceguard
alert notifications are displayed in Service Manager GUI.
Command to view SGeSAP alert:
# sapgetconf alerts
If you start a primary system manually without a primary package, then you cannot access the
production application clients using the network or monitor the cluster. Also, the primary system
does not involve in a cluster failover operation.
3.7.2 Starting and stopping of the secondary HANA system
If the secondary instance is not running, then run the secondary package on the node configured
as a secondary system, this will start the instance of the secondary system. The instance and its
resources are monitored by the cluster.
Command to view the cluster:
# cmmodpkg –e hdbs<SID>
3.7 SAP HANA cluster administration 33