[c-nsp] 7609 ES+, WS marking behaviour

[Velimir Filipov]

Hello.

Is it possible, that the device connected to your WS card interfaces is not trusting the CoS, but only the DSCP ?

So in fact your 7609 is correctly marking the CoS, but the next device unmark it. Consider applying mls qos trust cos on it.

Also where exactly do you sniff the packets to find out that the CoS is 0, but the DSCP is unchanged.

Maybe the CoS is lost somewhere else in the way.

Best regards.


Wednesday, April 9, 2014, 10:03:14 AM, you wrote:

> Hello Tony and thank you for the input

> Unfortunately I can not get rid of the Port-Channel in my setup, byt still
> performed the test with:

> physical-interface: GigE interface / switchport
> Logical-interface: SVI

> And got the same results though. I can not though understand the
> behaviour of ES+ regarding mls in a scenario with a box with mixed
> cards (ES+ & WS_67xx)

> The output for a show mls qos queuing for an ES+ interface (in
> switchport) depicts the

> port as untrusted


> #sh mls qos queuing interface tenGigabitEthernet 4/1
> В Weighted Round-Robin
> В  Port QoS is enabled
> В  Port is untrusted
> В  Extend trust state: not trusted [COS = 0]
> В  Default COS is 0


> #show tcam interface te 4/1 qos type1 ip

> * Global Defaults not shared

> ------------------------------------------------------
> QOS Results:
> A - Aggregate Policing В  В  В  F - Microflow Policing
> M - Mark В  В  В  В  В  В  В  В  В  В  T - Trust
> U - Untrust
> ------------------------------------------------------

> From this output does it means that the internal DSCP value assigned
> to the packet

> will be 0 and so an ip packet arriving in an ES+ cardfor a destination
> behind WS_67xx

> will have both DSCP=0 and 802.1p = 0?

> (from what I have seen only 802.1p = 0, DSCP is unchanged)



> Thanx Victor