NDT: piPEs Integration and Future Directions

1
NDT piPEs Integration and Future Directions

• Rich Carlson
• Summer Joint Tech
• RCarlson_at_internet2.edu
• July 21, 2004

2
NDT Background

• Web100 enhanced server handles testing and
  diagnostic services
• Java based and command line clients allows
  testing from any client (local or remote)
• Performance and configuration faults reported
  back to client
• Drill-down functions provide more details error
  reporting capabilities

3
piPEs Measurement Software Components
4
Historical Tasks

• Converted NDT distribution package to GNU
  automake
• Uses standard configure, make, make install
  methodology
• GNU style ndt-version.tar.gz distribution package
  
• Moved package into CVS repository to improve
  change tracking

5
NDT Feature Enhancements

• Configuration file support
• Better support for localhost testing
• Scheduling/queuing support
• Simple server discovery protocol
• Federation mode support
• Command line client support

6
Scheduling/Queuing Support

• Handles incoming client requests in a FIFO manner
• Handles both Java-based and command line clients
• Automatically updates client status and starts
  test when at head of queue
• Option allows administrator to disable this
  feature

7
Federation mode

• Allows multiple servers to coordinate testing
  services
• Simple server discovery protocol relies on
  traceroute
• Prefer local configuration testing over E2E
  performance testing
• Allows user to force performance test to
  specific server

8
Command Line client

• C program version of Java-based client
• Allows testing from remote clients
• Shares server with Java-based clients
• FreeBSD and Windows (cygwin) based clients have
  been tested
• Download NDT package and make web100clt from the
  src sub-directory

9
NDT Deployment

• Initial Abilene Federation
• 5 Abilene PoPs (ndt-city.abilene.ucaid.edu7123)
• New York
• Washington DC
• Indianapolis
• Sunnyvale
• Seattle
• StarLight peering point
• Test/development server at Ann Arbor

10
NDT Documentation

• Integrated NDT web site into Internet2 e2epi site
• http//e2epi.internet2.edu/ndt
• Created man pages for server programs
• Download space for source files
• List of Public and REN based severs
• Email discussion lists

11
NDT Experimental Features

• Bi-directional testing, server and client
  simultaneously send/receive data
• Sever CPU utilization values

12
On-going Activities

• Moved source code to sourceforge.net CVS
  repository
• http//www.sourceforge.net/projects/ndt
• Investigating how to sourceforge and Internet2
  web sites to avoid duplication of effort and
  files

13
Future Directions

• Focus on improving problem detection algorithms
• Duplex mismatch
• Link detection
• Improve performance tuning messages

14
Future Directions

• Complete deployment in Abilene POPs
• Expand deployment into University campus/GigaPoP
  networks