Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 

default QoS behavior on 4500- IOS

By default QoS is disabled. But what is its exact behaviour?

I've read that DSCP is trusted, COS untrusted when QoS is disabled.

What will be the result for the queuing on the egress queue?

Will packets scheduled based on the Cos value? this means:

COS 0

COS to DSCP mapping=> DSCP 0

DSCP to Tx queue=> Tx 1 for all traffic and DSCP value set to 0

or the DSCP value keeps maintained and the default DSCP to Tx queue mapping is used?

I've no hardware to test and I don't find the exact information online

5 REPLIES

Re: default QoS behavior on 4500- IOS

Per the QoS SRND, With QoS disabled, the port interface trust states default to trust DSCP. With QoS enabled, the trust state changes to untrusted and with no other QoS parameters explicitly configured, all egress traffic is marked with CoS 0 and DSCP 0. The queuing when QoS is off will be the queuing mechanism you have configured on the switch. I believe the default is WFQ.

Hope that helps.

Re: default QoS behavior on 4500- IOS

Thus with QoS disabled,

the 4 queues are used and scheduled according to the DSCP of the IP packet (unchanged)

Thus

1)if I attach a pc to a switch with Qos disabled

2)ping to another switch also with QoS disabled

3) The DSCP value will be unchanged

or will it be marked down to 0

Now material to test at the moment :(

Re: default QoS behavior on 4500- IOS

The DSCP value will be unchanged.

Re: default QoS behavior on 4500- IOS

ok, if this is true, then my question is answered ;)

thx

Re: default QoS behavior on 4500- IOS

I was confused by the following text

When

QoS is globally disabled (default), the incoming packet's DSCP value is trusted. However a Layer 2 packet's class-of-service (CoS) value would be

considered untrusted and a CoS value of zero would be used. This CoS value of 0 also maps to a DSCP value of zero.

http://www.cisco.com/en/US/prod/collateral/switches/ps5718/ps4324/prod_white_paper0900aecd8041691c.html

probably an error

231
Views
4
Helpful
5
Replies
CreatePlease to create content