Network related topics Bartosz Belter Wojbor Bogacki Marcin

Network related topics Bartosz Belter, Wojbor Bogacki, Marcin Garstka, Maciej Głowiak, Radosław Krzywania, Roman Łapacz FABRIC meeting Poznań, 25 September 2006 1

Network related topics in WP 2. 1 • To make the GRID gateway aware of the available transmission resources • To monitor the state of the network and use it as one of the decision criteria for the GRID gateway • To reserve the bandwidth needed for data transmission end secure the Qo. S parameters of the transmission 2

Quality of Service The goal of Quality of Service (Qo. S) in the network is the ability to provide an improved network service by providing dedicated bandwidth with controlled loss, latency and latency variation characteristics. Why Qo. S? • Applications sensitive to delay, delay variation or packet loss • Real time control from remote sites (astronomy, medicine) (synchronous, no packet loss) • Guaranteed capacity. Qo. S parameters: • one-way delay • one-way packet delay variation • capacity • packet loss 3

Tools for bandwidth reservations Two network technologies available: • IP routed transmission over GÉANT 2 and NRENs (limited capacity, wide availability) • Dedicated lightpaths in GÉANT 2 and other networks (unlimited capacity, limited availability) Different tools for bandwidth reservations in the two technologies: • AMPS for Premium IP Service in IP routed networks • Bo. D for optical networks Both tools developed by GN 2 project for implementation in GÉANT and NRENs 4

Premium IP and AMPS • Premium IP service • Premium IP traffic has priority over other traffic (best-effort) • Premium IP traffic gets the best possible Qo. S parameters • The amount of Premium IP traffic on a given link must be limited • Service must be booked in advance • Advance Multi-domain Provisioning System (AMPS) • Federated resource reservation system for Premium IP • Multidomain - an authenticated and authorized client can, via a single request, reserve an end-to-end path across multiple federated domains 5

Advance Multi-domain Provisioning System Features • Service Oriented Architecture • Web Services technology in use: interfaces specified in XML • Services: • Inter-domain Provisioning Service (multi-domain) • Intra-domain Provisioning Service (single-domain) • Network Information System (Layer 3 Topology) / Pathfinder Service • Policy Service • Multi-domain peer-to-peer federated architecture • Domains aware of their neighbours only • Trust relationship established between AMPS neighbours • Transaction Management • One-Phase-Commit 6

• Multidomain Premium IP – current status and plans AMPS version 2. 0 – Operational in GÉANT 2 (mutli-domain ready) • – Premium IP Pilot Service to be ready soon: • ARNES, HEAnet, LITNET, RENATER NRENs’ plans Status Diff. Serv/Qo. S Multi-domain PIP Current 12 - Future (Essential) 4 6 Future (Possible) 5 6 Will follow other NRENs 5 9 No interest 3 Source: 6 TERENA 2005 Compendium 7

Optical networks and Bandwidth on Demand • • Optical transmission is available in part of GÉANT 2 (GÉANT+ service) and in some NRENs User’s transmission directly on optical network (without IP routing) Access interfaces: Gigabit Ethernet, 10 Gigabit Ethernet, SDH Bandwidth up to 10 Gbps for a single connection Advanced reservation needed Bandwidth on Demand (Bo. D) service developed in GÉANT 2 for automatic reservations and provisioning of bandwidth in multiple technologies: • GFP over SDH, L 2 MPLS VPN, Native Ethernet, Premium IP Bo. D service is under development (not available yet but prototype already tested) Bo. D service will allow for a single reservation for multiple domains 8

Bo. D service in a heterogeneous network 9

Network monitoring and measurement - Perf. SONAR • Developed by GN 2 project, Internet 2 (USA), ESnet (USA), RNP (Brasil), University of Delavare • Infrastructure for network performance monitoring, making it easier to solve end-toend performance problems on paths crossing several networks. • Set of services delivering performance measurements in a federated environment. • Well-defined common interface to measurement/monitoring services is a network • Implemented services: ping (round trip time), iperf (throughput), ovamp (one way delay); others under preparation • Data repository for historical data • Measurement points in a network; measurements can be triggered by user/application • First measurements points already implemented in GÉANT 2 10

Implementation example - CLUSTERIX • Polish national research project started at the end of 2003 • To create productive, efficient and secure GRID environment • 12 local clusters connected via national network (dedicated 1 GE links) • PSNC is leading network related task – including active measurement and monitoring • The result – an integrated tool able to track and show the status of the network • Measurement agents controlled by a central manager • Two types of agents – backbone agents (in the network core) and local agents (withing computing clusters) • Five network parameters are collected: packet round-trip time, jitter, loss, packet reordering, packet duplications • Applications have access to the measured values but they do not trigger measurements 11

Conclusions • Our goal – to develop a network module for the GRID gateway – with interfaces to the services which are available in the network • The module will make the GRID gateway aware of the status of the network and will interface the management plane of the network to ensure the needed transmission parameters • Requirements for data transmission must be specified (bandwidth requirements, number of simultaneous transmissions, duration of a single transmission etc. )!!! 12