1 / 9

Supratik Bhattacharyya Sprint

Network Measurement and Monitoring: A Sprint Perspective <draft-bhattacharyya-monitoring-sprint-01>. Supratik Bhattacharyya Sprint. Outline. Background A two-level monitoring infrastructure Implementation issues. Monitoring benefits topology design capacity planning and forecasting

ozzie
Download Presentation

Supratik Bhattacharyya Sprint

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. Network Measurement and Monitoring:A Sprint Perspective <draft-bhattacharyya-monitoring-sprint-01> Supratik Bhattacharyya Sprint

  2. Outline • Background • A two-level monitoring infrastructure • Implementation issues

  3. Monitoring benefits topology design capacity planning and forecasting traffic engineering fault diagnosis customer-driven activities … Types of data needed packet-level flow-level path-level routing network-element specific Different time-scales Background

  4. ISPs need a two-tier infrastructure • Continuous collection • small set of metrics • longer time-scales • network-wide • On-demand collection • fine-grained information • short time-scales • selected points

  5. Our approach to Continuous Monitoring • Near-term • special-purpose systems to tap link (CMon) • summarize packet headers into flow-level data • periodically export select set of metrics • retain packet headers for past 24 hours (or more) • Long-term • migrate functionality into routers

  6. Implementation issues for CMon systems • Per-packet processing at line speeds • sampling is essential for higher speeds! • Single system for many tasks • Up-to-date routing information • Explosion in flow-table size • Information Export…

  7. Information export: design choices • Key metrics only • low export bandwidth but more processing on CMon • Per-flow info • less processing on CMon but high export bandwidth • O(Mbps) for OC-48 links • Different trade-offs possible between on-board computation and export bandwidth

  8. Relationship with IPFIX • Our work fits well within IPFIX architecture • flow definition, metering, data and export model, reliable and secure export, etc. • need a sophisticated control protocol • Our goal • build system specific to operators’ needs • feedback to IPFIX on lessons learned and new design requirements

  9. Further information: http://ipmon.sprint.com email ipmon@sprintlabs.com

More Related