On Fri, Oct 22, 2010 at 5:27 PM, Robinson, Eric <[email protected]> wrote: >>> I am building a 3-node cluster and adding it to a network that > already >>> had a separate 2-node cluster. >>> >>> The new 3-node cluster would have 2 nodes actively serving up >>> resources with 1 node acting as a failover for both of the active > nodes. > >> In this case all 3 nodes have to be connected to all rings >> if you want to use those rings for Pacemaker communications. >> And those rings have to be separate from existing cluster rings. > > So in my case, each of the back-to-back connections (crossover cables) > would be regarded as a separate ring?
Looks like you are mixing up physical connections and Corosync rings. Ring is an abstraction in Corosync. Crossover cable is a physical connection. DRBD doesn't need a Corosync "ring" for data replication, you can use your crossovers for that. Pacemaker/Corosync membership protocol though requires that all nodes were connected to the same network and form one or more abstract "rings" to communicate to each other. That means that using crossovers you can't build a cluster with more that 2 nodes. With that said if you have 3 servers connected to one network and also forming 2 cross-connected pairs you can build a 3 node cluster with 1 Corosync ring for Pacemaker communication and also use your crossovers for DRBD data replication. But those crossovers won't be considered as a Corosync rings. If you want to have real redundancy rings you have to replace your crossovers with a switch and connect all 3 nodes to it. To have more rings you have to add more switches. > > -- > Eric Robinson > > > > Disclaimer - October 22, 2010 > 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 > -- Serge Dubrouski. _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
