Redhat Linux Cluster with HP Blade system (bl680 G7)

[Md. Minhaz Khan]

Dear Concern,

We are going to implement two node Redhat linux cluster (RHEL 5.6 64 bit) with two HP Blade systems (2x BL680 G7 ).This two Blade system is attached into a Blade Chassis (Model:c7000). Each Blade system (BL680 G7) has one ILO3 & Each Blade Chassis has two physical LAN Port usually know as HP Onboard Administrator(OA) port. Usually ILO3 not connected with any Physical LAN, Its has only IP Address. HP Blade Chassis Onboard Administrator(OA) port physically connected with one of our Cisco Switch. This switch not used for production service traffic. We used this switch only for server Management related task.We are able to connect each blade system ILO3 through HP Onboard Administrator(OA) Lan.

Now we please guide us for the network diagram for cluster implementation with HP Blade system. Below is our IP address Block:

* bond0 (eth0 & eth2) = 172.16.10.1 (This Lan is used for Service Lan. Application users)

* bond1 (eth1 & eth3) = 192.168.10.1 ( This Lan is used for Cluster Heartbeat )

* OA1 = 172.31.202.31 ( This LAN is used to Manage the Blade Chasis)

* OA2 = This is the standby of OA1

* ILO3 of Blade system1(bl680c G7) = XXX.XXX.XXX.X (Please suggest us which subnet we will use, Shold we use 192.168.10.x or 172.31.202.x or .......)

* ILO3 of Blade system2 (bl680c G7) = XXX.XXX.XXX.X (Please suggest us which subnet we will use, Shold we use 192.168.10.x or 172.31.202.x or .......)

As summery,

Could you please explain, Recommended network connectivity diagram to configure fence device using HP proliant blade server(ILO3).We are using chassis OA LAN Port to connect the blade system ILO3.

Note: We already know below recommendation:

1) Make sure that you can connect from the OS of each blade to the iLO IP addresses of each cluster member blade.

2) The use of qdiskd with Red Hat Clustering is optional in most cases. The exception is a configuration with a two-node cluster where the fence devices are on a separate network from the cluster heartbeat network, requiring a quorum disk to prevent split-brain situations from causing a fence race.

3) For ILO3, Use IPMI LAN.

4) You may want to create a user account specifically for the fencing agent on the iLOs of the cluster member blades: this user accound needs the ability to switch the power of the blade off and on, but it does not need console access.

Thanks

Minhaz

[Alzhy]

That is pretty much it I believe.

For a 2 Node Cluster, it is highly recommended you set up a Disk Quorom.

What application(s) (or packages in SG Lingo) do you plan to run on your cluster?