1 / 19

Performance monitoring

Performance monitoring. TF-NGN meeting, Rome (Italy), 06-02-2003. Nicolas Simar, Network Engineer DANTE. Logical Model. Domain central tool. Logical Model. Inter domain communication. Data exchange. Need to have a standardise way of exchanging data between domain see what IPPM is doing

reginag
Download Presentation

Performance monitoring

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. Performance monitoring TF-NGN meeting, Rome (Italy), 06-02-2003 Nicolas Simar, Network Engineer DANTE

  2. Logical Model Domain central tool

  3. Logical Model

  4. Inter domain communication Data exchange • Need to have a standardise way of exchanging data between domain • see what IPPM is doing • see what e2epi is doing • anybody/anything else? • Requests and message format should be understood by every domain.

  5. Inter domain communication Inter domain measurement • Need to have a standardise way of measuring the metrics, measurement point compatibility • see what IPPM is doing • anybody/anything else? • Need to have a defined packet structure.

  6. Metric definition Singleton - Accuracy - cfr website • OWD - 1ms • OWPL - O(10^-(x+1), 10^-(x-1)) • IPDV - 1ms • Re-ordering • Two definitions at IETF • Interresting to histogram per “level of re-ordering” • traceroute • RTT ? - 1ms • for backward compatibility with existing systems

  7. Metric definition Services monitored • Measurement should be done between two points for ... (depending on service availability - up to each domain) • IPv4 and IPv6 • BE, Premium and LBE

  8. What do can be presented to who? • End user • current metric value • metric history • Planning • same as end-user • should be able to access raw data • NOC • same as planning • should be able to see the packets incoming in real time • should be able to monitor a particular session • should be able to set up a new session

  9. Statistics • Exchange statistics and/or raw data between domains • Which statistics do we want to provide (which ones are the most useful?) • Average, SDR (does it work on any sampling methods) • Average max, average, average min • Absolute max, min • Over which period? • For one given packet size in continuous mode

  10. Statistics • Statistic showed and exchanged between domains on which time scale (1min - 5 min)? • Statistics additivity/concatenation across several domains • Statistics accuracy across several domains • How do we want to sample? • Is there anybody which has already study it? Sampling

  11. Domain central tool Functions descriptions - 1st draft • Communication module • Request “analysor” module • Path finder module • Data “recuperator” module

  12. Domain central tool Functions descriptions - 1st draft • Communication module • with other domains and domain web-interface • check message format validity, authentication, request info to “request analysor” and send the result

  13. Domain central tool Functions descriptions - 1st draft • Request “analysor” module • receive a information request from communication module • check if this data is available in the domain • if yes, ask to the “path finder” module from which Point of measurement (PM) the data should come from. • ask to the “data recuperator” to retrieve data (either in a centralised DB, in a distributed DB or on the PM itself) • send information requested to communication module.

  14. Domain central tool Functions descriptions - 1st draft • Path finder module • receive a information request from communication module • check according to the information received from the request “analysor” module which PMs and which domain ingress-egress are involved on the path and send back this information • module should be linked to a network representation either via a database or to some routing information • some parts of this module are model specific • Quite challenging part :-)

  15. Domain central tool Functions descriptions - 1st draft • Data “recuperator” module • consists of several module to retrieve the data, up to one per type of information having to be retrieved (these modules are domain specific)

  16. Date storage in a domain • Raw data distributed in PM • Central database (to avoid too frequent access to MPs) • Statistics (statistics over which period of time, which statistics) • raw data (database size)

  17. Measurement box wish list • Wish list • by mid March • any contribution/advices/help welcome • metric, parameters, sampling, security, data storage, data accessibility, future evolution, accessibility, price, additional measurements, real time access of packet, 2 NIC (one for measurement, one to access data), scalability, else?

  18. Concept test • Need of at least three consecutive domains having partially implemented MPs(GARR, GÉANT, HEANET, SWITCH) • concept validation • software being build on top of it (DANTE has some resources)

  19. Miscelaneous • new mailing list with history feature (thanks to SWITCH :-) • Contact e2epi to see if both systems can be bridged, Intermon project. • Investigate which NRENs are interested by the concept to get their input • Investigation of graphical representation • Web page: http://www.dante.net/tf-ngn/perfmonit

More Related