Managing HP Serviceguard Extension for SAP for Linux, December 2013

changes must be reflected in the cluster package configuration. deploysappkgs(1) command
is aware of the existing package configurations and compares them to settings of the SAP
configuration and the operating system.
3.5 Upgrading SAP software
SAP rolling kernel switches can be performed in a running SAP cluster exactly as described in the
SAP Netweaver 7.x documentation and support notes.
Upgrading the application version of the clustered SAP application to another supported version
rarely requires changes to the cluster configuration. Usually SGeSAP detects the release of the
application that is packaged automatically and treats it as appropriate.
A list of supported application versions can be taken from the SGeSAP release note document.
The list of currently installed Serviceguard Solution product versions can be created with the
command
rpm -qa |grep -i serviceguard
For a safe upgrade of SAP with modular-style packages, switch all impacted SGeSAP packages
in package maintenance mode and perform a partial package start before the first SGeSAP specific
module becomes executed. Now, you can manually handle the SAP startup or shutdown operations
during the upgrade without interference from the Serviceguard cluster software.
deploysappkgs(1) and cmcheckconf(1) issued on the existing packages after upgrade give
hints on whether cluster configuration changes are required. Perform failover tests for all potential
failure scenarios before putting the system back in production.
Table 2 Summary of methods that allow SAP instance stop operations during package uptime
Usecase exampleEffectHow achieved?GranularityMethod
SAP rolling kernel switchSAP Instance service
monitoring of the
package is temporarily
suspended for stopped
instances; Stopped
instances cause alerts in
Serviceguard Manager
Ensure that package
parameter setting
sap_stop_blocked is set to
no and is applied. Stop
the instance as <sid>adm
with standard SAP
methods, for example by
calling sapcontrol …
–function Stop
SAP InstanceSAP stop block
deactivation
SAP software version
upgrade
All package service
monitoring is suspended;
Package cannot fail or
switch nodes while in
maintenance mode
cmmodpkg –m on
<pkgname>
Serviceguard
Package
Package
maintenance
mode
non-production SGeSAP
cluster trouble-shooting
All SGeSAP package
service monitoring is
temporarily suspended;
SGeSAP modules are
skipped during package
start
Create debug flag file
touch
debug_<packagename>
in the SG run directory
location, which is
/usr/local/cmcluster/run
on Red Hat and
/opt/cmcluster/run
on SUSE)
SGeSAP PackageSGeSAP debug
flag
Serviceguard patch
installation
Package can fail, but
cannot yet failover
cmhaltnode –dSerivceguard NodeLive Application
Detach
3.6 Package conversion
The deploysappkgs(1) command of SGeSAP/LX A.06.xx can still be used to create
modular-based cluster configuration files for NFS, database, SAP central and SAP replication
32 SAP cluster administration