RE: QOS in Cisco 7609

Not sure if we are on the same page, but the packet arriving on that
Gig Ethernet interface DOES have a Ethernet Header and probably has
COS premarked marked, which is being used by the router to make
queuing decisions.

I dont see the router doing a COS marking here. Its just performing a
PHB based on the existing Markings.(However nothing is stopping you to
do that as well.)

-Vijay Shekhar
CCIE#17589/CISSP#65114/RHCE
http://au.linkedin.com/in/vshekhar

Quoting Tortle Tang <tortletang_at_hotmail.com>:

>
> Hi Vijay
>
> Yes, layer 2 marking is for queuing. My question is when the
> packet arrives the interface, it should be a ip packet, how can the
> interface perform layer 2 marking ??
>
> Thanks,
> Terry
>
>
>
>
>
>> Date: Fri, 31 Dec 2010 09:31:36 +1100
>> From: v.shekhar_at_globalassurance.net
>> To: tortletang_at_hotmail.com
>> CC: ccielab_at_groupstudy.com
>> Subject: RE: QOS in Cisco 7609
>>
>> Terry,
>>
>> From what i can see in the config you have provided, L3 QoS policy
>> thats defined is used for Rate limiting input and output traffic,
>> Where as the L2 CoS policy is used to assign incoming packets to
>> appropriate ingress Queue. (Along with some Drop threshold defined for
>> the queues).
>>
>> IN summary L3 markings are used for for Rate limiting
>> L2 markings are used for queuing.
>>
>> HTH,
>> -Vijay Shekhar
>> CCIE#17589/CISSP#65114/RHCE
>> http://au.linkedin.com/in/vshekhar
>>
>>
>> Quoting Tortle Tang <tortletang_at_hotmail.com>:
>>
>> > Could anyone answer my question please ? How this layer 2 QOS works under
>> > layer 3 interface ???
>> >
>> > Thanks,
>> > Terry
>> >
>> >
>> >
>> >
>> >
>> >> From: tortletang_at_hotmail.com
>> >> To: davidbass570_at_gmail.com; ccielab_at_groupstudy.com
>> >> Subject: RE: QOS in Cisco 7609
>> >> Date: Wed, 29 Dec 2010 13:37:38 +1100
>> >>
>> >> Hi
>> >> The following is the policy.
>> >>
>> >> class-map match-any realtime_ipp
>> >> match ip precedence 5
>> >> policy-map PE_to_CORE_Police_RT
>> >> class realtime_ipp
>> >> police cir 600000000 conform-action transmit exceed-action drop
>> >>
>> >>
>> >> class-map match-any realtime_exp
>> >> match mpls experimental topmost 5
>> >> policy-map CORE_to_PE_Police_RT
>> >> class realtime_exp
>> >> police cir 600000000 conform-action transmit exceed-action drop
>> >>
>> >>
>> >> Thanks,
>> >> Terry
>> >>
>> >>
>> >>
>> >>
>> >> > Subject: Re: QOS in Cisco 7609
>> >> > From: davidbass570_at_gmail.com
>> >> > Date: Tue, 28 Dec 2010 20:02:38 -0600
>> >> > To: tortletang_at_hotmail.com
>> >> >
>> >> > Could you send the L3 policy out as well?
>> >> >
>> >> > Sent from my iPhone
>> >> >
>> >> > On Dec 28, 2010, at 6:04 PM, Tortle Tang
>> <tortletang_at_hotmail.com> wrote:
>> >> >
>> >> > > Hi
>> >> > >
>> >> > > I saw the following in cisco 7609, I am Just wondering how
>> it works ,
>> > as
>> >> the
>> >> > > interfaces is IP interface, however the qos is for COS (layer2).
>> >> > > Do your guys have any idea? or do you think the layer 2 QOS
>> is working
>> >> for
>> >> > > this layer 3 IP interface ?
>> >> > >
>> >> > >
>> >> > > Current configuration : 945 bytes
>> >> > > !
>> >> > > interface GigabitEthernet5/1
>> >> > > mtu 1534
>> >> > > ip address 10.104.234.2 255.255.255.252
>> >> > > ip mtu 1500
>> >> > > ip flow ingress
>> >> > > ip ospf message-digest-key 1 md5 7 020B555505575C2C1C5B1A4A
>> >> > > ip ospf bfd
>> >> > > wrr-queue bandwidth percent 65 35
>> >> > > wrr-queue queue-limit 40 30
>> >> > > wrr-queue random-detect min-threshold 1 40 80
>> >> > > wrr-queue random-detect min-threshold 2 70 80
>> >> > > wrr-queue random-detect max-threshold 1 80 100
>> >> > > wrr-queue random-detect max-threshold 2 80 100
>> >> > > wrr-queue cos-map 1 1 1
>> >> > > wrr-queue cos-map 1 2 0 4
>> >> > > wrr-queue cos-map 2 1 2 3
>> >> > > wrr-queue cos-map 2 2 6 7
>> >> > > mpls traffic-eng tunnels
>> >> > > mpls traffic-eng backup-path Tunnel9003
>> >> > > mpls accounting experimental input
>> >> > > mpls accounting experimental output
>> >> > > mpls ip
>> >> > > bfd interval 200 min_rx 200 multiplier 3
>> >> > > service-policy input CORE_to_PE_Police_RT
>> >> > > service-policy output PE_to_CORE_Police_RT
>> >> > > ip rsvp bandwidth 1000000
>> >> > > ip rsvp signalling hello
>> >> > >
>> >> > >
>> >> > > Thanks,
>> >> > > Terry
>> >> > >
>> >> > >
>> >> > > Blogs and organic groups at http://www.ccie.net
>> >> > >
>> >> > >
>> _______________________________________________________________________
>> >> > > Subscription information may be found at:
>> >> > > http://www.groupstudy.com/list/CCIELab.html
>> >>
>> >>
>> >> Blogs and organic groups at http://www.ccie.net
>> >>
>> >> _______________________________________________________________________
>> >> Subscription information may be found at:
>> >> http://www.groupstudy.com/list/CCIELab.html
>> >
>> >
>> > Blogs and organic groups at http://www.ccie.net
>> >
>> > _______________________________________________________________________
>> > Subscription information may be found at:
>> > http://www.groupstudy.com/list/CCIELab.html
>>
>>
>> Blogs and organic groups at http://www.ccie.net
>>
>> _______________________________________________________________________
>> Subscription information may be found at:
>> http://www.groupstudy.com/list/CCIELab.html

Blogs and organic groups at http://www.ccie.net
Received on Fri Dec 31 2010 - 12:42:24 ART