Managing HP Serviceguard Extension for SAP for Linux, December 2013

mkdir /home/<sid>adm/.hdb/<local_hostname>
cp /home/<sid>adm/.hdb/<installation node>/SSFS_HDB.DAT
/home/<nw-sid>adm/.hdb/<local_hostname>/SSFS_HDB.DAT
5.4.3 Network services synchronization
During the SAP installation the file /etc/services is updated with the SAP definitions. These
updates must be synchronized with the /etc/services on the secondary nodes. The very first
SAP installation on the primary node creates all the entries for the first four type of entries in
Table 22 (page 71).
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>_1DB2_db2<dbsid>_2DB2_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.
5.4.4 NFS and automount synchronization
1. Synchronize the automount configuration on all the secondary nodes, if it is not done in Phase
1.
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.
5.4.5 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
5.4 Post SAP installation tasks and final node synchronization (Phase 3a) 71