We will look at the STP settings on the switch. However, the switch works fine after link comes up. We suspected STP, too. Regards. Mark K Vallevand "If there are no dogs in Heaven, then when I die I want to go where they went." -Will Rogers THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. -----Original Message----- From: linux-cluster-bounces@xxxxxxxxxx [mailto:linux-cluster-bounces@xxxxxxxxxx] On Behalf Of Facundo M. de la Cruz Sent: Wednesday, September 17, 2014 02:04 PM To: linux clustering Subject: Re: Cman (and corosync) starting before network interface is ready On Sep 17, 2014, at 15:51, Rick Stevens <ricks@xxxxxxxxxxxxxx> wrote: > On 09/17/2014 08:20 AM, Vallevand, Mark K issued this missive: >> Tried replacing the switch with a crossover cable. The problem goes >> away. It looks like there is some odd delay in the switch. The NIC is >> configured, but it takes 4 seconds for the link to go up. Huh. >> >> We have a dedicated network for all the cluster traffic. Nothing else >> uses it. In the two-node case, we use a cable. In larger clusters we >> will use a switch. First delivery is for two-node clusters. But, I >> worry about that slow switch. > > Switches have to negotiate speeds, protocols, check for conflicting MACs and several other things (depending on the switch/router). It is > possible for that to take a couple of seconds. > > I'll bet that if you unplug the cable from the switch, then plug it > back in, you'll probably notice a slight delay in the port's link LED > lighting up as well. Pretty common and not necessarily indicative of a > problem. > ---------------------------------------------------------------------- > - Rick Stevens, Systems Engineer, AllDigital ricks@xxxxxxxxxxxxxx - > - AIM/Skype: therps2 ICQ: 22643734 Yahoo: origrps2 - > - - > - Never put off 'til tommorrow what you can forget altogether! - > ---------------------------------------------------------------------- > > -- > Linux-cluster mailing list > Linux-cluster@xxxxxxxxxx > https://www.redhat.com/mailman/listinfo/linux-cluster Hi everyone, Just let me ask one small thing. Did you enable Spanning Tree Protocol on the interconnect switch? STP is not compatible with TOTEM RRP, it's because STP is flapping all the time between BLOCKED / FORWARDING state on the port, then TOTEM will be not able to transmit heartbeat packages and when you get a number of four TOTEM error (an error is a time ~238 ms + overhead) the node can be fenced or can raise issue like this. Remember configure all the interconnect ports in the same multicast group too. Bests regards. -- Facundo M. de la Cruz (tty0) Information Technology Specialist Movil: +54 911 56528301 http://codigounix.blogspot.com/ http://twitter.com/_tty0 GPG fingerprint: DF2F 514A 5167 00F5 C753 BF3B D797 C8E1 5726 0789 "Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning." - Rich Cook -- Linux-cluster mailing list Linux-cluster@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/linux-cluster
