[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

RE: [Linux-cluster] RHEL Cluster Suite + Xen Dom0 = infinite reboots



This FAQ section gives good advice.  The Xen network-bridge scripts are
designed to work on hosts without any preconfigured bridge; however I
find it much more straightforward to configure the host for bridging
myself exactly as in the FAQ.  As a plus you have more complete control
over all your network settings.

You can still use the vif-bridge script as is.  I don't really know any
better way.

> -----Original Message-----
> From: linux-cluster-bounces redhat com
[mailto:linux-cluster-bounces redhat com]
> On Behalf Of Aaron Benner
> Sent: Wednesday, July 08, 2009 5:53 PM
> To: linux-cluster redhat com
> Subject: [Linux-cluster] RHEL Cluster Suite + Xen Dom0 = infinite
reboots
> 
> I have 3 xen Dom0 machines upon which I'm trying to build a cluster
> for HA DomUs.  At present the cluster config file simply lists the 3
> nodes.  No fencing, services, resources or failover domains have been
> defined.  I know that this is not what I will need moving to
> production.  I was using the most minimal cluster config I could to
> ensure that my problem was the interaction of Xen and the cluster
suite.
> 
> The problem is this:  when a node reboots it joins the cluster
> successfully, then xen tears down the network to build xenbr0, vif0.0,
> and peth0 (standard /etc/xen/scripts/network-bridge).  When this
> happens the rebooting node "fails" in the cluster's eyes.  The active
> nodes try to fence it.  Originally I had power fencing enabled and
> this situation resulted in the shootout at the o.k. corral with the
> failed node booting, failing and getting fenced forever.
> 
> I did find the gem at the very bottom of the FAQ in the
> GeneralQuestions section
>
(http://sources.redhat.com/cluster/wiki/FAQ/GeneralQuestions#xencluster
> ) that mentions this situation.  The "workaround" which also mentions
> a "more permanent solution" seems, well, clunky so I thought I'd ping
> the list to see if the more permanent solution exists and is just not
> well documented or if others have found a solution that doesn't
> require override of the default xen script behavior?
> 
> 
> --
> Linux-cluster mailing list
> Linux-cluster redhat com
> https://www.redhat.com/mailman/listinfo/linux-cluster




[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]