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

• A "fifth" Serviceguard package called masterMDM must also be configured for this
configuration type. It will be used to ensure that cluster-wide the four MDM Serviceguard
packages are started in the correct order: mdbMDM -> mdsMDM -> mdisMDM ->
mdssMDMregardless of on which cluster node they are started. The same is true for stopping
the packages - the reverse order will be used.
• The advantage of Multiple MDM Serviceguard packages is flexibility: it is possible to balance
the load by distributing the MDM servers over cluster nodes - but with the cost of requiring more
steps to install and run the system.
Setup Step: MDM010
Add MDM virtual IP addresses and hostnames to /etc/hosts.
The database will be accessible under the 172.16.11.97/mdbreloc virtual IP address/hostname,
the MDS component under the 172.16.11.95/mdsreloc virtual IP address/hostname and the
MDM NFS files systems under 172.16.11.95/mdmnfsreloc virtual IP address/hostname. MDIS
and MDSS do not require a separate virtual address. Both always connect to the virtual IP address
of the MDS server. A virtual IP address will be enabled on the cluster node where the corresponding
Serviceguard package is started and disabled when the package is stopped.
/etc/hosts
----------
172.16.11.95 mdsreloc # MDM reloc address for MDS
172.16.11.96 mdmnfsreloc # MDM reloc address for NFS
172.16.11.97 mdbreloc # MDM reloc address for DB
172.16.11.98 clunode1 # cluster node 1
172.16.11.99 clunode2 # cluster node 2
Setup Step: MDM020
Run ioscan and insf to probe/install new disk devices .
Scan for new disk devices on the first cluster node (clunode1). In the following example, the
storage used for this configuration is EVA / HSV200 based fibre storage and was already
initialized.
iocan -fnC disk
insf -e
disk 175 0/2/0/0.1.10.0.0.0.2 sdisk CLAIMED DEVICE HP HSV200
/dev/dsk/c12t0d2 /dev/rdsk/c12t0d2
disk 178 0/2/0/0.1.10.0.0.0.5 sdisk CLAIMED DEVICE HP HSV200
/dev/dsk/c12t0d5 /dev/rdsk/c12t0d5
Setup Step: MDM030
Create file systems and mount points on the first cluster node.
The following commands create the LVM file systems and mount points for the MDM components.
The database file system in this configuration has a size of 20 GB (/oracle/MDM), the file system
for the MDM components (/export/home/mdmuser) has a size of 7GB.
NOTE: The file system/export/home/mdmuser will be used by all 3 MDM server components
MDS, MDIS and MDSS.
clunode1:
mkdir /dev/vgmdmoradb
mkdir /dev/vgmdmuser
mknod /dev/vgmdmoradb/group c 64 0x500000
mknod /dev/vgmdmuser/group c 64 0x530000
pvcreate /dev/rdsk/c12t0d2
pvcreate /dev/rdsk/c12t0d5
vgcreate /dev/vgmdmoradb /dev/dsk/c12t0d2
vgcreate /dev/vgmdmuser /dev/dsk/c12t0d5
lvcreate -L 20000 -n lvmdmoradb /dev/vgmdmoradb
Installation and Configuration Considerations for MDM 5.5 in a Serviceguard legacy environment 141