Bas Kreukniet, Sr Network Specialist at SURF SARA NL-T1 Expectations, findings, and innovation Geneva Workshop 10 Februari 2014.

Slides:



Advertisements
Similar presentations
Multihoming and Multi-path Routing
Advertisements

Multihoming and Multi-path Routing
Release 5.1, Revision 0 Copyright © 2001, Juniper Networks, Inc. Advanced Juniper Networks Routing Module 9: Static Routes & Routing Table Groups.
KIT – University of the State of Baden-Wuerttemberg and National Research Center of the Helmholtz Association Steinbuch Centre for Computing (SCC)
Logically Centralized Control Class 2. Types of Networks ISP Networks – Entity only owns the switches – Throughput: 100GB-10TB – Heterogeneous devices:
Internetworking II: MPLS, Security, and Traffic Engineering
T1-NREN Luca dell’Agnello CCR, 21-Ottobre The problem Computing for LHC experiments –Multi tier model (MONARC) –LHC computing based on grid –Experiment.
© 2007 Cisco Systems, Inc. All rights reserved.Cisco Public ITE PC v4.0 Chapter 1 1 Addressing the Network – IPv4 Network Fundamentals – Chapter 6.
FNAL Site Perspective on LHCOPN & LHCONE Future Directions Phil DeMar (FNAL) February 10, 2014.
CS540/TE630 Computer Network Architecture Spring 2009 Tu/Th 10:30am-Noon Sue Moon.
BGP. 2 Copyright © 2009 Juniper Networks, Inc. BGP Overview Is an inter-domain routing protocol that communicates prefix reachablility.
Best Practices for ISPs
Swinog-3, 19 September 2001 Fabien Berger, BGP Oscillation …the Internet routing protocol is diverging! Fabien Berger CCIE#6143 IP-Plus.
Trial of the Infinera PXM Guy Roberts, Mian Usman.
CSEE W4140 Networking Laboratory Lecture 4: IP Routing (RIP) Jong Yul Kim
CSEE W4140 Networking Laboratory Lecture 4: IP Routing (RIP) Jong Yul Kim
Inherently Safe Backup Routing with BGP Lixin Gao (U. Mass Amherst) Timothy Griffin (AT&T Research) Jennifer Rexford (AT&T Research)
LHCONE Point2Point Service ‘BGP solution’ From the Netherlands: Freek Dijkstra, Sander Boele, Hans Trompert and Gerben van Malenstein LHCOPN - LHCONE meeting.
© 2009 Cisco Systems, Inc. All rights reserved. ROUTE v1.0—6-1 Connecting an Enterprise Network to an ISP Network Considering the Advantages of Using BGP.
1 Autonomous Systems An autonomous system is a region of the Internet that is administered by a single entity. Examples of autonomous regions are: UVA’s.
CISCO NETWORKING ACADEMY Chabot College ELEC IP Routing Protocol Highlights.
1 Pertemuan 20 Teknik Routing Matakuliah: H0174/Jaringan Komputer Tahun: 2006 Versi: 1/0.
1 Routing Protocols and Configuration Instructor: Te-Lung Liu Program Associate Researcher NCHC, South Region Office.
Objectives: Chapter 5: Network/Internet Layer  How Networks are connected Network/Internet Layer Routed Protocols Routing Protocols Autonomous Systems.
 Network Segments  NICs  Repeaters  Hubs  Bridges  Switches  Routers and Brouters  Gateways 2.
A short introduction to the Worldwide LHC Computing Grid Maarten Litmaath (CERN)
Commercial Peering Service Community Attribute Use in Internet2 CPS Caren Litvanyi lead network engineer peering team Internet2 NOC GigaPoP Geeks BOF January.
Lecture 4: BGP Presentations Lab information H/W update.
Using E2E technology for LHC Apr 3, 2006 HEPiX Spring Meeting 2006
Chapter 9. Implementing Scalability Features in Your Internetwork.
Border Gateway Protocol
Thoughts on Future LHCOPN Some ideas Artur Barczyk, Vancouver, 31/08/09.
Bandwidth-on-Demand evolution Gerben van Malenstein Fall 2011 Internet2 Member Meeting Raleigh, North Carolina, USA – October 3, 2011.
Page 110/27/2015 A router ‘knows’ only of networks attached to it directly – unless you configure a static route or use routing protocols Routing protocols.
Border Gateway Protocol (BGP) W.lilakiatsakun. BGP Basics (1) BGP is the protocol which is used to make core routing decisions on the Internet It involves.
Day11 Devices/LAN/WAN. Network Devices Hub Switches Bridge Router Gateway.
A comparison of overlay routing and multihoming route control Hayoung OH
CCNA 2 Week 7 Distance Vector Routing. Copyright © 2005 University of Bolton Topics Distance Vector Protocol Issues RIP IGRP.
INFN TIER1 (IT-INFN-CNAF) “Concerns from sites” Session LHC OPN/ONE “Networking for WLCG” Workshop CERN, Stefano Zani
Network to and at CERN Getting ready for LHC networking Jean-Michel Jouanigot and Paolo Moroni CERN/IT/CS.
LHC OPEN NETWORK ENVIRONMENT STATUS UPDATE Artur Barczyk/Caltech Tokyo, May 2013 May 14, 2013
Introduction & Vision. Introduction MANTICORE provides a software implementation and tools for providing and managing routers and IP networks as services.
CS 4396 Computer Networks Lab BGP. Inter-AS routing in the Internet: (BGP)
NORDUnet Nordic Infrastructure for Research & Education Workshop Introduction - Finding the Match Lars Fischer LHCONE Workshop CERN, December 2012.
LHC Open Network Environment Architecture Overview and Status Artur Barczyk/Caltech LHCONE meeting Amsterdam, September 26 th,
Internet Protocols. ICMP ICMP – Internet Control Message Protocol Each ICMP message is encapsulated in an IP packet – Treated like any other datagram,
1 Version 3.1 Module 6 Routed & Routing Protocols.
© 2005 Cisco Systems, Inc. All rights reserved. BGP v3.2—5-1 Customer-to-Provider Connectivity with BGP Connecting a Multihomed Customer to a Single Service.
© 2005 Cisco Systems, Inc. All rights reserved. BGP v3.2—3-1 Route Selection Using Policy Controls Using Multihomed BGP Networks.
NORDUnet Nordic Infrastructure for Research & Education Report of the CERN LHCONE Workshop May 2013 Lars Fischer LHCONE Meeting Paris, June 2013.
Inter-domain Routing Outline Border Gateway Protocol.
EGEE-II INFSO-RI Enabling Grids for E-sciencE EGEE and gLite are registered trademarks LHCOPN Operational model: Roles and functions.
© 2005 Cisco Systems, Inc. All rights reserved. BGP v3.2—5-1 Customer-to-Provider Connectivity with BGP Connecting a Multihomed Customer to Multiple Service.
A Strawman for Merging LHCOPN and LHCONE infrastructure LHCOPN + LHCONE Meeting Washington, DC, Jan. 31, 2013 W. E. Johnston and Chin Guok.
LHCOPN operational model Guillaume Cessieux (CNRS/FR-CCIN2P3, EGEE SA2) On behalf of the LHCOPN Ops WG GDB CERN – November 12 th, 2008.
100GE Upgrades at FNAL Phil DeMar; Andrey Bobyshev CHEP 2015 April 14, 2015.
Brookhaven Science Associates U.S. Department of Energy 1 n BNL –8 OSCARS provisioned circuits for ATLAS. Includes CERN primary and secondary to LHCNET,
David Foster, CERN LHC T0-T1 Meeting, Cambridge, January 2007 LHCOPN Meeting January 2007 Many thanks to DANTE for hosting the meeting!! Thanks to everyone.
LHC high-level network architecture Erik-Jan Bos Director of Network Services SURFnet, The Netherlands T0/T1 network meeting CERN, Geneva, Switzerland;
RIP v1– Routing Information Protocol RIP Versions –RIP v1 (original version, Doyle ch 5) –RIP v2 (improved version, Doyle ch 7) Simple distance-vector.
Ethernet 802.1ag Fault Management Across Domains Freek Dijkstra, Sander Boele, Ronald van der Pol – SARA TERENA Networking Conference – Reykjavík, 23 May.
EGEE-II INFSO-RI Enabling Grids for E-sciencE EGEE and gLite are registered trademarks ENOC status LHC-OPN meeting – ,
T0-T1 Networking Meeting 16th June Meeting
Autonomous Systems An autonomous system is a region of the Internet that is administered by a single entity. Examples of autonomous regions are: UVA’s.
Update on SINET5 implementation for ICEPP (ATLAS) and KEK (Belle II)
Bas Kreukniet, Network Specialist at SURFsara
LHC Open Network Project status and site involvement
BGP supplement Abhigyan Sharma.
Autonomous Systems An autonomous system is a region of the Internet that is administered by a single entity. Examples of autonomous regions are: UVA’s.
an overlay network with added resources
Presentation transcript:

Bas Kreukniet, Sr Network Specialist at SURF SARA NL-T1 Expectations, findings, and innovation Geneva Workshop 10 Februari 2014

Outline 1.Expectations from NL-T1 grid administrators 2.Findings while connecting to the LHCONE 3.Innovation: Ethernet OAM and NSI

Expectations from NL-T1 administrators Advice from grid administrators NL-T1: Bulk data with simple applications (grid-FTP). “Keep it simple” Network provisioning from application is considered “complex” Don’t rush to merge LHCOPN with LHCONE

NL-T1 connected to LHCONE since 20 Jan 2014

BGP routing starts at the connected site. BGP routing for T1’s: Not only a “NREN thing” – it already starts at your organisation! Focus on some BGP topics for connecting sites to LHC networks

LHCOPN connectivity

LHCONE connectivity /16 *[BGP/170] 1w2d 04:07:47, MED 120, localpref 100 AS path: I > to via xe-4/0/ NL-T1 AS1162 GÉANT AS20965 LHCONE-RS CERN AS20641 CERN AS513 LHCONE.inet.0: 133 destinations, 133 routes (133 active, 0 holddown, 0 hidden) + = Active Route, - = Last Active, * = Both

Preferred route: LHCOPN, LHCONE or Internet primary: direct T1–T1 over LHCOPN secondary: T1–T1 over LHCOPN via another T1 tertiary: LHCONE quaternary: Internet

Preferred route: route (a)symmetry If everyone makes this choice, all connections are symmetric. But: sites may have different preferences: 10 Gb/s 1 Gb/s 100 Gb/s site 1 site 2 ISP-B ISP-A

Tie-breaker between LHCOPN and LHCONE CNAF routers at NL-T1 LHCOPN /17 *[BGP/170] 14:58:18, localpref 100 AS path: I LHCONE /17 *[BGP/170] 1w2d 04:23:40, MED 120, localpref 100 AS path: I

LHCOPN / LHCONE route preference BNL routes at NL-T1 LHCOPN /24 *[BGP/170] 2w5d 09:35:43, MED 10, localpref 100 AS path: I > to via xe-1/1/0.0 [BGP/170] 3d 01:15:22, MED 51, localpref 100 AS path: I > to via xe-2/1/0.0 LHCONE /24 *[BGP/170] 1w2d 04:27:43, MED 120, localpref 100 AS path: I > to via xe-4/0/1.2012

Problems and concerns regarding BGP A site advertising his routes has no control who to send a route to. At best they can give hints with BGP communities. The site receiving a route decides which route to accept and how to accept.

BGP in LHC networks Only As is not enough. More info needed.  community for origin of a route T1/T2? Or even better: -site connected to LHCOPN -site connected to LHCONE - Site connected to both: Type A “prefer LHCONE for this route” Type B “prefer LHCOPN for this route” - Specials: dedicated link between two (T1) sites. (“VPN”or “private link”)

Route Preference Solutions Idea: Tag routes with two types of communities: One for origin or source One for destinations See also: BGP hinting by Martin Sweeny (Indiana U) BGP Always-compare-MED always on. We sometimes add metrics on incoming routes.

Operational Issues We received routes over LHC from a site, but traffic we send is blackholed by that site The site was still reachable over the Internet. This happened to us twice recently: on LHCOPN (accidental route redistribution) and LHCONE (incoming IP filter). Configuration errors will be made (we’re also just human) LHCOPN Link NL-T1 – TRIUMF link is still unstable 31 outages last 4 months  Monitoring remains important!

LHCONE and LHCOPN layer 2 monitoring Ethernet OAM monitoring or Layer 2 monitoring NIKHEF, TRIUMF to participate as Measurement Points Looking for T1’s and T2 to participate Advantages: Layer2 keep-alive, ping and traceroute Interdomain, intervendor solution L2 devices can be made visible unidirectional fibercuts can be signalled

LHCONE Innovation NL-T1 likes to partcipate in NSI for LHCONE NSI experiences so far: Use-case: Life Science Grid (LSG) in Holland makes use of NSI since autumn Freek contributed to standard Sander wrote NSI client and implemented it for “Cloud Bypassing” in the Life Science Grid.

Cloud Bypassing on Life Science Grid (LSG) Compute clusters at ±10 locations in the Netherlands

Cloud Bypassing on Life Science Grid (LSG) Offloading campus networks (some only have 1 Gb/s Internet)

LHCONE Innovation: Offloading is cheaper Internet full routing (incl backup): € 8k – €10k per month for 10 Gb/s LHCONE or dynamic lightpath: € 2k – 3k per month for 10 Gb/s

Questions? Erik Ruiter Bas Kreukniet Diederik Vandevenne Sander Boele Farhad Davani Freek Dijkstra