New Question
0

cannot connect the second virtual network adapter to vSwitch on a VM/default gateway is unreachable after hyper-v host is restarted

asked 2018-07-11 07:17:01 +0300

Hi Expert,

Background:

  1. 2 hosts with Hyper-V Server 2016 and Open vSwitch 2.7.0 installed.
  2. for each host, we have 2 NICs (NIC1/NIC2 are teaming members for public network) , the virtua switch name is FSOPublicNetwork.
  3. we are testing vxlan according to tihs doc: https://cloudbase.it/open-vswitch-2-5..., it's fine.

Two issues:

  1. we found that the default gateway is unreachable after restarting a Hyper-v host; maybe several minutes later and nothting to do, the default gateway become reachable, it's wired.
  2. we tried to connect the second virtual network adapter to the vSwitch on a VM, but failed and the error message is "failed to modify device 'Ethernet Connection"

OVS Configuration:

Bridge br-int
    Port br-int
        Interface br-int
            type: internal
    Port "vlnx150000001"
        Interface "vlnx150000001"
    Port "vlnx151000002"
        Interface "vlnx151000002"
    Port patch-tun
        Interface patch-tun
            type: patch
            options: {peer=patch-int}
Bridge br-tun
    Port patch-int
        Interface patch-int
            type: patch
            options: {peer=patch-tun}
    Port br-tun
        Interface br-tun
            type: internal
    Port "vxlan-1"
        Interface "vxlan-1"
            type: vxlan
            options: {in_key=flow, local_ip="172.31.153.20", out_key=flow, remote_ip="172.31.153.19"}
Bridge "br-port1"
    Port "br-port1"
        tag: 31
        Interface "br-port1"
            type: internal
    Port FSOPublicNetwork
        Interface FSOPublicNetwork

OVS datapath show

enter code heresystem@ovs-system:
    lookups: hit:5279083 missed:10029059 lost:0
    flows: 144
    port 1: br-port1 (internal)
    port 2: FSOPublicNetwork
    port 3: br-tun (internal)
    port 4: vxlan_sys_4789 (vxlan)
    port 5: vlnx150000001
    port 6: vlnx151000002
    port 7: br-int (internal)
edit retag flag offensive close merge delete

1 answer

Sort by » oldest newest most voted
0

answered 2018-07-11 09:57:46 +0300

for the second issue, some error from windows event logs is for your reference:

Hyper-V Switch EventID 68

Failed to create port A2999EE4-55C2-47FB-8C6F-63C6CCF5323B (Friendly Name: Dynamic Ethernet Switch Port) on switch A85E73A9-0CEF-426F-99A5-180EF5773181 (Friendly Name: FSOPublicNetwork). Status = {Data Not Accepted} The TDI client could not handle the data received during an indication..

Hyper-V Switch EventID 34

Failed to create port A2999EE4-55C2-47FB-8C6F-63C6CCF5323B (Friendly Name: Dynamic Ethernet Switch Port) on switch A85E73A9-0CEF-426F-99A5-180EF5773181 (Friendly Name: FSOPublicNetwork). The task was vetoed by a switch extension, or the switch extension stack is corrupted. Status = {Data Not Accepted} The TDI client could not handle the data received during an indication..

edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Question Tools

1 follower

Stats

Asked: 2018-07-11 07:17:01 +0300

Seen: 3 times

Last updated: Jul 11