Revision history [back]

Hi The issue is happening when new instance is creating or when instance is migrated to other host. So very often network port is misconfigured, like here:

Bridge br-int
    Controller "tcp:127.0.0.1:6633"
        is_connected: true
    fail_mode: secure
    Port patch-tun
        Interface patch-tun
            type: patch
            options: {peer=patch-int}
    Port "01620459-aa05-4a25-9bf3-41a9390d94b1"
        Interface "01620459-aa05-4a25-9bf3-41a9390d94b1"
    Port "715b022f-1bad-4f81-b9bf-9d0e4a2973f4"
        tag: 2
        Interface "715b022f-1bad-4f81-b9bf-9d0e4a2973f4"
    Port "502167c0-d71a-483d-b099-4e3496d53925"
        tag: 2
        Interface "502167c0-d71a-483d-b099-4e3496d53925"
    Port "57152408-69f5-4464-8121-730550ae193e"
        tag: 1
        Interface "57152408-69f5-4464-8121-730550ae193e"
    Port br-int
        Interface br-int
            type: internal

In that example Port "01620459-aa05-4a25-9bf3-41a9390d94b1" is configured without tag, which means of course that the network is not working in virtual machine. After restart of neutronovsagent service, it is recreated with tag and the network is connected. It's Openvswitch 2.7 and Ocata version of hyperv compute on Hyper-V Server 2016.

Hi The issue is happening when new instance is creating or when instance is migrated to other host. So very often network port is misconfigured, like here:

Bridge br-int
    Controller "tcp:127.0.0.1:6633"
        is_connected: true
    fail_mode: secure
    Port patch-tun
        Interface patch-tun
            type: patch
            options: {peer=patch-int}
    Port "01620459-aa05-4a25-9bf3-41a9390d94b1"
        Interface "01620459-aa05-4a25-9bf3-41a9390d94b1"
    Port "715b022f-1bad-4f81-b9bf-9d0e4a2973f4"
        tag: 2
        Interface "715b022f-1bad-4f81-b9bf-9d0e4a2973f4"
    Port "502167c0-d71a-483d-b099-4e3496d53925"
        tag: 2
        Interface "502167c0-d71a-483d-b099-4e3496d53925"
    Port "57152408-69f5-4464-8121-730550ae193e"
        tag: 1
        Interface "57152408-69f5-4464-8121-730550ae193e"
    Port br-int
        Interface br-int
            type: internal

In that example Port "01620459-aa05-4a25-9bf3-41a9390d94b1" is configured without tag, which means of course that the network is not working in virtual machine. After restart of neutronovsneutron ovs agent service, it is recreated with tag and the network is connected. It's Openvswitch 2.7 and Ocata version of hyperv compute on Hyper-V Server 2016.

Hi The issue is happening when new instance is creating or when instance is migrated to other host. So very often network port is misconfigured, like here:

Bridge br-int
    Controller "tcp:127.0.0.1:6633"
        is_connected: true
    fail_mode: secure
    Port patch-tun
        Interface patch-tun
            type: patch
            options: {peer=patch-int}
    Port "01620459-aa05-4a25-9bf3-41a9390d94b1"
        Interface "01620459-aa05-4a25-9bf3-41a9390d94b1"
    Port "715b022f-1bad-4f81-b9bf-9d0e4a2973f4"
        tag: 2
        Interface "715b022f-1bad-4f81-b9bf-9d0e4a2973f4"
    Port "502167c0-d71a-483d-b099-4e3496d53925"
        tag: 2
        Interface "502167c0-d71a-483d-b099-4e3496d53925"
    Port "57152408-69f5-4464-8121-730550ae193e"
        tag: 1
        Interface "57152408-69f5-4464-8121-730550ae193e"
    Port br-int
        Interface br-int
            type: internal

In that example Port "01620459-aa05-4a25-9bf3-41a9390d94b1" is configured without tag, which means of course that the network is not working in virtual machine. After restart of neutron ovs agent service, it is recreated with tag and the network is connected. It's Openvswitch 2.7 and Ocata version of hyperv compute on Hyper-V Server 2016.

Hi The issue is happening when new instance is creating or when instance is migrated to other host. So very often network port is misconfigured, like here:

Bridge br-int
    Controller "tcp:127.0.0.1:6633"
        is_connected: true
    fail_mode: secure
    Port patch-tun
        Interface patch-tun
            type: patch
            options: {peer=patch-int}
    Port "01620459-aa05-4a25-9bf3-41a9390d94b1"
        Interface "01620459-aa05-4a25-9bf3-41a9390d94b1"
    Port "715b022f-1bad-4f81-b9bf-9d0e4a2973f4"
        tag: 2
        Interface "715b022f-1bad-4f81-b9bf-9d0e4a2973f4"
    Port "502167c0-d71a-483d-b099-4e3496d53925"
        tag: 2
        Interface "502167c0-d71a-483d-b099-4e3496d53925"
    Port "57152408-69f5-4464-8121-730550ae193e"
        tag: 1
        Interface "57152408-69f5-4464-8121-730550ae193e"
    Port br-int
        Interface br-int
            type: internal

In that example Port "01620459-aa05-4a25-9bf3-41a9390d94b1" is configured without tag, which means of course that the network is not working in virtual machine. After restart of neutron ovs agent service, it is recreated with tag and the network is connected. It's Openvswitch 2.7 and Ocata version of hyperv compute on Hyper-V Server 2016.

Edit: Need to add to [ovs] section of neutron ovs agent: ofinterface agent:

of_interface = ovs-ofctl ovsdbinterface ovs-ofctl

ovsdb_interface = vsctl

As described in https://ask.cloudbase.it/question/1792/ovs-251-tunnel-problem-no-network-inside-vm/