• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 669
  • Last Modified:

Dealing with interface over-utilization on a cisco network

I'm an administrator for a large all cisco network at a major university.  Currently all of our internet traffic runs out one 6509 switch that serves as our gateway.  The external interface is 100 Mbs fdx ethernet when leaving our network.  We run multi-gig on the backbone.  Outside the gateway router traffic passes through a couple security routers and firewalls that are controlled by our parent organization and we have no ability to configure.  

Our students have recently discovered a legitimate and legal music and movie site with massive amounts of bandwidth.  As the word spread the average traffic inbound on the external interface of the gateway has pegged at 100% utilization with packets being dropped because theres nowhere for them to go.  Due to the site being legal and legalities pertaining to academic freedom I cannot block this site outright, nor do I want to.  I'm looking for a way to limit the amount of traffic bombarding that interface from within my span of control which runs from the access layer up through the core and the gateway router at the edge.

In addition to standard cisco 6500s, 4500s, and 3550s that compose most of our network traffic entering and leaving the gateway router is funneled through two cisco content engines, a websense server, and a pix firewall that we control before being passed up the security stack to the internet.  A solution using any of these pieces of equipment or a combination thereof would be acceptable.
  • 2
1 Solution
The best thing would be rate-limiting that traffic to a percentage of your interface bandwidth. Unfortunately if the gateway link is being pegged because of inbound traffic, the only place where you could make a real difference would be on the other side of that link- the side that it sounds like you do not control. You can configure rate-limiting on the router or on the PIX, but it still doesn't help if the outermost link to your domain is pegged with inbound traffic.

Perhaps you can find a way to get the folks on the other end to set up some basic QOS for you that limits that stuff? But next month there may be something else and they may not want to set a precedent...
dbauer3851Author Commented:
Thats pretty much exactly the situation.  Kids aren't dumb, any time you find a way to beat one thing they're doing they'll come up with a new one and the other end doesn't want to be in the business of dealing with that.
Perhaps you can limit the traffic TO that site down really low. Although it doesn't directly solve the problem, if you slow down the request for files enough, it should limit the amount of data that can come back. You would have to experiment unless you have some netflow or RMON analysis available to see just how much outbound data there is. Then try rate-limiting it to say, 50% of the current level.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

The new generation of project management tools

With monday.com’s project management tool, you can see what everyone on your team is working in a single glance. Its intuitive dashboards are customizable, so you can create systems that work for you.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now