From: Bob Sinclair (bob@bobsinclair.net)
Date: Sun Mar 25 2007 - 10:08:59 ART
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
This archive was generated by hypermail 2.1.4 : Sun Apr 01 2007 - 06:35:52 ART