Routing or ACL changes based on total bandwidth used?

[lostngone]

I have no idea about how I would go about doing this but maybe someone can point me in the right direction.

I have a remote office that has 2 connections connected to our central office. One connection is a private 128Kbps frame-relay link and the other is a 3Mbit/768Kbps VPN connection over the internet. At the remote office they both terminate into a 2811 and at the central office the VPN tunnel terminates at an ASA and the frame connection terminates into a cisco 3800 series router.

The problem is the Internet connection has a pretty small monthly cap and the phone company charges by the megabyte when you go over. My question is, is there some way to change routing, apply any access list or shutdown an interface when pre-set bandwidth limit is reached?

Any ideas would be greatly appreciated.

[andrew.prince]

Just to understand - if you pay for 100MBS and you go over, you want that link to shut for example?

[lostngone]

Correct, however it is more like 15 Gigabytes a month. This would not be a problem most time however for 2 or 3 months a year during heavy traffic they will go over and I would just like to have them switch to the slower link until I switch them back.

[andrew.prince · Accepted solution]

I suggest you look at:-

1) Get the SNMP OID for interface bandwidth/output/input bytes

2) Write either a TCL or EEM script to monitor the SNMP OID in 30 second intervals

3) Action the interface to close when the SNMP OID is = or > than the 15 GB

4) Send en email to yourself to notify you of the limit reached and the interface is closed.

HTH>

[Joseph W. Doherty]

Disclaimer

The  Author of this posting offers the information contained within this  posting without consideration and with the reader's understanding that  there's no implied or expressed suitability or fitness for any purpose.  Information provided is for informational purposes only and should not  be construed as rendering professional advice of any kind. Usage of this  posting's information is solely at reader's own risk.

Liability Disclaimer

In  no event shall Author be liable for any damages whatsoever (including,  without limitation, damages for loss of use, data or profit) arising out  of the use or inability to use the posting's information even if Author  has been advised of the possibility of such damage.

Posting

OER/PfR, might be a possible solution; the ASA could be a problem.

OER/PfR monitors actual traffic loads, and can move flows about.  It also is designed that it can take bandwidth $ costing into account when it make its decisions.