Uploaded image for project: 'ovsdb'
  1. ovsdb
  2. OVSDB-380

vxlan ports in Configuration datastore not created on device

    XMLWordPrintable

Details

    • Bug
    • Status: Resolved
    • Resolution: Cannot Reproduce
    • unspecified
    • None
    • Clustering
    • None
    • Operating System: All
      Platform: All

    • 7005

    Description

      Used Legacy Netvirt and stacked up 3 openstack nodes. Then performed operations like create Network/Subnet and instances.

      At the end of operations, the instances failed to participate in communication. then noticed that it was not a full mesh.

      From the output of ovs-vsctl show we notice that the vxlan ports in compute nodes are not connecting to control node.

      sudo ovs-vsctl show in various nodes
      [gvrangan@controlnode devstack]$ sudo ovs-vsctl show
      ed3798b7-0094-491c-bdd6-e8fdf7821bea
      Manager "tcp:10.128.0.3:6640"
      is_connected: true
      Manager "tcp:10.128.0.9:6640"
      is_connected: true
      Manager "tcp:10.128.0.7:6640"
      is_connected: true
      Bridge br-int
      Controller "tcp:10.128.0.9:6653"
      is_connected: true
      Controller "tcp:10.128.0.7:6653"
      is_connected: true
      Controller "tcp:10.128.0.3:6653"
      is_connected: true
      fail_mode: secure
      Port br-int
      Interface br-int
      type: internal
      Port "vxlan-10.128.0.5"
      Interface "vxlan-10.128.0.5"
      type: vxlan
      options:

      {key=flow, local_ip="10.128.0.4", remote_ip="10.128.0.5"}

      Port "vxlan-10.128.0.6"
      Interface "vxlan-10.128.0.6"
      type: vxlan
      options:

      {key=flow, local_ip="10.128.0.4", remote_ip="10.128.0.6"}

      Port "tap89b1db3d-ef"
      Interface "tap89b1db3d-ef"
      Bridge br-ex
      Port br-ex
      Interface br-ex
      type: internal
      ovs_version: "2.5.0"

      compute1

      [gvrangan@compute2 devstack]$ sudo ovs-vsctl show
      9ed900aa-b573-4fc8-9ae1-c2889c638fff
      Manager "tcp:10.128.0.3:6640"
      is_connected: true
      Manager "tcp:10.128.0.7:6640"
      is_connected: true
      Manager "tcp:10.128.0.9:6640"
      is_connected: true
      Bridge br-int
      Controller "tcp:10.128.0.9:6653"
      is_connected: true
      fail_mode: secure
      Port br-int
      Interface br-int
      type: internal
      Port "vxlan-10.128.0.5"
      Interface "vxlan-10.128.0.5"
      type: vxlan
      options:

      {key=flow, local_ip="10.128.0.6", remote_ip="10.128.0.5"}

      Port "tap8dca1a92-2c"
      Interface "tap8dca1a92-2c"
      Bridge br-ex
      Port br-ex
      Interface br-ex
      type: internal
      ovs_version: "2.5.2"

      compute 2

      gvrangan@compute1 devstack]$ sudo ovs-vsctl show
      795fa0e8-b4b2-49ee-b562-a2137f1bd585
      Manager "tcp:10.128.0.3:6640"
      is_connected: true
      Manager "tcp:10.128.0.9:6640"
      is_connected: true
      Manager "tcp:10.128.0.7:6640"
      is_connected: true
      Bridge br-int
      Controller "tcp:10.128.0.9:6653"
      is_connected: true
      Controller "tcp:10.128.0.3:6653"
      is_connected: true
      Controller "tcp:10.128.0.7:6653"
      is_connected: true
      fail_mode: secure
      Port "vxlan-10.128.0.6"
      Interface "vxlan-10.128.0.6"
      type: vxlan
      options:

      {key=flow, local_ip="10.128.0.5", remote_ip="10.128.0.6"}

      Port br-int
      Interface br-int
      type: internal
      Bridge br-ex
      Port br-ex
      Interface br-ex
      type: internal
      ovs_version: "2.5.2"

      Attachments

        1. odl1.zip
          116 kB
        2. odl2.zip
          68 kB
        3. odl3.zip
          67 kB
        4. ownership_info.txt
          8 kB
        5. topology_config.txt
          9 kB
        6. topology_operational.txt
          37 kB
        No reviews matched the request. Check your Options in the drop-down menu of this sections header.

        Activity

          People

            Unassigned Unassigned
            gvrangan Venkatrangan Govindarajan
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: