[c-nsp] Nightmare for load balancing of L2VPN traffic on CRS (traffic from ME3600)

[Adam Vitkovsky]

Hi Darren,

Been in the same shituation though I'm not familiar with CRS MPLS hashing algo I guess it also looks at the next header field after the bottom of the stack label and if it won't find 0x4 or 0x6 (hopefully in case of L2VPNs) it won't do src/dst IP address hash so for L2VPNs the hashing is done solely based on the VC label which is a bummer. 

And yes I've been asking for FAT-PW on MEs some time ago and there's no will at all... 

In our case we carried a bulk of VLANs in the high bandwidth PWs so we broke them into ever smaller PWs and that kind of helped to balance the traffic a little better. 

Otherwise without FAT-PW I guess the only option is to get MPLS-TE involved then you can tell which PW should use which TE tunnel thus balance the traffic "evenly" across the backbone. 
 

adam  
> -----Original Message-----
> From: cisco-nsp [mailto:cisco-nsp-bounces at puck.nether.net] On Behalf Of
> Darren Liew
> Sent: 09 April 2015 01:47
> To: cisco-nsp at puck.nether.net
> Subject: [c-nsp] Nightmare for load balancing of L2VPN traffic on CRS (traffic
> from ME3600)
> 
> Hi Guys,
> 
> We are a fixed line operator with majority of L2VPN xconnect traffic on our
> network. Our equipments are
> 
> CRS-8    - Core P router
> ME3600 - Access PE router
> 
> Most L2VPN xconnect traffic starts and ends at ME3600. We are beginning to
> see our CRS-8 not being able to load balance among the bundle LACP links
> due to hashing algorithm of CRS-8 box.
> 
> Cisco CRS-8 team suggested FAT-PW config at the ME3600 xconnect, but
> ME3600
> team claims there's no roadmap for FAT-PW.
> 
> Anyone face similar issues & mind to share some options available?
> 
> Thanks !
> 
> Rgds
> Darren
> _______________________________________________
> cisco-nsp mailing list  cisco-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/
---------------------------------------------------------------------------------------
 This email has been scanned for email related threats and delivered safely by Mimecast.
 For more information please visit http://www.mimecast.com
---------------------------------------------------------------------------------------