[c-nsp] R: ES20 aggregate QOS

Brian Turnbow b.turnbow at twt.it
Wed Jul 17 06:54:15 EDT 2013

Hi ,

> Hi,
> We've got a 7609 with ES20+ card in it (running SRD4 if it matters). We've got
> a service from a carrier that is sub-linerate so we would normally shape the
> sub-int to the speed of the service provided and then apply a child policy for
> the QoS.
> The question I have is whether you can have an aggregate shaper across two
> interfaces because for some of the services we have a VLAN that is
> terminated on a L3 dot1q sub-int as well an an EVC that bridges another
> VLAN (on the same service from the carrier).
> The config from this setup is below. I can obviously apply a qos-policy
> separately to both interfaces, but that means I need to decide on the split of
> traffic between the two inner VLANs and neither of them will be able to use
> the full bandwidth of the link (and it will be a fixed split).
> Is there a way to do any sort of aggregate QoS over multiple VLAN's on the
> ES20 cards ? I know that for most other cards the answer is NO, I'm just
> curious if the ES20 has any pleasant suprises in this area that I haven't come
> across yet as I've only been playing with them for about 6 months and
> haven't delved too deep into their capabilities.

Check out aggregate policies
it can aggregate between different sub interfaces.
Never tried it on ES cards , but AFAIK it is supported.


> I should note that there are lots of other services from the carrier delivered
> on the same interface (with different outer VLAN tag to identify each
> service), so using a 3-tier heirarchical QoS policy is not something that could
> be done.
> Thanks,
> Tony.
> outer tag (from carrier) = 1451
> inner tag (from us) = 585 & 583
> interface GigabitEthernet3/2
>  service instance 585 ethernet
>   encapsulation dot1q 1451 second-dot1q 585
>   rewrite ingress tag pop 2 symmetric
>   bridge-domain 530
>  !
> interface GigabitEthernet3/2.14510583
>  encapsulation dot1Q 1451 second-dot1q 583
>  ip address x.x.x.x/30
> _______________________________________________
> 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 e-mail is intended only for the addressee named above. 
As this e-mail may contain confidential or privileged information, 
if you are not the named addressee, you are not authorized to retain, read, 
copy or disseminate this message or any part of it.   
Please consider your environmental responsibility before printing this e-mail.

More information about the cisco-nsp mailing list