Uploaded image for project: 'genius'
  1. genius
  2. GENIUS-125

TEP with UNKNOWN state not cleared from ietf-interfaces-state on br-int delete and add

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Medium Medium
    • None
    • None
    • None
    • None

      Scenario:

      1. Two switches connected to ODL.
      2. Tunnels created among them by genius-auto-tunnel feature and they are in UP state.
      3. Bridge br-int is deleted on one switch and TEP corresponding to switch is also deleted from transport-zone.
      4. Bridge br-int is created again.
      5. TEP interface which was present on old br-int (that was deleted) is still present with UNKNOWN state in tep:show-state CLI and also in REST output of URL: http://localhost:8181/restconf/operational/ietf-interfaces:interfaces-state/

       Output:

      No Title

      {

                      "name": "tun9a610ac5fb8",

                      "lower-layer-if": [

                          "openflow:205394741551683:1"

                      ],

                      "type": "iana-if-type:tunnel",

                      "if-index": 4,

                      "statistics":

      {                     "discontinuity-time": "2018-04-12T10:05:13.738Z"                 }

      ,

                      "phys-address": "0a:9b:ca:40:1e:a9",

                      "admin-status": "up",

                      "oper-status": "unknown"

                  },

                  {

                      "name": "tun920ad5df93c",

                      "lower-layer-if": [

                          "openflow:249401263927879:1"

                      ],

                      "type": "iana-if-type:tunnel",

                      "if-index": 6,

                      "statistics":

      {                     "discontinuity-time": "2018-04-12T10:06:39.240Z"                 }

      ,

                      "phys-address": "3e:3e:2c:c3:0a:75",

                      "admin-status": "up",

                      "oper-status": "unknown"

                  },

       

       CLI output::

      opendaylight-user@root>tep:show-state

      Tunnel Name       Source-DPN        Destination-DPN   Source-IP         Destination-IP    Trunk-State  Transport Type

      -------------------------------------------------------------------------------------------------------------------------------------

      tun5e4fcc86a6b    266566598320975   11993393404231    192.168.56.251    192.168.56.250    UP          VXLAN

      tun9a4e266ac54    11993393404231    266566598320975   192.168.56.250    192.168.56.251    UP          VXLAN

      tun920ad5df93c    249401263927879   266566598320975   192.168.56.250    192.168.56.251    UNKNOWN     VXLAN

      tun9a610ac5fb8    205394741551683   266566598320975   192.168.56.250    192.168.56.251    UNKNOWN     VXLAN

      opendaylight-user@root>

       

      opendaylight-user@root>tep:show

      Tunnel Monitoring (for VXLAN tunnels): On

      Tunnel Monitoring Interval (for VXLAN tunnels): 10000

       

       

      TransportZone     TunnelType        SubnetMask        GatewayIP     VlanID       DpnID        IPAddress        PortName

      ------------------------------------------------------------------------------------------------------------------------------

      default-transport-zone  VXLAN             255.255.255.255/32  0.0.0.0       0            11993393404231 192.168.56.250

      default-transport-zone  VXLAN             255.255.255.255/32  0.0.0.0       0            266566598320975 192.168.56.251

      opendaylight-user@root>

            Edw7n Edwin Anthony
            tarunODLF Tarun Thakur
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated: