[ovs-dev] Support for MCAST_Snooping
Hi,
I am currently using the beta version of ovs(2.3.90) and have enabled the
multicast snooping configuration with the help of below command.
echo 2 >
/proc/sys/net/ipv4/conf/all/force_igmp_version
Configure bridge \fBbr0\fR to enable multicast snooping
ovs-vsctl set Bridge br0
mcast_snooping_enable=true
Set the multicast snooping aging time \fBbr0\fR to 300 seconds
ovs-vsctl set Bridge br0
other_config:mcast-snooping-aging-time=300
Set the multicast snooping table size \fBbr0\fR to 2048 entries
ovs-vsctl set Bridge br0
other_config:mcast-snooping-table-size=2048
Disable flooding of unregistered multicast packets to all ports
ovs-vsctl set Bridge br0
other_config:mcast-snooping-disable-flood-unregistered=true
Enable flooding of multicast packets on a specific port
ovs-vsctl set Port enp9s0f0
other_config:mcast-snooping-flood=true
Flow added
[root@Iron utilities]# ovs-ofctl add-flow br0 action=NORMAL
Then I verify the bridge detail and multicast table detail using below
command and I got below out put however Mcast table is showing empty.
[root@Iron utilities]# ovs-vsctl list bridge
_uuid : 55e136ae-abe0-4b0e-a99d-c96ecd4cc74e
auto_attach : []
controller : []
datapath_id : "a0369f4f3894"
datapath_type : ""
datapath_version: ""
external_ids: {}
fail_mode : []
flood_vlans : []
flow_tables : {}
ipfix : []
mcast_snooping_enable: true
mirrors : []
name: "br0"
netflow : []
other_config: {mcast-snooping-aging-time="300",
mcast-snooping-table-size="2048"}
ports : [121608b8-9dfa-440e-a8f0-33a4112135e4,
4f8bb613-fb2e-4c28-b85a-a706e85e1910, bb71c085-a88f-4ad4-a3e4-e228473dfaeb]
protocols : []
rstp_enable : false
rstp_status : {}
sflow : []
status : {}
stp_enable : false
[root@Iron utilities]# ./ovs-appctl fdb/show br0
port VLAN MACAge
3 0 a0:36:9f:4f:38:95 0
[root@Iron utilities]# ovs-appctl mdb/show br0
port VLAN GROUPAge
Can you please tell me if I missed out any configuration, if not why
multicast table showing empty???/ Please any one can help me on this.
Can you confirm as to whether the multicast snooping configuration is supported
at the group level? If yes then can you mention as to where this information
(registered group addresses and the mac addresses) is maintained on the
switch.
As far as i can see the host receives multicast traffic from all the
multicast groups irrespective of the group it has registered for. Is there
any other further configuration that is required?
Thanks,
Laxmikanta
___
dev mailing list
dev@openvswitch.org
http://openvswitch.org/mailman/listinfo/dev
Re: [ovs-dev] Support for MCAST_Snooping
Hi Cascardo,
Appreciated your quick response and find my below inline comment for
resolving the issue .
What is your bridge topology?
Laxmikanta:-My topology is very simple back to back connection.
Query-->
<--Join
TG1(As a Server)
OVS2.3.9---TG2(As a Host).
Can you send ovs-vsctl show?
Laxmikanta :-
[root@Iron vswitchd]# ovs-vsctl show
6d16c545-2a2a-46bf-bfee-be3dc5f408e8
Bridge "br0"
Port "enp9s0f0"
Interface "enp9s0f0"
Port "enp9s0f3"
Interface "enp9s0f3"
Port "br0"
Interface "br0"
type: internal
Does your host belong to any group, ie, has it sent any joins?
Laxmikanta:- Yes, TG2 sending join message.
Do you have a single port in the bridge?
Laxmikanta:- Two port in the bridge.
And are you receiving joins on that port, or only multicast messages
without any joins?
Laxmikanta:- I am able to see the multicast message and query message in
wirashark.
Thanks & Regards,
On Sat, Jul 18, 2015 at 5:31 PM, Thadeu Lima de Souza Cascardo <
casca...@redhat.com> wrote:
> [image: Boxbe] <https://www.boxbe.com/overview> Thadeu Lima de Souza
> Cascardo (casca...@redhat.com) is not on your Guest List
> <https://www.boxbe.com/approved-list?tc_serial=22012467437&tc_rand=2132617215&utm_source=stf&utm_medium=email&utm_campaign=ANNO_MWTP&utm_content=001&token=onQM22hN3ET%2BAGNTZhTJ7uqTK8kMK%2BaTJsAcRznHxyOprJ5k8WpXKuyJ1p0Hopuv&key=QhsarmB412AjKyoEofgwcLZug6e5b0MRaffuMFha6H8%3D>
> | Approve sender
> <https://www.boxbe.com/anno?tc_serial=22012467437&tc_rand=2132617215&utm_source=stf&utm_medium=email&utm_campaign=ANNO_MWTP&utm_content=001&token=onQM22hN3ET%2BAGNTZhTJ7uqTK8kMK%2BaTJsAcRznHxyOprJ5k8WpXKuyJ1p0Hopuv&key=QhsarmB412AjKyoEofgwcLZug6e5b0MRaffuMFha6H8%3D>
> | Approve domain
> <https://www.boxbe.com/anno?tc_serial=22012467437&tc_rand=2132617215&utm_source=stf&utm_medium=email&utm_campaign=ANNO_MWTP&utm_content=001&dom&token=onQM22hN3ET%2BAGNTZhTJ7uqTK8kMK%2BaTJsAcRznHxyOprJ5k8WpXKuyJ1p0Hopuv&key=QhsarmB412AjKyoEofgwcLZug6e5b0MRaffuMFha6H8%3D>
>
> On Sat, Jul 18, 2015 at 02:46:40PM +0530, laxmikanta.beh...@gmail.com
> wrote:
> > Hi,
> >
> > I am currently using the beta version of ovs(2.3.90) and have enabled
> the
> > multicast snooping configuration with the help of below command.
> >
> >
> > echo 2 >
> > /proc/sys/net/ipv4/conf/all/force_igmp_version
> > Configure bridge \fBbr0\fR to enable multicast snooping
> > ovs-vsctl set Bridge br0
> > mcast_snooping_enable=true
> > Set the multicast snooping aging time \fBbr0\fR to 300 seconds
> > ovs-vsctl set Bridge br0
> > other_config:mcast-snooping-aging-time=300
> > Set the multicast snooping table size \fBbr0\fR to 2048 entries
> > ovs-vsctl set Bridge br0
> > other_config:mcast-snooping-table-size=2048
> > Disable flooding of unregistered multicast packets to all ports
> > ovs-vsctl set Bridge br0
> > other_config:mcast-snooping-disable-flood-unregistered=true
> > Enable flooding of multicast packets on a specific port
> > ovs-vsctl set Port enp9s0f0
> > other_config:mcast-snooping-flood=true
> >
> > Flow added
> > [root@Iron utilities]# ovs-ofctl add-flow br0 action=NORMAL
> >
> > Then I verify the bridge detail and multicast table detail using below
> > command and I got below out put however Mcast table is showing empty.
> >
> > [root@Iron utilities]# ovs-vsctl list bridge
> > _uuid : 55e136ae-abe0-4b0e-a99d-c96ecd4cc74e
> > auto_attach : []
> > controller : []
> > datapath_id : "a0369f4f3894"
> > datapath_type : ""
> > datapath_version: ""
> > external_ids: {}
> > fail_mode : []
> > flood_vlans : []
> > flow_tables : {}
> > ipfix : []
> > mcast_snooping_enable: true
> > mirrors : []
> > name: "br0"
> > netflow : []
> > other_config: {mcast-snooping-aging-time="300",
> > mcast-snooping-table-size="2048"}
> > ports : [121608b8-9dfa-440e-a8f0-33a4112135e4,
> > 4f8bb613-fb2e-4c28-b85a-a706e85e1910,
> bb71c085-a88f-4ad4-a3
Re: [ovs-dev] Support for MCAST_Snooping
Hi Cascardo, Appreciating very much your help on this ! Please find attached tcpdump (wireshark files) and below requested MAC address details. Port MAC Address. enp9s0f0 a0:36:9f:4f:38:94 enp9s0f3 a0:36:9f:4f:38:97 TG1 a0:36:9f:4f:38:95 TG2 a0:36:9f:4f:38:96 Thanks & Regards, Laxmikanta On Jul 18, 2015 7:04 PM, "Thadeu Lima de Souza Cascardo" < casca...@redhat.com> wrote: > On Sat, Jul 18, 2015 at 06:44:20PM +0530, laxmikanta.beh...@gmail.com > wrote: > > Hi Cascardo, > > > > Appreciated your quick response and find my below inline comment for > > resolving the issue . > > > > What is your bridge topology? > > Laxmikanta:-My topology is very simple back to back connection. > > > >Query--> > > <--Join > > TG1(As a Server) > > OVS2.3.9---TG2(As a Host). > > > > > > Can you send ovs-vsctl show? > > Laxmikanta :- > > > > [root@Iron vswitchd]# ovs-vsctl show > > > > 6d16c545-2a2a-46bf-bfee-be3dc5f408e8 > > > > Bridge "br0" > > > > Port "enp9s0f0" > > > > Interface "enp9s0f0" > > > > Port "enp9s0f3" > > > > Interface "enp9s0f3" > > > > Port "br0" > > > > Interface "br0" > > > > type: internal > > > > Does your host belong to any group, ie, has it sent any joins? > > Laxmikanta:- Yes, TG2 sending join message. > > > > Do you have a single port in the bridge? > > Laxmikanta:- Two port in the bridge. > > > > And are you receiving joins on that port, or only multicast messages > > without any joins? > > Laxmikanta:- I am able to see the multicast message and query message in > > wirashark. > > > > Can you share that dump containing query/join and multicast message? It > would be > nice to know the MAC addresses of ports br0, enp9s0f3, enp9s0f0 and other > MAC > addresses belonging to TG1 and TG2, so we can try to match them with the > addresses in the dump. > > Cascardo. > > > > > Thanks & Regards, > > > > > ___ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev
[ovs-dev] IGMP Snooping support Last leave message.
Hi , IGMP Snooping table erasing multicast group IP after receiving the 1st leave message from host. vswitch is not waiting till receive the last leave message for the same multicast group IP from different host. *Description* 1. Host 1 and 2 both connected with port number 2. 2. Host 1(00:00:00:00:00:01) – sending Join message to Multicast group Ip(239.255.255.250) 3. After 100 sec 4. Host 2 (A0:36:9F:4F:38:97) – Sending Join message to same Multicast group Ip(239.255.255.250) 5. After 100 sec 6. Host1 –Sending Leave message to Multicast group Ip(239.255.255.250). After receive the 1st leave message, vswitch is erasing the group IP from IGMP snooping table. Please find below snap shot. Could you please confirm if OVS support the last leave message or not. Thanks & Regards, Laxmikanta ___ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev
Re: [ovs-dev] IGMP Snooping support Last leave message.
Hi, we are sending two different stream from same port using TG. Do you want to say that only one host can connect in each port. My use case is I connect multiple host in a single host. Please let us know if OVS support multiple host can connect in a single port. Thanks & Regards, Laxmikanta On Fri, Aug 7, 2015 at 12:44 AM, Flavio Leitner wrote: > On Fri, Aug 07, 2015 at 12:00:14AM +0530, laxmikanta.beh...@gmail.com > wrote: > > Hi , > > > > > > > > IGMP Snooping table erasing multicast group IP after receiving the 1st > > leave message from host. vswitch is not waiting till receive the last > > leave message for the same multicast group IP from different host. > > The default is one host per port, so the first leave will drop the > address from the multicast db. > > > *Description* > > > > > > > > 1. Host 1 and 2 both connected with port number 2. > > > > 2. Host 1(00:00:00:00:00:01) – sending Join message to Multicast > > group Ip(239.255.255.250) > > > > 3. After 100 sec > > > > 4. Host 2 (A0:36:9F:4F:38:97) – Sending Join message to same > > Multicast group Ip(239.255.255.250) > > > > 5. After 100 sec > > > > 6. Host1 –Sending Leave message to Multicast group > > Ip(239.255.255.250). > > > > After receive the 1st leave message, vswitch is erasing the > > group IP from IGMP snooping table. Please find below snap shot. > > Could you please confirm if OVS support the last leave message or not. > > How are you connecting your hosts? Usually you have one host per port > but that doesn't seem to be your use case. > > fbl > > ___ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev
