Open vSwitch configuration in 3.2

[tomstephens89]

Hi guys, Im new here but have been testing Proxmox as a potential replacement for a large VMWare ESXi environment and so far I think it is excellent!

I have just installed 3.2 on a test box and installed the openvswitch package. I am looking for some guidance on how to configure it in Proxmox VE 3.2.

My host has 2 NIC's, eth0 and eth1. I want to bond them in an active-backup configuration. There are 3 VLAN's trunked to the host. 10, 20 and 50.

How would I go about setting this up using OVS? With standard linux bridging & bonds I would create a bond for every VLAN such as bond0.50, bond0.10 etc.... Then create a bridge to each of those bonds.

I don't quite understand how to do the same with OVS and take advantage of its features.

Thanks
Tom

 

[Almost]

The same question. Please provide more info about OVS. How we can use it? If it have GUI interface or commands ? More INFO please.

 

[firegs]

A video tutorial would be super.

 

[spirit]

Hi guys, Im new here but have been testing Proxmox as a potential replacement for a large VMWare ESXi environment and so far I think it is excellent!

I have just installed 3.2 on a test box and installed the openvswitch package. I am looking for some guidance on how to configure it in Proxmox VE 3.2.

My host has 2 NIC's, eth0 and eth1. I want to bond them in an active-backup configuration. There are 3 VLAN's trunked to the host. 10, 20 and 50.

How would I go about setting this up using OVS? With standard linux bridging & bonds I would create a bond for every VLAN such as bond0.50, bond0.10 etc.... Then create a bridge to each of those bonds.

I don't quite understand how to do the same with OVS and take advantage of its features.

Thanks
Tom

you can use the gui.

you need to create an ovs bond. (!= linux bond), create an openvswitch bridge.

vlans are managed on the openvswitch, by port, like a real switch. So no need to bond0.50, bond0.10,...

you just need to define the vlan in your vm network nic config.

 

[Almost]

you can use the gui.

Gui is only for Bridging or Bonding, mb VLans as you say.

But what about SFlow NetFlow and another flexible settings of OVS. How we can control it ?

 

[spirit]

But what about SFlow NetFlow and another flexible settings of OVS. How we can control it ?

[/QUOTE]

I think you can edit /etc/network/interfaces,

and add OVS_EXTRA

auto vmbr0
iface vmbr0 inet static
        address  X.X.X.X
        netmask  255.255.255.0
        broadcast  X.X.X.
        ovs_type OVSBridge
        ovs_ports eth0
        ovs_extra set Bridge vmbr0 netflow....

 

[cctogaryback]

HI All , is their a problem with openvswitch i only ask because each time i create an ovs bridge i get an error openv switch not installed !
this is proxmox 3.2-4/e24a91c1 Ive install by apt-get install openvswitch-switch but wonder if this is the right way to go ?
any one offer some help ?

 

[dietmar]

Ive install by apt-get install openvswitch-switch but wonder if this is the right way to go ?

Yes, this is the right way.

 

[vizerei]

you can use the gui.

you need to create an ovs bond. (!= linux bond), create an openvswitch bridge.

vlans are managed on the openvswitch, by port, like a real switch. So no need to bond0.50, bond0.10,...

you just need to define the vlan in your vm network nic config.

I believe the OP asked how to do it. While what to do is great, a lot of people here are not familiar with OVS, get even more confused in proxmox's implimentation versus OVS tutorials on the web, and would appreciate some instruction. Proxmox recommends you configure using the GUI, but I am in a similar boat as I can't find out how to assign CT interfaces to a specific VLAN.

So how do you do this?

 

[spirit]

but I am in a similar boat as I can't find out how to assign CT interfaces to a specific VLAN.

gui for openvz veth vlan interface will be available soon in next proxmox release (linux bridge and ovs)

Currently it's only available for qemu.

 

[berny]

Hi,

Can Proxmox support provide a youtube video with an example on how to create an OVS to assign vlans to vm's.

Because it is pretty confusing.

Thanks in advance

 

[valshare]

same here. A little example how exactly to configure openvz where helpful

 

[c4rdinal]

you just need to define the vlan in your vm network nic config.

Could you please provide us with example on how to achieve this? This is very confusing. I've been working with this for 2 days now and still can't make it work.

Here's the steps I followed.
1. Created a vSwitch Bond1 (GUI)
2. Created a vSwitch Bridge vmbr1 (GUI)

edit /etc/network/interfaces

# network interface settings
auto vlan10
iface vlan10 inet manual
vlan_raw_device bond1

auto vlan100
iface vlan100 inet manual
vlan_raw_device bond1

auto vlan125
iface vlan125 inet manual
vlan_raw_device bond1

auto lo
iface lo inet loopback

auto eth0
iface eth0 inet manual

iface eth1 inet manual

auto eth2
iface eth2 inet manual
up ifconfig $IFACE 0.0.0.0 up
down ifconfig $IFACE down

auto eth3
iface eth3 inet manual
up ifconfig $IFACE 0.0.0.0 up
down ifconfig $IFACE down

auto bond1
iface bond1 inet manual
slaves eth2 eth3
bond_miimon 100
bond_mode 802.3ad
bond_xmit_hash_policy layer3+4

auto vmbr0
iface vmbr0 inet static
address 192.168.125.13
netmask 255.255.255.0
gateway 192.168.125.1
bridge_ports eth0
bridge_stp off
bridge_fd 0

auto vmbr1
iface vmbr1 inet static
address 192.168.100.222
netmask 255.255.255.0
broadcast 192.168.100.255
ovs_type OVSBridge
ovs_port vmbr1
ovs_extra set Bridge vmbr0 netflow
# up ifconfig $IFACE 0.0.0.0 up
# down ifconfig $IFACE down



# ifconfig
root@prox13:~# ifconfig | more
eth0 Link encap:Ethernet HWaddr 00:1b:21:3a:7d:78
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:8652 errors:0 dropped:0 overruns:0 frame:0
TX packets:2345 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1825337 (1.7 MiB) TX bytes:1050979 (1.0 MiB)
Memory:e2420000-e2440000

eth2 Link encap:Ethernet HWaddr 00:15:17:27:f0:92
UP BROADCAST SLAVE MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
Interrupt:20 Memory:e2600000-e2620000

eth3 Link encap:Ethernet HWaddr 00:15:17:27:f0:92
UP BROADCAST SLAVE MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
Memory:e2400000-e2420000

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:6485 errors:0 dropped:0 overruns:0 frame:0
TX packets:6485 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:877379 (856.8 KiB) TX bytes:877379 (856.8 KiB)

vmbr0 Link encap:Ethernet HWaddr 00:1b:21:3a:7d:78
inet addr:192.168.125.13 Bcast:192.168.125.255 Mask:255.255.255.0
inet6 addr: fe80::21b:21ff:fe3a:7d78/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:7965 errors:0 dropped:0 overruns:0 frame:0
TX packets:2368 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1446676 (1.3 MiB) TX bytes:1054640 (1.0 MiB)

vmbr1 Link encap:Ethernet HWaddr aa:97:37:49:c9:45
inet addr:192.168.100.222 Bcast:192.168.100.255 Mask:255.255.255.0
inet6 addr: fe80::a897:37ff:fe49:c945/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0

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

But still, I cannot ping the vmbr1 ip 192.168.100.222 from a remote host. I noticed that the bond1 interface is not ACTIVE. How can I fix this?