“Detective”: Integrating NDT and E2E piPEs Richard Carlson rcarlson@internet2.edu Internet2

System Architecture Deployment is an inside-out approach. Start with regularly scheduled tests inside, make sure it plays well with regularly scheduled tests outside. Question: How do we test to the end nodes (blue links)? 4/29/2019

Internal Measurement Infrastructure Components While this approach works for partial path analysis between 2 PMPs, extending this approach to the end host is problematic. 4/29/2019

Internal Measurement Infrastructure Tests Abilene Measurement Infrastructure monitors backbone with ongoing tests: BWCTL/Iperf OWAMP Traceroute To reach the desktop we need custom tests from the topologically “nearest” measurement node to the end user desktop. PacketCrafter (TBD) 4/29/2019

Reaching the Desktop Running test to/from user desktop AAA issues Test program may not be installed Test program may not be available AAA issues Who can run tests Who can review the results How are results archived Plan is to enhance the Internet2 Detective and NDT system to achieve this goal 4/29/2019

NDT Background Client/Server based system Web100 enhanced server handles testing and diagnostic services Java based client allows testing to any desktop Performance and configuration faults reported back to client Drill-down functions provide more details & error reporting capabilities 4/29/2019

NDT drawbacks Must know URL for each server Network path to server may be unknown Hard to know which server is ‘best’ Closest to desktop is better for local configuration diagnostics Closest to destination is better for E2E performance diagnostics 4/29/2019

“Detective” Features Federated mode of operation Multiple piPEs measurement node servers operating as single system Client automatically re-directed to ‘closest’ piPEs measurement node server Prefer configuration diagnostics Enhanced diagnostic functions Enhanced ‘drill-down’ functions Enhanced reporting functions 4/29/2019

Enhanced Diagnostic Functions PacketCrafter and Web100 data to identify configuration problems Duplex mismatch Excessive errors caused by HW faults MTU size and mismatch Middlebox in path WiFi connection Congestion notification Excessive Delay Operating in half-duplex mode 4/29/2019

Enhanced Diagnostic Functions PacketCrafter, OWAMP, BWCTL, Traceroute, and Web100 data to identify performance problems PMTU size and mismatch Middlebox in path TCP buffer size Packetcrafter is a new tool we intend to develop, analogous to OWAMP or BWCTL. It will be capable of crafting custom packet trains needed to diagnose end host problems. It will share network resources with other tools (e.g. BWCTL) by cooperative scheduling to ensure data integrity. 4/29/2019

Enhanced “Drill-Down” Functions Client can obtain performance tuning suggestions for destination IP Calculated BW*Delay product for destination Obtain RTT / OWAMP data for destination Obtain MTU data for destination Client can test to another PMP server Test to server in another measurement domain Test to server ‘closest’ to network egress point Test to server ‘closest’ to destination host 4/29/2019

Enhanced Reporting Features Server automatically determines appropriate contact info Local domain (desktop IP) Remote domain (destination IP) Core domain (Abilene NOC) GigaPoP domain Raw and derived data automatically forwarded to contact 4/29/2019

Server Discovery Module User contacts “well-known” piPEs measurement server (any measurement node in federation) Contacted piPEs measurement server runs traceroute back to desktop IP address Discovery Module uses traceroute data to find ‘closest’ server (ingress point) Contacted server re-directs client to that measurement server 4/29/2019

“Detective” Operation User presses “Detective” applet’s ‘START’ button to begin testing PacketCrafter testing module runs tests and Analysis module returns results ‘Drill-down buttons activate at end of test ‘Statistics’ button ‘More Details’ button ‘Continue Testing’ button ‘Report Problems’ button 4/29/2019

“Detective”: Integrated NDT and piPEs Architecture End Host makes a request to a “well-known piPEs measurement node server” through a web page (eventually Internet2 Detective) by downloading a Java Applet. “Well-known piPEs measurement node server” system does a traceroute back to the laptop. Redirect test request to “Topologically Nearest piPEs measurement node server.” (May be a NO-OP.) “Topologically Nearest piPEs measurement node server” invokes PacketCrafter tool through local interface and monitors Web100 variables on “Topologically Nearest piPEs measurement node server” to determine end host problems, if any. “Topologically Nearest piPEs measurement node server” system checks ongoing tests to other piPEs measurement nodes along the route to destination to determine if there are any known network problems along the path. 4/29/2019

“Detective” Measurement Software Components Working, deployed prototypes exist for Network Monitoring, Web Service, PMC, PMP, and Database. Work beginning on “Detective” applet, Discovery Module, Analysis Module, PacketCrafter and MDI. We call the end host analysis module the “Detective” in part because we intend to integrate this functionality into the Internet2 Detective eventually. 4/29/2019

“Continue Testing” Button User can enter destination name/address Obtain TCP tuning suggestions User can request test to remote piPEs measurement servers Allows performance testing of network path from end host User can request inter-piPEs-measurement-server tests and test results Access to partial path, intermediate node BWCTL, OWAMP, and Traceroute data 4/29/2019

Conclusions Divide & conquer approach to diagnostic and troubleshooting procedures Serious desktop configuration problems will be found quickly with little impact on backbone network “Detective” will provide single point of contact to piPEs measurement framework 4/29/2019

4/29/2019