Forgot to mention that in my virtual environment, when checking the multicast, i get this: netstat -g IPv6/IPv4 Group Memberships Interface RefCnt Group --------------- ------ --------------------- lo 1 224.0.0.1 eth0 1 239.255.1.178 eth0 1 224.0.0.1 eth1 1 239.255.1.177 eth1 1 224.0.0.1
while in the physical environment where the NICs are bonded, all i get is this: netstat -g IPv6/IPv4 Group Memberships Interface RefCnt Group --------------- ------ --------------------- lo 1 224.0.0.1 eth0 1 224.0.0.1 eth1 1 224.0.0.1 eth2 1 224.0.0.1 eth3 1 224.0.0.1 eth4 1 224.0.0.1 eth5 1 224.0.0.1 Is there a way to make the multicast bind to the bonded interface? Thanks, Jef On Wed, Jun 25, 2014 at 12:58 AM, Cayab, Jefrey E. <jca...@gmail.com> wrote: > Hi all, > > I used the same steps in the attached guide to build the cluster in > physical environment but when i got to "crm_mon -1", i always get this > error: > > Crm verify: Could not establish cib_ro connection: connection refused (111) > > Connection to cluster failed: transport endpoint is not Connected. > > > > Corosync configuration file is also attached. According to the network team, > the private network that I'm using (192.168.1.0/24) doesn't go via firewall. > > Please note that I was able to make this work in VMware Fusion; it just don't > want to cooperate in physical environment. > > Could this be due to network issue on the private network? > > I also noticed that with these steps, Pacemaker doesn't start on boot even > though Corosync starts fine. > > Please let me know if there are missing packages that I need to install. > > Appreciate your feedback(s). > > Thanks, > Jef > >
_______________________________________________ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org