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

failover. The SGeSAP monitor postpones monitoring activities while the instance is manually
stopped.
The SGeSAP monitor postpones monitoring activities while the instance is manually stopped. The
Serviceguard package continues to run and does not failover.
NOTE: To use this feature you must add SGeSAP HA library parameters to the SAP instance
profile.
If SGeSAP service monitors are configured to verify the performance of SAP Netweaver software,
special care must be taken when stopping and starting clustered Netweaver instances while the
SGeSAP package is running. Only if the SGeSAP HA library is configured in the SAP instance
profile, SAP system administrators can stop and restart clustered Netweaver instances without
interacting with the cluster software explicitly.
NOTE: For more information on how to configure the SGeSAP HA library for any SAP instance,
see installation steps MS405 and OS110.
During startup of the instance startup framework, a SAP instance with the SGeSAP HA library
configured , prints the following messages in the sapstartsrv.log file located at the instance
work directory:
SAP HA Trace: HP SGeSAP<versioninfo> (SG) <versioninfo> cluster-awareness
SAP HA Trace: Cluster <clustername> is up and stable
SAP HA Trace: Node <hostname> is up and running
SAP HA Trace: SAP_HA_Init returns: SAP_HA_OK ...
During startup of the instance startup framework, a SAP instance without the SGeSAP HA library
configured, prints the following message in the sapstartsrv.log file located at the instance
work directory:
No halib defined => HA support disabled
NOTE: Within a single Serviceguard package it is possible to mix instances having HA library
configured with instances not having HA library configured.
Subsequent startup or shutdown of an instance triggers the startup framework to dynamically
discover a package that has the instance configured. A corresponding sapstartsrv.log entry
is as follows:
SAP HA Trace: Reported package name is <packagename>
While the cluster package is running, <sid>adm can issue the following command for a SAP
instance with HA library configured:
sapcontrol -nr <instancenr> -function Stop
The SAP instance shuts down as if there is no cluster configuration. The cluster package continues
to run and the filesystems remain accessible. Depending on the service monitors that are configured
for the instance, one or more operations are logged to the package logfile
/var/adm/cmcluster/log/<packagename>.log in the subsequent monitoring intervals.
<date> root@<node> sapdisp.mon[xxx]: (sapdisp.mon,check_if_stopped):
Manual stop operation detected for DVEBMGS41
<date> root@<node> sapdisp.mon[xxx]: (sapdisp.mon,dispmon_monitors):
Manual stop in effect for DVEBMGS41
Other methods provided by SAP's sapcontrol command for instance shutdown work in the
similar way.
HP Serviceguard Manager displays a package alert that lists the manually halted instances of a
package. The service monitoring for a halted instance is automatically suspended until you restart
the instance.
22 SGeSAP Cluster Administration