Ok so that means when if you apply a policy-map ingress or egress to a physical interface all of the associated sub-interfaces will use the same policy-map (same token bucket)? Instead of applying the same policy-map to different sub-interfaces which uses a different token bucket (IE: 2 100M policies instead of a 1 100M policy shared across all associated sub-interfaces).
Thanks On Wed, Jul 20, 2016 at 11:04 AM, Antoine Monnier < mrantoinemonn...@gmail.com> wrote: > not sure that s what you are looking for: if you apply the policy-map at > the physical interface level, it will apply for all traffic in the sub > interfaces. > > On Wed, Jul 20, 2016 at 4:45 PM, Curtis Piehler <cpiehl...@gmail.com> > wrote: > >> In simpler terms I am looking for a shared token bucket configuration >> across multiple sub-interfaces on the classic IOS platform >> >> On Wed, Jul 20, 2016 at 1:08 AM, Curtis Piehler <cpiehl...@gmail.com> >> wrote: >> >> > I have a particular scenario doing some QoS on classic IOS devices. >> > >> > I have two WAN sub-interfaces part of a physical interface and a service >> > policy defined that shapes the "WAN" to 100M. Is there a way I can make >> > both sub-interfaces derive from this one policy-map. >> > >> > On an ASR9000 I know you can do service-policy out >> shared-policy-instance >> > xyz. >> > >> > What if you apply the service-policy to the physical interface (has no >> IP) >> > ? Will the two sub-interfaces derive from that? >> > >> > Thanks >> > Curtis >> > >> _______________________________________________ >> cisco-nsp mailing list cisco-nsp@puck.nether.net >> https://puck.nether.net/mailman/listinfo/cisco-nsp >> archive at http://puck.nether.net/pipermail/cisco-nsp/ >> > > _______________________________________________ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/