2004.8.26 Jaehwa Lee/KOREN jhlee@noc.kr.apan

1. The 3rd InternationalHEP DataGrid Workshop KOREN E2E Performance: Network Engineering Activity 2004.8.26 Jaehwa Lee/KORENjhlee@noc.kr.apan.net Presented by Joonbok Lee/KAIST

2. Contents • Goal • Activity 2.1 etop Visualization 2.2 Network WeatherMap 2.3 Traffic Engineering System • Concluding Remark

3. 1. Goal • End-to-End Performance from the Network’s point of view. • End-to-End Performance Monitoring • Traffic Monitoring and Traffic Engineering

4. Goal • Activity • 2.1 etop Visualization • 2.2 Network WeatherMap • 2.3 Traffic Engineering System • Concluding Remark

5. etop: Edge-to-edge performance system • System Architecture

6. Metrics and Tools *owamp: implementation of the OWAMP protocol that is currently going through the standardization process within IETF. http://www.internet2.edu/~shalunov/ippm/draft-ietf-ippm-owdp-08.txt http://e2epi.internet2.edu/owamp/

7. Iperf UDP Iperf UDP Iperf UDP Iperf UDP Iperf UDP Iperf TCP Iperf TCP Iperf TCP Iperf TCP Iperf TCP Measurement and Data collecting • 6 machines were deployed. • Each machine send probe packets by using ping, iperf and owamp They report result to main DB server in Daejeon. CRON CRON CRON CRON CRON

8. Data Presentation (TCP Throughput)

9. Data Presentation (TCP Throughput)

10. Data Presentation (UDP Throughput)

11. Data Presentation (UDP Throughput)

12. Data Presentation (Jitter) Jitter(ms)

13. Data Presentation (RTT)

14. Goal • Activity • 2.1 etop Visualization • 2.2 Network WeatherMap • 2.3 Traffic Engineering System • Concluding Remark

15. 2.2 Network WeatherMap • To show current link utilization. • Netmap v1.3 • http://aetos.it.teithe.gr/~v13/netmap/ • based on existing images (only support PNG format) • It uses SNMP to collect data from other devices • Multiple Network WeatherMaps • Multiple MRTG Style Graph • {Host, CPU, Memory} Information

16. KOREN Netmap Deployment

17. UI – Devices List

18. UI – Traffic data

19. Goal • Activity • 2.1 etop Visualization • 2.2 Network WeatherMap • 2.3 Traffic Engineering System • Concluding Remark

20. 2.3 Traffic Engineering System • Background • users and traffic have grown on the Internet • both users and network managers need to have an understanding of the network performance • Traffic Engineering System • A software system to manage and measure various values which indicate network performance • To optimize the utilization of existing network resources for load balance and failure recovery • To manage the network of KOREN

21. TES Architecture TES Server Web Server User Manager Server Process Data Collection Module Analysis Module DB SNMP Diagnosis Module - Traffic Engineering System Architecture-

22. Internal TES Architecture - Traffic Engineering System Architecture-

23. Data Collection Module • Collect traffic information about each Node of the KOREN • Using active measurement data, SNMP MIB, flow information, and, … Data Collection Module

24. Analysis Module • Calculate the performance measurement metric with the collected data • Insert parsed measurement metric into database • Reporting to diagnosis module or network manager Throughput Utilization Link error Available bandwidth DB Data Collection Module Diagnosis Module Analysis Module Threshold < Load Threshold > Load Network Manager

25. Diagnosis Module • For the detection of abnormal situations via the observation of the network • The various conditions • C1: Outgoing overload : concentrated traffics from a node • C2: Incoming overload : concentrated traffics towards a node • C3: multicast/broadcast : The traffic which is not notified to the network manager • C4: Link error : abnormal physical error • Reporting a diagnosis result to network manager

26. 3. Concluding Remarks • KESG (KOREN Engineering Study Group) are working for • Those systems will be used by end users as well as network managers. • Contact Information: • jhlee@noc.kr.apan.net • Etop and Network weathermap (prototype) • http://indigo.cheju.ac.kr/~indigo/etop/www/