Network Measurement and Monitoring: A Sprint Perspective <draft-bhattacharyya-monitoring-sprint-01> - PowerPoint PPT Presentation

About This Presentation
Title:

Network Measurement and Monitoring: A Sprint Perspective <draft-bhattacharyya-monitoring-sprint-01>

Description:

1. Network Measurement and Monitoring: A Sprint Perspective ... 9. Further information: http://ipmon.sprint.com. email ipmon_at_sprintlabs.com ... – PowerPoint PPT presentation

Number of Views:25
Avg rating:3.0/5.0
Slides: 10
Provided by: timothy82
Learn more at: https://www.ietf.org
Category:

less

Transcript and Presenter's Notes

Title: Network Measurement and Monitoring: A Sprint Perspective <draft-bhattacharyya-monitoring-sprint-01>


1
Network Measurement and MonitoringA Sprint
Perspective ltdraft-bhattacharyya-monitoring-spri
nt-01gt
  • Supratik Bhattacharyya
  • Sprint

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

3
Background
  • 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

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_at_sprintlabs.com
Write a Comment
User Comments (0)
About PowerShow.com