To be honest, I've only tested this setup on KVM's. About to do some prototyping on actual hardware next week - with the above setup.
What does your cluster.conf look like? If I set the altname parameter under <clusternodes> in cluster.conf - corosync-objctl seems to show the right thing. Selection of the interface, I believe, is based on the address specified by "altname" above. Cheers, /gav On 28 August 2012 17:45, Jan Bares <[email protected]> wrote: > Hi, > > Just out of curiosity: > >> > For those interested. >> > The configuration that I've settled on is >> > Two Nodes running qpidd + 1 Quorum Node >> > Each node has 2 Nics, allocated on separate switching >> infrastructure/networks. >> > One network is for cluster comms the other to serve requests (its >> also >> > used as a backup interface - I'm using Totem - RRP (Redundant Ring >> > Protocol)). > > CMAN doesn't support binding totem to specific interface, are you sure that > your setup works as described? I have eth0 for requests and management and > eth1 dedicated for cluster network. Unfortunately CMAN uses eth0 for cluster > communication, I can verify it with iptables and corosync-objctl. There is no > way how to configure eth1 as totem bind address in cluster.conf. > > Can someone verify that the first of ethX will be used? I can mitigate the > problem above by switching eth0 and eht1 but I want to be sure the bind > interfaces is not selected randomly. > > Thanks, Jan > > > > > > DISCLAIMER > WOOD & Company Financial Services, a.s. and its branches are authorized and > regulated by the CNB as Home State regulator and in Poland by the KNF, in > Romania by the CNVM, in Slovakia by the NBS and in the UK by the FSA as Host > State regulators. For further information about WOOD & Co., its investment > services, financial instruments and associated risks, safeguard client assets > (incl. compensation schemes) and contractual relationship please see our > website at www.wood.cz under section Corporate Governance. > > Unless otherwise stated, this transmission is neither an offer nor the > solicitation of an offer to sell or purchase any investment. All estimates, > opinions and other information contained herein are subject to change without > notice and are provided in good faith but without legal responsibility or > liability. Opinion may be personal to the author and may not reflect the > opinions of WOOD & Co. Communications from sales persons, sales traders or > traders should not be regarded as investment research and may contain > opinions or trading ideas which are different from WOOD & Co. investment > research opinions. > > This e-mail and any attachments are confidential and may be privileged or > otherwise protected from disclosure. If you are not a named addressee you > must not use, disclose, distribute, copy, print or rely on this e-mail and > any of its attachments. Please notify the sender that you have received this > email by mistake by replying to the email, and then delete the email and any > copies of it. Although WOOD & Co. routinely screens e-mails for viruses, > addressees should scan this e-mail and any attachments for viruses. WOOD & > Co. makes no representation or warranty as to the absence of viruses in this > e-mail or any attachments. Please note that to ensure regulatory compliance > and for the protection of our clients and business, we may monitor and read > e-mails sent to and from our server(s). > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
