OVSBond + OVSBridge setup problem

E

ejmerkel

Renowned Member
Proxmox Subscriber
Sep 20, 2012
121
4
83
In the GUI I created an OVSBond named bond1 of interfaces eth1 and eth3 and then created an OVSBridge named vmbr1. However after rebooting, if I do an ifconfig there is no bond1 interface or vmbr1. Here is the relevant section of the interfaces file.

Code: 
iface eth1 inet manual


iface eth3 inet manual

allow-vmbr1 bond1
iface bond1 inet manual
        ovs_bonds eth1 eth3
        ovs_type OVSBond
        ovs_bridge vmbr1
        ovs_options lacp=active lacp-time=fast bond_mode=balance-tcp

auto vmbr1
iface vmbr1 inet manual
        ovs_type OVSBridge
        ovs_ports bond1

The switch ports that these interfaces plugs into show that they are DOWN (no link). In the GUI

bond1 shows Active=No and Autostart=no (there is no option for Autostart to be checked).
vmbr1 shows Active=No and Autostart=Yes

These devices were working when setup as a regular linux bond.

Code: 
#ovs-vsctl show
96d93704-76d6-4bcd-8ea9-7837b208f681
    ovs_version: "1.4.2"


#ovs-appctl bond/show bond1
no such bond
ovs-appctl: ovs-vswitchd: server returned reply code 501

It is almost like the GUI config is not making it into the OVS config. I am running PVE 3.1-1/ao6c9f73 which is the free version with updates run.

Does anyone have any idea what could be wrong with our setup?

Thanks,
Eric
 
I bought a subscription and then did an upgrade. I am now showing proper version.

Code: 
dpkg -l | grep openvs
ii  openvswitch-common               2.3.0-1                       amd64        Open vSwitch common components
ii  openvswitch-switch               2.3.0-1                       amd64        Open vSwitch switch implementations

But I am still not seeing what I should.

Code: 
ovs-vsctl show
a42c5694-b695-4b2a-b401-ccac1f252fdc
    ovs_version: "2.3.0"

ovs-appctl bond/show bond1
no such bond
ovs-appctl: ovs-vswitchd: server returned an error

Both Bond1 and vmbr1 show Active=no. The ethernet's in question, do now show ethernet link. Here is the relevant interfaces section.

Code: 
auto bond1
allow-vmbr1 bond1
iface bond1 inet manual
        ovs_bonds eth1 eth3
        ovs_type OVSBond
        ovs_bridge vmbr1
        ovs_options lacp=active lacp-time=fast bond_mode=balance-tcp


auto vmbr1
iface vmbr1 inet manual
        ovs_type OVSBridge
        ovs_ports bond1

Any idea what else to look at?

Thanks,
Eric
 
Last edited:
Just to followup as I continue to investigate this, it is almost as if the GUI config is not getting propagated to the OVS config.

Code: 
[COLOR=#000000][FONT=tahoma]/etc/openvswitch/conf.db does not exist ... (warning).[/FONT][/COLOR]
[COLOR=#000000][FONT=tahoma]Creating empty database /etc/openvswitch/conf.db.[/FONT][/COLOR]

I am not sure but perhaps this is related to http://forum.proxmox.com/threads/18858-Openvswitch-init-problems-at-boot

Perhaps OVS is not production ready?

Code: 
proxmox-ve-2.6.32: 3.3-139 (running kernel: 2.6.32-34-pve)
pve-manager: 3.3-5 (running version: 3.3-5/bfebec03)
pve-kernel-2.6.32-32-pve: 2.6.32-136
pve-kernel-2.6.32-34-pve: 2.6.32-140
lvm2: 2.02.98-pve4
clvm: 2.02.98-pve4
corosync-pve: 1.4.7-1
openais-pve: 1.1.4-3
libqb0: 0.11.1-2
redhat-cluster-pve: 3.2.0-2
resource-agents-pve: 3.9.2-4
fence-agents-pve: 4.0.10-1
pve-cluster: 3.0-15
qemu-server: 3.3-3
pve-firmware: 1.1-3
libpve-common-perl: 3.0-19
libpve-access-control: 3.0-15
libpve-storage-perl: 3.0-25
pve-libspice-server1: 0.12.4-3
vncterm: 1.1-8
vzctl: 4.0-1pve6
vzprocps: 2.0.11-2
vzquota: 3.1-2
pve-qemu-kvm: 2.1-10
ksm-control-daemon: 1.1-1
glusterfs-client: 3.5.2-1

Thanks again for any input.

Best regards,
Eric
 
You must log in or register to reply here.
Top Bottom