From: Alexandros Sichlimiris (a.sichlimiris@reading.ac.uk)
Date: Wed Mar 09 2005 - 16:28:09 GMT-3
null void wrote:
Hello,
>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.
>
what I understand from the above is that if the direction of the packet
is from a switch to a router then you can use match and set CoS values
on the switch because it has 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,
>
that is the opposite direction (router to switch)
>the router should set the CoS value of the packet,
>
>since the switch can process the layer 2 CoS header marking.
>
>
the router sets the CoS value,
>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).
>
>
and for both the above cases, as you said, you can only apply the
service-policy outbound.
>A user can set up to 8 different CoS markings.
>
>
HTH
>_______________________________________________________________________
>Subscription information may be found at:
>http://www.groupstudy.com/list/CCIELab.html
This archive was generated by hypermail 2.1.4 : Sun Apr 03 2005 - 17:56:44 GMT-3