Connect. Communicate. Collaborate

Towards Multi-domain Monitoring for the Research Networks

Nicolas Simar, Dante

TNC 2005, Poznan, June 2005

Connect. Communicate. Collaborate• Motivations• Observations

– e2e troubleshooting is not straightforward• End system vs network based problem• Don’t want to spend too much time when the problem isn't on your

network– IP e2e doesn’t stop at the boundaries of a domain

• Monitoring is done “locally” to your network• Examples: Video-conference, high data rate transfer.• Network researchers needs network information.• The end-users currently don’t have any or very little view about the

networks. • Visualisation currently dictated either by the tool of the data provider

• Facilitate the retrieval of monitoring information from multiple administrative domains.

Connect. Communicate. Collaborate• Network Transparency Today

LAN LAN

User A

NREN

NREN

GEANT GEANT

NREN

NREN

LAN LAN

User B

?

? ?

Information availableonly by the local managers

? ?

Connect. Communicate. Collaborate• Solution Proposed

• Design and Implement a framework– Act as an abstraction layer: define “standard” Interfaces to request

data/test, retrieve information.– Takes care of the difficult bits: service discovery, AA– Allow each network to edit it’s own resources access policy.

• Integrate a set of tools within the framework. Enhance the tools with new capabilities.

• Visualisation decoupled from the data storage, capture and from the tools.

• Build useful and innovative visualisation tools to demonstrate the capabilities and the usability

Connect. Communicate. Collaborate• Solution Proposed

Connect. Communicate. Collaborate• Goal: Network Transparency

LAN LAN

User A

NREN

NREN

GEANT GEANT

NREN

NREN

LAN LAN

User B

Information available (credential based)

Last Mile

Connect. Communicate. Collaborate• Solution Proposed

• Measurements targeted based on requirements analyse– Delay: OWD, IPDV, OWPL, RTT, traceroute– Bandwidth: Link utilisation, TCP achievable bandwidth– Router information: interface drops, interface errors

• Additional techniques – Netflow– Packet capture

Connect. Communicate. Collaborate• Services

• Measurement Point Service (MP)• Measurement Archive Service (MA)• Look-up Service (LS)• Authentication Service (AS)• Transformation Service (TS)• Topology Service (ToS)• Resource Protector Service (RP)

Connect. Communicate. Collaborate

Here is who I am, I’d like to access MA B

Where Link utilisation along - Path a,b,c,d,e,f?a,b,c: Network A – LS A, c,d,e,f : Network B, MA B, RA B

Client

Network A Network B

LS A LS BMA A MA B

RA A RA B

a b

c de f

Where Link utilisation along - Path a,b,c?a,b,c : Network A, MA A, RA A Token MBHere is who I am, I’d like to access MA A

Get link utilisation c,d,e,fHere you go

Token MA

Get Link utilisation a,b,cHere you go

Useful graph

Connect. Communicate. Collaborate• Services (base)

• Measurement Point Service– Publishes measurement data to one or several consumer– Capability of starting a new tests– Initiates active measurements, queries passive measurement

devices or packet capture – Integrated within the tools or wrapper around legacy tools

• Measurement Archive Service– Storage of measurement data (over long period of time)– A MP or a TS publish data to the MA

Connect. Communicate. Collaborate• Services (base)

• Lookup Service– Allows the client to discover the existing services and other LS

services.– Dynamic: services registration themselves to the LS and mention

their capabilities, they can also leave or be removed if a service gets down.

• Authentication Service (GN2-JRA5)– Authentication functionality for the framework– Users can have several role, the authorisation is done based on the

user role.– Trust relationship between networks

Connect. Communicate. Collaborate• Services

• Transformation Service– Transform the data (aggregation, concatenation, correlation,

translation, etc).• Topology Service

– Make the network topology information available to the framework.– Find the closest MP, provide topology information for visualisation

tools• Resource protector

– Arbitrate the consumption of limited resources.

Connect. Communicate. Collaborate• Current Status

• Service Oriented Architecture– Web-services, Axis Tomcat– Interfaces – follow the GGF NM-WG

• Prototype (for end of August)– To check that General Framework Design is working and to ensure the

connections between services are working. – To investigate and implementing technology for exchanging information

between services – Provide interesting data from existing database. – Simple version of the base services for link utilisation. CNM visualisation

tool to retrieve and show link capacity and link utilisation.– Partners: Abilene, ESnet, GÉANT, GRnet, PSNC, Uninett, …

Connect. Communicate. Collaborate• Current Status

• JRA1 – enhancement of the DFN IPPM– Other chosen tools: RRD tools, BWCTL– Pending: netflow and packet capture– Visualisation: integration of CNM and Nemo

• Next steps:– Integration of IPPM– On-demand test client– Path based performance visualisation client

Connect. Communicate. Collaborate• Solution Proposed

• The design and the implementation of the framework: jointly done between GN2-JRA1 and Internet2 PAT– Active contribution from ESnet

– Metcalf’s Law - our version: The value of a performance measurement framework scales with the square of the deployment footprint

Connect. Communicate. Collaborate• Information

• GN2-JRA1 website http://www.geant2.net/

>Research > Performance Measurement• Mailing list archives

– Prototype - http://mail.geant2.net/gn2-jra1-prototype/– RFE - http://mail.geant2.net/gn2-jra1-rfe/

• DFN IPPM - http://www-win.rrze.uni-erlangen.de/ippm/• DFN CNM – http://www.cnm.dfn.de/• Uinett NEMO - http://software.uninett.no/