From: Ahmed Mustafa (ahmed.mustafa@sbcglobal.net)
Date: Thu Apr 22 2004 - 22:26:49 GMT-3
Cisco DQOS clearly states that COS can only be set on trunk ports, not
access.
HTH,
Ahmed
----- Original Message -----
From: "Kenneth Wygand" <KWygand@customonline.com>
To: "ccie2be" <ccie2be@nyc.rr.com>; "Group Study" <ccielab@groupstudy.com>
Sent: Thursday, April 22, 2004 9:21 AM
Subject: RE: QoS on 3550
> I'm trying to test this out as we speak. I'm trying to set the IP
> Precedence in a route map assigned to a local policy in a 2500 series
> router, but I'm receiving the following... is this because I cannot set
> ISL or DOT1Q encapsulation on a 2500-series router? I believe I should
> be able to set the TOS bit on any platform because there is a TOS field
> in all IP packets.
>
>
>
> <snip>
>
> ip local policy route-map SETFLASH
>
>
>
> route-map SETFLASH permit 10
>
> set ip precedence flash
>
>
>
> r1#ping 10.0.0.2
>
> *Mar 1 00:12:43.951: %SYS-5-CONFIG_I: Configured from console by
> console
>
>
>
> Type escape sequence to abort.
>
> Sending 5, 100-byte ICMP Echos to 10.0.0.2, timeout is 2 seconds:
>
>
>
> *Mar 1 00:12:47.163: IP: s=10.0.0.1 (local), d=10.0.0.2, len 100,
> policy match
>
> *Mar 1 00:12:47.167: IP: route map SETFLASH, item 10, permit
>
> *Mar 1 00:12:47.171: IP: s=10.0.0.1 (local), d=10.0.0.2, len 100,
> policy reject
>
> ed -- normal forwarding.
>
> *Mar 1 00:12:49.163: IP: s=10.0.0.1 (local), d=10.0.0.2, len 100,
> policy match
>
> *Mar 1 00:12:49.167: IP: route map SETFLASH, item 10, permit
>
> *Mar 1 00:12:49.167: IP: s=10.0.0.1 (local), d=10.0.0.2, len 100,
> policy reject
>
> ed -- normal forwarding.
>
> *Mar 1 00:12:51.163: IP: s=10.0.0.1 (local), d=10.0.0.2, len 100,
> policy match
>
> *Mar 1 00:12:51.167: IP: route map SETFLASH, item 10, permit
>
> *Mar 1 00:12:51.171: IP: s=10.0.0.1 (local), d=10.0.0.2, len 100,
> policy reject
>
> ed -- normal forwarding.
>
> *Mar 1 00:12:53.163: IP: s=10.0.0.1 (local), d=10.0.0.2, len 100,
> policy match
>
> *Mar 1 00:12:53.167: IP: route map SETFLASH, item 10, permit
>
> *Mar 1 00:12:53.167: IP: s=10.0.0.1 (local), d=10.0.0.2, len 100,
> policy reject
>
> ed -- normal forwarding.
>
> *Mar 1 00:12:55.163: IP: s=10.0.0.1 (local), d=10.0.0.2, len 100,
> policy match
>
> *Mar 1 00:12:55.167: IP: route map SETFLASH, item 10, permit
>
> *Mar 1 00:12:55.167: IP: s=10.0.0.1 (local), d=10.0.0.2, len 100,
> policy reject
>
> ed -- normal forwarding.
>
> Success rate is 0 percent (0/5)
>
> </snip>
>
>
>
> Any ideas?
>
>
>
> Kenneth E. Wygand
> Systems Engineer, Project Services
>
> CISSP #37102, CCNP, CCDP, ACSP, Cisco IPT Design Specialist, MCP, CNA,
> Network+, A+
> Custom Computer Specialists, Inc.
>
> "I am not really smart. I just stick with problems longer."
> -Albert Einstein
>
>
>
> Custom Computer Specialists, Inc.
>
> "Celebrating 25 Years of Excellence"
>
>
>
> -----Original Message-----
> From: ccie2be [mailto:ccie2be@nyc.rr.com]
> Sent: Thursday, April 22, 2004 11:57 AM
> To: Group Study
> Subject: QoS on 3550
>
>
>
> Hi guys,
>
>
>
> I'm trying to understand something which has me confused.
>
>
>
> Recall these facts:
>
>
>
> At layer 2, only ISL or 802.1q trunks have fields to carry layer 2 QoS
> info.
>
>
>
> Regular ethernet frames don't and can't carry any QoS info.
>
>
>
> Given the above,
>
>
>
> Q1) Can cos be set on frames coming into or going out of regular access
> port on a 3550?
>
>
>
> Q2) If so, how does this work?
>
>
>
> Q3) Can someone confirm that's there's no problem or Gotcha's on
> setting layer 3 QoS on frames coming into or leaving a regular access
> port?
>
>
>
> Thanks in advanced, Tim
>
> [GroupStudy removed an attachment of type image/gif which had a name of
image001.gif]
>
> _______________________________________________________________________
> 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:53 GMT-3