connect communicate collaborate perfSONAR MDM News Domenico Vicinanza DANTE (UK)

connect communicate collaborate Agenda perfSONAR Service Pilot in the GEANT service AREA perfSONAR User Panel New simplified perfSONAR UI New web-based perfSONAR UI (coming soon) Interoperability news New measurement points added in ESnet and Internet2 Interoperable, transatlantic bandwidth measurement example with perfSONAR UI

connect communicate collaborate perfSONAR Service Pilot perfSONAR MDM is currently in a service pilot phase GEANT and 8 NRENs implementing the perfSONAR MDM service for their NOC/PERT engineers. More NRENs will be invited to join the pilot

connect communicate collaborate Actual committed deployers Monitoring with perfSONAR MDM 4

connect communicate collaborate perfSONAR MDM User Panel A user panel has been established: To ensure perfSONAR MDM is developed to meet user requirements To represent the views, needs and experiences of the different types of perfSONAR users Representative group of NREN NOC and PERT network engineers Strong two-way communication between the service development team the user community. Regular phone/VC meetings to discuss the quality of the service First face-to-face meeting organised during the 2011 TNC in Prague Contact:

connect communicate collaborate Simplified user interface Two versions downloadable from Just three tabs: Interfaces statistics tab (RRD-MA) Circuit tab (One-way delay, Jitter, Packet loss, traceroute) BWCTL tab )

connect communicate collaborate perfSONAR UI interface for NOC/PERT engineers Three simple tabs

connect communicate collaborate perfSONAR UI interface for developers and deployers The whole set of functionalities

connect communicate collaborate RRD-MA Purpose: Monitor link utilisation, input errors, packet drops Provide access to historical measurements Strategy: Query router interfaces using SNMP from a perfSONAR server Store data into RRD files – made accessible through web-service

connect communicate collaborate RRD-MA User Interface (java stand-alone version)

connect communicate collaborate RRD-MA User Interface (web version)

connect communicate collaborate RRD-MA Path analysis using traceroute (web interface)

connect communicate collaborate HADES-MA/MP (OWD, jitter, packet loss, traceroute)| Purpose: Monitor OWD, jitter, packet loss, traceroute variations – Regularly scheduled – On demand (to be implemented) Provide access to historical measurements Strategy: Sending 9 packets every minute from pS server (Meas. Point) – Measure OWD, jitter, packet loss and tracking IP route Store data into perfSONAR SQL-MA archive – made accessible through web-service

connect communicate collaborate HADES User Interface (java stand-alone version)

connect communicate collaborate HADES User Interface – OWD, jitter packet loss (web version)

connect communicate collaborate HADES User Interface – route comparison (web version) Simple route comparison

connect communicate collaborate BWCTL-MP/MA (Achievable bandwidth) Purpose: Measure the achievable bandwidth between two MPs – Regularly scheduled and on demand Provide access to historical measurements Strategy: Run bandwidth test between MPs using a web-service interface to BWCTL Display data with graph and store into perfSONAR SQL- MA archive – made accessible through web-service

connect communicate collaborate BWCTL-MP/MA User Interface (java stand-alone version)

connect communicate collaborate BWCTL-MP User Interface (web interface)

connect communicate collaborate BWCTL-MA User Interface (web interface)

connect communicate collaborate Interoperability with North America 43 measurement points in the GÉANT service area 8 measurement points in ESnet 9 measurement points in Internet2 GEANT ESnet Internet2

connect communicate collaborate Example: From Tromsoe (Uninett) … Running perfSONAR-MDM

connect communicate collaborate …to Houston (ESnet) Running perfSONAR-PS

connect communicate collaborate Results in just two clicks: Tromsoe - Houston

connect communicate collaborate Example: Washington-Frankfurt

connect communicate collaborate perfSONAR MDM website

connect communicate collaborate perfSONAR Twitter

connect communicate collaborate Conclusions perfSONAR MDM service pilot currently inlcudes 8 NRENs User Panel perfSONAR web UI almost ready for deployment Interoperability – 17 measurement points from Internet2/ESNet in perfSONAR UI New website and twitter Follow perfSONAR at:

connect communicate collaborate Thank you!!

connect communicate collaborate Additional slides for info: Introduction to perfSONAR

connect communicate collaborate perfSONAR MDM in a nutshell perfSONAR MDM is the GÉANT multi-domain monitoring service Collaboratively deployed by GEANT and NRENs Objectives – three use cases from DICE: Network troubleshooting Circuit monitoring (including dynamic circuits/AutoBAHN) SLA verification Strategy: perform network monitoring actions in different network domains make the information available thanks to a common protocol – Cross-domain monitoring capability – Access network performance metrics from across multiple domains network problems and performance bottlenecks can be traced and eliminated quickly proactively identify and prevent problems before service disruption occurs

connect communicate collaborate perfSONAR MDM: accessing network information across several domains perfSONAR is carried out by a consortium of organisations (GÉANT, ESnet, Internet2 and RNP) perfSONAR aims at making it easier to solve end-to-end performance problems on paths crossing several networks. Authorized users can have access to network performance for diagnosis and troubleshooting

connect communicate collaborate perfSONAR as unifying layer across domains Domain 3 Domain 1Domain 2 Domain 4 perfSONAR Services perfSONAR Each domain has its own local monitoring perfSONAR UI (visualization) Scripts/API

connect communicate collaborate The perfSONAR Measurement Strategy User Interface/API perfSONAR Measurement Point Router/Network equipment User Interface/AP perfSONAR Measurement Point Router/Network equipment

connect communicate collaborate perfSONAR is based on OGF Standards perfSONAR philosophy: Open/Modular Multi-Domain (Web Services) Interoperable Integrates: Network measurement tools Network measurement archives Discovery (lookup service) Authentication and authorization Data Manipulation Topology Visualization perfSONAR uses the OGF NM-WG Recommendations (ontology) and Schemata

connect communicate collaborate Additional slides for info: E2EMon

connect communicate collaborate End-to-End link monitoring in perfSONAR across multiple domains Point A PointB Domain A Domain B Domain C Goal: (near) real-time monitoring (link status) of the whole end-to-end Link A-B, when constituent links are crossing multiple domains E2ELink A-B

connect communicate collaborate perfSONAR E2EMon Approach: correlation of domain-based info Point A PointB Domain A Domain B Domain C E2ELink A-B perfSONAR MP or MA perfSONAR MP or MA E2Emon correlator perfSONAR Measurement Point (MP) or Measurement Archive (MA) DomainLink and (partial) ID_Link info E2E link view for users E2ECU operators

connect communicate collaborate How does E2E monitoring work Each domain installs software probes to capture up/down status of their links from network hardware This status info sent to a local perfSONAR Measurement Point Collecting network status info [UP / DOWN only] Historical archive for network status info Checks info and reformats into XML for collection The Correlation Engine then: Queries PerfSONAR Measurement points Concatenates information from constituent links to form End- to-End multi-domain links

connect communicate collaborate E2E Monitoring

connect communicate collaborate Each perfSONAR server can be thoroughly monitored Monitoring the perfSONAR monitoring Infrastructure Based on Nagios+Cacti: 35 Checks per server, covering hardware, software and services Automatic notification, detailed history Detailed, three-layer monitoring to improve reliability: Hardware layer: CPU, MEM, disk space, network interfaces, TCP/UDP traffic, temperature Resource layer: login attempts, Tomcat RRT, eXist RTT, MySQL, NTP Service layer: perfSONAR services availability and performance Additional tools: Syslog server (with MySQL support) security log auditing (with automatic report tools)

connect communicate collaborate Monitoring the monitoring servers: the interfaces (Nagios-Cacti)

connect communicate collaborate Detailed and proved incident management procedures Well defined procedures for Incident Management: Incident Management Third party supplier involved