160 likes | 278 Views
perfSONAR and Wavelengths Monitoring. DICE Meeting – Ottawa – 12 th of July 2006 Matthias Hamm - DFN Nicolas Simar - DANTE. Agenda. Use case Providing the data Visualisation Achievements Next Step. Model for E2E Links. E2E Links are dedicated optical multi-gigabit connections
E N D
perfSONAR and Wavelengths Monitoring DICE Meeting – Ottawa – 12th of July 2006 Matthias Hamm - DFN Nicolas Simar - DANTE
Agenda • Use case • Providing the data • Visualisation • Achievements • Next Step
Model for E2E Links • E2E Links are dedicated optical multi-gigabit connections • Essentially P2P links (circuits) framed as SDH/SONET or Ethernet • Cooperation of several NRENs needed to operate E2E Links • Users need Single Point of Contact (SPOC) • E2E Link Coordination Unit (E2ECU) brings together Users and NRENs GEANT2 E2E Link 1 NREN1 NREN2 NREN3 E1 E3 E2E Link 3 E2E Link 2 E2
Basic Characteristics of E2E Link Monitoring • Status information corresponds to network layer 1 and 2 • Status information is logical abstraction • Multiple technologies and vendors used to provide a e2e service. • No information about physical devices necessary • Domain and Interdomain (ID) link status provided by NRENs • E2E link status: aggregation of NREN and ID links
Technical Building Blocks for E2E operations • E2ECU as Single Point of Contact (SPOC) • 30 NRENs participating • Several hundreds of E2E links expected • Common Tools: • E2E Monitoring System • CMDB • perfSONAR compliant monitoring data exchange • XML registry file schema integrated within the NMWG XML schema
Status Information for E2E Monitoring System • Operational States: • Up – link is available • Degraded – link is up, but has reduced performance • Down – unavailable • Unknown – state is unknown • Administrative States: • NormalOperational • Maintenance • TroubleShooting • UnderRepair • Unknown
Agenda • Use case • Providing the data • Visualisation • Achievements • Next Step
NREN in charge of retrieving the data from the NMS/DB to analyse them and pass the information to a java class. About 700-1000 lines of code for GÉANT – 15 days. JRA1 Provides the “mySQL MA service” code maintains it. Provides the script to write into the DB JRA4 in charge of the E2E NOC visualisation. Data Exchange for E2E Monitoring – Archive scenario Connect. Communicate. Collaborate
Other Data Exchange (for information) • Measurement Point Service for Alcatel NMS • Can currently retrieve SES, UAS, ES, BBE from Alcatel NMS via IOO module • On demand • Reference implementation • Beta version of software available for download • Measurement Point Service for SNMP • SNMP.get • On demand • Beta version of software available for download
JRA4-WI3 part: Retrieve data from NRENs Aggregate states for E2E links E2E link status visualisation (and other) tools NREN part: Retrieve data from NMS/DB Calculate states for links Write data into XML registry file Done in real-time Data Exchange for E2E Monitoring – proxy Scenario
Agenda • Use case • Providing the data • Visualisation • Achievements • Next Step
Scenario E2E Link for DEISA SURFnet DFN SURFnet-MUE SURFnet-SARA DFN-LRZ DFN-MUE E2E Link for LHC DANTE-AMS DANTE-GEN SWITCH DANTE SWITCH-GEN End Point Demarc. Point Domain Link ID Link ID-Link Partial Info (shared mon.)
Agenda • Use case • Providing the data • Visualisation • Achievements • Next Step
Achievements • perfSONAR XML format fixed (GGF NMWG compliant). • Exchange procedure specified • Reference implementation of a MP service ready (DFN – LZR). • Status information provided every 5 min. • Pull interface. • Reference implementation of a MA service ready (DANTE). • Historical status information provided. • Pull interface. • Visualisation prototype implemented.
Agenda • Use case • Providing the data • Visualisation • Achievements • Next Step
Next Steps • Implementation of a graphical Weathermap. • Support NREN in data provisioning (two deployable tools scenarios) • Push interface (end October). • Scheduler (end October). • Historical information. • Authentication/Authorisation (GN2–JRA5)