[c-nsp] Shared Policy Instances and Aggregate Policing on ASR9K

Chris Mason chrixm at outlook.com
Sat Jan 19 12:24:29 EST 2013


Hi,
I am looking for some clarification on QoS on the ASR9K with respectto VLANs and aggregate policing. I have 3 VLANs running over aBundle and I am receiving unmarked traffic that I need to unconditionallymark based on VLAN.
(I have omitted the ingress policy-map and class-map syntax forbrevity so I hope the following makes sense)
interface Bundle-Ether100.101 set dscp cs2!interface Bundle-Ether100.102 priority level 1 police rate percent 50 set dscp ef!interface Bundle-Ether100.103 priority level 1 police rate percent 50 set dscp ef!
I am receiving EF traffic on two different sub-interfaces but I don'twant to receive more than 50% EF in total on each of the physicalinterfaces in the Bundle. I am unable to apply the policy to the mainBundle interface as I need to mark traffic based on a per VLAN basis(ok, I could probably match vlan in that scenario). However, it is myunderstanding that this is what a Shared Policy Instance is meant forand was wondering if the following would give my desired result?
interface Bundle-Ether100.101 set dscp cs2!interface Bundle-Ether100.102 priority level 1 police rate percent 50 set dscp ef shared-policy-instance SPI-EF50!interface Bundle-Ether100.103 priority level 1 police rate percent 50 set dscp ef shared-policy-instance SPI-EF50!
I would tie both the two policies attached to the EF VLANs to the sameSPI - would this limit my EF traffic to 50% of the total physicalbandwidth or would this not give me my desired result?
Thanks in advance,Chris
(as a side note, how come 'puck.nether.net' rejects messages when I attempt to post to the list from a subscribed Google Mail address? They are getting rejected with the following message:
Google tried to deliver your message, but it was rejected by the recipient domain. We recommend contacting the other email provider for further information about the cause of this error. The error that the other server returned was: 535 535-5.7.1 Username and Password not accepted.
How come it needs a Username/Password when delivering to the MX?) 		 	   		  


More information about the cisco-nsp mailing list