Configuring 4 Node Cluster using MC Service Guard

[Vimal Upreti]

Hi
I'm quite new to HP-UX. So this query is bit generic & lengthy.
I have to configure 4 Node Cluster using MC Service Guaard. Following are the details:

a. 3 Nodes will be active & 4th Node will be standby for all the 3.
b. Each Server/Node will have 6 NICs, 2 for External Network, 2 for Internal & 2 for Heartbeat with Failover option in all 3 Networks.
c. 2nd Node will be actually accessed by External Network. So its NICs for External Network has to be active but other 3 Nodes External Interfaces will be down. In case of failover External Interfaces of Standby Server should become Active.
d. Ist Node will run 6 Application Packages, 2nd Node 2 Application Package & 3rd Node will run 4 Application Packages
e. Each Application Package is associated with Oracle Database.

Now in this scenario, can somebody provide me the configuration steps, Scripts for failover or Best practices papers.

Thanks in advance.
Vimal

[Devender Khatana]

Hi Vimal,

Checked the attached doc.

HTH,
Devender

[Bharat Katkar]

Hi Vimal,.
Devendar has provided you a nice doc. Just go through it thoroughly and map it to your setup.
You can also visit www.hp.docs.com for more detail information.
Wish you all the best.
Regards,

[Thayanidhi]

Hi Vimal,

The network configuration you are looking for looks highly complex.
You can define multiple hearbeat (and data) lans, but you cannot make which adaptor to failover to which adaptor! For example you cannot define lan2 to failover to lan4 only. When ever any lan fails it fails over to any standby lan!
Your packages always has a logical IP (e.g. lanx:1), So, when package moves to another node, the target node should already have same subnet to bound.

I suggest you combine internal and external network by some means.

May be I am wrong!

Regds
TT

[Duncan Edmonstone]

Vimal,

You sure like going in at bthe deep end don't you... If you're new to HPUX, a 4 node serviceguard cluster is NOT where you should be starting. I would *strongly* suggest that you go on some training in serviceguard before attempting this - one of the first and most important best practices is that you are trained to do the job in hand!

The network configuration you have described however isn't going to work with Serviceguard... for example if a package runs on host A out of a given subnet , and you want that package to be able to run on host B, then that host must have an active IP interface on that subnet, even when it isn't running the package - otherwise how would the node know that it *can* run the package and connect to that subnet? These are excatly the sort of issues that a Serviceguard course would resolve... meanwhile a good place to start is the Serviceguard documentation here:

http://docs.hp.com/en/ha.html#Serviceguard

HTH

Duncan

[Vimal Upreti]

Many thanks to Devender for providing a nice & most appropriate document on 2 Node SG.
Though recently I have completed 5 Days course from HP-H6487S (Hands-On with MC/ServiceGuard) but it was just a basic course mostly covers 2 Node Clustering with 2-3 NICs.
After reading Devender's Doc. things are clearer. I have some queries for 4 Node Cluster:
a. There are approx. 12 VGs in EVA3000 for 12 (6+2+4)Applications. 4th Node will act as a Spare Node for failover of any 3 active Nodes. In this scenario, Do I need to export & import MAP file of all 12 VGs in all 4 Nodes or Only on the (4th) Spare Node.
b. On the Network Side there are 3 types of dual Interfaces (External, Internal & Heartbeat). All 4 Nodes will have active Internal & Heartbeat LAN but Only 2nd Node will have External LAN also active. This is for security from Outside. (Outside world will access only 2nd Node)
i. Now in this situation Can Package Failover be possible?
ii. How can the External LAN of Spare Node (4th) will become active in case of Failover of 2nd Node?

Please do let me know if the query is not clear.

Thanks again.
Vimal

[Devender Khatana · Accepted solution]

Hi Vimal,

Thanks for the appreciation.Also the value of posts is accessed by points you assign to replies to your threads with relevance of the replies.

If you want all packages to run on all four nodes when required, you require to import all vg's to all hosts.
Moreover , If you want to switch packages to only standby node then importing VG's only standby node would be enough. Moreover every node is SG will have all three IP's and the public IP is given to a package so that in case of fail over it is accessible for the appropriate node where package is running.
I think you are confused with external, internal & heartbeat IP.

Actually you need to populate package IP for user traffic.

Also what about your plans of quorum server. Have you planned for that.

HTH,
Devender

[Vimal Upreti]

Hi Devender,
I think I got your point. Please correct me if I 'm wrong:
a. There will be IP address associated with each Application (Package). This IP address should be of the same range which is given to public LAN.
b. There will be 12 IP addresses for 12 Application Packages.
c.In this situtaion we cannot configure an External LAN for outside world, since this will be of different Subnet & there will be no communication with external LAN to the Package IP Address.

i. Regarding Quroum Server, I was planning to allocate one of the VG on SAN i.e. (VG01) as Lock Disk. Do you feel this is correct?
ii. If I export & import of all the 12 VGs in all the Nodes, Is there any harm? Since for VG01, I have to do export/import in all the Nodes for Quorum Disk.
Moreover of manual failover in case of 2 Node failure, it will reduce extra efforts for migrating VGs.

Please advice.

Thanks again.
Vimal

[Bharat Katkar]

"b. There will be 12 IP addresses for 12 Application Packages.
c.In this situtaion we cannot configure an External LAN for outside world, since this will be of different Subnet & there will be no communication with external LAN to the Package IP Address."

There will be communication of external LAN on Package IP adress provided you do proper Routing Configuration.

If the router is configured to allow external LAN to access the Package IP address Subnet then it can access and you decide to whom you want to allow access to.

Regards,