[c-nsp] CBWFQ/PQ Support on 6500/SUP720-3BXL
David Granzer
dgranzer at gmail.com
Wed Jun 25 10:24:21 EDT 2008
Hi Zahid,
you can not match EXP bits within a WRR queue. The EXP value is copied
to the internal DSCP and if the internal DSCP to EXP and the internal
DSCP to CoS maps are consistent then you can match according CoS
within a WRR queue.
Regards,
David
On 6/18/08, Zahid Hassan <zhassan at gmx.net> wrote:
>
> Many thanks David, this is makes perfect sense now.
>
> I don't have any P routers in my core only PEs.
>
> This is my scenario:
>
> CE1-----PE1-----PE2----CE2
>
> So as per your explanation, on PE1 and PE2 I will have to match
> on both DSCP and EXP bits as the PEs will see both IP and labelled
> packets at the ingress depending on whether the packets are coming
> from a CE or a PE.
>
> Assuming that this is the case, then back to my original my question.
>
> How to match on EXP bits within a WRR queue ?
>
> I can match EXP bits with policy-maps but policy-maps doesn't support LLQ or
> Priority queuing.
>
>
> Any further help or input on this will be greatly appreciated.
>
>
> Regards,
>
>
> Zahid
>
>
>
>
>
>
>
>
>
> -----Original Message-----
> From: David Granzer [mailto:dgranzer at gmail.com]
> Sent: 18 June 2008 12:34
> To: Zahid Hassan
> Cc: cisco-nsp at puck.nether.net; DTODD at partners.org
> Subject: Re: [c-nsp] CBWFQ/PQ Support on 6500/SUP720-3BXL
>
> Hi Zahid,
>
> I have tested the following with policy maps. The classification of the
> packet is performed at the ingress, so if the packet enters router as IP
> packet (Input Edge) then you must on egress interface match according DSCP
> value, if the packet enters router as labeled packet (LSRs in the Core of an
> MPLS) then you must on egress interface match according MPLS EXP value.
>
> When I (re)read some docs it seems that the following rules apply for your
> scenario with wrr and might help.
>
> PFC3BXL or PFC3B mode MPLS QoS maps the EXP value to the internal DSCP using
> the EXP-to-DSCP global map
>
> The PFC3BXL or PFC3B assigns the egress CoS based on the internal
> DSCP-to-CoS global map. If the default internal DSCP-to-EXP and the internal
> DSCP-to-CoS maps are consistent, then the egress CoS has the same value as
> the imposed EXP.
>
> Maybe someone else can clarify much better.
>
> Regards,
> David
>
>
> On 6/11/08, Zahid Hassan <zhassan at gmx.net> wrote:
> > Thanks David.
> >
> > One clarification about your earlier email.
> >
> > I am thinking of deploying this on my core facing interfaces.
> >
> > Basically on the interfaces where I have LDP/TDP enabled.
> >
> > So my question now is, will these interfaces be able to
> > understand or see any DSCP markings in MPLS packets ?
> >
> > Will a match on DSCP markings work for MPLS packets on LDP/TDP
> > enabled interfaces ?
> >
> >
> > Regards,
> >
> >
> > Zahid
> >
> >
> >
> >
> > -------- Original-Nachricht --------
> > > Datum: Wed, 11 Jun 2008 13:52:07 +0200
> >
> > > Von: "David Granzer" <dgranzer at gmail.com>
> > > An: "Zahid Hassan" <zhassan at gmx.net>
> >
> > > CC: "Todd, Douglas M." <DTODD at partners.org>,
> > > cisco-nsp at puck.nether.net
> > > Betreff: Re: [c-nsp] CBWFQ/PQ Support on 6500/SUP720-3BXL
> >
> >
> > > On 6/11/08, Zahid Hassan <zhassan at gmx.net> wrote:
> > > > Thanks Douglas, I am still tyring to the find out if there is a
> > way to > do this with wrr-queues.
> > > >
> > > > The bit that I am not sure about is how to match on EXP bits
> > within > wrr-queues.
> > > >
> > > >
> > > > Does anyone know if this is at all possible ?
> > >
> > > Zahid see what I wrote in preceding email. I think this is what you
> want.
> > >
> > > For MPLS packets the EXP value is mapped into an internal DSCP and
> > you > can assign into wrr queues according DSCP value.
> > >
> > > David
> > >
> > > >
> > > >
> > > > Regards,
> > > >
> > > >
> > > > Zahid
> > > >
> > > >
> > > >
> > > >
> > > > -------- Original-Nachricht -------- > > > Datum: Wed, 11 Jun
> > 2008 05:52:42 -0400 > > > Von: "Todd, Douglas M."
> > <DTODD at PARTNERS.ORG> > > > > > An: "Zahid Hassan" <zhassan at gmx.net>
> > > > > > > CC: cisco-nsp at puck.nether.net > > > Betreff: RE: [c-nsp]
> > CBWFQ/PQ Support on 6500/SUP720-3BXL > > > > > > > Zahid:
> > > > >
> > > > > We were looking at the same senerio and found that we must use
> > a SIP > type > > > card > > > to do any traffic shaping. The
> > 6500 does not have this type of > feature.
> > > > > SIP-200/400 for either DS1/100FD/1G type of connections.
> > > > >
> > > > > Hope this helps.
> > > > >
> > > > > Douglas
> > > > >
> > > > > -----Original Message-----
> > > > > From: cisco-nsp-bounces at puck.nether.net > > >
> > [mailto:cisco-nsp-bounces at puck.nether.net] On Behalf Of
> David Granzer
>
> > > > > Sent: Wednesday, June 11, 2008 5:46 AM > > > To: Zahid Hassan
> > > > > Cc: cisco-nsp at puck.nether.net > > > Subject: Re: [c-nsp]
> > CBWFQ/PQ Support on 6500/SUP720-3BXL > > > > > > On 6/11/08, Zahid
> > Hassan <zhassan at gmx.net> wrote:
> > > > > > Many thanks for this David.
> > > > > >
> > > > > > Yes, the "priority" and as well as the "bandwidth" command
> > doesn't > > > > seems to be supported in either ingress or egress
> direction.
> > > > > >
> > > > > > I am thinking of configuring "wrr-queues" and I don't know
> > if I > can > > > > at all match on EXP bits.
> > > > > >
> > > > > > Does anyone know how to match on EXP bits within a wrr-queue ?
> > > > >
> > > > > For MPLS packets, the EXP value is mapped into an internal
> > DSCP so > that > > > the > > > PFC3BXL or PFC3B can apply
> > non-MPLS QoS marking and policing.
> > > > >
> > > > >
> > >
> >
> http://www.cisco.com/en/US/docs/switches/lan/catalyst6500/ios/12.2SXF/
>
> > native/con
> > > > > figuration/guide/mplsqos.html
> > > > >
> > > > > David
> > > > >
> > > > > >
> > > > > >
> > > > > > Thanks in advance.
> > > > > >
> > > > > >
> > > > > > Zahid
> > > > > >
> > > > > > -------- Original-Nachricht -------- > > > > > Datum:
> > Wed, 11 Jun 2008 10:36:32 +0200 > Von: "David Granzer"
> > > > > > <dgranzer at gmail.com> > An: "Zahid Hassan" <zhassan at gmx.net> >
> CC:
> > > > > > "Cisco NSP Puck Nether Net (Cisco NSP)"
> > > <cisco-nsp at puck.nether.net>,
> > > > > > zhassan at bis-internet.co.uk > Betreff: Re: [c-nsp] CBWFQ/PQ
> > Support > on > > > > 6500/SUP720-3BXL > > > > > > > > > > > >
> > > Hello, > > > > > > > > > > n 6/11/08, Zahid Hassan
> > <zhassan at gmx.net> wrote:
> > > > > > > > Dear All,
> > > > > > > >
> > > > > > > >
> > > > > > > > I have a requirement to implement CBWFQ/LLQ matching
> > > > on > > > > EXP bits on a 6500 with SUP720-3BXL.
> > > > > > > >
> > > > > > > > Since the "priority" command is not supported within a
> > > > > > policy-map, > > I am wondering if this can be achieved
> > using > > > "wrr-queues".
> > > > > > > >
> > > > > > > > This is the failure message when I apply the
> service-policy:
> > > > > > > >
> > > > > > > > 6500(config-if)#service-policy input CORE-THREE-CLASS
> > > > > > > > priority command is not supported in input direction >
> > > for this > > > > interface configuration failed!
> > > > > > >
> > > > > > > above you try using priority in ingress direction which
> > is not > > > > > > supported generally. Second problem in your case
> > will be that > > > > > 6500/7600 LAN cards does not support CBWFQ
> > like 7200/7301 etc. You > > > > > > must use L2 QoS, see "Quality
> > of Service on Cisco Catalyst 6500"
> > > > > > >
> > > > > > >
> > > > > >
> > >
> >
> http://www.cisco.com/en/US/prod/collateral/switches/ps5718/ps708/prod_
> > > > > > white_paper0900aecd803e5269.html > > > > >
> > > > > >
> > David > > > > > > > > > > > > > > > > > > > > > > This is
> > for a WS-X6704-10GE linecard with supports 1p7q8t.
> > > > > > > >
> > > > > > > > I will be really grateful for input or pointers about
> this.
> > > > > > > >
> > > > > > > > Thanking in you advance.
> > > > > > > >
> > > > > > > >
> > > > > > > > Regards,
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > Zahid
> > > > > > > >
> _______________________________________________
> > > > > > > > cisco-nsp mailing list cisco-nsp at puck.nether.net > >
> > > > > >
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> > > > > > > > archive at
> http://puck.nether.net/pipermail/cisco-nsp/
> > > > > > > >
> > > > > >
> > > > > >
> > > > > > --
> > > > > > GMX startet ShortView.de. Hier findest Du Leute mit Deinen
> > > Interessen!
> > > > > > Jetzt dabei sein:
> http://www.shortview.de/?mc=sv_ext_mf@gmx
> > > > > >
> > > > > _______________________________________________
> > > > > cisco-nsp mailing list cisco-nsp at puck.nether.net > > >
> > https://puck.nether.net/mailman/listinfo/cisco-nsp
> > > > > archive at
> http://puck.nether.net/pipermail/cisco-nsp/
> > > > >
> > > > > No virus found in this incoming message.
> > > > > Checked by AVG.
> > > > > Version: 7.5.524 / Virus Database: 270.2.0/1494 - Release Date:
> > > 6/10/2008
> > > > > 7:22
> > > > > AM
> > > > >
> > > > >
> > > > > The information transmitted in this electronic communication
> > is > intended > > > only > > > for the person or entity to whom
> > it is addressed and may contain > > > confidential > > > and/or
> > privileged material. Any review, retransmission, dissemination > or
> > > > > other > > > use of or taking of any action in reliance upon
> > this information by > > > persons or > > > entities other than the
> > intended recipient is prohibited. If you > received > > > this > >
> > > information in error, please contact the Compliance HelpLine at > >
> > > 800-856-1983 and > > > properly dispose of this information.
> > > > >
> > > > >
> > > >
> > > >
> > > > --
> > > > Ist Ihr Browser Vista-kompatibel? Jetzt die neuesten > >
> > Browser-Versionen downloaden:
> http://www.gmx.net/de/go/browser > > >
> > > _______________________________________________
> > > > cisco-nsp mailing list cisco-nsp at puck.nether.net > >
> > https://puck.nether.net/mailman/listinfo/cisco-nsp
> > > > archive at
> http://puck.nether.net/pipermail/cisco-nsp/
> > > >
> >
> >
> > --
> >
> > GMX startet ShortView.de. Hier findest Du Leute mit Deinen Interessen!
> > Jetzt dabei sein:
> http://www.shortview.de/?mc=sv_ext_mf@gmx
> >
>
>
>
More information about the cisco-nsp
mailing list