ee another dscp value in the counters. (besides mine).
i tried with dscp mutation and re-mapping, but it did't work.
so..start NOT trusting the edge/customers ports.
>
>
> Paul
>
>
>
> -Original Message-
> From: Scott Morris [mailto:s...@emanon.com]
> Sent:
[mailto:s...@emanon.com]
Sent: 12 November 2009 14:41
To: Bogdan
Cc: nanog@nanog.org
Subject: Re: qos 3560
Look at "show mls qos map" to see the defaults that may be rewriting
your information depending on trust (or non-trust) mechanisms you have
configured.
If you trust CoS, a frame receiv
Look at "show mls qos map" to see the defaults that may be rewriting
your information depending on trust (or non-trust) mechanisms you have
configured.
If you trust CoS, a frame received with cos5 and dscp46 will get
rewritten to dscp 40 with default maps...
"show mls qos interface (intf)" is als
hello
indeed, a fellow nanoger gave me this hint.
1. i had to enable mls qos globally in "network" switches
2. set the mls qos trust dscp on the uplinks (ingress port)
thanks
ps thanks to andrey.gordon too :)
On 11/12/2009 03:21 PM, Brian Feeny wrote:
>
> You should make sure that any li
You should make sure that any links that go between devices have trust
set. In your case if your doing DSCP,
then make sure each link that goes between devices which must carry
tagged packets have trust dscp set.
Brian
On Nov 12, 2009, at 5:11 AM, Bogdan wrote:
hello
i am playing with
hello
i am playing with qos on some devices
- cisco 3560
- cisco 7609
and i have some things that i don't seem to understand.
1. in 3560, i enable mls qos, on the ingress port applyed policy map,
classify the packets with acl, mark, all good. on the egress ports i use
srr-queue with shape/share,
6 matches
Mail list logo
