From: Steven Dake <sdake@redhat.com>
To: "S, Prashanth" <Prashanth.S@lsi.com>
Cc: "openais@lists.linux-foundation.org"
<openais@lists.linux-foundation.org>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: [Openais] Multicast and Xen Bridge Networking issues
Date: Wed, 26 May 2010 09:09:05 -0700 [thread overview]
Message-ID: <4BFD47A1.1090501@redhat.com> (raw)
In-Reply-To: <04FB0DCDF7702C409F7E481C74E6A9BF029258F7E7@inbmail02.lsi.com>
On 05/26/2010 02:24 AM, S, Prashanth wrote:
> We have two (physical) machines. Each of them is hosting one Linux
> Virtual Machine (HVM) on top of Xen Hypervisor 3.4.1, The VMs are able
> to communicate with each other (using Xen Bridge Networking) thru the
> ethernet on the physical hosts. However, Corosync (part of OpenAIS HA
> suite) in VM is not able to detect and communicate with the other VM. We
> are not seeing any messages exchanged between the nodes. We found that
> corosync generated multicast messages are reaching the (Xen virtual)
> bridge. However, the bridge is not forwarding the UDP multicast messages
> to the ethernet. Does anybody know how to make multicast traffic flow
> across Xen Bridge? Also do we need any special route setting to achieve
> multicast routing between VM hosted on different machines.
>
> Regards,
>
> Prashanth
>
>
Most common problem for these symptoms is that iptables is turned on in
the host OS. Verify iptables is configured correctly on the host, and
then we can talk more after that.
Regards
-steve
>
> _______________________________________________
> Openais mailing list
> Openais@lists.linux-foundation.org
> https://lists.linux-foundation.org/mailman/listinfo/openais
prev parent reply other threads:[~2010-05-26 16:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-26 9:24 Multicast and Xen Bridge Networking issues S, Prashanth
2010-05-26 16:09 ` Steven Dake [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4BFD47A1.1090501@redhat.com \
--to=sdake@redhat.com \
--cc=Prashanth.S@lsi.com \
--cc=openais@lists.linux-foundation.org \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.