[LACP-9] In addition to LAG group-id, another group entry is created with type=all and action=drop Created: 01/Jun/15  Updated: 18/Jun/15  Resolved: 18/Jun/15

Status: Resolved
Project: lacp
Component/s: General
Affects Version/s: unspecified
Fix Version/s: None

Type: Bug
Reporter: Mahesh Manivasagam Assignee: Kalaiselvi
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All

External issue ID: 3463

 Description   

Create a LAG connectivity between a host and switch(2 member LAG) and check the dump-groups table for the switch.

On checking the dump-group table, the LAG group is created with type=select and action to the ports.

But in addition to it, an additional group entry is randomly created with group-id = all, action = drop. There is no need to have an additional group entry with a drop action explicitly specified.

mininet> sh ovs-ofctl -O Openflow13 dump-groups s1
OFPST_GROUP_DESC reply (OF1.3) (xid=0x2):
group_id=36314,type=select,bucket=weight:0,actions=output:1,output:2
group_id=60544,type=all,bucket=weight:0,actions=drop <<<<random group entry

 Comments   
Comment by Mahesh Manivasagam [ 01/Jun/15 ]

Mininet topology used:
-----------------------

H S (2 links between the host & switch)

OpenVswitch version: 2.3.1

Controller image used: LACP distribution image 329.

Comment by Kalaiselvi [ 05/Jun/15 ]

In the switch, if all the ports are made part of the lag interfaces, the broadcast group entry created for the switch is removed of all the interfaces.
But the broadcast group entry is retained so that when further ports are added as physical ports or ports come out of lag they are added to the retained broadcast group entry.
The design is modified to retain the broadcast group entry even if all the ports are removed from it.

Generated at Wed Feb 07 20:05:58 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.