Druckos Blog

a Blog with tips and tricks around Linux

Bonding Howto Debian

Bonding Howto Debian

Do 15 Dezember 2011

Beschreibung und wichtige Erfahrungen Bonding unter Debian

Note Dies ist eine Auflistung an wichtigen Infos während der Evaluierung unserer Systeme

Caution Duplex Binding

Kernel.org Beschreibung

Beschreibung

http://www.dodgenet.de-Software-bonding.html

This is true markdown text.

# python code

from Fabric import fabric
username="Foo" 
print "Hello %s" % username 
1
print "Willkommen"

Note (http:--forum.proxmox.com-threads-848-Bonding-Bridging-and-vLANS) Dietmar, your network-fu is better than mine. You nailed it! That’s the correct config for the interfaces file to make it work properly. I’ll post a completed one below for others to benefit from. THANK YOU! Two things to note 1 - the web interface won’t allow bond creation on interface.vlan, only interface (eth0 is OK but eth0.56 is not). However, if it is manually put into the interfaces file, it works, and shows up properly in the web interface. 2 - you asked for a usage case scenario for more than 10 bridges? I have 11 vlans on my network, so I need to have 11 bridges. Actually, I also need to have 11 bonds as well.

Apparently, I could configure this manually and be OK - I was just making a suggestion for getting the web interface more usable. I think 0-99 of both bonds and bridges would cover most everyone. I would like to convert all my production KVM servers (running Debian- Ubuntu + KVM) over to Proxmox. One of those systems has 18 Guests, with 30+ bridges. I don’t want to move to Proxmox on that system until the web interfaces fully supports its configuration (as others in my organization are wary of the command line - go figure). BTW - GREAT work with Proxmox! This is a real break through in getting KVM into the mainstream.

Would love to see the community get more involved in the development cycle (SCM access), but your quality control has been great, V1 is quite stable in a variety of work loads, so its hard to argue any changes there - it just might help in getting more features added quicker. Anyway, my example interfaces file with two working bonds of different vLANS on two separate bridges: # network interface settings auto lo iface lo inet loopback auto eth0.56 iface eth0.56 inet manual auto eth1.56 iface eth1.56 inet manual auto eth0.11 iface eth0.11 inet manual auto eth1.11 iface eth1.11 inet manual auto bond0 iface bond0 inet manual slaves eth0.56 eth1.56 bond_miimon 100 bond_mode active-backup pre-up ifup eth0.56 eth1.56 post-down ifdown eth0.56 eth1.56 auto bond1 iface bond1 inet manual slaves eth0.11 eth1.11 bond_miimon 100 bond_mode active-backup pre-up ifup eth0.11 eth1.11 post-down ifdown eth0.11 eth1.11 auto vmbr0 iface vmbr0 inet static address 10.5.56.72 netmask 255.255.254.0 gateway 10.5.57.4 bridge_ports bond0 bridge_stp off bridge_fd 0 auto vmbr1 iface vmbr1 inet static address 10.11.0.48 netmask 255.255.252.0 gateway 10.11.0.1 bridge_ports bond1 bridge_stp off bridge_fd 0

<interface type='bridge'>
    <source bridge='br109'->
    <model type='ne2k_pci'->
</interface>

Comments