From: Narbik Kocharians (narbikk@gmail.com)
Date: Tue Mar 27 2007 - 00:33:35 ART
Actually the priority Queue for Egress is Queue 1 but for Ingress it can be
either Queue 1 or Queue 2. But as you all stated there is no Ingress
Queueing on 3550s.
On 3/26/07, Digital Yemeni <digital.yemeni@gmail.com> wrote:
>
> Yup that's right! Even the priority queue of both switch differ! On the
> 3550
> queue 4 is the priority queue while on the 3560 queue 1 is! You can go
> thru
> the book referenced by Bob! It's reaaaaaaaaally a great book for QoS!
>
> On 3/27/07, Gary Braver <gbraver@fastlanenetworks.com> wrote:
> >
> > Bob
> >
> > Great write up. One question: I thought the 3560 also based QoS
> > decisions
> > on an internal DSCP value with the value being set by a combination of
> the
> > frames DSCP to CoS mapping value and the per interface Cos to Queue
> > mapping.
> >
> > I guess it gets very confusing, especially to me when one platform uses
> > one
> > sytax and another uses a different.
> >
> > So to prepair for the lab one should configure lan qos on both 3550
> > (wrr-queue statements), and 3560 (srr-queue statements)?
> >
> > Thanks
> > Gary
> >
> > -----Original Message-----
> > From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
> > Bob
> > Sinclair
> > Sent: Sunday, March 25, 2007 9:09 AM
> > To: Digital Yemeni
> > Cc: ccielab@groupstudy.com
> > Subject: Re: 3560 SRR
> >
> > Digital Yemeni wrote:
> > > Hi group,
> > >
> > > I know that we can set the CoS mapping via the "wrr-queue cos-map"
> > interface
> > > command on the 3550. Since this command is not available on the 3560,
> > how
> > > can we do it on a 3560 interface?
> > >
> > > The "mls qos srr-queue input cos-map" is only a global command as far
> as
> > i
> > > know! is there any way to set it as per interface on the 3560?
> > >
> > > Thanks in advance!
> > >
> > >
> > Just to confirm, there is no way to do per-interface cos-maps on the
> > 3560. For reference, here are some other QoS differences between the
> > 3550 and the 3560:
> >
> > The 3550 permits per-interface specification of buffer depths, whereas
> > the 3560 allows you to create two queue-sets globally then apply one of
> > the queue-sets per-interface. The queue-set allows you to configure
> > buffers, not cos-to-queue mappings.
> >
> > The 3550 permits input and output service policies. The 3560 permits
> > only input service policies.
> >
> > The 3550 priority queue out is queue 4, the 3560 priority queue outbound
> > is queue 1.
> >
> > The 3550 does not support traffic shaping, the 3560 does.
> >
> > The 3550 permits a direct vlan match in a class-map, the 3560 uses
> > hierarchical policies applied to an SVI for vlan matches.
> >
> > The 3550 does not provide configurable drop thresholds on FE ports, the
> > 3560 does.
> >
> > The 3550 maps traffic to queues based on CoS value, the 3560 can also
> > map traffic to queues based on internal DSCP value.
> >
> > The 3550 does not support output bandwidth limits per port, the 3560
> > does. (However the 3550 has output policing matching on DSCP)
> >
> > Tim Szigeti's book "End-to-End QoS Network Design" has a table comparing
> > QoS features on the Catalysts at page 264.
> >
> >
> > --
> >
> >
> > Bob Sinclair CCIE 10427 CCSI 30427
> > www.netmasterclass.net
> >
> > _______________________________________________________________________
> > Subscription information may be found at:
> > http://www.groupstudy.com/list/CCIELab.html
> >
>
>
>
> --
> Best Regards!
> Digital, CCIE# to be assigned by Cisco when it collects enough $$ out of
> me!
> :p
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
>
-- Narbik Kocharians CCIE# 12410 (R&S, SP, Security) CCSI# 30832 Network Learning, Inc. (CCIE class Instructor) www.ccbootcamp.com (CCIE Training)
This archive was generated by hypermail 2.1.4 : Sun Apr 01 2007 - 06:35:53 ART