Upload
conrad-benson
View
217
Download
4
Embed Size (px)
Citation preview
Connect. Communicate. Collaborate
perfSONAR and Wavelengths Monitoring
LHC meeting, Cambridge, 16 of June 2006
Matthias Hamm - DFN
Nicolas Simar - DANTE
Connect. Communicate. CollaborateAgenda
• Use case• perfSONAR• Providing the data• Visualisation• Achievements• Next Step• perfSONAR L3 infos
Connect. Communicate. CollaborateModel for E2E Links
GEANT2
NREN1 NREN2 NREN3E1 E3
E2
E2E Link 1
E2E Link 2E2E Link 3
• 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
Connect. Communicate. Collaborate
Organisational Building Blocks for E2E operations
TNOC-1
E2ECUE2E Monitoring System
CMDB
Access to common data and tools
Trigger coordination activity (according to Workflow Def.)
GEANT Network
GEANT Network
TTS TNOC-2TTS
TNOC-NTTS
NMS
NRENNetwork
NRENNetwork
NMS
NREN Network
NREN Network
NMSProvide mon. data
TTS
Connect. Communicate. CollaborateWorkflows for E2ECU (1)
• Workflows define the interaction between Actors• Actors: Authorized Users (no End Users), e.g. LHC GGUS;
E2ECU; NREN TNOCs• Mostly human/organisational communication• Full life cycle of E2E links is covered• For now, only Workflows for technical aspects are defined• Proposal given by JRA4/WI3 => agreement has to be
reached
Connect. Communicate. Collaborate
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
Connect. Communicate. Collaborate
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 link (CBF) status provided by
NRENs• E2E link status: aggregation of NREN and ID links
Connect. Communicate. Collaborate
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
Connect. Communicate. CollaborateAgenda
• Use case• perfSONAR• Providing the data• Visualisation• Achievements• Next Step• perfSONAR L3 infos
Connect. Communicate. CollaborateperfSONAR philosophy
• Available– People can find it (Discovery)– “Community of trust” allows access across
administrative domain boundaries (AA)• Ubiquitous
– Widely deployed– Reliable
• Open source• Can be modified and adopted by a group.
Connect. Communicate. CollaborateperfSONAR philosophy
We take care of the data movement• Build perfSONAR middleware• AA Service, Lookup Service (LS), Measurement Archives services
(MA), Measurement Point services (MP).• Allows diversity on the measurement layer and on the visualization
layer.– You can mix and match them.
• ISTF, DFN, RNP, EGEE have built some visualisation tools. • Data from Abilene, ESnet and GEANT2 can be accessed the same
way.
Connect. Communicate. CollaborateperfSONAR philosophy
Decouple the Problem Space:• Analysis and Visualization• Performance Data Sharing• Performance Data Generation
Analysis & Visualization
Measurement Infrastructure
Performance Tools Performance
Tools
Analysis & Visualization
Measurement Infrastructure
API
API
Connect. Communicate. CollaborateAgenda
• Use case• perfSONAR• Providing the data• Visualisation• Achievements• Next Step• perfSONAR L3 infos
Connect. Communicate. Collaborate
Data Exchange for E2E Monitoring – Archive scenario
• NREN in charge of retrieving the data from the NMS/DB, to analyse them and pass the information to a java class.
• JRA1 to produce – the “mySQL MA service”
code – maintain it.– script to write into the DB
• JRA4 in charge of the E2E NOC visualisation.
Connect. Communicate. Collaborate
Connect. Communicate. CollaborateOther Data Exchange
• 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
Connect. Communicate. Collaborate
Data Exchange for E2E Monitoring – proxy Scenario
• 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
Connect. Communicate. CollaborateAgenda
• Use case• perfSONAR• Providing the data• Visualisation• Achievements• Next Step• perfSONAR L3 infos
Scenario for Demo
DFNSURFnet
DANTE
SWITCH
SURFnet-SARA
End Point Demarc. Point
SURFnet-MUE
DFN-MUE DFN-LRZ
DANTE-AMS
DANTE-GEN
SWITCH-GEN
E2E Link for DEISA
E2E Link for LHC
Domain Link ID Link ID-Link Partial Info (shared mon.)
Connect. Communicate. CollaborateAgenda
• Use case• perfSONAR• Providing the data• Visualisation• Achievements• Next Step• perfSONAR L3 infos
Connect. Communicate. CollaborateAchievements
• 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.
Connect. Communicate. CollaborateAgenda
• Use case• perfSONAR• Providing the data• Visualisation• Achievements• Next Step• perfSONAR L3 infos
Connect. Communicate. CollaborateNext 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, )
Connect. Communicate. CollaborateAgenda
• Use case• perfSONAR• Providing the data• Visualisation• Achievements• Next Step• perfSONAR L3 infos
Connect. Communicate. CollaborateThe Team
© gms’ photos, Flickr
• Arnes
• Belnet
• Carnet
• Cesnet
• DANTE
• DFN
• FCCN
• GRNet
• ISTF
• PSNC
• Nordunet (Uninett)
• Renater
• RedIRIS
• Surfnet
• SWITCH
• ESnet
• Internet2
• UoD
• RNP
Connect. Communicate. CollaborateJRA1 – perfSONAR works– Main Services
• Lookup Service (LS)• L3 Topology Service (TopS)• AA service
– Services Common Features• Push interface• Service registration• Schema
– Measurement Archive (MA)• Relational Database (RDB)
MA • Round Robin Database
(RRD) MA• Hades (delay) MA• RIPE TTM MA• BWCTL MA• L1-L2 status MA
– Measurement Points• SSH/Telnet Measurement
Point (MP)• SNMP MP• BWCTL MP (TCP
throughput)• CLI MP• Hades MP
– Visualisation• perfsonarUI• CNM• VisualperfSONAR• NEMO
– Metric Concatenation Framework (MCF)
– Collaboration with Internet2, ESnet and RNP.
Connect. Communicate. CollaborateRelevant services
• Command Line MP (Measurement Point) - Java– Uses abstraction to easily integrate *most* unix
command-line tools– Allow to trigger on-demand tests between two remote
hosts– Currently integrated cl-tools: bwctl, owamp, traceroute,
ping (ntptime soon)– http://www.perfsonar.net/jra1-wiki/index.php/
CLMPService• BWCTL MP - Perl• HadesMA (Perl)
– Latency data (DFN-IPPM data)