[c-nsp] ASR9k Bundle QoS in 6.0.1

Nick Cutting ncutting at edgetg.com
Thu Jun 16 11:42:24 EDT 2016

Your customers are running MPLS between their sites - across L2 MPLS provider Links?
This is something that I also want to do as an enterprise man, but was always worried about MTU etc.

Just so I understand - this also causes a hashing issue for the ISP's as the sources and destinations are many labels deep - and you only see the /30 IP's I have chosen for the links across your backbone? 

-----Original Message-----
From: cisco-nsp [mailto:cisco-nsp-bounces at puck.nether.net] On Behalf Of Tom Hill
Sent: Thursday, June 16, 2016 11:27 AM
To: cisco-nsp at puck.nether.net
Subject: Re: [c-nsp] ASR9k Bundle QoS in 6.0.1

On 16/06/16 15:50, Robert Williams wrote:
> Also (for us anyway) carrying 'other carriers' between our sites, even 
> on IOS-XR with Flow-Aware labels it doesn't balance. Reason is that 
> only see the other carriers' MPLS core IPs (the real customer 
> IP/port/data is even deeper inside the packet and the 9k won't go that 
> deep for the hashing).
> Plus, more and more customers are also using this approach, running 
> MPLS on their own core, so it can become quite an issue. It fails to 
> balance because the (two) adjacencies of the customer boxes are always 
> the same. So it all gets stuck on a single member of a bundle.
> Quite frustrating actually, but unavoidable I believe.

Ah, quite. An interesting problem - and one that could come to you by surprise if your customers are enabling MPLS without telling you.

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/

More information about the cisco-nsp mailing list