vmbr0 is not up

Adam Cheung

New Member
Nov 21, 2016
5
0
1
40
Hi,

I've change my setup from linux bridge to openvswitch, everything works flawlessly.
But I found that vmbr0 is not up in cli nor web interface. Why?
Thanks in advance!

root@pve5:~# ovs-vsctl show
e55e4552-ce67-4b02-b5ae-f4efc1a8c0f2
Bridge "vmbr0"
Port "tap150i0"
Interface "tap150i0"
Port "bond0"
Interface "eth0"
Interface "eth1"
Interface "eth3"
Interface "eth2"
Port "vlan1"
Interface "vlan1"
type: internal
Port "tap150i1"
Interface "tap150i1"
Port "veth151i0"
tag: 3
Interface "veth151i0"
Port "veth111i0"
Interface "veth111i0"
Port "fwln114o0"
Interface "fwln114o0"
type: internal
Port "tap113i1"
Interface "tap113i1"
Port "vmbr0"
Interface "vmbr0"
type: internal
Port "fwln998o0"
tag: 3
Interface "fwln998o0"
type: internal
Port "veth183i0"
tag: 2
Interface "veth183i0"
Port "veth182i0"
tag: 2
Interface "veth182i0"
Port "tap190i0"
tag: 2
Interface "tap190i0"
Port "veth112i0"
tag: 2
Interface "veth112i0"
Port "veth105i0"
Interface "veth105i0"
Port "tap115i0"
tag: 2
Interface "tap115i0"
Port "tap208i0"
tag: 2
Interface "tap208i0"
ovs_version: "2.6.0"
root@pve5:~# pveversion --verbose
proxmox-ve: 4.4-79 (running kernel: 4.4.35-2-pve)
pve-manager: 4.4-12 (running version: 4.4-12/e71b7a74)
pve-kernel-4.4.6-1-pve: 4.4.6-48
pve-kernel-4.2.6-1-pve: 4.2.6-36
pve-kernel-4.4.35-2-pve: 4.4.35-79
pve-kernel-4.2.8-1-pve: 4.2.8-41
lvm2: 2.02.116-pve3
corosync-pve: 2.4.0-1
libqb0: 1.0-1
pve-cluster: 4.0-48
qemu-server: 4.0-108
pve-firmware: 1.1-10
libpve-common-perl: 4.0-91
libpve-access-control: 4.0-23
libpve-storage-perl: 4.0-73
pve-libspice-server1: 0.12.8-1
vncterm: 1.2-1
pve-docs: 4.4-3
pve-qemu-kvm: 2.7.1-1
pve-container: 1.0-93
pve-firewall: 2.0-33
pve-ha-manager: 1.0-40
ksm-control-daemon: 1.2-1
glusterfs-client: 3.5.2-2+deb8u3
lxc-pve: 2.0.7-1
lxcfs: 2.0.6-pve1
criu: 1.6.0-1
novnc-pve: 0.5-8
smartmontools: 6.5+svn4324-1~pve80
zfsutils: 0.6.5.8-pve14~bpo80
openvswitch-switch: 2.6.0-2
# network interface settings; autogenerated
# Please do NOT modify this file directly, unless you know what
# you're doing.
#
# If you want to manage part of the network configuration manually,
# please utilize the 'source' or 'source-directory' directives to do
# so.
# PVE will preserve these directives, but will NOT its network
# configuration from sourced files, so do not attempt to move any of
# the PVE managed interfaces into external files!

auto lo
iface lo inet loopback

iface eth0 inet manual

iface eth1 inet manual

iface eth2 inet manual

iface eth3 inet manual

allow-vmbr0 bond0
iface bond0 inet manual
ovs_bonds eth0 eth1 eth2 eth3
ovs_type OVSBond
ovs_bridge vmbr0
ovs_options lacp=active bond_mode=balance-tcp vlan_mode=native-untagged

auto vmbr0
iface vmbr0 inet manual
ovs_type OVSBridge
ovs_ports bond0 vlan1

allow-vmbr0 vlan1
iface vlan1 inet static
address 192.168.x.x
netmask 255.255.255.0
gateway 192.168.x.x
ovs_type OVSIntPort
ovs_bridge vmbr0
root@pve5:/etc/network# ifconfig vmbr0
vmbr0 Link encap:Ethernet HWaddr b8:ca:3a:f5:xx:xx
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:879994 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

Picture of Web Interface
https://drive.google.com/open?id=0B2vXTGt0Cnmdbl9GeWdkUkJ6LUE
 
By default an ovs bridge is shown as down when no IP address is assigned to it - but works. You can consider this as (minor) ovs bug, but it does not affect the proper functionality.
 

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 yours easily in our online shop.

Buy now!