Cleaning up network inerfaces file, need some input

K

kameleon

Guest
My current /etc/network/interfaces looks like this:

Code:
auto lo
iface lo inet loopback

auto eth0
iface eth0 inet manual

auto eth1
iface eth1 inet manual

auto eth2
iface eth1 inet manual
mtu 9000

auto eth3
iface eth1 inet manual
mtu 9000

auto bond0
iface bond0 inet manual
slaves eth0 eth1
bond_miimon 100
bond_mode 6

auto bond1
iface bond1 inet manual
slaves eth2 eth3
bond_miimon 100
bond_mode 6
mtu 9000

auto bond0.2
iface bond0.2 inet manual
vlan-raw-device bond0

auto bond0.3
iface bond0.3 inet manual
vlan-raw-device bond0

auto bond0.4
iface bond0.4 inet manual
vlan-raw-device bond0

auto bond0.5
iface bond0.5 inet manual
vlan-raw-device bond0

auto bond0.6
iface bond0.6 inet manual
vlan-raw-device bond0

auto bond0.7
iface bond0.7 inet manual
vlan-raw-device bond0

auto bond0.8
iface bond0.8 inet manual
vlan-raw-device bond0

auto bond0.9
iface bond0.9 inet manual
vlan-raw-device bond0

auto bond0.10
iface bond0.10 inet manual
vlan-raw-device bond0

auto bond0.11
iface bond0.11 inet manual
vlan-raw-device bond0

auto bond0.12
iface bond0.12 inet manual
vlan-raw-device bond0

auto bond0.13
iface bond0.13 inet manual
vlan-raw-device bond0

auto bond0.14
iface bond0.14 inet manual
vlan-raw-device bond0

auto bond0.15
iface bond0.15 inet manual
vlan-raw-device bond0

auto bond1.20
iface bond1.20 inet manual
vlan-raw-device bond1
mtu 9000

auto vmbr0
iface vmbr0 inet static
        address 10.8.1.152
        netmask 255.255.255.0
        gateway 10.8.1.1
        bridge_ports bond0
        bridge_stp off
        bridge_fd 0

auto vmbr2
iface vmbr2 inet manual
bridge_ports bond0.2
bridge_stp off
bridge_fd 0

auto vmbr3
iface vmbr3 inet manual
bridge_ports bond0.3
bridge_stp off
bridge_fd 0

auto vmbr4
iface vmbr4 inet manual
bridge_ports bond0.4
bridge_stp off
bridge_fd 0

auto vmbr5
iface vmbr5 inet manual
bridge_ports bond0.5
bridge_stp off
bridge_fd 0

auto vmbr6
iface vmbr6 inet manual
bridge_ports bond0.6
bridge_stp off
bridge_fd 0

auto vmbr7
iface vmbr7 inet manual
bridge_ports bond0.7
bridge_stp off
bridge_fd 0

auto vmbr8
iface vmbr8 inet manual
bridge_ports bond0.8
bridge_stp off
bridge_fd 0

auto vmbr9
iface vmbr9 inet manual
bridge_ports bond0.9
bridge_stp off
bridge_fd 0

auto vmbr10
iface vmbr10 inet manual
bridge_ports bond0.10
bridge_stp off
bridge_fd 0

auto vmbr11
iface vmbr11 inet manual
bridge_ports bond0.11
bridge_stp off
bridge_fd 0

auto vmbr12
iface vmbr12 inet manual
bridge_ports bond0.12
bridge_stp off
bridge_fd 0

auto vmbr13
iface vmbr13 inet manual
bridge_ports bond0.13
bridge_stp off
bridge_fd 0

auto vmbr14
iface vmbr14 inet manual
bridge_ports bond0.14
bridge_stp off
bridge_fd 0

auto vmbr15
iface vmbr15 inet manual
bridge_ports bond0.15
bridge_stp off
bridge_fd 0

auto vmbr20
iface vmbr20 inet static
address 192.168.130.51
netmask 255.255.255.0
bridge_ports bond1.20
bridge_stp off
bridge_fd 0
mtu 9000

auto vmbr20:1
iface vmbr20:1 inet static
address 192.168.131.51
netmask 255.255.255.0
bridge_ports bond1.20:1
bridge_stp off
bridge_fd 0
mtu 9000

auto vmbr20:2
iface vmbr20:2 inet static
address 192.168.132.51
netmask 255.255.255.0
bridge_ports bond1.20:2
bridge_stp off
bridge_fd 0
mtu 9000

auto vmbr20:3
iface vmbr20:3 inet static
address 192.168.133.51
netmask 255.255.255.0
bridge_ports bond1.20:3
bridge_stp off
bridge_fd 0
mtu 9000

But I want to clean it up. I also read in one thread where you don't have to specify the bridge devices anymore for kvm instances, just select the proper vlan tag. Can I safely omit the bridge and bond devices? After some thought I put together the config below:

Code:
auto lo
iface lo inet loopback

auto eth2
iface eth2 inet manual
    address 192.168.130.12
    netmask 255.255.255.0
    mtu 9000

auto eth3
iface eth3 inet manual
    address 192.168.130.22
    netmask 255.255.255.0
    mtu 9000

auto vmbr0
iface vmbr0 inet static
    address 10.8.1.152
    netmask 255.255.255.0
    gateway 10.8.1.1
    bridge_ports eth0 eth1
    bridge_stp off
    bridge_fd 0

Should that work the way I am thinking? Or will I still need the bond0 and various devices for vlans for the eth0 and eth1 to be bonded?
 
I have setup the machines with this and am testing now. I will report back on my results. Thanks!
 
Sharp eye. Although I did fix that before I ifup'd the interfaces on the actual server. :) My current running config is this:

Code:
auto lo
iface lo inet loopback

auto eth2
iface eth2 inet static
    address 192.168.120.12
    netmask 255.255.255.0
    mtu 9000

auto eth3
iface eth3 inet static
    address 192.168.120.22
    netmask 255.255.255.0
    mtu 9000

auto vmbr0
iface vmbr0 inet static
    address 10.8.1.152
    netmask 255.255.255.0
    gateway 10.8.1.1
    bridge_ports eth0 eth1
    bridge_stp off
    bridge_fd 0
 
Ok, did some testing today. Everything seems to work, but there are a few issues.

The biggest issue is on the machine with 4 network interfaces I dedicated 2 to the san. However it seems to only use 1 for traffic as I only get 109-115MB/sec just like the single interface servers. Before I was getting over 200MB/sec. Do I need to setup the bond again or go back to multiple class-C networks?

Secondly I have not tested this but with the last setup above, should I be able to one of the network interfaces on vmbr0 and traffic still flow right?
 
Do I need to setup the bond again

Yes, If you want to use bonding (but only a single one).

Secondly I have not tested this but with the last setup above, should I be able to one of the network interfaces on vmbr0 and traffic still flow right?

Sorry, don't really understand that question?
 
Yes, If you want to use bonding (but only a single one).

So this is only via the web interface? Is that why it can only handle one bond?

Sorry, don't really understand that question?
Sorry I typed that on my phone and I totally missed a word. It should have read: Secondly I have not tested this but with the last setup above, should I be able to drop one of the network interfaces on vmbr0 and traffic still flow right? Basically I am asking if binding the eth0 and eth1 to the vmbr0 if it gives me some sort of failover capabilities or will I need a bond there instead?
 
More testing today. I setup the machine with 4 interfaces with a bond on eth2 and eth3. However I am still only getting around 110MB/sec from that machine to the SAN. I know it can hit over 200MB as it has done it. So maybe I have to go back to multiple class-C networks? The SAN in question is a Dell MD3200i with dual controllers that have 4 ports each. According to the Dell setup docs they have you setup each of the 4 ports on a separate class-C. I wonder if that is for throughput? This is my first SAN to setup so I am learning as I go.
 
More testing today. I setup the machine with 4 interfaces with a bond on eth2 and eth3. However I am still only getting around 110MB/sec from that machine to the SAN. I know it can hit over 200MB as it has done it. So maybe I have to go back to multiple class-C networks? The SAN in question is a Dell MD3200i with dual controllers that have 4 ports each. According to the Dell setup docs they have you setup each of the 4 ports on a separate class-C. I wonder if that is for throughput? This is my first SAN to setup so I am learning as I go.
Hi,
do you use the right bond-mode (also on the switch?)?

Perhaps use the search function (pve1.x) or look here: http://forum.proxmox.com/threads/3271-balance-rr-bond-unbalanced

Udo
 
Have you tried to re-write the bond statement for the two bridged ports??

ie. iface bond0 inet manual slaves eth0 eth1
bond_miimon 100
bond_mode 802.3ad


auto vmbr0
iface vmbr0 inet static
address x.x.x.x
netmask 255.255.255.0
gateway x.x.x.x
bridge_ports bond0
bridge_stp off
bridge_fd 0

~g003222
 

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!