On 05/11/11 18:25, Robinson, Eric wrote: > A couple of things are fixed. The "ring FAULTY" messages were caused by > genuine network communication failures (go figure) which in turn had two > root causes. One was my error and the other was Red Hat's. Although I > have set up bonding many times before, on these servers I had > BONDING_OPS instead of BONDING_OPTS, so the bonding driver was not > seeing my chosen configuration. It was therefore defaulting to > round-robin behavior, which does not work in my switching environment. > This caused about every other packet to be dropped. (I discovered this > after learning about /proc/net/bonding, which showed that my bonded > links were actually in rr mode instead of active-backup as I had > thought.) Plus, I had copied the bad config file to all nodes, > compounding the problem. > > The second problem is Red Hat's. The RHEL 6 installation program creates > ifcfg-ethX scripts that contain quotes, such as > > device="eth0" > > instead of the more common > > device=eth0 > > It turns out that these quotes prevent the devices from coming up at > boot time. (I got this little clue and some other good information from > Florian at hastexo--thank you.) I removed the quotes and now the devices > come up nicely on reboot. This problem is quite reproducible. In one > case, I even removed quotes from eth0 and eth2, but left them in eth1 > and eth3. After reboot, only eth0 and eth2 came up. > > Now I have a working corosync+pacemaker cluster. Whew. > > -- > Eric Robinson > > > > > > > > Disclaimer - November 5, 2011 > This email and any files transmitted with it are confidential and intended > solely for [email protected]. If you are not the named addressee > you should not disseminate, distribute, copy or alter this email. Any views > or opinions presented in this email are solely those of the author and might > not represent those of Physicians' Managed Care or Physician Select > Management. Warning: Although Physicians' Managed Care or Physician Select > Management has taken reasonable precautions to ensure no viruses are present > in this email, the company cannot accept responsibility for any loss or > damage arising from the use of this email or attachments. > This disclaimer was added by Policy Patrol: http://www.policypatrol.com/ > _______________________________________________ > Linux-HA mailing list > [email protected] > http://lists.linux-ha.org/mailman/listinfo/linux-ha > See also: http://linux-ha.org/ReportingProblems Eric, Please file a bug against the scripts then.
Thank you. Regards, Tristan -- Tristan Santore BSc MBCS TS4523-RIPE Network and Infrastructure Operations InterNexusConnect Mobile +44-78-55069812 [email protected] Former Thawte Notary (Please note: Thawte has closed its WoT programme down, and I am therefore no longer able to accredit trust) For Fedora related issues, please email me at: [email protected] _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
