1 / 13

TransPAC Measurement Update

TransPAC Measurement Update. John Hicks - jhicks@iu.edu Chris Robb - chrobb@iu.edu James Williams - williams@iu.edu. Rationale for tool development. NSF requires a better accounting of how TransPAC is facilitating international scientific cooperation.

mgarber
Télécharger la présentation

TransPAC Measurement Update

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. TransPAC Measurement Update John Hicks - jhicks@iu.edu Chris Robb - chrobb@iu.edu James Williams - williams@iu.edu

  2. Rationale for tool development NSF requires a better accounting of how TransPAC is facilitating international scientific cooperation. Who is interacting with whom, when and how much???

  3. Tokyo XP - 2000

  4. Chicago XP: The Future • Replacement of Cisco 7505 router with Juniper M20 • cflowd data would still not give an accurate picture of the network traffic characteristics but TransPAC OC3mon does.

  5. TransPAC interface at ST DV Utokyo to UIC Slide courtesy of Linda Winkler - STAR TAP

  6. TransPAC Flow Analysis Tool

  7. Some technical details of our application flow tool. Raw NetFlow data is currently collected by Daniel McRobb’s cflowd. Other collectors will be supported in the future. Data streams are written to disk every 5 minutes. Dave Plonka’s CFlow perl module is used to examine raw cflowd output. Tobi Oetiker’s RRDtool is used to archive and display information. Data buckets are accumulated for known applications. Unknown applications are profiled and tracked.

  8. Flow Analysis Tool Futures Tool development includes interactive application monitoring via the web. Creating support for other data collection mechanisms and types such as OC3mon. One possible additional use is for end-users to monitor and troubleshoot their own application usage. User privacy and anonymity are complex issues and need further thought and broader discussion. This Tool is not ready for primetime! We are presenting a work in progress. But, we are happy to discuss the Tool and how it might fit into your individual situation.

  9. TransPAC Network Monitoring Repository • Links to IU-developed software • Links to I2 working group efforts • Links to national and international efforts

  10. TransPAC Network Application Analysis Repository

  11. Future Plans • Make TransPAC flow analysis tool available • Work more closely with all flow analysis efforts • Organize a flow analysis panel at INET2001, if interest...

  12. Flow Analysis - INET2001 • Rationale for detailed flow analysis • Tools (current and near future) for flow analysis • Legal issues surrounding analysis at this detailed level

  13. For additional information and discussion Indiana University James Williams - williams@iu.edu John Hicks - jhicks@iu.edu Chris Robb - chrobb@iu.edu

More Related