From: DW (kapsi1911@hotmail.com)
Date: Tue Mar 08 2005 - 03:02:50 GMT-3
Yes, when using MQC on a router you can issue a "set cos" only in an
outbound service-policy. When using MQC on the 3550 you can issue a "set
cos" only in an input service-policy.
DAve
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
null void
Sent: Monday, March 07, 2005 7:23 PM
To: ccielab@groupstudy.com
Subject: Configuration Nuance regarding COS marking ??
Does anyone have thoughts on this statement ? I am interpreting this as
saying that if you want to mark traffic leaving your LAN interface
heading into your Layer 2 Fabric on the routers LAN/ETHERNET interface
you can only apply a service policy outbound on the interface ??
TIA
Marking a packet with a local CoS value allows users to associate a
Layer 2 Class of Service value with
a packet. The value can then be used to classify packets based on
user-defined requirements. Layer 2 to
Layer 3 mapping can also be configured by matching on the CoS value,
since switches already have the
capability to match and set CoS values. If a packet that needs to be
marked to differentiate user-defined
QoS services is leaving a router and entering a switch, the router
should set the CoS value of the packet,
since the switch can process the layer 2 CoS header marking.
The CoS value cannot be marked as part of an input traffic policy (which
is attached to an interface using
the service-policy input command). A CoS value marking can only be
applied to output traffic policies
(which are attached using the service-policy output command).
A user can set up to 8 different CoS markings.
This archive was generated by hypermail 2.1.4 : Sun Apr 03 2005 - 17:56:42 GMT-3