RE: qos 3560

2009-11-12 Thread Bogdan
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:

RE: qos 3560

2009-11-12 Thread Martin, Paul
[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

Re: qos 3560

2009-11-12 Thread Scott Morris
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

Re: qos 3560

2009-11-12 Thread Bogdan
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

Re: qos 3560

2009-11-12 Thread Brian Feeny
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