|
1. WORK PACKAGE NUMBER |
2. REVISION NO. 0 |
3. DATE PREPARED 1/5/00 |
||||||
|
4. WORK PACKAGE TITLE Internet End-to-End Performance Monitoring (IEPM) |
5. BUDGET AND REPORTING CODE KJ-01 |
|||||||
|
6. WORK PROPOSAL TERM 12 Months |
7. IS THIS WORK PACKAGE INCLUDED IN THE INSTITUTIONAL PLAN? No |
|||||||
|
8. DOE PROGRAM MANAGER George Seweryniak |
11. HEADQUARTERS ORGANIZATION Energy Research |
14. DOE ORGANIZATION CODE |
||||||
|
9. OPERATIONS OFFICE WORK PROPOSAL REVIEWER |
12. OPERATIONS OFFICE Oakland |
15. DOE ORGANIZATION CODE
|
||||||
|
10. CONTRACTOR WORK PROPOSAL MANAGER |
13. CONTRACTOR NAME Stanford Linear |
16. CONTRACTOR CODE 55 |
||||||
|
17. WORK PROPOSAL DESCRIPTION (Approach, anticipated benefit in 200 words or less.)
This proposal covers the further development and deployment of
end-to-end Internet monitoring (IEPM) tools. The success of the
current efforts [1]
[2], both within and
beyond the High Energy Physics (HEP) community and the Energy Sciences
Network (ESnet) has provided ample incentive to extend the capabilities
of the existing tools, and develop new ones for purposes not
previously envisioned by the project.
The project will further develop tools for an improved understanding
of the critical components that limit end-to-end performance, and
electronically publish results in the form of tables and graphs
similar to those already developed. In addition the project
intends to develop new tools to aid understanding in the same
low impact (on the network and servers), low cost (to deploy), and
understandable mechanisms as before.
The aspect of problem diagnosis using the tools and data will be
refined. Furthermore
new tools intended to aid visualization and understanding of the
analyzed results by expert and layman alike will be developed.
These tools, existing and new, and the increased emphasis on the
visualization aspect, will lead to a greater understanding of the
dynamics of the Internet and help provide realistic service quality
expectations and identify where extra resources may be effectively
applied. |
|
18. CONTRACTOR WORK PROPOSAL MANAGER
|
19. OPERATIONS OFFICE REVIEW OFFICIAL
|
|||||||||||||||
|
20. ATTACHMENTS
|
||||||||||||||||
|
21. STAFFING (in Staff Years)
a. SCIENTIFIC b. OTHER DIRECT c. TOTAL DIRECT
|
FY2001 |
FY2002
|
FY2003 |
BY+1 |
BY+2 |
TOTAL TO COMPLETE |
||
|
22. OPERATING EXPENSE (in Thousands) a. OBLIGATIONS b. COSTS
|
|
|
|
|
|
|
||
|
23. EQUIPMENT a. OBLIGATIONS b. COSTS
|
|
|
|
|
|
|
||
|
24. MILESTONE SCHEDULE (To be defined for each project) |
|
|
|
|
|
|
||
In January 2000, the PingER data gathering tools are deployed at 28 sites in 15 countries, and several more sites are expected to join in Q1 2000. A total of 593 remote nodes at 424 sites in 72 countries are probed by the monitoring sites, providing performance metrics on 2138 end-to-end pairs. PingER is thought to be the largest network performance monitoring project in existence. As with so many aspects of modern computing and networking, the needs of the HEP and ESnet communities continues to push the envelope, and the PingER tools are an important part in measuring the success.
Select and deploy an extended set of Beacon sites to represent the expanded areas covered by the measurements. The current set of about 56 sites was selected when we were monitoring about 30 countries and 1200 pairs. Both these numbers are more than doubled today and continue to expand with new requirements. The concept and requirements for Beacon sites are documented in http://www-iepm.slac.stanford.edu/pinger/beacon.html (PingER Beacon Sites), and briefly are a selected subset of all the sites, that are monitored by all measurement sites.
In co-operation with HEPNRC, SLAC will continue to develop and deploy the timeping program and include the new concept of directives where the host monitoring site can have greater control over the parameters by specifying the scheduling mechanism and frequency at which to send probes, the size of the probes, the type of probes to send, and the way the results are logged. The ability to customize the frequency and size of the probes will allow finer detailed monitoring of high performance links, and lower impact on poorly provisioned links. Also more detailed logging of results will allow more statistics and new metrics to be developed. In addition the data gathering will be amended to use protocols other than ICMP ping. For example, the version of ping developed at NIKHEF can be used to specify the Per Hop Behaviour (PHB) for a network using Differentiated Services. There are also TCP-based ping-like tools such as sting [3] and SYNACK which can be called by PingER instead of ping. These tools will be particularly useful for the study to compare reported performance to detect evidence of rate limiting. Also use of the ULM format for recording results will be explored, and the tools available to analyse ULM formatted data will be evaluated. Traceroute studies will be expanded and data will be gathered routinely to provide historical routing information. As before, all raw and processed data and results will be made public via the web to enable researchers and networkers to perform their own analyses and acclerate progress and understanding in this important field.
Development of the analysis tools will involve a big drive to take more advantage of databases for the storage and retrieval of data. Tools using perl and java database connectivity will be developed. Standard SQL will be used to make the code as platform-independent as possible. The guthrie program which manages the details of the large number of nodes involved in the PingER project, and provides smooth scaling to handle thousands of pairs of sites, will be enhanced to provide a GUI front end and a version using the Java runtime environemt (JRE) will be developed. Existing tools to automatically modify the list of nodes (see http://www-iepm.slac.stanford.edu/monitoring/remote_sites.html ) and produce spreadsheet ready versions of group affiliations will be extended.
There are a large number of analysis projects under way, including further analysis and new tools. SLAC is working on methods to detect ICMP rate limiting, where ping probes are limited for security or bandwidth reasons and may mistakenly indicate poorer network performance than is the case. In addition methods to detect links employing other non-standard or advanced techniques such as load balancing will be developed to further understand accurate performance monitoring. Tools such as TTCP and SmartBit will be utilized to further understand how different protocols work and validate the PingER methodology, especially as it relates to predicting TCP throughput. A new project involving passive monitoring using the OC3MON box and the Coral-Reef [4] is just beginning and work will be done to compare performance with active measurement tools. SLAC is taking a leading role in monitoring performance for the 6bone/6REN IPv6 network. Currently there is 1 monitoring site at SLAC, but we expect to deploy the IPv6 version of PingER at two new sites; at the 6-TAP in Chicago and at the CERNet NOC in China in Q1 2000. SLAC is also working on detailed analysis of connectivity to East Europe and South America for the ICFA SCIC and ESnet-International groups. Also Internet2-International and NATO are interested in our measurement and analysis of performance to remote and poorly provisioned regions.
The project has continually caused suprises and questions had to be addressed that had not been forseen, sometimes resulting in a whole new line of enquiry and research. Also, some initial trials have failed to provide the necessary information. One such area of initial trials is that of visualisation. The project continues to examine tools and renewed effort to collaborate with developers to incorporate features that can be exploited by the unique nature of the Energy-Labs' requirements will be undertaken. The existing WWW pages of tables and graphs will be complemented with new graphing techniques and more data analysis tools will be reviewed and tool-specific formats may be included in the table for power users. A new weather-map type front end will be explored along with already under review tools such as cichild, otter, and trunks-map. Another aspect of the project that will be reworked in collaboration with the XIWT is the ability to use PingER for anomaly detection and near real-time trouble-shooting, although it is still not envisioned that these tools will be used as a front line warning mechanism for network operations centers.
SLAC continues to actively work with The Cross Industry Working Team and has forged links with other commercial interests including the NetPredict start-up.
Those involved in the IEPM effort have a long history of Networking and Network monitoring. In addition the IEPM effort so far has established many new alliances and connections. SLAC has deployed machines from the AMP, Surveyor, RIPE and NIMI network performance projects. In addition collaborations with UCLA and CEEsat/NATO are being developed. SLAC has numerous publications and has been invited to participate in many workshops and network activities and given many talks throughout the world.
And coninued gathering and analysis of monitoring data.
In addition,
Furthermore, we have been invited to take part in a staggering number of conferences and workshops this year. We will present papers and/or give talks at;
Revised 10 January 2000
URL:
http://www-iepm.slac.stanford.edu/about/fwp/fwp-00.html
Comments to
iepm-l@slac.stanford.edu