Uploaded image for project: 'CORD'
  1. CORD
  2. CORD-2299

Missing flows in Group Table along with bucket association to the group flow

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Resolved (View Workflow)
    • Priority: Blocker
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Fabric
    • Labels:

      Description

      We are encountering issues with missing flows in the group table. Netcfg for the concerned flows are given below.

      onos> netcfg ports of:0000000000000001/47
      {
      "interfaces" : [

      { "name" : "047-xe0/0/20 CCRA", "ips" : [ "172.16.41.2/24", "2001:0558:FF10:04D5::1FD/120" ], "vlan-tagged" : [ 31 ], "vlan-native" : "41", "mac" : "A8:2B:B5:6E:88:F0" }

      ]
      }
      onos> netcfg ports of:0000000000000001/51
      {
      "interfaces" : [

      { "name" : "-51 RUR", "vlan-untagged" : "31", "ips" : [ "10.252.145.89/29", "2001:0558:FF10:04D4::3/64" ], "mac" : "A8:2B:B5:6E:88:F0" }

      ]
      }

      The subnet 10.252.145.89/29 is the one bridged between the two ports on VLAN 31. This VLAN is present only on these two ports. Have attached the full netcfg. This works on and off. Every time we restart OFDPA, it immediately starts working. Post that, it stops at times.
      We see that sometimes, the group-flows are getting deleted. in the above case, there are two group table rules missing.

      We do see the following rule in table 50 for VLAN 31:

      id=47000084cf7afd, state=ADDED, bytes=0, packets=0, duration=79401, liveType=UNKNOWN, priority=5, tableId=50, appId=org.onosproject.segmentrouting, payLoad=null, selector=[VLAN_VID:31], treatment=DefaultTrafficTreatment

      {immediate=[], deferred=[GROUP:0x401f0000], transition=TABLE:60, meter=None, cleared=false, metadata=null}

      If we do a grep for GROUP: 0x401f000, we don’t find any entries.

      onos> groups | grep -i 0x401f0000
      id=0x401f0000, state=ADDED, type=ALL, bytes=0, packets=0, appId=org.onosproject.segmentrouting, referenceCount=1

      Comparing with other setups where it works, the following rules are not there. This is required to bridge the traffic on port 47.

      id=0x1f0034, bucket=1, bytes=0, packets=0, actions=[OUTPUT:47] ### ======= New group to be added
      id=0x401f0000, bucket=1, bytes=0, packets=0, actions=[GROUP:0x1f0033] ###  0x1f0033 is an existing group rule but need to be linked with 0x401f0000
      id=0x401f0000, bucket=2, bytes=0, packets=0, actions=[GROUP:0x1f0034] ### -> The new group entry 0x1f0034 need to be linked with 0x401f0000

      When we have multiple VLANs on the port (one native VLAN and other tagged). The tagged VLAN is bridged only.

      As you can see there is no buckets associated with the group (0x401f0000). Hence the traffic is not getting bridged on VLAN 31.

      groupId = 0x400a0000 (L2 Flood, VLAN ID = 10, Index = 0): duration: 26207, refCount:1
      bucketIndex = 0: referenceGroupId = 0x000a0007
      bucketIndex = 1: referenceGroupId = 0x000a0005
      bucketIndex = 2: referenceGroupId = 0x000a0006
      groupId = 0x401f0000 (L2 Flood, VLAN ID = 31, Index = 0): duration: 26207, refCount:1
      groupId = 0x40290000 (L2 Flood, VLAN ID = 41, Index = 0): duration: 26207, refCount:1
      bucketIndex = 0: referenceGroupId = 0x0029002f

      We have an integration environment where we are facing this issue. And looking for a way to restore it without bringing the switch down or doing a OFDPA restart. Hence trying the group flow addition via the REST API and facing below issues with that.

      The switches being used are QMX (5912/5916) and Tomahawk (7712)
      Request you to prioritize the issue.

        Attachments

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

          Activity

            People

            Assignee:
            Unassigned
            Reporter:
            gsdatta Subramanya Datta Gunt
            Watchers:
            3 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:

                Gerrit Reviews

                There are no open Gerrit changes