Proxmox 3.3 + vSWITCH + BOND + VLAN

C

c4rdinal

New Member
Nov 13, 2012
20
0
1
Hi,

I have a problem configuring BONDED VLAN using vSwitch on Proxmox 3.3. I can see all the interfaces as ACTIVE and ifconfig indeed show that they are up and running. I have searched thoroughly Proxmox site and Googled for a couple of days but did not find exactly what I'm looking for. However, I made some progress and hopefully might help someone in the future.

I posted the Screenshot of the GUI just in case someone with the same problem can relate to it and be able to solve it.

Here's the /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

auto eth1
iface eth1 inet manual

auto eth2
iface eth2 inet manual
bond-master bond1

auto eth3
iface eth3 inet manual
bond-master bond1

auto bond1
allow-vmbr1 bond1
iface bond1 inet manual
ovs_bonds eth2 eth3
ovs_type OVSBond
ovs_bridge vmbr1
ovs_options lacp=active bond_mode=balance-slb

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
allow-ovs vmbr1
iface vmbr1 inet static
address 192.168.100.222
netmask 255.255.255.0
broadcast 192.168.100.255
ovs_type OVSBridge
ovs_ports bond1

You will get this error because bond1 "Recieved a packet with it's own address" errors.

Oct 13 13:34:28 prox13 kernel: [ 2409.104092] 8021q: adding VLAN 0 to HW filter on device bond1
Oct 13 13:34:28 prox13 kernel: [ 2409.104993] 8021q: VLANs not supported on bond1
Oct 13 13:34:28 prox13 kernel: [ 2409.355777] 8021q: VLANs not supported on bond1
Oct 13 13:34:28 prox13 kernel: [ 2409.514515] 8021q: VLANs not supported on bond1

To fix above error, add these entries to /etc/sysctl.conf:

net.bridge.bridge-nf-call-ip6tables = 0
net.bridge.bridge-nf-call-iptables = 0
net.bridge.bridge-nf-call-arptables = 0
net.bridge.bridge-nf-filter-vlan-tagged = 0

sysctl -p


I'm close but still have some error:

bond1: Warning: the permanent HWaddr of eth2 - 00:15:17:27:f0:92 - is still in use by bond1. Set the HWaddr of eth2 to a different address to avoid conflicts.

root@prox13:~# ifconfig | grep -A 1 HWaddr
bond1 Link encap:Ethernet HWaddr 00:15:17:27:f0:92
inet6 addr: fe80::215:17ff:fe27:f092/64 Scope:Link
--
eth0 Link encap:Ethernet HWaddr 00:1b:21:3a:7d:78
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
--
eth2 Link encap:Ethernet HWaddr 00:15:17:27:f0:92
UP BROADCAST RUNNING SLAVE MULTICAST MTU:1500 Metric:1
--
eth3 Link encap:Ethernet HWaddr 00:15:17:27:f0:92
UP BROADCAST SLAVE MULTICAST MTU:1500 Metric:1
--
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
--
vmbr1 Link encap:Ethernet HWaddr aa:97:37:49:c9:45
inet6 addr: fe80::a897:37ff:fe49:c945/64 Scope:Link

QUESTION:
1. I noticed that bond1, eth2 and eth3 uses the same MAC address. Is this normal behavior due to Bonded interface?
2. I still can't ping vmbr1 IP address. And ifconfig shows no ip address even it was configured in the /etc/network/interfaces. How can I fix this?
3. Any comment with the config posted above? Pls, pls?

I'm stuck now for 3days and is losing direction. I'll appreciate any help please.

Many thanks in advance.
 

Attachments

  • Proxmox Network Config.jpg
    Proxmox Network Config.jpg
    101.4 KB · Views: 60
Last edited:
You need to use OVSIntPort's to separate out your vlans into interfaces on the host. Do not attempt to mix regular linux bridging, bonding and vlans with OVS, it won't work (you can't assign a vlan to an ovs bond). Also, you could never use a bond directly that was part of a bridge, that wouldn't work even if you weren't using OVS.

Here's my /etc/network/interfaces that uses bonds, bridges, and vlans. Hopefully it will clarify things for you. I've never used the GUI for this stuff so don't know how it translates.

Code: 
auto lo
iface lo inet loopback

allow-vmbr0 ovsbond
iface ovsbond inet manual
  ovs_bridge vmbr0
  ovs_type OVSBond
  ovs_bonds eth0 eth1
  # Needed for using an mtu other than 1500
  pre-up ( ifconfig eth0 mtu 9000 && ifconfig eth1 mtu 9000 )
  ovs_options bond_mode=balance-tcp lacp=active other_config:lacp-time=fast
  mtu 9000

auto vmbr0
allow-ovs vmbr0
iface vmbr0 inet manual
  ovs_type OVSBridge
  ovs_ports ovsbond vlan50 vlan55
  mtu 9000

# Proxmox cluster communication vlan
allow-vmbr0 vlan50
iface vlan50 inet static
  ovs_type OVSIntPort
  ovs_bridge vmbr0
  ovs_options tag=50
  ovs_extra set interface ${IFACE} external-ids:iface-id=$(hostname -s)-${IFACE}-vif
  address 10.50.10.44
  netmask 255.255.255.0
  gateway 10.50.10.1
  mtu 1500

# Ceph cluster communication vlan (jumbo frames)
allow-vmbr0 vlan55
iface vlan55 inet static
  ovs_type OVSIntPort
  ovs_bridge vmbr0
  ovs_options tag=55
  ovs_extra set interface ${IFACE} external-ids:iface-id=$(hostname -s)-${IFACE}-vif
  address 10.55.10.44
  netmask 255.255.255.0
  mtu 9000
 
brad_mssw said:
You need to use OVSIntPort's to separate out your vlans into interfaces on the host. Do not attempt to mix regular linux bridging, bonding and vlans with OVS, it won't work (you can't assign a vlan to an ovs bond). Also, you could never use a bond directly that was part of a bridge, that wouldn't work even if you weren't using OVS.

Here's my /etc/network/interfaces that uses bonds, bridges, and vlans. Hopefully it will clarify things for you. I've never used the GUI for this stuff so don't know how it translates.
Click to expand...

Hi brad_mssw,

Thank you so much for taking the time to explain and sharing the configs. However I tried to implement what you posted with only a few modification, but I can't seem to make it work. No matter how I tried it failed. I'm not sure why.

Some of the problems where:
1. All the interfaces don't become Active. I only got the loopback active and nothing else using the posted config.
2. ALL NIC interfaces don't become ACTIVE on boot. I will have to provide: bond-master bond0 for eth0, eth1 to become active. I'm not sure if this is correct but below option makes NIC ACTIVE. However, there is no IP Address as configured in the interface.
Code: 
auto eth0
    iface eth0 inet manual
    bond-master bond0

3. Manually changing vmbr1 status using ifconfig vmbr1 up, makes the interface active but does not show in ifconfig the hardcoded IP Address (192.168.125.13/24), which I believe it should.
4. Using vmbr0 throws an error:
vmbr0: ERROR while getting interface flags: No such device

As preparation, I always delete the contents of /etc/udev/rules.d/70-persistent-net.rules

# cat /proc/net/dev shows the interfaces
eth0 eth1 eth2 eth3 bond0


Here's what I did.
Code: 
    auto lo
    iface lo inet loopback

##### [B]I TRIED TO EXCLUDE THIS FROM THE CONFIG BUT STILL NOT WORKING[/B] #####        
    auto eth0
    iface eth0 inet manual
    #Without this option, no matter what I do cannot make the bond0 interface active or up    
    bond-master bond0  

    auto eth1
    iface eth1 inet manual
    bond-master bond0
#############################################################

        allow-vmbr1 bond0
        iface bond0 inet manual
          ovs_bridge vmbr1
          ovs_type OVSBond
          ovs_bonds eth0 eth1
          # Needed for using an mtu other than 1500
          pre-up ( ifconfig eth0 mtu 9000 && ifconfig eth1 mtu 9000 )
          ovs_options bond_mode=balance-tcp lacp=active other_config:lacp-time=fast
          mtu 9000

        auto vmbr1
        allow-ovs vmbr1
        iface vmbr1 inet manual
          ovs_type OVSBridge
          ovs_ports bond0 vlan50 
          mtu 9000

        # Proxmox cluster communication vlan
        allow-vmbr1 vlan50
        iface vlan50 inet static
          ovs_type OVSIntPort
          ovs_bridge vmbr1
          ovs_options tag=50
          ovs_extra set interface ${IFACE} external-ids:iface-id=$(hostname -s)-${IFACE}-vif
          address 192.168.125.13
          netmask 255.255.255.0
          gateway 192.168.125.1
          mtu 1500

I used bond0 since whenever you generate OVS_BOND using the gui it normally label it as bondN. Logs doesn't show anything meaningful or show any clue about the problem. I've been trying so hard to fix it myself, but sorry, I failed several attempts and have no clue on how to proceed further.

I also, tried "AS IS" the configs and only changing the IP address for vlan 50. But still failed to make it work. I'm very sure that all NICs are working and is installed.

I hope you can help me fix my problem. Appreciate your support.

Many thanks
Reply With Quote
 
Last edited:
The part you said you tried to exclude, you definitely need to exclude.

However, that's not the core of your problem, I guess I forgot to mention there is an OVS bug at boot at the moment. I ended up writing a wiki on OVS yesterday since I saw a bunch of people were hitting things I hit. It is available here: https://pve.proxmox.com/wiki/Open_vSwitch

Take note of the 'Startup Workaround' !
 
dietmar said:
AFAIK that bug is fixed, so I removed that section.
Click to expand...

Are you sure? I just hit that last week when using the latest pve-no-subscription and had to hunt around for the fix. Which is why I included it in the wiki I created for Open vSwitch. I can try removing it from one of my servers in my test lab to verify.
 
@c4rdinal:

What do you want to do with your vlan10,vlan100 && vlan125 ?

Ovs-int port are only administrative port, to this will not tag packets coming from the vms.

The only way I known is to tag port by port, that's what proxmox is doing when you use vlan tag on qemu vm network interface.
 
brad_mssw said:
Are you sure? I just hit that last week when using the latest pve-no-subscription and had to hunt around for the fix. Which is why I included it in the wiki I created for Open vSwitch. I can try removing it from one of my servers in my test lab to verify.
Click to expand...

Hello brad_mssw,

I can't thank you enough for your effort to answer my post. Now I have seen all the interfaces ACTIVE, eth0 eth1 vmbr0 bond0 and vlan125 having the right IP. BUT I DON'T SEE THE BRIDGE (vmbr0) INTERFACE, is this a normal behavior. And, I still cannot establish a connection to the machine from a remote host. I was hoping that from a remote host (physically connected via switch or cross cable) I can connect to it. ping tests failed

Code: 
C:\Users\Administrator>ping 192.168.125.13 -t

Pinging 192.168.125.13 with 32 bytes of data:
Reply from 192.168.125.77: Destination host unreachable.
Reply from 192.168.125.77: Destination host unreachable.
Reply from 192.168.125.77: Destination host unreachable.
Reply from 192.168.125.77: Destination host unreachable.
Reply from 192.168.125.77: Destination host unreachable.
Request timed out.
Request timed out.
Request timed out.

I already switched to the second interface but that failed as well.

1. Am I wrong to conclude that the assigned IP to VLAN125 can be used for proxmox management? Like access http://192.168.125.13:8006?
2. I'm planning to add another bonded interfaces BOND1 for eth2 eth3 and use vmbr1. I'm assuming this is possible using the config with a slight adjustment on names of interface? Am I correct?
3. In my currently running setup I have tap interfaces and vmbr interfaces. I don't see this now when running ifconfig. Should I expect those interfaces now? Sorry, it's my first time using openswitch.

Thanks so much for clearing many things to me. :)
 
Last edited:
spirit said:
@c4rdinal:

What do you want to do with your vlan10,vlan100 && vlan125 ?

Ovs-int port are only administrative port, to this will not tag packets coming from the vms.

The only way I known is to tag port by port, that's what proxmox is doing when you use vlan tag on qemu vm network interface.
Click to expand...

Am I wrong to conclude that the assigned IP to VLAN125 can be used for proxmox management? Or that I can access proxmox at VLAN125 as if it was a physical Interface of proxmox?
I also assume that I can assign those vlans to my VMs to establish networking. I'm still not able to establish any connection and all I get is a Destination host unreachable error. I tried DHCP Lease to see if that will push some config to the interface but that won't work either. Which only means, I'm still not getting packets through the interface.

I never had this issue with Proxmox 3.2 using linux bridge interfaces. :( But I've learned a lot so far. I hope I can finally make this work. I'm doing the best I can though to fix it myself, I just don't have the answer right now. pls bear with me.

Thanks for all your help.
 
Last edited:
c4rdinal;102061 I also assume that I can assign those vlans to my VMs to establish networking. .[/QUOTE said:
The ovs-int interfaces, tag vlan when packet are going out of this interface.
But your vms are not plugged on the ovs-int, so they are not tagged.
Code: 
eth0<-----ovs vmbr0<---tag-----ovs-int
                  <----------- vms interface.
What proxmox is doing when defined tag on qemu network interface is
Code: 
eth0<-----ovs vmbr0<---tag-----ovs-int
                   <----tag------ vms interface.

Can you send a working implementation for your setup with linux bridge ? like this, I could help you to translate it to ovs.
Click to expand...
 
Hello Spirit,

Firstly, thank you for taking time to answer. Here's my working setup for linux bridge.

# network interface settings

auto bond1
iface bond1 inet manual
slaves eth2 eth3
bond_miimon 100
bond_mode 802.3ad
bond_downdelay 200
bond_updelay 200

auto vlan10
iface vlan10 inet manual
vlan-raw-device bond1

auto vlan100
iface vlan100 inet manual
vlan-raw-device bond1

auto lo
iface lo inet loopback

iface eth0 inet manual

iface eth1 inet manual

iface eth2 inet manual

iface eth3 inet manual

#Proxmox Management
auto vmbr125
iface vmbr125 inet static
address 192.168.125.11
netmask 255.255.255.0
gateway 192.168.125.1
bridge_ports eth0
bridge_stp off
bridge_fd 0

auto vmbr10
iface vmbr10 inet static
address 192.168.10.11
netmask 255.255.255.0
bridge_ports vlan10
bridge_stp off
bridge_fd 0

auto vmbr100
iface vmbr100 inet static
address 192.168.100.11
netmask 255.255.255.0
bridge_ports vlan100
bridge_stp off
bridge_fd 0

#DRBD Interfaces
auto vmbr0
iface vmbr0 inet static
address 10.0.0.1
netmask 255.255.255.0
bridge_ports eth1
bridge_stp off
bridge_fd 0
post-up ifconfig eth1 mtu 9000

Also, I have a few clarification/questions:
1. Am I wrong to conclude that the assigned IP to VLAN125 can be used for proxmox management? Like access http://192.168.125.13:8006? using this setup?
2. I'm planning to add another bonded interfaces BOND1 for eth2 eth3 and use vmbr1. I'm assuming this is possible using the config with a slight adjustment on names of interface? Am I correct?
3. In my currently running setup I have tap interfaces and vmbr interfaces. I don't see this now when running ifconfig. Should I expect those interfaces now? Sorry, it's my first time using openswitch.
 
Ok, I understand more better now, with the vmbr100,vmbr10. (used for the vms right ?)
So, for this setup, you don't want to define vlan in proxmox qemu/openvz vm network interfaces (right ?)

In this case, I think we can do something like

Code: 
eth2  ---ovs bond1----ovs vmbrmain---[ tagged here]----ovsint (vlan125)
eth3                              ---[ tagged here]----ovsint (vlan10)----------------ovs vmbr10
                                   ---[ tagged here]----ovsint (vlan100)--------------ovs vmbr100

the trick is to plug new ovs on top on a main ovs, through ovsint interface. Like this the vlan will be tagged when packets is going out.


So, I think this should work.

Code: 
auto eth2
iface eth2 inet manual


auto eth3
iface eth3 inet manual


auto vmbrmain
allow-ovs vmbrmain
  iface vmbrmain inet manual
  ovs_type OVSBridge
  ovs_ports bond1 vlan50 vlan100 vlan125 


allow-vmbrmain bond1
  iface bond1 inet manual
  ovs_bridge vmbrmain
  ovs_type OVSBond
  ovs_bonds eth2 eth3
  ovs_options bond_mode=balance-tcp lacp=active other_config:lacp-time=fast
 
allow-vmbrmain vlan125
        iface vlan125 inet static
        ovs_type OVSIntPort
        ovs_bridge vmbrmain
        ovs_options tag=125
    address 192.168.125.11
    netmask 255.255.255.0
    gateway 192.168.125.1


allow-vmbrmain vlan10
        iface vlan10 inet static
        ovs_type OVSIntPort
        ovs_bridge vmbrmain
        ovs_options tag=10
    address 192.168.10.11
    netmask 255.255.255.0


allow-vmbrmain vlan100
        iface vlan100 inet static
        ovs_type OVSIntPort
        ovs_bridge vmbrmain
        ovs_options tag=100
    address 192.168.100.11
    netmask 255.255.255.0




auto vmbr10
allow-ovs vmbr10
  iface vmbrmain inet manual
  ovs_type OVSBridge
  ovs_ports vlan10 




auto vmbr100
allow-ovs vmbr100
  iface vmbrmain inet manual
  ovs_type OVSBridge
  ovs_ports vlan100
 
Last edited:
spirit said:
Ok, I understand more better now, with the vmbr100,vmbr10. (used for the vms right ?)
So, for this setup, you don't want to define vlan in proxmox qemu/openvz vm network interfaces (right ?)
Click to expand...

Thank you for the illustration. Now it's getting clear to me how it's working. :)

1. Yes, I wan vmbr100, vmbr10 to be used by my vms. If possible vmadmin as well.
2. And I could say yes, it's not necessary to define vlan in proxmox qemu/openvz vm NIC.

For the posted config, it still won't allow me to access proxmos. Ping shows RTO from remote host. I made a few correction (like vlan 50, should be vlan125) and some adjustment to reflect my test server settings as follows:

Code: 
auto eth0
iface eth0 inet manual

auto eth1
iface eth1 inet manual


auto vmbrmain
allow-ovs vmbrmain
  iface vmbrmain inet manual
  ovs_type OVSBridge
  ovs_ports bond0 vlan10 vlan100 vlan125 


allow-vmbrmain bond0
  iface bond0 inet manual
  ovs_bridge vmbrmain
  ovs_type OVSBond
  ovs_bonds eth0 eth1
  ovs_options bond_mode=balance-tcp lacp=active other_config:lacp-time=fast
 
 
allow-vmbrmain vlan125
        iface vlan125 inet static
        ovs_type OVSIntPort
        ovs_bridge vmbrmain
        ovs_options tag=125
    address 192.168.125.10
    netmask 255.255.255.0
    gateway 192.168.125.1


allow-vmbrmain vlan10
        iface vlan10 inet static
        ovs_type OVSIntPort
        ovs_bridge vmbrmain
        ovs_options tag=10
    address 192.168.10.10
    netmask 255.255.255.0


allow-vmbrmain vlan100
        iface vlan100 inet static
        ovs_type OVSIntPort
        ovs_bridge vmbrmain
        ovs_options tag=100
    address 192.168.100.10
    netmask 255.255.255.0


auto vmbr10
allow-ovs vmbr10
  iface vmbrmain inet manual
  ovs_type OVSBridge
  ovs_ports vlan10 

  
auto vmbr100
allow-ovs vmbr100
  iface vmbrmain inet manual
  ovs_type OVSBridge
  ovs_ports vlan100

The vmbrmain didn't come up auto, so I initiated ifconfig vmbrmain up and it went up. But this can't access.

I'm really sorry the thread is taking too long. :(

But I'm really thankful for all your support here to resolve my issues..
 
Last edited:
t. I made a few correction (like vlan 50, should be vlan125)
Click to expand...

oh sorry, typo error.

c4rdinal said:
The vmbrmain didn't come up auto, so I initiated ifconfig vmbrmain up and it went up.
Click to expand...
.

maybe try to rename it with a number, like vmbr0. I don't remember exactly if the init script need it or not.


can you do a #ovs-vsctl show

to display the current config ?
 
spirit said:
oh sorry, typo error.

.

maybe try to rename it with a number, like vmbr0. I don't remember exactly if the init script need it or not.


can you do a #ovs-vsctl show

to display the current config ?
Click to expand...
Hi Spirit,

Thanks for your reply. Here's the result you are asking.

Code: 
#ovs-vsctl show
08a7aa09-8b54-489f-bbc4-8930b9926a6d
    Bridge "vmbr0"
        Port "vlan10"
            tag: 10
            Interface "vlan10"
                type: internal
        Port "bond0"
            Interface "eth0"
            Interface "eth1"
        Port "vlan125"
            tag: 125
            Interface "vlan125"
                type: internal
        Port "vlan100"
            tag: 100
            Interface "vlan100"
                type: internal
        Port "vmbr0"
            Interface "vmbr0"
                type: internal
    ovs_version: "2.3.0"

# ifconfig
Code: 
bond0     Link encap:Ethernet  HWaddr 6a:93:56:cc:cb:d4  
          inet6 addr: fe80::6893:56ff:fecc:cbd4/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:7 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:0 (0.0 B)  TX bytes:578 (578.0 B)

eth0      Link encap:Ethernet  HWaddr 00:07:e9:a5:76:a8  
          inet6 addr: fe80::207:e9ff:fea5:76a8/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:535 errors:0 dropped:0 overruns:0 frame:0
          TX packets:11 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:72550 (70.8 KiB)  TX bytes:1088 (1.0 KiB)

eth1      Link encap:Ethernet  HWaddr 00:07:e9:a5:76:a9  
          inet6 addr: fe80::207:e9ff:fea5:76a9/64 Scope:Link
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:14862 errors:0 dropped:0 overruns:0 frame:0
          TX packets:50 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:1639582 (1.5 MiB)  TX bytes:5910 (5.7 KiB)

venet0    Link encap:UNSPEC  HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00  
          inet6 addr: fe80::1/128 Scope:Link
          UP BROADCAST POINTOPOINT RUNNING NOARP  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:3 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

vlan10    Link encap:Ethernet  HWaddr ea:8a:9a:4b:38:b6  
          inet addr:192.168.10.10  Bcast:192.168.10.255  Mask:255.255.255.0
          inet6 addr: fe80::e88a:9aff:fe4b:38b6/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:7 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:0 (0.0 B)  TX bytes:578 (578.0 B)

vlan100   Link encap:Ethernet  HWaddr b2:f4:41:db:16:4b  
          inet addr:192.168.100.10  Bcast:192.168.100.255  Mask:255.255.255.0
          inet6 addr: fe80::b0f4:41ff:fedb:164b/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:7 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:0 (0.0 B)  TX bytes:578 (578.0 B)

vlan125   Link encap:Ethernet  HWaddr 66:a3:8b:47:57:fe  
          inet addr:192.168.125.10  Bcast:192.168.125.255  Mask:255.255.255.0
          inet6 addr: fe80::64a3:8bff:fe47:57fe/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:510 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:0 (0.0 B)  TX bytes:40800 (39.8 KiB)

vmbr0     Link encap:Ethernet  HWaddr 00:07:e9:a5:76:a8  
          inet6 addr: fe80::207:e9ff:fea5:76a8/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:524 errors:0 dropped:0 overruns:0 frame:0
          TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:41956 (40.9 KiB)  TX bytes:468 (468.0 B)
 
Oh, ok, I think I was too tired ;)

vmbr100 and vmbr10 are not created, bacause
iface ... is wrong is vmbr100 and vmbr10


good one is:

Code: 
auto vmbr100
allow-ovs vmbr100
  iface vmbr100 inet manual
  ovs_type OVSBridge
  ovs_ports vlan100




auto vmbr10
allow-ovs vmbr10
  iface vmbr10 inet manual
  ovs_type OVSBridge
  ovs_ports vlan10


Note that you should be able already to reach vlanX interfaces.
 
spirit said:
Oh, ok, I think I was too tired ;)

vmbr100 and vmbr10 are not created, bacause
iface ... is wrong is vmbr100 and vmbr10


good one is:

Code: 
auto vmbr100
allow-ovs vmbr100
  iface vmbr100 inet manual
  ovs_type OVSBridge
  ovs_ports vlan100

auto vmbr10
allow-ovs vmbr10
  iface vmbr10 inet manual
  ovs_type OVSBridge
  ovs_ports vlan10


Note that you should be able already to reach vlanX interfaces.
Click to expand...

Hi Mate,

Sorry, but it is still not working. I can't establish any connection to the server both on switch and crosscable.

Here's ovs-vsctl show output

Code: 
350c05df-e373-4a69-b1f0-e094549f79e0
    Bridge "vmbr10"
        Port "vmbr10"
            Interface "vmbr10"
                type: internal
    Bridge "vmbr100"
        Port "vmbr100"
            Interface "vmbr100"
                type: internal
    Bridge "vmbr0"
        Port "vmbr0"
            Interface "vmbr0"
                type: internal
        Port "bond0"
            Interface "eth1"
            Interface "eth0"
        Port "vlan125"
            tag: 125
            Interface "vlan125"
                type: internal
        Port "vlan100"
            tag: 100
            Interface "vlan100"
                type: internal
        Port "vlan10"
            tag: 10
            Interface "vlan10"
                type: internal
    ovs_version: "2.3.0"

I feel so useless now. Sorry mate for the wasting your time. Pls bear with me for little while here.

Thanks alot!!
 
I'm 100% sure that all is correct now on openvswitch,

So I don't understand why it's not working.

(Do you kernel 3.10 or 2.6.32 ? I think kernel 3.10 works better with ovs and vlan).

Are you sure that you physical switch is correctly configured ? (does it work with linux bridges ?).
are you sure that is eth0 and eth1 are the correct interfaces for bond0 ?
 
You must log in or register to reply here.

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!

Quick Navigation

Home Get Subscription Wiki Downloads Proxmox Customer Portal About

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!
Community platform by XenForo® © 2010-2024 XenForo Ltd.
Top Bottom
Back