1 / 18

The perfSONAR Network Monitoring Framework

The perfSONAR Network Monitoring Framework. Maurizio Molina (on behalf of Nicolas Simar) DANTE COST TMA tech. Seminar Samos, 23 rd Sep 2008. The GÉANT Network. DANTE operates GÉANT2 Backbone network for National Research and Education Networks in Europe

chico
Télécharger la présentation

The perfSONAR Network Monitoring Framework

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. The perfSONAR Network Monitoring Framework Maurizio Molina (on behalf of Nicolas Simar) DANTE COST TMA tech. Seminar Samos, 23rd Sep 2008

  2. The GÉANT Network • DANTE operates GÉANT2 • Backbone network for National Research and Education Networks in Europe • 30+ NRENs, 2 global connectivity providers (Telia and GCrossing), peerings with other research networks (Abilene, Canarie, Clara, TEIN2, SINET…)

  3. The GÉANT Network (IP layer) • 20 Juniper routers • tenths of GBit/s of aggregated traffic • Main accesses and the backbone 10Gbit/s Pls see www.dante.net

  4. The Services • So…. Just a big pipe? No! • Services • Dedicated L1-L2 circuits via multiple technologies • Performance Monitoring services (perfSONAR) • Support for federation of National AA Infrastructures (eduGAIN) and wireless roaming (eduROAM) • Security Service NEW! Very NEW!

  5. perfSONAR • Infrastructure to monitor multi-domain services • Based on web-services • Collaboration: GÉANT2 (15 partners), Internet2, ESnet, RNP. • http://www.perfsonar.net/

  6. perfSONAR philosophy

  7. Open access instances • OWD, OWPL, traceroute and throughput (TCP) servers • over 40 servers across Europe • IP circuit utilisation (optionally: input errors, output drops) • Deployed in more than 10 networks • Demo GUIs • http://monstera.man.poznan.pl/jra1-wiki/index.php/PerfSONAR_Tools • perfsonarUI self-paced Tutorial • http://cbt.geant2.net/repository/perfsonar_ui/perfsonar_online_training_0.2/player.html

  8. perfsonarUI

  9. How to Access the Web-services • perfsonarUI • The list of web-services - http://perfsonar.acad.bg/ • Click on Service Address, then on Service Status. • If the status is green, then the web-services can be accessed • Service URL: http://srv4.dir.garr.it:8080/geant2-java-rrd-ma/services/MeasurementArchiveService • Web-service Interface Documentation – • Identify the web-service Type in the URL • E.g. http://xxx/geant2-java-rrd-ma /services/xxx • Go to the SVN • http://anonsvn.internet2.edu/svn/perfsonar/trunk/ • Go to the folder of the web-service Type you are looking for • Examples in “Interface Specification.doc “ and the rnc can be found under the “schema” folder

  10. Support • Need help, you want to provide some feedback • perfsonar-user@perfsonar.net • Knowledge base • http://kb.perfsonar.eu/ (under population)

  11. Next Steps • Simple Authorization • Organisation and role based. • Using EduGAIN attributes • Creation of a Multi-Domain Monitoring service across Europe (MDM Service in Pilot phase) • Current target NOCs and PERTs

  12. Of Interest • But not deployed • Flow Aggregation MA • http://wiki.perfsonar.net/jra1-wiki/index.php/Flow_Selection_and_Aggregation_MA • Flow Subscription MP • http://wiki.perfsonar.net/jra1-wiki/index.php/Flow_Subscription_MP

  13. Understanding the needs of the operators • NOCs react mostly on alarms triggered by equipment or service being up/down. • They don’t often encounter performance issues • Either there aren’t, or the users got used to have degraded performances from time to time and don’t complain about them. • If the NOCs are given tools, they need • To be told by an alarm when something goes bad (and they shouldn’t be overwhelmed by alarms) • To be able to understand at a glance what’s going on (interpretation) • To be able to act on some network elements to resolve the issues (otherwise it is useless to them) • Without it, there is little benefits to them.

  14. Understanding the needs of the operators • There is also the need for planning tools reasonably simple to use. • There are three gaps that need to be filled between the operators and the users • “geographical gap”: • network boundaries vs end-to-end • “TCP/IP model gap”: • network operators are up to the IP layer (unless offering additional services running), the users are at the application layer. • “time gap”: • the network operators have 5 minutes average statistics, the packet lifetime is few ms, an application inter-action is around few seconds/minutes.

More Related