link aggregation - bundling 2 lagg interfaces together
ml at my.gd
Fri Feb 4 17:13:44 UTC 2011
On 2/4/11 4:55 PM, Freddie Cash wrote:
> On Fri, Feb 4, 2011 at 4:13 AM, Damien Fleuriot <ml at my.gd> wrote:
>> I have a firewall with 2x Intel pro dual port cards.
>> On Intel A , port 1 goes to switch 1, port 2 goes to switch 2
>> On Intel B , port 1 goes to switch 1, port 2 goes to switch 2
>> I have created the following 2 lagg devices using LACP:
>> lagg0 = A1 + B1
>> lagg1 = A2 + B2
>> This works fine.
>> Now, what I had in mind was creating a lagg2 device using lagg0 and
>> lagg1 with failover.
>> That would provide redundancy in case of a switch failure.
> Couple different options:
> - create a single lagg0 device using all port NIC ports
> - create your lagg0 using A1 + B2, and your lagg1 using A2+B1
> Both of those will give you fail-over support for losing a single NIC
> port, an entire NIC, or an entire switch.
> Of course, if your switched aren't stacked to support LACP across
> them, then you will be limited to a single links bandwidth. But you
> will be extremely safe. :)
Well, if I create lagg0 A1 + B2 and lagg1 A2+B1 , I'll end up with 2 laggs.
How though, to I bind my vlan interfaces to *both* laggs ?
I'm not sure that can be done.
Currently and in the interim, I've put our WAN vlan on lagg0 and our 2
internal vlans on lagg1 ;)
More information about the freebsd-stable