GANT Performance Monitoring

1
GÉANT Performance Monitoring
TPM Workshop 2004 , Geneva (CH), 17/03/04
Nicolas Simar, Network Engineer DANTE
2
Overview

• Performance Monitoring Introduction
• GN1 work
• GN2 plans
• Inter-operability issues

3
Goal

• Make network management and performance
  information from different domains available
  through a well specified interface to various
  authorised user communities
• GÉANT, NRENs, Regional networks NOCs
• PERT - Performance Enhancement Response Team
• high data volume transfer users (as GRID)
• end-user who would like to see or understand the
  e-2-e behaviour of RD networks.

4
Framework Layers
5
Overview

• Performance Monitoring Introduction
• GN1 work
• GN2 plans
• Inter-operability issues

6
GN1 Objectives

• Distributed Monitoring System
• Provide Edge to Edge Monitoring
• Respect Administrative Boundaries
• Standardized Interfaces
• NMWG Request and Reply Formats
• Extensibility
• Network Characteristics
• Measurement Points (MPs)

7
Domain Tool Architecture
8
Domain Tool Components

• Communication Module
• Interfacing (End Users -under development - and
  Other Domains -planned for September 2004-)
• Authentication and Authorization (nothing fancy
  during GN1)
• Analyser
• Targeting requests to the appropriate entity -
  send request to the appropriate domain (September
  2004)
• Concatenating data from multiple domains
  (September 2004)
• PathFinder
• Match requests with Measurement Points and
  Domains (September 2004)

9
Domain Tool Components

• Data Provider
• Gather data from Measurement Points (OWD, jitter
  RIPE TTM)
• Provide Data Storage if necessary (done for OWD
  and jitter)
• Capability to provide aggregated as well as
  unprocessed data (max, min, avg, 95 percentile)

10
Where do we stand?

• Capability to gather data from RIPE TTM Boxes
• Provide One Way Delay and Jitter Information
• Capability to provide raw and processed data
  (avg., min, max and 95 percentile)
• Database to store data
• Schema capable of storing multiple
  characteristics and different types of data(raw
  or processed)
• Can store test description
• Based on NMWG methodology section specification
• SOAP Server
• Request Format based on NMWG request specification

11
Overview

• Performance Monitoring Introduction
• GN1 work
• GN2 plans
• Inter-operability issues

12
GN2 JRA1 - Performance Monitoring and Management

• 3 years project, starting in September 2004 (15
  Europeans NRENs involved and DANTE).
• Development of a performance Monitoring
  infrastructure operating across multiple domains
• User can access data in a uniform way and start
  on-demand tests.

13
GN2 Framework Layers
14
Goals - target Users

• Make network management and performance
  information from different domains available to
  various authorised user communities
• GÉANT, NRENs, Regional networks NOCs
• PERT - Performance Enhancement Response Team
• high data volume transfer users (as GRID)
• end-user who would like to see or understand the
  E2E behaviour of RD networks.

15
User Interface

• A User Interface retrieves data from different
  domains and tailors the data representation to a
  specific group of user.
• Targets NOC, PERT and generic end-user.
• Topology based view
• SLA verification

16
Domain Controller

• Ensure that different monitoring agents deployed
  in the various domains can inter-operate and be
  queried in the same way by User Interface
  instances independently of their localisation.
• High level functionality provide the user
  interface, AA, Resource discovery (pathfinder),
  negotiate test, interface with other
  domain/framework

17
Measurement Points and Metric

• Activity will focus in five areas
• One-way delay, IPDV and traceroute
• Available Bandwidth (IP for sure, TCP/UDP less
  sure)
• Flow Based Traffic Measurement
• Passive Monitoring
• Network Equipment information
• Quite IP-centric.

18
Timescale
19
Timescale

• Requ. Requirements, state-of-the art,
  evaluation of tools and user interfaces
• Metric Def Metric definition, data aggregation,
  multi-domain concatenation
• General framework design (SD-MD) modules
  definition, information flow and interfaces
  definitions (4)
• Implementation (SD-MD) 5 type of measurement
  points, 4 data consumers and the framework

20
Starting Point

• Starts from GN1 Performance Monitoring framework
  (data retrieval, storage and export using a well
  define interface) and take into account other
  experiences.
• Uses NRENs experience in tool development.
• Need to take into account the variety of tools
  and metric existing across the NRENs.

21
Overview

• Performance Monitoring Introduction
• GN1 work
• GN2 plans
• Inter-operability issues

22
Measurement Infrastructure Federation

• Why a Federation?
• Multiple measurement frameworks in existence and
  under development (piPEs, NLANR Advisor, NLANR
  AMP, etc.).
• No static best practice measurement framework
  is likely to emerge, given academics being
  academics.
• Future measurement frameworks can build on
  shoulders of current efforts, not feet.
• Performance Measurement Architecture Workshop
  (NSF Grant ANI-0314723)

23
Measurement Infrastructure Federation Interfaces
24
Measurement Infrastructure Federation Requirements

• Agreement on Characteristic Names
• Access and Authentication
• Discovery (Measurement Frameworks, Domains,
  Nodes, Databases)
• Test/Data Request Schema
• Result Report Schema
• Inter-Framework Tests
• Resource Allocation Broker for Tools
• Concatenation of Homogeneous Characteristics
  Results Gathered by Heterogeneous Tools

25
GGF Network Measurement Working Group

• Hierarchy of Network Performance Characteristics
• Request Schema Requirements and Sample
  Implementation
• Report Schema Requirements and Sample
  Implementation

26
Establishing a Performance Measurement Mesh

• Issues include
• Scheduling in the presence of scarce resources
• Making the tool bidirectional
• Adding security
• Ensuring correct source/target pairs
• Data collection / mining / analysis / display
• Example
• BWCTL for Iperf plus prototype PMD

27
Open Research Issues

• Access and Authentication
• Discovery of Measurement Nodes (Super-Traceroute
  )
• Discovery of Measurement Databases
• Inter-framework Testing
• Compilation of results on partial paths
• Normalization of identical characteristics
  gathered by heterogenous tools

28
Conclusions

• We can do partial path analysis, although making
  sense of the results is still a big issue.
• We can speak the same measurement language,
  although its still evolving.
• We are working together in growing numbers, but
  we need critical mass (become de facto standard).
• We need to be able to find each other.
• We need to be able to verify each others
  identity.