[j-nsp] Problems with Link Aggregation
Mark Tinka
mark.tinka at seacom.mu
Sun Apr 21 11:11:53 EDT 2013
On Wednesday, March 06, 2013 04:15:45 PM Filippo Cugini
wrote:
> However, when we send traffic on the aggregated link,
> just one ge works, and we experience packet loss when we
> exceed the throughput of 1000mbps. Indeed, the
> statistics of all interfaces show that only the
> ge-0/0/12 is utilized to forward the data traffic, while
> the other two interfaces send and receive only signaling
> packets.
We've seen this when flows are non-IP, i.e., in our case,
the flows were MPLS-based.
TAC came back to say the system won't load share if the
flows aren't direct IP (unlike Cisco switches, it can't look
beyond the MPLS frames to reveal the IP packets and hash on
that).
Not sure if this was your traffic type.
We saw the issue on the EX4200's.
Mark.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part.
URL: <https://puck.nether.net/pipermail/juniper-nsp/attachments/20130421/74a3d8f5/attachment.sig>
More information about the juniper-nsp
mailing list