> On 22 Oct 2014, at 2:15 am, John Scalia <jayknowsu...@gmail.com> wrote: > > Hi all, again, > > My network engineer and I have found that the VM's hypervisor was set up to > block multicast broadcasts by our security team.
Blocked or lost? These links might be worth a look: https://access.redhat.com/solutions/784373 https://bugzilla.redhat.com/show_bug.cgi?id=880035 > We're not really certain why or if we can change that for at least my 3 > systems. He's speaking with them now. Anyway, as you don't have to configure > corosync on CentOS or Redhat, and there isn't even an > /etc/corosync/corosync.conf on these systems, what problems could I cause by > creating a config file and would the system actually use it on a restart? I > want to try setting the multicast address to a unicast one, at least for > testing. > > This whole setup seems a little odd since CentOS uses CMAN and pacemaker, but > corosync is getting started and I see all the systems listening on port 5404 > and 5405 similar to as follows: > > udp 0 0 10.10.1.129:5404 0.0.0.0:* > udp 0 0 10.10.1.129:5405 0.0.0.0:* > udp 0 0 239.192.143.91:5405 0.0.0.0"* > > So, if CentOS uses CMAN and pacemaker, why is corosync still in the mix? CMAN == corosync + some magic that gets loaded as a plugin > -- > Jay > _______________________________________________ > Linux-HA mailing list > Linux-HA@lists.linux-ha.org > http://lists.linux-ha.org/mailman/listinfo/linux-ha > See also: http://linux-ha.org/ReportingProblems _______________________________________________ Linux-HA mailing list Linux-HA@lists.linux-ha.org http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
