[Pacemaker] Node crash when 'ifdown eth0'

[Tim Serong]

On 12/1/2009 at 11:05 AM, hj lee <kerdosa at gmail.com> wrote: 
> On Fri, Nov 27, 2009 at 3:05 PM, Steven Dake <sdake at redhat.com> wrote: 
>  
> > On Fri, 2009-11-27 at 11:32 -0200, Mark Horton wrote: 
> > > I'm using pacemaker 1.0.6 and corosync 1.1.2 (not using openais) with 
> > > centos 5.4.  The packages are from here: 
> > > http://www.clusterlabs.org/rpm/epel-5/ 
> > > 
> > > Mark 
> > > 
> > > On Fri, Nov 27, 2009 at 9:01 AM, Oscar Remí-rez de Ganuza Satrústegui 
> > > <oscarrdg at unav.es> wrote: 
> > > > Good morning, 
> > > > 
> > > > We are testing a cluster configuration on RHEL5 (x86_64) with pacemaker 
> > > > 1.0.5 and openais (0.80.5). 
> > > > Two node cluster, active-passive, with the following resources: 
> > > > Mysql service resource and a NFS filesystem resource (shared storage in 
> > a 
> > > > SAN). 
> > > > 
> > > > In our tests, when we bring down the network interface (ifdown eth0), 
> > the 
> > 
> > What is the use case for ifdown eth0 (ie what are you trying to verify)? 
> > 
>  
> I have the same test case. In my case, when two nodes cluster is disconnect, 
> I want to see split-brain. And then I want to see the split-brain handler 
> resets one of nodes. What I want to verify is that the cluster will recover 
> network disconnection and split-brain situation. 

Try this, on one node:

  # iptables -A INPUT -s ip.of.other.node -j DROP
  # iptables -A OUTPUT -d ip.of.other.node -j DROP

HTH,

Tim


-- 
Tim Serong <tserong at novell.com>
Senior Clustering Engineer, Novell Inc.