[ovs-discuss] IGMP snooping/query support in Openvswitch
Justin Pettit
jpettit at nicira.com
Wed Dec 11 07:38:41 UTC 2013
You have more ports attached to br-int than in your diagram, and they're not all on the same VLAN. This is really more a question of how Neutron is configuring OVS than how OVS works. Here's a page that shows how Neutron wires things up:
http://docs.openstack.org/grizzly/openstack-network/admin/content//under_the_hood_openvswitch.html
You'll probably have better luck posting your question about how multicast works in Neutron on a Neutron mailing list.
--Justin
On Dec 10, 2013, at 8:57 PM, Taurus Cheung <Taurus.Cheung at harmonicinc.com> wrote:
> Hi Justin,
>
> Configuration details:
> 1) The 2 VMs are running on the same OpenStack compute node (Grizzly version)
> 2) Both VMs have a virtual nic to receive multicast traffic in VLAN 1002
> 3) Openvswitch version is 1.9.0
> 4) ovs quantum plugin is configured in tenant_network_type vlan
> 5) The ovs bridge interface is eth1
> (output of "ovs-vsctl show")
> Bridge br-int
> Port "qvo128d8126-0c"
> tag: 1
> Interface "qvo128d8126-0c"
> Port "qvof11a3165-a5"
> tag: 2
> Interface "qvof11a3165-a5"
> Port "qvo0cf1ef19-80"
> tag: 1
> Interface "qvo0cf1ef19-80"
> Port "qvo48fdea98-df"
> tag: 2
> Interface "qvo48fdea98-df"
> Port br-int
> Interface br-int
> type: internal
> Port "qvo191216ce-02"
> tag: 2
> Interface "qvo191216ce-02"
> Port "qvo5de83fb2-d4"
> tag: 2
> Interface "qvo5de83fb2-d4"
> Port "int-br-eth1"
> Interface "int-br-eth1"
> Bridge "br-eth1"
> Port "eth1"
> Interface "eth1"
> Port "br-eth1"
> Interface "br-eth1"
> type: internal
> Port "phy-br-eth1"
> Interface "phy-br-eth1"
> 6) eth1 is physically connected to a Cisco L3 switch. That switch port is a VLAN trunk port, properly configured in VLAN group 1002. The multicast source is input from another port on the same switch.
> +---------------------------------+
> |Compute Node |
> | +-------------------------+ |
> | |VLAN 1002 | |
> | | +-----+ +-----+ | |
> | | |VM-A | |VM-B | | |
> | | +----++ ++----+ | |
> | +--------+-------+--------+ |
> | | | |
> | +-+-------++ |
> | | br-int | |
> | +------+----------+-------+ |
> | | | |
> | | OVS | |
> | +------+----------+-------+ |
> | | br-eth1 | |
> | +-----+----+ |
> | | |
> +------------+---+---+------------+
> | eth1 |
> +---+---+
> |
> |
> |
> |
> | Trunk port in VLAN 1002
> +---------------------+-+-+------------------------+
> |Cisco switch +---+ |
> | |
> | +---+ |
> +---------------------+-+-+------------------------+
> |
> |
> Multicast Source
>
>
> Our experiment result is “VM-B would not receive the multicast traffic joined by VM-A”.
>
> Regards,
> Taurus
>
> -----Original Message-----
> From: Justin Pettit [mailto:jpettit at nicira.com]
> Sent: Wednesday, December 11, 2013 11:53 AM
> To: Taurus Cheung
> Cc: discuss at openvswitch.org
> Subject: Re: [ovs-discuss] IGMP snooping/query support in Openvswitch
>
> On Dec 10, 2013, at 7:39 PM, Taurus Cheung <Taurus.Cheung at harmonicinc.com> wrote:
>
> > That's good my understanding is correct.
> >
> > Although OVS doesn't support IGMP snooping, could I know what underlying mechanism in OVS result in "VM-B would not receive the multicast traffic joined by VM-A"?
>
> How's it configured? Did you install any flows or VLANs? Anything else that may affect configuration?
>
> --Justin
More information about the discuss
mailing list