Re: [ovs-discuss] Clarification on the documentation related to bonding

2014-12-11 Thread Ben Pfaff
On Thu, Dec 11, 2014 at 02:36:12PM -0800, Vinay Bannai wrote: > Yes, our experience has been in regards to using active-tlb and active-slb > across multiple switches with M-LAG on the switches and LACP. Multiple switches with M-LAG essentially act like a single switch, so you can use that setup wi

Re: [ovs-discuss] Clarification on the documentation related to bonding

2014-12-11 Thread Vinay Bannai
Thanks Scott. Yes, our experience has been in regards to using active-tlb and active-slb across multiple switches with M-LAG on the switches and LACP. On Thu, Dec 11, 2014 at 12:14 PM, Scott Lowe wrote: > Vinay, some switches have support for multi-chassis link aggregation > (often called MLAG)

Re: [ovs-discuss] Clarification on the documentation related to bonding

2014-12-11 Thread Scott Lowe
Vinay, some switches have support for multi-chassis link aggregation (often called MLAG). For MLAG-capable switches, you should be able to use any LACP-based bonding mechanism across multiple **correctly configured** switches. However, in the absence of MLAG support, LACP-based bonding types can

[ovs-discuss] Clarification on the documentation related to bonding

2014-12-11 Thread Vinay Bannai
Reading through the 'INTERNALS" document in vswitchd directory, I saw a statement under "Active Backup Bonding" that I would like to get clarified. Active Backup bonds send all traffic out one "active" slave until that slave becomes unavailable. Since they are significantly less complicated than