[LACP-7] In scenarios wherein the message exchange between switch & controller results in OF version set to OF1.0, the LACP module should throw up an error/warning message instead of processing the LACP packets Created: 28/May/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: Linux
Platform: All

External issue ID: 3409
Priority: Normal

 Description   

In case of creating an topology with switch version set to OF 1.0 & the controller OF version set to 1.3, the message exchange between them results in the OF version being set to 1.0.

In the above case, the LACP module should throw up an error or warning with info. "OF version mismatch" and also it should not add LACP flows to take the LACP PDU's to the controller. This will result in the LAG being created on the LACP module, but then the corresponding group wouldn't have been created on controller/switch side as the group programming is introduced only with OF version 1.3

mininet> sh ovs-ofctl -O Openflow10 dump-flows s1
NXST_FLOW reply (xid=0x4):
cookie=0x3000000000000000, duration=9.985s, table=0, n_packets=16, n_bytes=1984, idle_age=5, priority=5,dl_dst=01:80:c2:00:00:02,dl_type=0x8809 actions=CONTROLLER:65535 <<<<lacp flow entry is added. This will result in unnecessarily taking the packets to the controller.

 Comments   
Comment by Mahesh Manivasagam [ 28/May/15 ]

Issue seen on latest integration build(1901)

Comment by Kalaiselvi [ 05/Jun/15 ]

Openflow plugin does not share the switch's openflow version through notifications or in the data-store information.
So, LACP does not differentiate between openflow1.0 and openflow1.3 switches.
The information that for LACP to work properly switches have to support openflow1.3 will be published in the LACP user guide document.
Lacp feature will not throw any warning and avoid flow installation for switches in openflow1.0. LACP aggregate interfaces will be created for the switches. but the lag will not be informed to switches via the group table entries for these switches.

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