From: Serhat Aslan (serhatworks@gmail.com)
Date: Fri Jul 13 2007 - 19:40:04 ART
Hi Mike,
The root of the problem is nature of the voip traffic (time sensitive
applications..), AFAIK, this commands add to cisco playground when the first
3550 series intrudes, 3550 series switches are important role at cisco voip
based ecosystem, its esential part of the carrying the voip traffic through
the LAN networks.
Both advanced qos +VOIP-vlan is address in this case. Some iphones has got
2 port, their aim are easily integrate the existing lan network, when an
computer plug on this phone; 35xx switch must care which is data
communication or voip communication, after all may be you want to change the
traffic attributes/qos etc... So we use this commands for both
classification, identification generally the qos purposes for the voip and
data traffic by setting or adjusting their DSCP/CoS values.
----
Serhat Aslan
On 7/13/07, Mike Kraus (mikraus) <mikraus@cisco.com> wrote:
>
> 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
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
This archive was generated by hypermail 2.1.4 : Sat Aug 18 2007 - 08:17:40 ART