Well, its actually on a Proliant blade and I'm going in through a virtual console (an ILO) to issue the ifdown commands. I'm doing power-fencing on the ILO itself (its one of the ways you can do it with Redhat Cluster). -----Original Message----- From: Eric Kerin [mailto:eric@xxxxxxxxxxx] Sent: Monday, July 18, 2005 2:26 PM To: Jeff Harr Cc: linux clustering Subject: RE: kernel: CMANsendmsg failed: -101 On Mon, 2005-07-18 at 14:06 -0400, Jeff Harr wrote: > Thanks for the help, Eric. Its interesting that you mentioned taking > down cman BEFORE taking the interfaces down, because when I was testing > my failover I did: ifdown bond0. My thinking was that the heartbeat > would die and everything would work. It didn't occur to me that it > would mess up cman - do you think that's what's doing it? Should I > instead just pull the cables? (I'm asking because it's a long drive to > the site just for the test, but will if you think that's the problem). > > Thanks again, > Jeff > Well normally when a machine is fenced, it is not shut down, just powered off. So that would definatly be the problem if the network interface is still down when you are shutting down the system. How are you issuing commands to the servers after taking down the network interface if you're not on site? I take it you aren't using power controllers to fence the machines, just using fence_manual, or an I/O fencing mechanism? Thanks, Eric Kerin <eric@xxxxxxxxxxx> -- Linux-cluster@xxxxxxxxxx http://www.redhat.com/mailman/listinfo/linux-cluster