It seems to not like using the 192.168.198.1 address. I've reconfigured with different addresses and it is working fine. I still don't know why we need a multicast address to use the broadcast method. Cheers, Alan
On Tue, Feb 9, 2010 at 4:16 PM, Alan Jones <[email protected]> wrote: > I'm trying to configure corosync with two networks. > The first network is "public" and uses a switch that is not configured to > support multicast. > The second network is a directly connected cable. > Q1: Why do I have to specify multicast address and port when I'm using > broadcast? > Q2: Why does the ring fail on the second network even though I can ping > each the other? > Please see attach config and log files. > Thanks! > Alan > > # ping 192.168.198.1 > PING 192.168.198.1 (192.168.198.1) 56(84) bytes of data. > 64 bytes from 192.168.198.1: icmp_seq=5 ttl=64 time=0.072 ms > 64 bytes from 192.168.198.1: icmp_seq=6 ttl=64 time=0.122 ms > 64 bytes from 192.168.198.1: icmp_seq=7 ttl=64 time=0.074 ms > > --- 192.168.198.1 ping statistics --- > 8 packets transmitted, 3 received, 62% packet loss, time 7000ms > rtt min/avg/max/mdev = 0.072/0.089/0.122/0.024 ms, pipe 2 > # corosync-cfgtool -s > Printing ring status. > Local node ID 2047453376 > RING ID 0 > id = 192.168.9.122 > status = ring 0 active with no faults > RING ID 1 > id = 192.168.198.2 > status = Marking seqid 126 ringid 1 interface 192.168.198.2 FAULTY > - adminisrtative intervention required. > >
_______________________________________________ Openais mailing list [email protected] https://lists.linux-foundation.org/mailman/listinfo/openais
