Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 09 Mar 2012 08:52:42 -0500
From:      Jon Radel <>
To:        bo wang <>
Subject:   Re: Fwd: Some questions about Link Aggregation and Failover
Message-ID:  <>
In-Reply-To: <>
References:  <> <> <> <> <> <> <> <> <>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help

This is a cryptographically signed message in MIME format.

Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable

On 3/9/12 4:08 AM, Damien Fleuriot wrote:
> Well that's exactly what I'm trying to show you.
> Link aggregation will *NOT* allow you to get 200mbs between 2 servers b=
> sending data over the 2 cables.
> As per the example I pasted below, link aggregation uses a load
> balancing algorithm to share the traffic across several links.
> It will *NOT* use *BOTH* links for a single "source ip - destination ip=
> pair.

All of which is explained at least twice in the document the OP claims=20
to have used

once in the section on LACP:

"LACP balances outgoing traffic across the active ports based on hashed=20
protocol header information and accepts incoming traffic from any active =

port. The hash includes the Ethernet source and destination address,=20
and, if available, the VLAN tag, and the IPv4/IPv6 source and=20
destination address."

and once in Example 32-1, which is presumably being used as the cookbook =

for this project:

"Since frame ordering is mandatory on Ethernet links then any traffic=20
between two stations always flows over the same physical link limiting=20
the maximum speed to that of one interface. The transmit algorithm=20
attempts to use as much information as it can to distinguish different=20
traffic flows and balance across the available interfaces."

Has use of Gig ethernet been considered?

--Jon Radel


Want to link to this message? Use this URL: <>