[j-nsp] Load balancing using Ethernet Aggregate interface ae0

[Doug Hanks]

If I understand your question correctly ...

LACP requires a single signaling plane, so the remote devices need to be a virtual-chassis, mc-lag, VSS or some other virtualization technology.

If you use a static LAG, there's no signaling at all, and the above still applies, as the packets have to be reassembled on the remote device.  If the remote devices truly are separate, you will just end up black holing the traffic.  In this case just using a routing protocol.

Doug

-----Original Message-----
From: juniper-nsp-bounces at puck.nether.net [mailto:juniper-nsp-bounces at puck.nether.net] On Behalf Of medrees
Sent: Tuesday, March 15, 2011 11:06 PM
To: juniper-nsp at puck.nether.net
Subject: [j-nsp] Load balancing using Ethernet Aggregate interface ae0

Hi Expertise

         I'm going to create new Aggregate Ethernet for M10i router to load
balance the traffic among these interfaces and I know that juniper router
can do this aggregation even if the remote side is connected to two
different devices, so in this case I won't deploy LACP and will use the ON
mode , but I'm confused if it will work correctly and what is the operation
mechanism the router use to can force the other side devices to load share
the downstream traffic on aggregated physical interfaces.

So if anyone can help me with documentation or his experience for this task
send to me.

Thanks in advance.


_______________________________________________
juniper-nsp mailing list juniper-nsp at puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp