[LACP-12] On scaling the LAG number to 8(8-member ports) LAG's, some ports that are associated to the LAG interface are displayed in SELECT type group as well as the ALL type group under the dump-groups cli for the particular switch. Created: 03/Jun/15  Updated: 09/Jun/15  Resolved: 09/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: Done 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: 3559

 Description   

Mininet Topology: 32 Hosts & Switches and 8 links connecting each host to the switch. Configure the Hosts on LACP mode and check if the LAG groups are formed on the

switch side.
Openvswitch version: 2.3.1
Build no: Integration build 2133

Steps to recreate:
1. Bring up the controller and feature install the LACP module.
2. Once the controller is setup, create a mininet topology script as specified above and check if the group & flow entries are formed on all the switches. <<<Group and

flow entries are missing for few switches. <<<<A similar bug has already been raised for this case.
3. Also for the group entries that have been generated, check to see if the created group entries have all the ports associated to the select type group and not in the

all type. <<<<<In this case, the ports part of the LAG are displayed under the select type group as well as the ALL type group. Looks like the removal of the ports

weren't successful during then. This scenario happens only as we scale up the number of LAG's.

Dump-flows & Dump-groups o/p:

mininet> sh ovs-ofctl -O Openflow13 dump-groups s7
OFPST_GROUP_DESC reply (OF1.3) (xid=0x2):
group_id=44617,type=all,bucket=weight:0,actions=drop
group_id=49152,type=select,bucket=weight:0,actions=output:2,output:1,output:3,output:4,output:6,output:5,output:7,output:8
mininet> sh ovs-ofctl -O Openflow13 dump-groups s8
OFPST_GROUP_DESC reply (OF1.3) (xid=0x2):
group_id=7545,type=all,bucket=weight:0,actions=output:8 <<<port 8 present under all type groupid
group_id=41236,type=select,bucket=weight:0,actions=output:2,output:3,output:4,output:6,output:7,output:8,output:5,output:1 <<<<port 8 present under select type groupid as well

On checking the node specific REST API, the ports were associated to both the SELECT type group as well as the ALL type group under the group tag.

ALL type group:
---------------
{
group-id: 7545
group-type: "group-all"
opendaylight-group-statistics:group-desc: {
group-id: 7545
buckets: {
bucket: [1]
0: {
bucket-id: 0
watch_group: 4294967295
watch_port: 4294967295
weight: 0
action: [1]
0: {
order: 0
output-action: {
output-node-connector: "8" <<<<node-connector 8 present under the ALL group
max-length: 0
}-
}-
-
}-
-
}-
group-type: "group-all"
}

Select type group:
-------------------
{
group-id: 41236
group-type: "group-select"
opendaylight-group-statistics:group-desc: {
group-id: 41236
buckets: {
bucket: [1]
0: {
bucket-id: 0
watch_group: 4294967295
watch_port: 4294967295
weight: 0
action: [8]
0: {
order: 7
output-action: {
output-node-connector: "1"
max-length: 0
}-
}-
1: {
order: 2
output-action: {
output-node-connector: "4"
max-length: 0
}-
}-
2: {
order: 1
output-action: {
output-node-connector: "3"
max-length: 0
}-
}-
3: {
order: 0
output-action: {
output-node-connector: "2"
max-length: 0
}-
}-
4: {
order: 6
output-action: {
output-node-connector: "5"
max-length: 0
}-
}-
5: {
order: 5
output-action: {
output-node-connector: "8" <<<<<node connector present under Select group
max-length: 0
}-
}-
6: {
order: 4
output-action: {
output-node-connector: "7"
max-length: 0
}-
}-
7: {
order: 3
output-action: {
output-node-connector: "6"
max-length: 0
}-
}-
-
}-
-
}-
group-type: "group-select"
}



 Comments   
Comment by Kalaiselvi [ 09/Jun/15 ]

https://git.opendaylight.org/gerrit/#/c/22166/

Avoided re-addition of nodes for duplicate notifications.

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