Managing HP Serviceguard Extension for SAP for Linux, December 2013

<date> root@<node> sapdisp.mon[xxx]: (sapdisp.mon,check_if_stopped):
Manual stop in effect for DVEBMGS41
Other functions provided by sapcontrol for instance shutdowns work in a similar way.
The HP Serviceguard Manager displays a package alert (see Figure 12 (page 25)) that lists the
manually halted instances of a package. The SGeSAP software service monitoring for a halted
instance is automatically suspended until the instance is restarted.
An SGeSAP package configuration parameter allows blocking of administrator-driven instance
stop attempts for the SAP startup framework. If a stop operation is attempted, the
sapstartsrv.log file contains the following entries:
trusted unix domain socket user is stopping SAP System …
SAP HA Trace: Reported package name is ERS41SYA
SAP HA Trace: Reported resource name is SYA_ERS41
SAP HA Trace: SAP_HA_FindSAPInstance returns: SAP_HA_OK …
SAP HA Trace: sap_stop_blocked=yes is set in package config
SAP HA Trace: The stop request is blocked by the cluster …
NOTE: 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. Instance status is visualized in the Serviceguard Manager GUI which
continues to provide a full picture of components that are up to the cluster administrators. The
SGeSAP monitoring suspends operation while the instance is manually stopped.
Packages that have several Netweaver instances configured, continue to monitor all the instances
that are not manually halted. If any actively monitored instance fails, it results in a failover and
restart of the whole package.
One of the methods to restart a manually halted instance is to issue the following command:
sapcontrol -nr <instnr> -function Start
Any other startup method provided by SAP's sapcontrol command works in the similar way.
Example of messages added to the package log:
<date> root@<node> sapdisp.mon[xxx]: (sapdisp.mon,check_if_stopped):
Manual start operation detected for DVEBMGS41
<date> root@<node> sapdisp.mon[xxx]: (sapdisp.mon,check_if_stopped):
Resume monitored operation of DVEBMGS41
If the instance fails to start, the service monitor enters the yellow state. The yellow state is printed
as a warning to the package log and displayed as a package alert in the HP Serviceguard
Manager.
<date> root@<node> sapdisp.mon[xxx]: (sapdisp.mon,check_if_stopped):
Resume monitored operation of DVEBMGS41
<date> root@<node> sapdisp.mon[xxx]: (sapdisp.mon,dispmon_monitors):
WARNING: Dispatcher of DVEBMGS41 - monitor state:YELLOW,2
The service monitor remains in yellow state for up to five monitoring intervals. Then, it changes
to red state and fails the package with the next monitoring interval. If another instance halt
operation is issued while the monitor is in yellow or red state, the monitoring is suspended again
and the package failover is prevented. This occurs regardless of whether the manual halt succeeds
or not. It is an effective way to prevent undesirable failovers.
Issuing a Serviceguard package halt is always possible whether or not instances are currently
halted. The halt operation causes the cluster to loose any manually halted state of the package.
28 SAP cluster administration