I misspoke. There are 6 modes. From the bonding.txt documentation, there are 6 modes:
-balance-rr -active-backup -balance-xor -broadcast -802.3ad (aggregation) -balance-tlb -balance-alb The behavior is dependent upon the switch configuration; for example you are doing aggregation to a single switch, or high redundancy across two physical switches. In a virtual environment, to mirror a prod env, you would likely need to also have additional virtual switches. Otherwise the virtual NICs would not behave the same way as the physical. Make sense? Cheers; E! On Tue, May 11, 2010 at 13:18, Robert Citek <[email protected]> wrote: > On Tue, May 11, 2010 at 2:00 PM, Wilson, Eric <[email protected]> wrote: >> I have done quite a lot of this on physical servers. There are >> effectively 8 different channel bond scenarios. We have done it in >> fail over and aggregated bandwidth scenarios. Your choice will be >> highly dependent on your network architecture. > > When you say 8 scenarios, what do you mean and what are they? > >> I've done none on virtual servers though, as I don't see the benefit. > > For us the advantage would be for simulations. The idea would be to > model part or all of an existing physical environment in a virtualized > setting. We could then experiment with some changes which might be > disruptive in the real environment. Once we have an optimal set of > changes we can then implement them in the physical environment. > > Regards, > - Robert > > -- > Central West End Linux Users Group (via Google Groups) > Main page: http://www.cwelug.org > To post: [email protected] > To subscribe: [email protected] > To unsubscribe: [email protected] > More options: http://groups.google.com/group/cwelug > -- Central West End Linux Users Group (via Google Groups) Main page: http://www.cwelug.org To post: [email protected] To subscribe: [email protected] To unsubscribe: [email protected] More options: http://groups.google.com/group/cwelug
