A question that I'm faced with currently. Here's my setup:
Cisco ASA 5510
15Mbps Internet Connection @ $1350/month
The bandwidth was originally meant for 35-45 people but we've grown quite quickly to roughly 60-65 people. Needless to say, when I check bandwidth logs it's almost always spiked at 15Mbps.
I did use Wireshark to do some poking around to see what was hogging up our bandwidth but with everything running through CDNs and Cloud Services it proved difficult to get a good grasp of where our bandwidth was going. So the question is do I ONLY implement bandwidth management through ASA OR upgrade the Internet to 50Mbps ($1600/month) and then implement bandwidth management through ASA?
Any suggestions on how to segment the 15Mbps connection if we decided ONLY to go with the bandwidth management solution? Thanks.
UPDATE 1
Installed PRTG and used packet content to monitor the traffic. As I suspected still pretty vague. My Top Connections include the following:
a204-2-160-16.deploy.akamaitechnologies.com
ec2-50-16-212-159.compute-1.amazonaws.com
a204-2-160-48.deploy.akamaitechnologies.com
a72-247-247-133.deploy.akamaitechnologies.com
mediaserver-sv5-t1-1.pandora.com
Other than the Pandora destination, the rest doesn't tell me much on how to properly control the bandwidth.
Any thoughts or suggestions? Thanks.
M
Best Answer
A better understanding of the traffic would help. A tool that has really visualized this for us is Paessler PRTG PRTG. There is a free trial. You can monitor Netflow on the ASA and determine what is using bandwidth and generating traffic. It may be you could install a proxy that caches content and so users that visit common sites do not actually go to the web. You may have one or two users impacting the connection much more than others