[LACP-11] LAG entry creation doesn't happen when trying to scale the number of LAG's to 128 entries. Created: 02/Jun/15 Updated: 24/Jun/15 Resolved: 24/Jun/15 |
|
| Status: | Resolved |
| Project: | lacp |
| Component/s: | General |
| Affects Version/s: | unspecified |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Mahesh Manivasagam | Assignee: | Rajesh B Sindagi |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: All |
||
| External issue ID: | 3541 |
| Description |
|
Mininet Topology: 128 Host & Switches and 2 links connecting each host and switch. Configure the Hosts on LACP mode and check if the LAG groups are formed on the switch side. Steps to recreate: Dump-flows & Dump-group entries o/p: Waited for an hour to check if the entries were added, but it wasn't the case. The dump-flows cli for the switches didn't show the LACP flow entry. In this scenario, the flows and groups entries aren't updated for any of the 128 switches. Even with 64 Hosts & Switches, the same issue can be hit. But it was sporadic(could hit this issue once in 7-8) attempts. But then with 128, the issue is hit everytime. On querying LACP/node-specific API's, the entries also weren't getting displayed. |
| Comments |
| Comment by Rajesh B Sindagi [ 17/Jun/15 ] |
|
Workaround for the defect - Start OpenDaylight controller with LACP module and then have the network connect to the controller. |
| Comment by Kalaiselvi [ 18/Jun/15 ] |
|
In the given test scenario, though the openflow listener does a Handshake with the underlying switches available in the topology, |
| Comment by Rajesh B Sindagi [ 24/Jun/15 ] |
|
Below CL, fixes this issue. |
| Comment by Rajesh B Sindagi [ 24/Jun/15 ] |
|
Root cause: Below CL, fixes this issue. |