On 15/04/2015 07:42, Mark Tinka wrote:
> On 14/Apr/15 18:27, Nick Hilliard wrote:
>> What platform though?  This problem is massively platform specific and the 
>> ability to implement PE entropy labels or do deep packet lookups for 
>> lag/ecmp load balancing will depend entirely on the chipset capabilities.
> 
> MX on Trio.

right, both trio and asr9k can do lag/ecmp balancing based on payload
inspection to some degree, but it's complicated and hacky.  There's a
discussion of asr9k in the Cisco support forums:

> https://supportforums.cisco.com/document/111291/asr9000xr-loadbalancing-architecture-and-characteristics

If possible, the best way to handle this problem is to use FAT-PW on the
PE.  If this isn't possible, then there are limits to what can be done by P
routers.  I don't know how the crs platform handles this, which is what the
OP was interested in.

Nick

_______________________________________________
cisco-nsp mailing list  [email protected]
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/

Reply via email to