100 likes | 232 Vues
This proposal outlines a comprehensive approach to infrastructure monitoring focused on OWD, IPDV, and OWPL metrics. The project aims to partner with NRENs to enhance Service Level Agreement (SLA) verification and assess network health across multiple domains. Divided into two phases, the first phase will establish the key metrics to monitor, the necessary hardware and software for accurate data collection, and methodologies for assessing measurement precision. In the second phase, we will expand monitoring to include additional network and user-visible metrics, ensuring a robust framework for performance analysis.
E N D
Monitoring infrastructure • Multidomain monitoring infrastructure • OWD, IPDV, OWPL and traceroute per CoS - else? • SLA verification and service “health” • per link, edge-to-edge, end-to-end • Target: Q3 2003 • We are interested in • working in partnership with NRENs • feedback from community
Monitoring infrastructure • Dedicated boxes for measuring • sessions established between the boxes according to what need to be monitored
Phases • The work is divided in two phases: • the first one focuses on monitoring OWD, IPDV and OWPL. • the second one aims to monitor additional metrics (networks ones and user-visible metrics)
Steps of the first phase • Define which metric have to be monitored and how to monitor them. • Which hardware, which OS and other technical issue + how to evaluate the measurement accuracy(?) • Build a monitoring box or modify an existing one. • Software to collect data, store and present them.
Metrics challenges • OWD • meaningful measurements (from STM-1 to STM-64, ...), amount of traffic to be send (one probe or more?), pattern • measurement accuracy (< 1ms or several ms?) • go for GPS, but not available everywhere • How to test the measurement accuracy? • HW, OS impact on measurement? • How to present the results?
Metrics challenges (cont) • IPDV • how far is it from what the applications ask for? • OWPL • how many packet have to be send per circuit speed? Which pattern to use?
Data storage • RR database? • every packets or min, avg, max? • fileds needed in the packets? • Communication between boxes and with other type of boxes (IETF) • How to represent end-to-end as a succession of edge-to-edges?
Who can commit for some effort? • Who is interested?