Uploaded image for project: 'ONOS'
  1. ONOS
  2. ONOS-4688

OpenFlow Error message with type OFPET_BAD_ACTION is not handled

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 1.6.0, 1.7.0, 1.6.1
    • Fix Version/s: 1.6.0, 1.7.0, 1.6.1
    • Component/s: None
    • Labels:
    • Environment:

      3 switch linear topology

    • Story Points:
      5

      Description

      When flow addition is tried with imperfect combination of match and action, OVS is rejecting the flow addition with Open flow error message with type OFPET_BAD_ACTION. Due to missing support for the same, the flow is remaining in pending add state and there by resulting in indefinite loop for flow addition.

      Detailed analysis:
      With further analysis, we have made the following observations:

      • Under the error scenario, OVS switch sending the OF error message by embedding the OF flow mod message as data. The embedded OF Flow MOD message (data) is truncated to 64 bytes.
      • Due to data truncation, flood light controller is not able to parse it correctly as the length field for the OpenFlow message is not matching the length of the data (OF message), resulting in retuning null.
      • And in ONOS, it is observed that message handling for error handling for type OFPET_BAD_ACTION is missing.

      Attachments:
      1. JSON Object for flow addition
      2. WS traces. (Packet no: 67 and 68)
      3. Error logs in onos

        Attachments

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

          Activity

            People

            Assignee:
            princepereira Prince Pereira
            Reporter:
            princepereira Prince Pereira
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Dates

              Created:
              Updated: