I hope you realize that [email protected] is a public mailing list. Nothing on it can be confidential.
Yes. This is a property of how OpenFlow is defined. On Tue, Jun 23, 2015 at 05:01:24PM +0000, [email protected] wrote: > Dell - Internal Use - Confidential > Hi Ben, > If we use group type "indirect" instead of "all", multiple egress ports in > output action would still fail, right? > > thanks > > -----Original Message----- > From: Ben Pfaff [mailto:[email protected]] > Sent: Tuesday, June 23, 2015 9:22 PM > To: Ramalingham, Kavitha > Cc: [email protected]; K, Kalaiselvi; Sindagi, Rajesh; Venkataraghavan, C; > Balasubram, Vasanthan; Manivasagam, Mahesh > Subject: Re: [ovs-discuss] Issue with Broadcast Group > > On Tue, Jun 23, 2015 at 03:42:33PM +0530, [email protected] wrote: > > I tested with the below mentioned topology, having a broadcast flow > > whose actions were set to broadcast group ID. When I tried to ping > > from host h1 to h2, ARP request packet is sent out to only one port > > and not to all ports. We have created a group of type "all" with the > > egress ports set to port3 and port4. The expectation here is that any > > flow that uses this group has to egress the traffic on both the ports. > > In the below tcpdump capture you can see that ARP-Request traffic goes > > out of port4 and not thro' port3. > > Your "all" group has one bucket with two output actions. That's a mistake, > because OpenFlow says that the actions in a bucket are an "action set", > meaning that only one action of each type can be effective. The solution is > to use two buckets, each with one output action. _______________________________________________ discuss mailing list [email protected] http://openvswitch.org/mailman/listinfo/discuss
