[Linux-cluster] RE: HP DL380 G4 & cluster fencing options

[Jones, Dave]

Hello James.

Thank you for the reply.
As I was trying to explain, the ILO network is out of band, therefore
there is no way for the cluster to connect to, login or otherwise
interact with the ILO controller.  ILO is on an different subnet and
different cabling infrastructure with no routing to the rest of the LAN.
So unless there is something I'm not understanding, ILO is not an
option.

I'm looking for other ways to fence these systems.

Thanks,
Dave


-----Original Message-----
From: linux-cluster-bounces at redhat.com
[mailto:linux-cluster-bounces at redhat.com] On Behalf Of Hofmeister, James
(WTEC Linux)
Sent: Friday, September 26, 2008 11:42 PM
To: linux clustering
Subject: [Linux-cluster] RE: HP DL380 G4 & cluster fencing options

Hello Dave,

RE: HP DL380 G4 & cluster fencing options

Using ILO fencing should work fine as long as the ILO for 'all' of the
cluster node are connected to the same physical network and IP subnet.
The ILO IP network does not need to be the same as the heartbeat/admin
traffic network.

Regards,
James Hofmeister
Hewlett Packard Linux Solutions Engineer

|-----Original Message-----
|From: linux-cluster-bounces at redhat.com
|[mailto:linux-cluster-bounces at redhat.com] On Behalf Of Jones, Dave
|Sent: Friday, September 26, 2008 2:52 PM
|To: Linux-cluster at redhat.com
|Subject: [Linux-cluster] HP DL380 G4 & cluster fencing options
|
|
|
|(I apologize if this double-posts, long story)
|
|Hello all.
|
|I have what I hope are a few simple questions on RHEL 5.2
|clustering using HP DL380 hardware.
|
|Long story short, we have several HP DL380-G4s that we are
|trying to set up in a test cluster but we do not have any of
|the obvious fencing options available to us.  ILO fencing does
|not seem to be an option because our standards dictate ILO be
|on an out-of-band network.
|We have SCSI fencing in place but I'm not convinced it is
|working properly nor that it is reliable.
|I hope to find funding to get an APC Masterswitch in place but
|that is not our standard so I need approval.
|
|In the meantime, can anyone offer any answers on the following
|questions?
|
|1) Are TripLite or other power controllers supported aside
|from what is on the hardware list?
|        (http://www.redhat.com/cluster_suite/hardware/)
|
|2) Is there a reliable way to change the SAN switch fencing
|controls to use SNMP (preferred) or perhaps SSH?
|        According to 'man fence_brocade' the system uses telnet.
|        An interactive login to a 256-port switch is bad
|enough, but doing so over an unencrypted telnet session just
|isn't going to fly!
|        I would think this would be a relatively trivial
|change to the script.
|        Has anyone done something like it?
|
|3) Does anyone have any experience clustering DL380s and have
|recommended Primary & Secondary fencing methods or advice they
|would be willing to share?
|
|4) Is anyone out there using only 1 fencing method with GFS
|filesystems in Production environment?
|
|Thanks,
|Dave
|
|Confidentiality Warning:  This e-mail contains information
|intended only for the use of the individual or entity named
|above.  If the reader of this e-mail is not the intended
|recipient or the employee or agent responsible for delivering
|it to the intended recipient, any dissemination, publication
|or copying of this e-mail is strictly prohibited.  The sender
|does not accept any responsibility for any loss, disruption or
|damage to your data or computer system that may occur while
|using data contained in, or transmitted with, this e-mail.
|If you have received this e-mail in error, please immediately
|notify us by return e-mail.  Thank you.
|
|
|
|
|--
|Linux-cluster mailing list
|Linux-cluster at redhat.com
|https://www.redhat.com/mailman/listinfo/linux-cluster
|

--
Linux-cluster mailing list
Linux-cluster at redhat.com
https://www.redhat.com/mailman/listinfo/linux-cluster

Confidentiality Warning:  This e-mail contains information intended only for the use of the individual or entity named above.  If the reader of this e-mail is not the intended recipient or the employee or agent responsible for delivering it to the intended recipient, any dissemination, publication or copying of this e-mail is strictly prohibited.  The sender does not accept any responsibility for any loss, disruption or damage to your data or computer system that may occur while using data contained in, or transmitted with, this e-mail.  
If you have received this e-mail in error, please immediately notify us by return e-mail.  Thank you.