Thanks - just need a little clarification on 2 points. I have 2 serials, so I need to shape on both correct?

2nd question - with regards to using percentage vs using bits how is that written 75% for example?

Thanks again

best to do it on the hub if you have hub&spoke. if you want to shape 75% of the reserved bandwidth, the use 75%. I believe by default 75% of the interface bandwidth is reseved by the "max-reserved-bandwidth" command.

thanks - when I try to apply it to the interface I get

interface bandwidth is less than 8000 bps.

Very aggravating. What can I be doing wrong?

What I wound up doing and it seems to be working fine is on each serial in the bundle:

traffic-shape rate

Looks to be working good, any downside to doing it this way?

by just applying generic shaping directly under the interface will work but it's not scalable. In your case you better off using MQC frame-relay traffic shaping using the map-class and referencing a policy-map. By doing it this way you can apply shaping per DLCI's because by default when you apply it under the serial interface, the shaping affects all DLCI's configure under the interface.

see this http://blog.internetworkexpert.com/2008/01/22/legacy-frts/

if error you are getting, send me the output show run int [your frame-relay interface]

sh int [frame-relay interface]

Thanks - I tried again using map-class and found my mistake was applying it to the wrong interface (sub interface).

This works perfectly at limiting bandwidth but I'm still confronted with the orginal problem that brought me here to trying to limit outbound bandwidth.

This circuit is a multimeg (3meg total). There is so much congestion outbound, that connection to a web server running on this circuit are very slow and often timeout. When I applied the policy map, I effectively cut outbound traffic to 2.5 Mbits but still the connections to web server from the outside are terrible.

I looked at the interface that I applied policy map to and see alot of drops, which I assume is because of the policy map itlself but I also assume that it's responsible for connections issues to web server.

Any thoughts on this?

Thanks again for all of your input, it's been very helpful.

Other than many shaper's implementation of (W)FQ, if you have outbound congestion, you might be better served but how you manage that congestion.

Could you clarify what type of multi-meg interface this is that provides 3 Mbps? I would assume it's something like dual T-1s, but if so, they're not bonded?