Correction, it is NOT working now. It lasted longer after I switched to miimon, but one ring eventually failed.
1. How often does it attempt to auto-recover, if at all? 2. How can I enable more advanced debugging to see why the ring is failing? -- Eric Robinson Director of Information Technology Physician Select Management, LLC 775-885-2211 x 111 > -----Original Message----- > From: [email protected] > [mailto:[email protected]] On Behalf Of > Robinson, Eric > Sent: Thursday, November 03, 2011 4:43 AM > To: General Linux-HA mailing list > Subject: Re: [Linux-HA] ringid FAULTY adminisrtative > intervention required > > > > > I have two rings configured. Everything looks fine until > > I bring up > > > > the second node. Then the second ring on both nodes reports: > > > > > > > > status = Marking seqid 21 ringid 1 interface 198.51.100.55 > > > FAULTY - > > > > adminisrtative intervention required. > > > > > > > > The rings are on different switch fabrics and cannot see > > > each other at > > > > all, but I have given them different mcast addresses and > > > ports anyway > > > > (spaced by 2). > > > > > > > > Any thoughts? > > > > > > Just out of curiosity, how are you expecting anyone to be > > able to give > > > a useful answer on this if you're not even posting your Corosync > > > config? > > > > > > Florian > > > > > > > <snip> > > > Never mind, it is working now. The problem is with the > Ethernet bonding. > I'm using arp_ip_target and it is not working right, so the > bonded interface is unreliable. Works fine if I use miimon > instead. Corosync was just detecting that, I guess. I do have > to get the arp_ip_target working, though, so I have more work to do. > > --Eric > > > > Disclaimer - November 3, 2011 > This email and any files transmitted with it are confidential > and intended solely for General Linux-HA mailing list. 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 > _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
