HP Serviceguard Extension for SAP (SGeSAP) manual SGeSAP Modular Package Configuration

package_type failover

:

ip_address …

:

service_name lc<LCSID>knl

service_cmd “/sapdb/<LCSID>/db/sap/lccluster monitor” service_restart 3

All other standard parameters should be chosen as appropriate for the individual setup.

The sgesap/livecache module parameters of the package configuration file are as follows:

lc_system determines the name of the clustered liveCache.

The lc_virtual_hostname specified corresponds to the virtual hostname of the liveCache. For hot standby liveCache systems, this is the same value that gets specified with hss_enable in dbmcli. The virtual hostname is a string value. It is not possible to specify the corresponding ipv4 or ipv6 address instead. If the string is empty, the DNS resolution of the first specified ip_address will be substituted. In this case, the script only works properly if reliable address resolution is available. Domain name extensions are not part of the virtual hostname.

lc_startmode defines the operation mode into which the Liveache should be started automatically as part of a package startup/failover operation. Legal values are

offline = only vserver will be started

admin = Livecache started in admin mode

slow = Livecache started in cold -slow mode

online = Livecache started in online mode

lc_userkey sets the Livecache userkey that is mapped for the operating system level administrator to the Livecache control user (via XUSER settings). The value needs to be set if the default control userkey 'c' is not used.

liveCache Installation Step: LC172

If hss is required, additional hot standby parameters can be set.

A hot standby initialization during startup might require hardware-based copy mechanisms of the underlying storage array. lc_copy_mechanism defines which hardware-based copy mechanism is to be used. Currently the only supported value is businesscopy.

A hot standby Livecache instance does not detect a Livecache shutdown. It won't reconnect to the restarted Livecache master without external trigger. The hot standby cluster package will send this trigger, except lc_standby_restart is set to no.

A hot standby initialization procedure can perform a plausibility check of its storage configuration. Pre-saved ids of LUNs are compared with current ids to prevent that outdated configuration information is used for cloning. This adds to the robustness of the initialization process, but for large implementations it significantly slows down the standby startup. By setting lc_avoid_idcheck to no the check can be turned off.

liveCache Installation Step: LC211

Log in on the primary node that has the shared logical volumes mounted.

Create a symbolic link that acts as a hook that informs SAP software where to find the liveCache monitoring software to allow the prescribed interaction with it. Optionally, you can change the ownership of the link to sdb:sdba.

ln -s /etc/cmcluster/<LCSID>/saplc.mon \ /sapdb/<LCSID>/db/sap/lccluster

liveCache Installation Step: LC216

For the following steps the SAPGUI is required. Logon to the APO central instance as user SAP*. Start transaction /nlc10 and enter LCA for the logical connection.

/nlc10 -> Logical connection -> LCA -> liveCache -> Create/Change/Delete Connection

Change liveCache server name to the virtual IP name for the liveCache and save it.

SGeSAP Modular Package Configuration 103