[nsp] QoS tricks redux

Dmitri Kalintsev dek at hades.uz
Tue Nov 18 17:11:17 EST 2003


Inbound "prioritisation" isn't possible, because you are busy receiving bits
from the wire and cannot tell the wire which bits are of interest and which
are not - they (bits) already are in the order that the sending device put
them in. You can only classify or drop on inbound, while you're trying to do
priority queueing and shaping.

On Tue, Nov 18, 2003 at 02:54:32PM -0700, Christopher J. Wolff wrote:
> Either I found a discrepancy between cisco TAC
> http://www.cisco.com/en/US/customer/tech/tk543/tk545/technologies_tech_note0
> 9186a0080114326.shtmland IOS 12.3.1(a)
> or I've misunderstood the explanation.  Please consider the following.
> class-map match-any ipprec5
> match ip precedence 5
> class-map match-any 4megabit
> match access-group 196 (matches all IP)
> policy-map voippriority
>  class ipprec5
>   priority 100
> policy-map voippriority+4mCIR
>  class 4megabit
>   shape average 4000000
>    service-policy voippriority
> interface FastEthernet0/1.100
> --- heres the rub
> According to the web page above I should be able to enter service-policy
> voippriority+4mCIR; however, the router won't take it.  The only command
> that will take is service-policy output voippriority+4mCIR.  Alas, I need
> inbound prioritization as well?
> Any suggestions are, as always, tremendously appreciated.


More information about the cisco-nsp mailing list