Managing HP Serviceguard Extension for SAP for Linux (May 2013)

Table 22 Services on the primary node

RemarksService name

Dispatcher portssapdp<INR>

Dispatcher ports (secure)sapdp<INR>s

Gateway portssapgw<INR>

Gateway ports (secure)sapgw<INR>s

Port for (ABAP) message server for installation <SID>sapms<SID>

SAP hostctrlsaphostctrl

SAP hostctrl (secure)saphostctrls

Oracle listener porttlistsrv

MaxDBsql6

MaxDBsapdbni72

SAP DB2 communication portssapdb2<DBSID>

DB2_db2<dbsid>

DB2_db2<dbsid>_1

DB2_db2<dbsid>_2

DB2_db2<dbsid>_END

NOTE:

• <INR> = 00..99.

• There are no services related to Sybase ASE database in /etc/services. Ports used by

Sybase ASE may be assigned to different services. Those entries should be removed from

/etc/services to avoid confusion.

NFS and automount synchronization

1. Synchronize the automount configuration on all the secondary nodes, if it is not done in Phase

2. Create the mount points for the directories that are used by the NFS package and the automount

subsystem.

For example:

mkdir -p sapmnt/C11

Synchronize the /etc/auto.master and /etc/auto.direct from the primary node to

all secondary nodes.

Reload the autofs with /etc/init.d/autofs reload.

SAP hostagent installation on secondary cluster nodes

It is recommend to have a SAP hostagent installation on each clusternode, even though it is not a

requirement for SGeSAP. Such an installation might exist on these hosts through a previous

installation. If not, it must be installed according to the instructions in SAP note 1031096. The

sapinst used for instance installation may offer an option to install the hostagent. This step can

be executed within or directly after phase 2. Make sure that both the uid of sapadm and the gid

of sapsys are identical in all the cluster nodes.

64 Clustering SAP using SGeSAP packages