ASSID[1]=SG1; ASHOST[1]=extern1; ASNAME[1]=D; ASNR[1]=02; ASTREAT[1]=7; ASPLATFORM[1]="HP-UX"

Example 2:

The failover node is running a Central Consolidation System QAS. It shall be stopped in case of a failover to this node.

ASSID[0]=QAS; ASHOST[0]=node2; ASNAME[0]=DVEBMGS; ASNR[0]=10; ASTREAT[0]=8; ASPLATFORM[0]="HP-UX"

The failover node is running the Central Instance of Consolidation System QAS. There are two additional Application Servers configured for QAS, one inside of the cluster and one outside of the cluster. The complete QAS shall be stopped in case of a failover. In this case, ${STOP_DEPENDENT_INSTANCES} is specified for the Central Instance of QAS.

ASSID[0]=QAS; ASHOST[0]=node2; ASNAME[0]=DVEBMGS; ASNR[0]=10; ASTREAT[0]=24; ASPLATFORM[0]="HP-UX"

ASSID[1]=QAS; ASHOST[1]=node3; ASNAME[1]=D; ASNR[1]=11; ASTREAT[1]=8; ASPLATFORM[1]="HP-UX"

ASSID[2]=QAS; ASHOST[2]=extern1; ASNAME[2]=D; ASNR[2]=12; ASTREAT[2]=8; ASPLATFORM[2]="HP-UX"

The Central Instance is treated the same way as any of the additional packaged or unpackaged instances. Use the ASTREAT[*]-arrayto configure the treatment of a Central Instance. For Example, if a Central Instance should be restarted as soon as a DB-package fails over specify the following in sapdb<SID>.config:

ASSID[0]=SG1; ASHOST[0]=node2; ASNAME[0]=DVEBMGS; ASNR[0]=00;

ASTREAT[0]=${RESTART_DURING_FAILOVER}; ASPLATFORM[0]="SG-PACKAGE";

ASPKGNAME="ciSG1"

If you don't restart the SAP Instances during database failover, make sure to turn on the DB-RECONNECTfeature within their profile. Step IS1110 will describe how to achieve that.

Installation Step: LS680

The REM_COMM value defines the method to be used to remotely execute commands for Application Server handling.

It can be set to ssh to provide secure encrypted communications between untrusted hosts over an insecure network.

Information on how to set up ssh for each node refer to Section Cluster Node Configuration.

Default value is remsh.

Example:

REM_COMM=remsh

Installation Step: LS690

Use the AS_PSTART variable to specify the startup procedure of the configured Application Servers.

The default value here is AS_PSTART=1 for parallel startup and AS_PSTART=0 for sequential startup. Be aware that setting AS_PSTART=0 will slow down your total failover time.

Example:

AS_PSTART=1

Optional Step: OS700

If your setup consists of application servers that are significantly slower than the Central Instance host, it is possible that the Central Instance shuts down before application server shutdown is completed.

This can lead to unsafe shutdowns and Instance crash.

To be safe, specify one of the following:

WAIT_OWN_AS=1

the shutdown of all application servers takes place in parallel, but the scripts do not continue before all of these shutdown processes have come to an end.

Legacy Package Configuration 75

Page 75
Image 75
HP Serviceguard Extension for SAP (SGeSAP) ASTREAT0=$RESTARTDURINGFAILOVER ASPLATFORM0=SG-PACKAGE, ASPSTART=1, WAITOWNAS=1