New Question

Revision history [back]

click to hide/show revision 1
initial version

Why OVS bridge fails after a reboot on Windows 2016?

We're creating an ovs bridge, and then a bond on Windows 2016 Core:

ovs-vsctl add-br br0 ovs-vsctl add-bond br0 bond0 "Ethernet" "Ethernet 1" bond_mode=balance-slb Enable-NetAdapter br0 New-NetIPAddress -InterfaceAlias "br0" -IPAddress XX.XX.XX.XX -PrefixLength 26

Everything works fine up to the point when we reboot the server, after the reboot the interface is not restored, ovs-vsctl show returns the error:

ovs-vsctl show Bridge br0 Port br0 Interface br0 type: internal error: "could not add network device br0 to ofproto (Invalid argument)" Port "bond0" Interface "Ethernet 4" Interface Ethernet

Can anyone advise what might be happening?

Why OVS bridge fails after a reboot on Windows 2016?

We're creating an ovs bridge, and then a bond on Windows 2016 Core:

ovs-vsctl add-br br0
ovs-vsctl add-bond br0 bond0 "Ethernet" "Ethernet 1" bond_mode=balance-slb
Enable-NetAdapter br0
New-NetIPAddress -InterfaceAlias "br0" -IPAddress XX.XX.XX.XX -PrefixLength 26

26

Everything works fine up to the point when we reboot the server, after the reboot the interface is not restored, ovs-vsctl show returns the error:

ovs-vsctl show
    Bridge br0
        Port br0
            Interface br0
                type: internal
                error: "could not add network device br0 to ofproto (Invalid argument)"
        Port "bond0"
            Interface "Ethernet 4"
            Interface Ethernet

Ethernet

Can anyone advise what might be happening?