[c-nsp] limiting bandwidth per flow over a T1?

Barton F. Bruce barton at gnaps.com
Fri Jul 7 20:26:41 EDT 2006


If you were routing, there are various things to do.

This would help let you see what is happening:

    sho ip cac flo

 you could:

 rate-limit input access-group 105 496000 10000 20000 conform-action
transmit exceed-action drop
 rate-limit input access-group 106 496000 10000 20000 conform-action
transmit exceed-action drop
 rate-limit input access-group 107 496000 10000 20000 conform-action
transmit exceed-action drop
 rate-limit input access-group 117 256000 8000 20000 conform-action transmit
exceed-action drop

where each access group is looking for specific IPs or ports or whatever you
can use to select traffic for rate limiting.
you can have a LOT of these on an interface.

here is shaping that is a bit more gentle and also gets applied to an
interface:

traffic-shape group 140 768000 12000 12000 1000
 traffic-shape group 141 768000 12000 12000 1000
 traffic-shape group 142 768000 12000 12000 1000
 traffic-shape group 143 768000 12000 12000 1000
 traffic-shape group 144 384000 12000 12000 1000
 traffic-shape group 145 768000 12000 12000 1000
 traffic-shape group 146 768000 12000 12000 1000
 traffic-shape group 147 768000 12000 12000 1000
 traffic-shape group 148 768000 12000 12000 1000
 traffic-shape group 149 768000 12000 12000 1000

there are more options, and hopefully someone will give you something that
works with bridging.

Probably not the way to do it, but configuring the ports so you run frame
relay with several PVCs built lets you run different traffic down each, and
you have all of FR's CIR type controls to play with, too.



----- Original Message ----- 
From: "Scott Granados" <sgranados at jeteye.com>
To: <cisco-nsp at puck.nether.net>
Sent: Friday, July 07, 2006 7:51 PM
Subject: [c-nsp] limiting bandwidth per flow over a T1?


> *This message was transferred with a trial version of CommuniGate(r) Pro*
> I have what might be a simple question but I wasn't sure what
> technology, if any would support what I want to do.
>
>
>
> I have two routers, one 1720 with T1 wicc and one 2621 also with wicc. A
> single T1 (standard ESF B8ZS all 24 channels) connects our offices to
> our production environment at a local DC.  I have various users who pass
> all sorts of traffic over this loop 2 and from mainly ssh and http.
> Also, both routers aren't actually ip routing but are bridging.  My
> question is, can I apply a rule to say the serial interfaces where any
> one flow or session won't use up more than 1.2 megs of the t1 (just as a
> for instance).  I'm having individual users who are file transfer happy
> flooding this guy and showing the rest of us using ssh and or http over
> the same loop no love what so ever.  I'd like to just keep things so
> that big file transfers don't make the ssh sessions hang or lag quite so
> much.  Ideas?
>
>
>
> Suggestions, buy a T3 and heavier gear?:)
>
>
>
> Any pointers would be appreciated, thanks!
>
>
>
> _______________________________________________
> 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