The perfSONAR Network Monitoring Framework - PowerPoint PPT Presentation

1 / 18
About This Presentation
Title:

The perfSONAR Network Monitoring Framework

Description:

over 40 servers across Europe. IP circuit utilisation (optionally: input errors, ... To be able to understand at a glance what's going on (interpretation) ... – PowerPoint PPT presentation

Number of Views:90
Avg rating:3.0/5.0
Slides: 19
Provided by: Robe350
Category:

less

Transcript and Presenter's Notes

Title: The perfSONAR Network Monitoring Framework


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/perf
    sonar_online_training_0.2/player.html

8
perfsonarUI
9
(No Transcript)
10
(No Transcript)
11
(No Transcript)
12
(No Transcript)
13
How to Access the Web-services
  • perfsonarUI
  • The list of web-services - http//perfsonar.acad.b
    g/
  • 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.it8080/geant2-j
    ava-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

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

15
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

16
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

17
Understanding the needs of the operators
  • NOCs react mostly on alarms triggered by
    equipment or service being up/down.
  • They dont often encounter performance issues
  • Either there arent, or the users got used to
    have degraded performances from time to time and
    dont complain about them.
  • If the NOCs are given tools, they need
  • To be told by an alarm when something goes bad
    (and they shouldnt be overwhelmed by alarms)
  • To be able to understand at a glance whats 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.

18
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.
Write a Comment
User Comments (0)
About PowerShow.com