C6500 QoS - Link between Internal DSCP and CoS value

[parisdooz12]

Hi,

there is something I find strange on C6500 about QoS: C6500 derive an internal DSCP value for it's internal use, but when configuring the qos mapping on output interfaces, only a cos  value (I guess, an internal cos value) can be used. Is it a misunderstanding from me, or is it really illogic?

Thanks

P.          

[Joseph W. Doherty]

Disclaimer

The  Author of this posting offers the information contained within this  posting without consideration and with the reader's understanding that  there's no implied or expressed suitability or fitness for any purpose.  Information provided is for informational purposes only and should not  be construed as rendering professional advice of any kind. Usage of this  posting's information is solely at reader's own risk.

Liability Disclaimer

In  no event shall Author be liable for any damages whatsoever (including,  without limitation, damages for loss of use, data or profit) arising out  of the use or inability to use the posting's information even if Author  has been advised of the possibility of such damage.

Posting

6500s do map DSCP into internal CoS values.  I suspect this might be both because it works nicely with L2 CoS and/or L3 IP Precedence.  I.e. it may have been quite logical at the time the 6000/6500 series were first designed.

[parisdooz12]

Yes, it is strange, because I guess 6500s do map with CoS values since the begining, so why not to speak abour internal CoS values in documents, in place of internal DSCP value?