Posted on 2012-08-13
I work for a bank with 2 buildings, connected with Cisco 1900 routers and talking via a Cisco ASA VPN riding over a DSL connection. One branch has four employees, six workstations, one windows 2003 domain controller and the main building has about 30 employees, a variety of servers, workstations and networked printers.
We have various problems that I like to attribute mostly to latency. If I do a continuous ping to our B2B partner, most responses are fast, some are 100-700 ms. Meanwhile, other applications work, but slowly. The speeds are inconsistent, sometimes fast, and sometimes slow.
All http traffic rides the VPN from branch to main and then out to the Internet, as does the B2B traffic (basically a telnet session).
Major changes include adding the ATMs to the network, using an online backup service, WSUS, Symantec Endpoint and the bank image software.
I contend the culmination of the changes is saturating the DSL pipe on the VPN. The end users often complain about things being slow, stuff not working, etc. However, the problems are intermittent.
So, here’s the question:
How can I inexpensively monitor the network from a speed perspective, without using the ASA – I’m not conversant enough in Cisco IOS. If you were to try to prove my point (about the DSL being saturated) then how would you go about it? The DSL is showing 640K up speed and 3Mbps down, but the provider only promises 70% of those rates. This is a rural area, so no other networking options are available, save installing a second DSL line and perhaps dividing the traffic (http on one, VPN on another).