Mandatory naming convention for OVSBridge and OVSBond?

tok1

New Member
May 3, 2020
5
0
1
52
Hi,

I am building a new Proxmox 6.2 server right now using Open vSwitch-based network configuration. I came up with a (from ovs-perspective) perfectly fine working configuration that is however not accepted by Proxmox, apparently due to naming:

Code:
# Loopback interface
auto lo
iface lo inet loopback

auto gig-br
allow-ovs gig-br
iface gig-br inet manual
  ovs_type OVSBridge
  ovs_ports gig-bond mgmt1
  ovs_mtu 9000
# GigE-Bridge

auto tengig-br
allow-ovs tengig-br
iface tengig-br inet manual
  ovs_type OVSBridge
  ovs_ports tengig-bond mgmt0 sid-vlan10
  ovs_mtu 9000
# TenGigE-Bridge

allow-gig-br enp35s0
iface enp35s0 inet manual
    ovs_mtu 9000
# GigE-Top

allow-gig-br enp36s0
iface enp36s0 inet manual
    ovs_mtu 9000
# GigE-Bottom

allow-gig-br gig-bond
iface gig-bond inet manual
  ovs_bridge gig-br
  ovs_type OVSBond
  ovs_bonds enp35s0 enp36s0
  ovs_options bond_mode=balance-tcp lacp=active other_config:lacp-time=fast tag=1 vlan_mode=native-untagged
  ovs_mtu 9000
# Gig-Bond

allow-gig-br mgmt1
iface mgmt1 inet static
  ovs_type OVSIntPort
  ovs_bridge gig-br
  ovs_options tag=99
  address 192.168.99.5
  netmask 255.255.255.0
  ovs_mtu 1500

allow-tengig-br enp43s0
iface enp43s0 inet manual
    ovs_mtu 9000
# TenGigE-Right

allow-tengig-br enp43s0d1
iface enp43s0d1 inet manual
    ovs_mtu 9000
# TenGigE-Left

allow-tengig-br tengig-bond
iface tengig-bond inet manual
  ovs_bridge tengig-br
  ovs_type OVSBond
  ovs_bonds enp43s0 enp43s0d1
  ovs_options bond_mode=balance-tcp lacp=active other_config:lacp-time=fast tag=1 vlan_mode=native-untagged
  ovs_mtu 9000
# TenGigE-Bond

allow-tengig-br sid-vlan10
iface sid-vlan10 inet static
  ovs_type OVSIntPort
  ovs_bridge tengig-br
  ovs_options tag=10
  address 192.168.1.4
  netmask 255.255.255.0
  ovs_mtu 9000

allow-tengig-br mgmt0
iface mgmt0 inet static
  ovs_type OVSIntPort
  ovs_bridge tengig-br
  ovs_options tag=99
  address 192.168.99.10
  netmask 255.255.255.0
  gateway 192.168.99.1
  ovs_mtu 1500

Open vSwitch is fine with it and network is fully functional (!), no errors in the journal either:
Code:
> ovs-vsctl show
4bcb6001-2b9f-478d-be6f-7149ecab36b9
    Bridge tengig-br
        Port tengig-bond
            tag: 1
            Interface "enp43s0"
            Interface "enp43s0d1"
        Port "sid-vlan10"
            tag: 10
            Interface "sid-vlan10"
                type: internal
        Port "mgmt0"
            tag: 99
            Interface "mgmt0"
                type: internal
        Port tengig-br
            Interface tengig-br
                type: internal
    Bridge gig-br
        Port gig-br
            Interface gig-br
                type: internal
        Port gig-bond
            tag: 1
            Interface "enp35s0"
            Interface "enp36s0"
    ovs_version: "2.12.0"

But Proxmox WebGUI, System > Network, lists both the bonds and the bridges as UNKOWN. And does not offer any of the bridges to select while creating a new Container or VM - the dropdown list is simply empty.

After renaming bonds and bridges to vmbr0, vmbr1, bond0, bond1 and rebooting, everything worked. Is Proxmox imposing a mandatory naming convention that does not exist with ovs itself?

Regards
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get your own in 60 seconds.

Buy now!