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

cmmakepkg –m sgesap/livecache
lc<LCSID>.config
Alternatively, from the Serviceguard Manager Main page, click on Configuration in the menu
toolbar, then select Create a Modular Package from the drop down menu. Click on the yes radio
button following Do you want to use a toolkit? Select the SGeSAP toolkit. In the Select the SAP
Components in the Package table, select SAP Livecache Instances. Then click Next>>.
liveCache Installation Step: LC172
Customize the content of the liveCache package configuration file or follow the package creation
dialog screens of the GUI.
The sgesap/livecache module parameters of the package configuration file are as follows (GUI
labels are given in brackets) :
lc_system (liveCache Name) determines the technical name id of the clustered liveCache, usually
a three letter denominator.
The lc_virtual_hostname (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 (Start Mode) 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 (User Key) 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 need to 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.
Serviceguard Manager will automatically assume that Business copy is used, in case the Enable
Standby checkbox gets selected.
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 monitor saplc.mon
will send this trigger, except lc_standby_restart is set to no. In the Serviceguard Manager
configuration screen, the Enable Standby Restart box needs to be cleared to disable the restart
trigger.
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 (Disable Storage Checks) to no the check can be turned off.
The package should include the sg/service module and specify a package service monitor
saplc.mon, but the Service Command should be given as /sapdb/<LCSID>/db/sap/lccluster
monitor.
liveCache Installation Step: LC211
SGeSAP Modular Package Configuration 129