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

Flows not being removed with intents

    XMLWordPrintable

    Details

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

      7 switch, 24 host topology with Flow Objectives enabled. See the attatched image for the web ui view of the topology

    • Story Points:
      3
    • Epic Link:

      Description

      When a Multi to Single point intent is installed and then later removed, not all of the flows installed by the intent are removed in all the switches. These remaining flows can interfere with the flows installed by later intents and cause routing issues.

      output of the flows any flows any of:0000000000000005 after 3 intents have been installed and removed:

      onos> flows any of:0000000000000005
      deviceId=of:0000000000000005, flowRuleCount=6
          id=20000964f38f7, state=ADDED, bytes=512, packets=12, duration=785, priority=40000, tableId=0, appId=org.onosproject.core, payLoad=null, selector=[ETH_TYPE:arp], treatment=DefaultTrafficTreatment{immediate=[OUTPUT:CONTROLLER], deferred=[], transition=None, meter=None, cleared=false, metadata=null}
          id=20000b90d5c0d, state=ADDED, bytes=40905, packets=505, duration=785, priority=40000, tableId=0, appId=org.onosproject.core, payLoad=null, selector=[ETH_TYPE:lldp], treatment=DefaultTrafficTreatment{immediate=[OUTPUT:CONTROLLER], deferred=[], transition=None, meter=None, cleared=false, metadata=null}
          id=20000bc47a77c, state=ADDED, bytes=40905, packets=505, duration=785, priority=40000, tableId=0, appId=org.onosproject.core, payLoad=null, selector=[ETH_TYPE:bddp], treatment=DefaultTrafficTreatment{immediate=[OUTPUT:CONTROLLER], deferred=[], transition=None, meter=None, cleared=false, metadata=null}
          id=15000038bdb17c, state=ADDED, bytes=0, packets=0, duration=533, priority=100, tableId=0, appId=org.onosproject.net.intent, payLoad=null, selector=[IN_PORT:10, ETH_DST:00:00:00:00:00:08, ETH_TYPE:ipv4], treatment=DefaultTrafficTreatment{immediate=[OUTPUT:8], deferred=[], transition=None, meter=None, cleared=false, metadata=null}
          id=15000042aee04f, state=ADDED, bytes=0, packets=0, duration=499, priority=100, tableId=0, appId=org.onosproject.net.intent, payLoad=null, selector=[IN_PORT:10, ETH_TYPE:ipv4], treatment=DefaultTrafficTreatment{immediate=[OUTPUT:8], deferred=[], transition=None, meter=None, cleared=false, metadata=null}
          id=150000757d1bea, state=ADDED, bytes=2114, packets=29, duration=709, priority=100, tableId=0, appId=org.onosproject.net.intent, payLoad=null, selector=[IN_PORT:10], treatment=DefaultTrafficTreatment{immediate=[OUTPUT:8], deferred=[], transition=None, meter=None, cleared=false, metadata=null}
      

      The latter 3 flows are the flows remaining after the intent has been uninstalled.
      The three intents were installed between 10.1.0.7/24, 10.1.0.10/24 and 10.1.0.4/24
      if a fourth multi to single intent is installed between 200.1.0.3/24, 200.1.0.4/24 and 200.1.0.2/24 the left over flows from the previous intents will redirect the packets sent to 200.1.0.2/24 to 10.1.0.4/24

      The ONOS logs do not show any errors or exceptions.

        Attachments

          Issue Links

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

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                ximara Jeremy Songster
              • Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: