Thursday, October 17, 2013

Using Alternate Methods for Creating Heartbeat Rings in SecureGuard in HP-UX Clusters

www.unixbabuforum.inWe're working with HP in configuration of one HP9000 rp8420 for our SAP environment consisting of several vPars for SAP CI/DB and APP. My customer wants to implement SecureGuard as Cluster for some vPars to give high availability to the design. 
Now HP engineers are talking about a very huge amount of Ethernet ports in order to implement such clusters, they said that at least two heartbeat networks should be configured and those ones can be config as vlan or as crossover cables. Coming from the IBM AIX/HACMP arena i'm used to create heartbeat rings using either ethernet, SCSI, SSA or even SAN based LUNs. 
Is there any way we can use another alternate method for creating heartbeat rings in SecureGuard in HPUX clusters? 

www.unixbabuforum.inGood idea to implement HP' recommendation for many IPs. If you have two nodes a minimum of 6 IPs are required. One Primary, one standby IP and one heart IP for each server. Total of six IPs. The logic behind having so many is to eliminate a single point of failure for your network cards(to have redundency). You see should your primary NIC fail, then your standby NIC takes over. That's the beauty of SG. As for your heartbeat you will need one heartbeat NIC on each server connected to a separate VLAN/subnet. The logic behind is to have your HEARTBEAT NICs on separate subnets /NICs from your production subnet. The cross-over cable is a good idea in an enviroment where your two nodes are close to each other. If you can implement the cross over method it is very good because your heartbeat will be connected NIC A to NIC B and not NIC A to patch panel A to switch A then to you company network then to switch B to patch panel B and finally to NIC B. 
To make a long story short this config is to ensure proper redundency of the NETWORK protion of the cluster. 


www.unixbabuforum.inThere is no other way. That's what service gaurd expects. Here is what I mean; try this in a test environment where SG is installed. 
# cmquerycl -v -C cmclconfig.ascii -n NODE1 -n NODE2 -n NODE3.... ; NODE? being number of nodes in your cluster if you have one! 
# view cmclconfig.ascii 
If you have a cluster configured it will read the cluster and dump it's information in the ascii file. Search the ascii file for "HEARTBEAT_IP" and you will see that the field requires an IP address. 
I also want to mention that when I attended the SG course they did not mention an alternative method of implementing HEARTEAT. They did give us two methods to implement the CLUSTERLOCK item. You can use DISK METHOD or SERVER METHOD to implement the CLUSTERLOCK. 

0 comments:

Post a Comment

 
Design by BABU | Dedicated to grandfather | welcome to BABU-UNIX-FORUM