Re: Clarification needed - Catalyst "Internal QoS" Label....

Yes, internal DSCP can be static for an interface, or based on COS
(using cos-to-dscp mapping) or TOS (using DSCP) by defining your "trust".

-Carlos

Robert Miele @ 28/12/2011 13:13 -0300 dixit:
> Hi Carlos,
>
> Can the internal label be either DSCP or CoS based?
>
> The non-IP traffic I was thinking about was ARP.
>
> Thanks again!
>
>> Date: Wed, 28 Dec 2011 12:16:33 -0300
>> From: tron_at_huapi.ba.ar
>> To: guile474_at_hotmail.com
>> CC: ccielab_at_groupstudy.com
>> Subject: Re: Clarification needed - Catalyst "Internal QoS" Label....
>>
>> Robert Miele @ 28/12/2011 11:59 -0300 dixit:
>>> Thanks for the reply Carlos,
>>>
>>> I referred to it as "internal QoS" label as I believe I read somewhere
>>> online that on the 3560 it could either be DSCP or CoS.
>>>
>>> So the internal DSCP label and the DSCP label present in the L3 packet
>>> header can be two different values?
>> Yep, no problem for the switch, and you can keep the incoming value
>> on exit with DSCP transparency.
>>
>>> Also, are these internal DSCP labels applied to non-IP traffic?
>> I would say so, but I don't know. Is there non IP trafic ? :)
>>
>>> Thanks again!
>> You are welcome,
>> -Carlos
>>>
>>> > Date: Wed, 28 Dec 2011 07:42:29 -0300
>>> > From: tron_at_huapi.ba.ar
>>> > To: guile474_at_hotmail.com
>>> > CC: ccielab_at_groupstudy.com
>>> > Subject: Re: Clarification needed - Catalyst "Internal QoS" Label....
>>> >
>>> > I guess you are referring to "internal DSCP" ?
>>> > If so, this is a normalized way of treating QoS clasification of
> trafic
>>> > across different architectures.
>>> >
>>> > I would not call it a "parameter" because you don't set it.
>>> > It is a value that gets attached to flowing frames/packets (a field,
> if
>>> > you like, but not in the packet but in a control data structure
> internal
>>> > to the switch). And it determines how the QoS functions affect the
>>> > frame during its switching.
>>> >
>>> > This way you can define policies on input interfaces (to pay attention
>>> > to COS os TOS or static values) and mappings, and then use the same
>>> > internal treatment for all based on internal DSCP. It also allows you
>>> > to do remarking on exit of TOS (or not).
>>> >
>>> > -Carlos
>>> >
>>> > Robert Miele @ 27/12/2011 23:22 -0300 dixit:
>>> > > Hello,
>>> > >
>>> > > I'm hoping someone can help me understand the concept of the
>>> "internal QoS"
>>> > > label on the 3560 Catalyst switch from an architectual viewpoint.
>>> > >
>>> > > For example, is this "internal QoS" a parameter internal to the
>>> switch, or is
>>> > > a field added to the packet, or is it simply rewriting the value in
> the
>>> > > DSCP/CoS fields.
>>> > >
>>> > > Thanks!
>>> > >
>>> > >
>>> > > Blogs and organic groups at http://www.ccie.net
>>> > >
>>> > >
> _______________________________________________________________________
>>> > > Subscription information may be found at:
>>> > > http://www.groupstudy.com/list/CCIELab.html
>>> > >
>>> > >
>>> > >
>>> > >
>>> > >
>>> > >
>>> > >
>>> >
>>> > --
>>> > Carlos G Mendioroz <tron_at_huapi.ba.ar> LW7 EQI Argentina
>>> >
>>> >
>>> > Blogs and organic groups at http://www.ccie.net
>>> >
>>> >
> _______________________________________________________________________
>>> > Subscription information may be found at:
>>> > http://www.groupstudy.com/list/CCIELab.html
>>> >
>>> >
>>> >
>>> >
>>> >
>>> >
>>> >
>> --
>> Carlos G Mendioroz <tron_at_huapi.ba.ar> LW7 EQI Argentina
>
>
> Blogs and organic groups at http://www.ccie.net
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
>
>
>
>
>
>
>

-- 
Carlos G Mendioroz  <tron_at_huapi.ba.ar>  LW7 EQI  Argentina
Blogs and organic groups at http://www.ccie.net