1. Continuous Throughput Testing and Dynamic Visualization Utilizing Network Diagnostic Tool (NDT) To solve our problem ;)

2. 2 Why did we do this project? 1.MCNC was requested to perform network throughput and quality testing for hundreds of K-12 schools in NC. 2.We had several constraints that limited our testing ability. 3.TIME was an issue, we had to move fast!! 4.Visualization was extremely important to convey the results to both technical and non-technical audiences.

3. 3 What was the problem to solve? 1.Perform network testing at remote locations with virtually no IT “hands” on-site. 2.We could not install any software or hardware at the remote sites. 3.The data should reflect the actual network performance of the student “end-host” computers. 4.How to get the results in a format that anyone can read/understand.

4. 4 What did we do? Wrote Custom PHP Scripts Parsed web100srv log files for results Extracted date/time, IP address, upload and download speeds Wrote data to RRD files for later graphing / analysis Modified NDT java applet Manipulated applet to run continuously after “start” initiated Tcpbw100.java modified to re-run test every 5 min after the start button is clicked Built 4 NDT Servers With all the usual suspects (NDT v.5.4.12, Web100 modified kernel, Userland libraries) Imaged every box with CactiEZ CD Beta v0.2b

5. 5 Testing, Testing, 1,2,3… We needed to see how the modified NDT would operate with a heavy load Conducted initial testing on staff at MCNC on one NDT server We estimated we needed 4 NDT servers--somewhat arbitrary (but it worked!) Challenges –Firewall ports –Screensaver/Sleep mode We tested schools over a week and coordinated timing with Tech Directors across the State of NC.

6. 6 Results! We had ~130 schools attempt the testing. Of those, we had around 80 schools with enough data to show connection quality. Results varied among schools and school systems. One problem we found (after the fact) is several school systems used NAT, so results were inconclusive for individual schools.

7. 7 Results! (cont’d)

8. 8 Next Steps… 1.Ability to enter information before running the test, and capturing that information into the logs/results. 2.Integration into Cacti (automatically create graphs and datasources in MYSQL. 3.Ability to pick times the test will run again. 4.Ability to start testing without having to press “Start”. 5.Based on results of tests, recommend TCP tuning parameters.

9. DEMO ! Vision – Communication - Collaboration NDT Test NDT Test Results

10. Questions? Comments? Vision – Communication - Collaboration Andrew @ mcnc.org Carla @ mcnc.org

11. 11 Just in Case

12. 12 Just in Case

13. 13 Just in Case 2