From: Serhat Aslan (serhatworks@gmail.com)
Date: Fri Jul 13 2007 - 09:39:19 ART
Hi,
Golden rule : Keep It Simple (light version of kiss :),
On the logical interface like tunnel interfaces, we can't apply bandwidth
related options directly on them so for overcome this problem we create the
two level policy (here -> {aka. hierarchical}), first we define the traffic
within basic policy-map after that. we set them bandwidth related options.
Below it is why on Cisco.com Documentation info:
http://www.cisco.com/en/US/tech/tk543/tk545/technologies_tech_note09186a008017405e.shtml
<snap>
When an interface becomes congested and packets start to queue, you can
apply a queuing method to packets waiting to be transmitted. Cisco IOS
logical interfaces do not inherently support a state of congestion and do
not support the direct application of a service policy that applies a
queuing method. Instead, you need to apply a hierarchical policy as
follows:
</snap>
------
Serhat Aslan
On 7/13/07, Djerk Geurts <djerk@djerk.nl> wrote:
>
> > Rack1SW2(config-if)#service-policy input PMAP203
> > %QoS: policy-map with police action at parent level not
> > supported on Vlan203
> > interface.
>
> Is this because it's applied on ingress to a vlan? I'm asking this as I
> know
> applying service-policies to vlans can be tricky as it's a virtual
> interface
> as far as the switch is concerned so what does the swutch see as in/egress
> in relation to the vlan.
>
> One match per class is due to the logic which can only handle one action
> per
> pass. Adding hierarchy makes the 'packet' go through the logic again. (Am
> I
> wrong? This is what I see with hardware based routing logic)
>
> I figure I have some labbing to do on my 3560 tonight. Any
> input/corrections/references welcome!
>
> Djerk
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
This archive was generated by hypermail 2.1.4 : Sat Aug 18 2007 - 08:17:40 ART