mls qos cos override - what is the application?

From: Mike Kraus \(mikraus\) (mikraus@cisco.com)
Date: Fri Jul 13 2007 - 16:10:05 ART

• Next message: Mike Kraus \(mikraus\): "RE: Class-default contradiction"
• Previous message: Gary Duncanson: "Re: Do you feel some topics are titled so big and scary"
• Next in thread: Serhat Aslan: "Re: mls qos cos override - what is the application?"
• Maybe reply: Serhat Aslan: "Re: mls qos cos override - what is the application?"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]

By default, an interface is not trusted on a switch. I understand that
the mls qos cos override command does the following:

"Even if a port is previously set to trust DSCP, CoS, or IP precedence,
this command overrides the previously configured trust state, and all
the incoming CoS values are assigned the default CoS value configured
with the mls qos cos command."

But why would you ever do this? If you didn't want to trust a port, why
did you configure to trust it in the first place? Or conversely, if you
didn't want to trust a port any longer, why not remove the trust rather
than overriding the trust?

I just don't see the application of when you would use mls qos cos
override, rather than just not trusting the cos/dscp values on an
interface. Any suggestions?

Thanks,
 Mike

• Next message: Mike Kraus \(mikraus\): "RE: Class-default contradiction"
• Previous message: Gary Duncanson: "Re: Do you feel some topics are titled so big and scary"
• Next in thread: Serhat Aslan: "Re: mls qos cos override - what is the application?"
• Maybe reply: Serhat Aslan: "Re: mls qos cos override - what is the application?"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]

This archive was generated by hypermail 2.1.4 : Sat Aug 18 2007 - 08:17:40 ART