[c-nsp] 3560 QoS/shaping

Yan Filyurin yanf787 at yahoo.com
Thu Jan 15 00:05:04 EST 2009


What's the difference between normal and special condition.  As in are you able to do something with it, where it could go either to a shaped queue or a shared queue based on its DSCP for example?




________________________________
From: Brad Henshaw <brad.henshaw at qcn.com.au>
To: Jon Lewis <jlewis at lewis.org>
Cc: cisco-nsp at puck.nether.net
Sent: Wednesday, January 14, 2009 11:57:32 PM
Subject: Re: [c-nsp] 3560 QoS/shaping

Jon Lewis wrote: 

> That also won't work in this special case, as the
> rate-limiting/shaping is only to be done on a class of traffic,
> and only if that traffic has to egress through a particular
> port.  Under normal conditions, the traffic won't need to be
> shaped.

In that case I think you're boned. Can you kludge up a dedicated
interface
for this traffic (in this scenario) to egress?

> > You'd need a 3750ME for anything much more advanced -- and even
then, 
> > this functionality is limited to two of the gig ports. I think the 
> > 3400ME's support egress policies but they have their own limits and 
> > retardations in this respect.
> The 6500 PFC3 can do policing on ingress/egress.  Is there anything
>  between the 6500 and 3550 that does?

Only the 3750ME (on ES ports) at any decent granularity that I'm aware
of
- others on the list might have more to add.

>From memory the 4948 can do rate-based shaping of its egress queues
but that would likely require messing with DSCP markings and DSCP-queue
maps.

Regards,
Brad
_______________________________________________
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/



      


More information about the cisco-nsp mailing list