From: Niche (jackyliu419@gmail.com)
Date: Tue Nov 15 2005 - 02:19:44 GMT-3
I agree with Chris, is there any special purpose to you for matching vlan in
your configuration?
Cheers~
Jacky
On 11/15/05, Chris Lewis <chrlewiscsco@yahoo.com> wrote:
>
> As you are applying this to an access port, you do not have to match on a
> vlan, as all packets on that interface will belong to that vlan anyway
>
> *Daniel Berlinski <Daniel.Berlinski@telecom.co.nz>* wrote:
>
> Niche
>
> I see your point but I can't do a class-default in this scenario. I get a:
> QoS: Mixing of VLAN classes and non-VLAN classes is not allowed.
> QoS: Policy-map MARKING failed checking.
> Policymap is detached from the interface(s).
>
> Doc CD says: "You cannot configure both port-based classification and
> VLAN-based classification at the same time. When you configure the match
> vlan vlan-list command, the class map becomes per-port per-VLAN based. If
> you configure a policy map that contains both port-based and VLAN-based
> class maps, the switch rejects the policy map when you attach it to an
> interface"
>
> Any suggestions?
>
>
> ________________________________
>
> From: Niche [mailto:jackyliu419@gmail.com]
> Sent: Tue 15/11/2005 4:19 p.m.
> To: Daniel Berlinski
> Cc: ccielab@groupstudy.com
> Subject: Re: 3550 QoS Marking
>
>
> Hi there,
>
> "mls qos cos 3" will not kick-in cause your port is not a trunk port (and
> I assume that port is not connecting to a 7960). You can use class-default
> for marking remaining traffic to precedence 3.
>
> Cheers~
> Jacky
>
>
> On 11/15/05, Daniel Berlinski wrote:
>
> Hi everyone.
>
> Will the following configs mark HTTP traffic coming from vlan 12 with
> precedence 5 and mark the remaining traffic with precedence 3?
>
>
>
-----------------------------------------------------------------------------
---------------------------------------------
> mls qos
> access-list 170 permit tcp any any eq www
>
> class-map match-any HTTP
> match access-group 170
> class-map match-all VLAN12
> match vlan 12
> match class-map HTTP
>
> policy-map MARKING
> class VLAN12
> set ip precedence 5
>
> interface FastEthernet0/2
> switchport access vlan 12
> switchport mode access
> mls qos cos 3
> service-policy input MARKING
>
> Rack1SW1#sh mls qos inter fa0/2
> FastEthernet0/2
> Attached policy-map for Ingress: MARKING
> trust state: not trusted
> trust mode: not trusted
> COS override: dis
> default COS: 3
> DSCP Mutation Map: Default DSCP Mutation Map
> trust device: none
>
-----------------------------------------------------------------------------
------------------------------------------------------------------
>
>
> From the documentation CD: "You cannot configure both port-based
> classification and VLAN-based classification at the same time. When you
> configure the match vlan vlan-list command, the class map becomes per-port
> per-VLAN based. If you configure a policy map that contains both port-based
> and VLAN-based class maps, the switch rejects the policy map when you
attach
> it to an interface"
>
> Will "mls qos cos 3" under the interface mark the remaining traffic with
> precedence 3?
>
> Best regards
>
> This communication, including any attachments, is confidential. If you are
> not the intended recipient, you should not read it - please contact me
> immediately, destroy it, and do not copy or use any part of this
> communication or disclose anything about it. Thank you. Please note that
> this communication does not designate an information system for the
purposes
> of the Electronic Transactions Act 2002.
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
>
> __________________________________________________
> Do You Yahoo!?
> Tired of spam? Yahoo! Mail has the best spam protection around
> http://mail.yahoo.com
This archive was generated by hypermail 2.1.4 : Thu Dec 01 2005 - 09:12:06 GMT-3