* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project
Download The technological landscape of GEANT2
Survey
Document related concepts
Internet protocol suite wikipedia , lookup
Distributed firewall wikipedia , lookup
Computer network wikipedia , lookup
Deep packet inspection wikipedia , lookup
TV Everywhere wikipedia , lookup
Zero-configuration networking wikipedia , lookup
Piggybacking (Internet access) wikipedia , lookup
Net neutrality law wikipedia , lookup
Cracking of wireless networks wikipedia , lookup
Recursive InterNetwork Architecture (RINA) wikipedia , lookup
Network tap wikipedia , lookup
List of wireless community networks by region wikipedia , lookup
Transcript
Connect. Communicate. Collaborate The perfSONAR Network Monitoring Framework Maurizio Molina (on behalf of Nicolas Simar) DANTE COST TMA tech. Seminar Samos, 23rd Sep 2008 The GÉANT Network Connect. Communicate. Collaborate • 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…) The GÉANT Network (IP layer) Connect. Communicate. Collaborate • 20 Juniper routers Pls see www.dante.net • tenths of GBit/s of aggregated traffic • Main accesses and the backbone 10Gbit/s The Services Connect. Communicate. Collaborate • So…. Just a big pipe? No! • Services – Dedicated L1-L2 circuits via multiple technologies – Performance Monitoring services (perfSONAR) NEW! – Support for federation of National AA Infrastructures (eduGAIN) and wireless roaming (eduROAM) – Security Service Very NEW! perfSONAR Connect. Communicate. Collaborate • Infrastructure to monitor multi-domain services • Based on web-services • Collaboration: GÉANT2 (15 partners), Internet2, ESnet, RNP. • http://www.perfsonar.net/ perfSONAR philosophy Connect. Communicate. Collaborate Open access instances Connect. Communicate. Collaborate • 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/jra1wiki/index.php/PerfSONAR_Tools – perfsonarUI self-paced Tutorial • http://cbt.geant2.net/repository/perfsonar_ui/perfsonar_online_training_ 0.2/player.html perfsonarUI Connect. Communicate. Collaborate Connect. Communicate. Collaborate Connect. Communicate. Collaborate Connect. Communicate. Collaborate Connect. Communicate. Collaborate How to Access the Webservices Connect. Communicate. Collaborate • 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-rrdma/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 Support Connect. Communicate. Collaborate • Need help, you want to provide some feedback – [email protected] • Knowledge base – http://kb.perfsonar.eu/ (under population) Next Steps Connect. Communicate. Collaborate • 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 Of Interest Connect. Communicate. Collaborate • But not deployed • Flow Aggregation MA – http://wiki.perfsonar.net/jra1wiki/index.php/Flow_Selection_and_Aggregation_MA • Flow Subscription MP – http://wiki.perfsonar.net/jra1wiki/index.php/Flow_Subscription_MP Understanding the needs of the operators Connect. Communicate. Collaborate • 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. Understanding the needs of the operators Connect. Communicate. Collaborate • 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.