I have heard of NetQoS. Is this an appliance or a piece of software? Where does it run? The site does not give much away.
Cheers, Aaron. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Joe Loiacono Sent: Tuesday, May 13, 2008 11:56 PM To: Rick Martin Cc: [EMAIL PROTECTED]; [email protected] Subject: Re: [c-nsp] Prove it's not the network! Two things might help. 1) Active performance monitoring Set up iperf on both ends of your link. Periodically (e.g., for 30 seconds every hour) burst as high as you can (large windows, etc.). Graph this continually. That will show the actuall capacity achievable. You can even set up multiple client-server iperf pairs and use comparisons betwen them to isolate problems to different network segments. See, for example: http:ensight.eos.nasa.gov (this is custom, so you'd have to develop your own :-) 2) Application performance monitoring NetQoS has a sharp tool called SuperAgent (SA). SA installs in your data center and can track performance from all clients to any specified application (e.g., Outlook). What is neat about it is you don't have to instrument the clients to be able to understand their performance - it is all determined by examing the TCP traffic flow traversing the single point where SA is installed. The reports break the performance down into several segments, one of which is the network. This can eliminate the network as a source of performance problems (if that is the case.) I don't work work for NetQoS, and there are other similar products. Joe "Rick Martin" <[EMAIL PROTECTED]> Sent by: [EMAIL PROTECTED] 05/13/2008 11:15 AM To <[email protected]> cc Subject [c-nsp] Prove it's not the network! I know this is not really a Cisco specific question but it is definitely in support of Cisco hardware. How do most of you folks prove that "the problem" is not the network? We utilize CA Spectrum and eHealth for availability and statistical analysis but in some instances that does not cut it. We don't typically have much trouble proving that a T1 is serving up 1.5 meg of bandwidth. Customers complain that their access is slow, we show that they are using all available bandwidth and eventually sell them more bandwidth and the problem is resolved. The more difficult effort is when there is plenty of available bandwidth and a particular application is slow (Outlook in the case I am involved in now). This is a very high level political official and we must come to a resolution. All tools we have available to us today indicate that there is not a problem with the network. Typical utilization on the T1 is about 500 to 600K peak during the day. Certain management continues to point the finger at the network. We have used Internet based speed tests that at times show less than 1.5Meg download speeds, I explain the variables in the Internet and the particular tool in use as well as local contention for the bandwidth etc to no avail, once they see less than 1.5 meg speed the finger points to the network. I still must somehow "prove" that the network is not the issue. I am interested in an Internet speed test like tool to install at the core of our network that would provide a sustained upload or download test that would run for longer periods of time than a regular speed test. I would like to fill the pipe while graphing in Ehealth or as part of the selected tool to prove that the contracted bandwidth is available in both directions. Any recommendations for products would be appreciated. We are currently looking at SolarWinds WAN Killer and a traffic generator from Omnicore LanTraffic V2. I am also open to different "types" of solutions to point to where the problem is actually located. Thanks in advance for any suggestions Rick Martin Network Engineer State of Arkansas, Department of Information Systems _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/ _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/ _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
