[nsp] Upstream traffic-shaping?

[Rubens Kuhl Jr.]

Customers will probably be happier if you shape first and limit later.
Limiting right away is a bad thing, TCP reacts badly to packet loss.
You can shape the traffic going out of eth 0/0 with GTS groups, creating an
ACL with the IP address of each customer, like this:

(adapted from
http://www.cisco.com/en/US/products/sw/iosswrel/ps1831/products_configuration_guide_chapter09186a00800c60cc.html#16775)

access-list 101 permit 10.10.10.10
access-list 102 permit 10.10.10.20
access-list 103 permit 10.10.10.30
!
interface eth0/0
 traffic-shape group 101 64000
 traffic-shape group 102 64000
 traffic-shape group 103 256000


Rubens




----- Original Message ----- 
From: "Stephen J. Wilcox" <steve at telecomplete.co.uk>
To: "Vincent De Keyzer" <vincent at dekeyzer.net>
Cc: <cisco-nsp at puck.nether.net>
Sent: Friday, January 16, 2004 4:05 PM
Subject: Re: [nsp] Upstream traffic-shaping?


> have you tried rate-limit rather than traffic-shape?
>
> On Fri, 16 Jan 2004, Vincent De Keyzer wrote:
>
> > * a 2610 in a customer building, with a NM-4E in slot 1
> > * Eth 0/0 is connected to the PoP router
> > * Eth1/0 to Eth1/3 are for the customers
> > * the service offered to all customers is identical: Internet access.
> >
> > Question is: how do I limit upstream traffic?
> >
> > Downstream is easy: I apply "traffic-shape rate" on the Eth1/x ports.
But
> > what about upstream?
> >
> > Vincent
> >
> > _______________________________________________
> > 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/
> >
>
> _______________________________________________
> 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/
>