From: ccie2be (ccie2be@nyc.rr.com)
Date: Thu Apr 22 2004 - 08:44:08 GMT-3
Hi guys,
I'm considering just adding the "mls qos" to both Cat's when I take the lab.
Here's my reasoning.
There might be certain features besides the obvious QoS stuff that require
this command in order to work properly, for example, certain types of
access-lists that need to examine QoS data inside the layer 3 portion of the
packet.
There's no downside to enabling "mls qos" unless explicitly forbidden.
Does anybody think this is a bad idea? If so, why?
Thanks in advance
----- Original Message -----
From: "Yasser Abdullah" <yasser@alharbitelecom.com>
To: "'Ahmed Mustafa'" <ahmed.mustafa@sbcglobal.net>;
<ccielab@groupstudy.com>
Sent: Thursday, April 22, 2004 2:19 AM
Subject: RE: mls command
> As per the command reference guide, 'mls qos' is recommended before
> enabling voice vlan. Until you enter the mls qos command, QOS processing
> is disabled and all CoS values will be mapped to the same queue (1).
>
> Brgds,
>
> Yasser
>
> -----Original Message-----
> From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
> Ahmed Mustafa
> Sent: Thursday, April 22, 2004 8:32 AM
> To: ccielab@groupstudy.com
> Subject: mls command
>
> Is command "MLS QOS" required if the port is configured only for 802.1P
>
> For example,
>
> interface fastethernet 0/5
> switchport voice vlan dot1p
>
> _______________________________________________________________________
> Please help support GroupStudy by purchasing your study materials from:
> http://shop.groupstudy.com
>
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
>
> _______________________________________________________________________
> Please help support GroupStudy by purchasing your study materials from:
> http://shop.groupstudy.com
>
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
This archive was generated by hypermail 2.1.4 : Mon May 03 2004 - 19:48:52 GMT-3