Uploaded image for project: 'lacp'
  1. lacp
  2. 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

    XMLWordPrintable

Details

    • Bug
    • Status: Resolved
    • Resolution: Won't Do
    • unspecified
    • None
    • General
    • None
    • Operating System: Linux
      Platform: All

    • 3409
    • 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.

      Attachments

        No reviews matched the request. Check your Options in the drop-down menu of this sections header.

        Activity

          People

            kalaiselvi_k@dell.com Kalaiselvi
            mahesh_manivasagam@dell.com Mahesh Manivasagam
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: