Configure HP MC/ServiceGuard cluster configuration on LINUX

Configure linux serviceguard Cluster, configure linux MC Serviceguard Cluster, configure linux cluster serviceguard, setup linux Serviceguard cluster


HP Serviceguard, formerly known as MC/ServiceGuard, is a high-availability cluster software produced by HP that runs on HP-UX and Linux.

This document will guide you to install and configure the 2 node MC Service Guard cluster configuration on Linux

Refer the link for HP Serviceguard Cluster Package Configuration.

Checkout the link to understand the Basic High-Availability Cluster Concepts which is for beginners Click here

My Setup:

Primary Node Server :
Hostname : selva1.learnitguide.net
OS : RHEL 5.4
Node 1 Lan Port 1 : 10.10.10.10 (Connected to swtich for administrator use to manage the server)
Node 1 Lan Port 2 : 172.19.1.10 (Connected directly to Node 2 Lan Port 2 to have a heartbeat link)
MC Service GUARD : Evaluation version 11.19

Secondary Node Server :
Hostname : selva2.learnitguide.net
OS : RHEL 5.4
Node 2 Lan Port 1 : 10.10.10.11 (Connected to swtich for administrator use to manage the server)
Node 2 Lan Port 2 : 172.19.1.11 (Connected directly to Node 1 Lan Port 2 to have a heartbeat link)
MC Service GUARD : Evaluation version 11.19

Installation MC Service guard:

Make sure this package is NOT installed, If it is installed , remove it
rpm -e authd
Download Service guard for linux from HP Site and Install those packages from iso images using rpm -ivh.

[root@selva1 IA32]# rpm –ivh SGLic-6.0-SG11.19.rhel5.i386.rpm
[root@selva1 IA32]# rpm –ivh sg_pidentd-3.0.19-2.i386.rpm
[root@selva1 IA32]# rpm –ivh serviceguard-A.11.19.01-0.rhel5.i386.rpm
After installing the serviceguard-A.11.19.01-0.rhel5.i386.rpm, that will give you the warning as identd daemon not running on this node. So run the identd service

[root@selva1 IA32]# /etc/init.d/identd start
[root@selva1 IA32]# chkconfig identd on

After starting the service and make entry to your path settings in your profile file to find out the Service Guard clusters command, else you need to mention the command path.

If you see your .bash_profile file from your home directory PATH variable will be there as default
PATH=$PATH:$HOME/bin
So append it as
PATH=$PATH:$HOME/bin:/usr/local/cmcluster/bin
And run the command as
[root@selva1 IA32]# source /root/.bashrc
All commands from service guard will be available if you typed just cm and pressing tab twice.

Config file is /etc/cmcluster.conf

Default location will be /usr/local/cmcluster. Do these above installation steps on both the nodes.

Configure the nodes

Make sure you have a proper network configuration with at least two seprerated subnets for Heartbeats or one seperated subnet and make an host entries in /etc/hosts file, because we will define in all cluster config files using the hostname so it should resolve by hostname,
10.10.10.10 selva1.learnitguide.net selva1
172.19.1.10 hb1
10.10.10.11 selva2.learnitguide.net selva2
172.19.1.11 hb2
Go to the default config location for Service Guard /usr/local/cmcluster/conf.

Create the node list,
[root@selva1 IA32]# vi cmclnodelist
like,

selva1 root
selva2 root
Plan for lock lun if you are using 2 node cluster by iSCSI or FC and make a lun
available to the host selva1 and selva2.

[root@selva1 IA32]# fdisk –l
My lock lun is /dev/sdb
Else you can make a Quorum server by below,

Configure a Quorum server

Mount the SGLX CD and install the RPM,
cd x86_x86-64/RedHat5/Serviceguard/IA32
rpm -ivh qs-A.02.00.04-0.rhel5.i386.rpm
Authorize hosts to connect,
vi /usr/local/qs/conf/qs_authfile
like,

selva1.learnitguide.net
selva2.learnitguide.net

Add to init,
mkdir -p /var/log/qs

vi /etc/inittab
like,
qs:345:respawn:/usr/local/qs/bin/qs >/var/log/qs/qs 2>/var/log/qs/qs_error
apply,
telinit q
Check it's up,
ps aux | grep qs
note there should be two listening ports,
netstat -an --inet

e.g.,
...
tcp 0 0 0.0.0.0:60277 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:1238 0.0.0.0:* LISTEN

...
Note. 1238 corresponds to the registered "hacl-qs" service.

In case it says "permission denied", just kill the processes,
pkill qsc
they will restart automaticly and reread the "qs_authfile".

Do the same setup in the second node selva2.

Configuring Cluster configurations:

Go to the directory
[root@selva1 IA32]# cd /usr/local/cmcluster/conf
[root@selva1 IA32]# cmquerycl -v -n selva1 –n selva2 -C mycluster.ascii
[root@selva1 IA32]# vi mycluster.ascii
Change your cluster name as you want and STATIONARY IP and HEARTBEAT IP Correctly.

Check you config file for any errors, if you found any errors, try to correct it.
[root@selva1 IA32]# cmcheckconf –v –C mycluster.ascii
Apply the configuration file,
[root@selva1 IA32]# cmapplyconf –v –C mycluster.ascii
Check the cluster status,
[root@selva1 IA32]# cmviewcl
Both the nodes should be up. If everything goes well, now you can go for creating the cluster packages for your database or application. Package Configuration will give you in next updates.
HP Serviceguard, MC Serviceguard Cluster, Configure linux serviceguard Cluster, configure linux MC Serviceguard Cluster, Step by Step MC Serviceguard Cluster, configure linux cluster, configure linux cluster serviceguard, setup linux Serviceguard cluster
May 29, 2015

Post a Comment

[disqus][facebook][blogger]

Contact Form

Name

Email *

Message *

Powered by Blogger.
Javascript DisablePlease Enable Javascript To See All Widget