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         : "0000a0369f4f3894"
> datapath_type       : ""
> datapath_version    : "<unknown>"
> 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  MAC                            Age
>                     3     0         a0:36:9f:4f:38:95       0
> 
> [root@Iron utilities]# ovs-appctl mdb/show br0
>                  port  VLAN  GROUP                Age
> 
> 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?
> 

What is your bridge topology? Can you send ovs-vsctl show? Does your host belong
to any group, ie, has it sent any joins? Do you have a single port in the
bridge? And are you receiving joins on that port, or only multicast messages
without any joins?

Multicast snooping will not prevent local multicast (224.0.0.0/24) messages from
flooding. And it will not prevent multicast messages from getting into the ports
in any way. It will just control how those messages are forwarded to the other
ports on the bridge.

For example, if you have a group of 5 VMs, all attached to a port each to the
bridge, and three of them join a non-local group (say 239.255.255.1), messages
to that group will only be forwarded to those three VMs.

By the way, I wouldn't suggest you force IGMP version 2. If there is a querier
on your network, it might use a different version and it would be preferred to
use that version. Ideally, it would be using IGMPv3, which uses less
messages/datagrams.

Hope that helps.
Cascardo.

> 
> 
> 
> Thanks,
> Laxmikanta
> _______________________________________________
> dev mailing list
> dev@openvswitch.org
> http://openvswitch.org/mailman/listinfo/dev
_______________________________________________
dev mailing list
dev@openvswitch.org
http://openvswitch.org/mailman/listinfo/dev

Reply via email to