[c-nsp] QOS on ASR9K

Tue Oct 6 04:09:40 EDT 2015

Hello,

Thanks for your reply. Am not shaping in the child policy just added the
priority for management.

Seems like a bug: 
https://tools.cisco.com/bugsearch/bug/CSCuo66446/?referring_site=bugquickvie
wclick

Alex

De :  Brian Turnbow <b.turnbow at twt.it>
Date :  Mon, 5 Oct 2015 19:08:00 +0200
À :  kaviraj Daboo <alex.william21 at outlook.com>,
"'cisco-nsp at puck.nether.net'" <cisco-nsp at puck.nether.net>
Objet :  RE: [c-nsp] QOS on ASR9K

Hi 

I took a look and found this in the qos guide
ASR 9000 Ethernet Line Cards
Queueing is supported at all levels of hierarchical policies:
* Top level‹Two parameters only: excess bandwidth and maximum bandwidth
* Middle level‹Minimum bandwidth, excess bandwidth, and maximum bandwidth
* Bottom level‹Two parameters only: minimum bandwidth or excess bandwidth;
and maximum bandwidth with 128 Mbps upper limit

Didn¹t know about this one but you should be only at the second level and
not the third as I see itŠ.
Are you shaping at the child policy ? that should be the third level.
I was able to apply it to a 1gig interface successfully ( don¹t have a ten
gig I can play with)

interface GigabitEthernet0/0/0/4.10
 service-policy output shared-1gbps shared-policy-instance vlan10
!
interface GigabitEthernet0/0/0/4.11
 service-policy output shared-1gbps shared-policy-instance vlan11

policy-map vlan10
 class class-default
  service-policy child
  shape average 300 mbps
 !

I think you are hitting some kind of bugŠ. Or maybe a line card limitation.

Brian

From: Alex william [mailto:alex.william21 at outlook.com]
Sent: lunedì 5 ottobre 2015 16:04
To: Brian Turnbow; 'cisco-nsp at puck.nether.net'
Subject: Re: [c-nsp] QOS on ASR9K

Hi,

Tried it but seems like in my classes I can¹t go above 128Mbps :(

!!% 'prm_ezhal' detected the 'warning' condition 'Cannot support child/flat
shape rate > 128Mbps¹

Thanks.

Regards,

Alex

De : Brian Turnbow <b.turnbow at twt.it>
Date : Mon, 5 Oct 2015 15:13:00 +0200
À : kaviraj Daboo <alex.william21 at outlook.com>,
"'cisco-nsp at puck.nether.net'" <cisco-nsp at puck.nether.net>
Objet : RE: [c-nsp] QOS on ASR9K

Hi 

You don¹t need to add to the physical interface the policy (unless of course
you have traffic there).
I mixed up the order Š sorry my badŠ it should be
service-policy output shared-2gbps shared-policy-instance vlan10

Brian

From: Alex william [mailto:alex.william21 at outlook.com]
Sent: lunedì 5 ottobre 2015 13:38
To: Brian Turnbow; 'cisco-nsp at puck.nether.net'
Subject: Re: [c-nsp] QOS on ASR9K

Hello,

tested but got the following error:

SPI service policy name conflict: Different Service policy vlan10 is already
configured in same direction for SPI shared-2gbps

My config:

Created the interface policy of 2Gbps:

policy-map shared-2gbps

 class class-default

  shape average 2 gbps

 !

 end-policy-map

Created the subinterfaces policies:

policy-map vlan10

 class class-default

  service-policy child

  shape average 300 gbps

 !

 end-policy-map

!

policy-map vlan11

 class class-default

  service-policy child

  shape average 200 mbps

 !

 end-policy-map

!

policy-map vlan12

 class class-default

  service-policy child

  shape average 100 mbps

!

In the child policy I added:

policy-map child

 class MGMT

  priority level 1

 !

 class class-default

 !

 end-policy-map

!

Added the parent QOS to the physical interface:

interface TenGigE0/1/0/5

service-policy output shared-2gbps

And I was able to add the policy to only one subinterface:

interface TenGigE0/1/0/5.10

 service-policy output vlan10 shared-policy-instance shared-2gbps

On applying to the second interface I got the error.

interface TenGigE0/1/0/5.11

 service-policy output vlan11 shared-policy-instance shared-2gbps

Thanks.

Regards,

Alex

Le 10/5/15, 14:13, « Brian Turnbow » <b.turnbow at twt.it> a écrit :

> 
> Hi  Alex,
> 
>  
> 
> on the 9k you can check out shared policy instance for this.
> 
> " Using SPI, a single instance of qos policy can be shared across multiple
> subinterfaces, allowing for aggregate shaping of the subinterfaces to one
> rate. All of the subinterfaces that share the instance of a QoS policy must
> belong to the same physical interface. The number of subinterfaces sharing the
> QoS policy instance can range from 2 to the maximum number of subinterfaces on
> the port."
> 
>  
> 
> So you can have a 2G shared policy and single subinterface policies like this
> 
>  
> 
> service-policy output customerlimit shared-policy-instance interfacelimit
> 
>  
> 
>  
> 
> Brian
> 
>  
> 
>  
> 
>  
>> 
>> -----Original Message-----
>> 
>> From: cisco-nsp [mailto:cisco-nsp-bounces at puck.nether.net] On Behalf Of
>> 
>> Alex william
>> 
>> Sent: lunedì 5 ottobre 2015 08:04
>> 
>> To: cisco-nsp at puck.nether.net
>> 
>> Subject: [c-nsp] QOS on ASR9K
>> 
>> Hello,
>> 
>> I have a physical interface of 10G with several subinterfaces. I want to add
>> a
>> 
>> QoS limiting the bandwidth of each subinterface.
>> 
>> My need are:
>> 
>> The physical interface has a bandwidth of 2Gbps. I have a total 12
>> 
>> subinterfaces, 6 subinterfaces should be limited to 200Mbps each, 5 should be
>> 
>> limited to 100Mbps, And the last one should be limited 300Mbps. In case of
>> 
>> saturation, each subinterface should allow management IP with highest
>> 
>> priority.
>> 
>> I tried the following configuration:
>> 
>> Classes to match each vlan:
>> 
>> class-map match-any vlan10
>> 
>>   match vlan 10
>> 
>>   end-class-map
>> 
>> class-map match-any vlan11
>> 
>>   match vlan 11
>> 
>>   end-class-map
>> 
>> class-map match-any vlan12
>> 
>>   match vlan 12
>> 
>>   end-class-map
>> 
>> A grand parent policy map of 2Gbps:
>> 
>> policy-map QoS-2Gbps
>> 
>> class class-default
>> 
>> shape average 2Gbps
>> 
>> service-policy parent
>> 
>> The parent policy:
>> 
>> policy-map parent
>> 
>> class vlan10
>> 
>> service-policy child
>> 
>> shape average  200Mbps
>> 
>> The child policy:
>> 
>> Policy-map child
>> 
>> Class Mgmt
>> 
>> Priority level 1
>> 
>> Class class-default
>> 
>> I added the grand parent policy to the interface in output direction. But
>> traffic
>> 
>> is matching only class-default. When I checked, the match vlan only works in
>> 
>> ingress traffic and I want to limit only egress traffic.
>> 
>> I tried a different approach by creating a parent QoS of 200Mbps, 100Mbps
>> 
>> and 300Mbps and added it to each subinterface but I am limited to only 8
>> 
>> queues ID so am being able to apply it only to 2 subinterface.
>> 
>> The router is an ASR9K, with low-lined 10Gbps card and IOS version: 4.2.1
>> 
>> Can someone help please?
>> 
>> Regards,
>> 
>> Alex
>> 
>> _______________________________________________
>> 
>> 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/
> 
>  
> 
>  