PacificWave Update for APAN-23. John Silvester Professor of Electrical Engineering, USC PI TransLight/PacificWave Project (NSF) Board Member, CENIC

Transcription

1 PacificWave Update for APAN-23 John Silvester Professor of Electrical Engineering, USC PI TransLight/PacificWave Project (NSF) Board Member, CENIC

2 International Connectivity and Exchanges 2 Visualization courtesy of Bob Patterson, NCSA.

3 PacificWave 3 US West Coast R&E Distributed Exchange with PoP s in Seattle, Sunnyvale, Los Angeles TransLight/PacificWave project. (NSF-OCI-IRNC [# ]). - PI: John Silvester (USC), Co-PI: Ron Johnson (UW) - Key partners: AARNet, CENIC, PNWG, University of Hawaii.

4 Context of Pacific Wave 4 The US States on the Pacific Coast [Alaska, Washington, Oregon, California, Hawaii] have collaborated in networking for several years. (e.g. US Pacific Consortium is an affiliate of APAN) Many international links enter the US through Washington and California (and to a certain extent Hawaii although they tend to remain local there) Seattle, Los Angeles, and Sunnyvale are natural places for exchange points Led to the development of Pacific Wave a collaboration between CENIC and PNWG to build out exchange capabilities on West Coast.

5 Pacific Wave an Open Exchange 5 Extensible peering exchange and lambda integrated facility Nodes (starting in early 2005) in Seattle and Los Angeles, connected by 10GbE wave(s) provisioned over National LambdaRail (2,241 kilometers) AUP free Supports IPv4 and IPv6; multicast enabled Based on Layer 2, Ethernet connections (for layer 3 peering) Provides 24x7 NOC support. Priced consistently from node to node Allows participants to self-select their peering Allows participants to connect to one-location and access participants at all Pacific Wave nodes Supports advance applications Welcomes any research or development network that can meet the minimum network configuration requirements (connect with a router; support BGP; support jumbo-frames) Support GLIF connectivity as a participant in Global Optical Lightpath Exchange (GOLE) development

6 PacificWave, Starlight, and Atlantic Wave 6 Visualization courtesy of Bob Patterson, NCSA.

7 TransLight/PacificWave Project 7 Facilitate international R&E connections on US Pacific Coast Assist in the termination (equipment, backhaul) of AARnet SXTransport links through Hawaii to Seattle and Los Angeles Assist in build-out of Hawaii connectivity to observatories Further develop PacificWave exchange capabilities Assist in operation of IEEAF link Tokyo-Seattle Assist in operation and support of other IRNC projects Assist in operation and support of other International R&E networks participating in PW Develop and operate advanced capabilities to support optical interconnect and exchange needs of R&E networks

8 Hawaii Connection Opportunities 8

9 Application Drivers A Sampler 9 e-vlbi and other astronomy projects (Gemini, Express, CSIRO) HPC development & deployment strategies Sensor networks, environmental monitoring ORION, Neptune & Station Aloha, BioMirror, Ocean Genomics, CREON, NEESGrid and seismic projects and programs Telehealth, telemedicine, disease monitoring and control (Centie, Stanford, ) High definition video for HDTV, immersive videoconferencing, megaconferences, collaboratories & VO development

10 PW-Activities ( ) Transpac2 connected to PW-Los Angeles with 10GbE Ultralight joins PW-Los Angeles at 10GbE AARnet SX-North connected to PW-Seattle Sunnyvale Exchange point site Operational Cinegrid joins PW-Los Angeles at one GigE Mimos Berhad joins PW-Los Angeles at one GigE ESNet joins PW-Sunnyvale at 10GbE Singaren adds a one GigE at PW-Los Angeles NII/Sinet joins PW-Los Angeles with three GigE ports TWAREN/TANET2 upgrades to 10GbE in PW-Los Angeles Palo Alto Exchange point site Operational KreoNet2/KOREN upgrades port to 10 gigabit at PW-Seattle Translight/Pacific Wave and Translight/Starlight connect via 10GbE connection donated by Cisco KAREN/REANNZ joins PW-Seattle at 1 GbE NREN joins PW-Sunnyvale at 10GbE CUDI joins PW-Los Angeles at 1 GbE CLARA joins PW-Los Angeles at 1 GbE

11 Extension to CUDI and CLARA 11 ONS Cenic Cenic Optical Optical backbone backbone LA (818) PWLA EXCH TLPW Project: Extension of 1G circuits to connect CUDI and CLARA SDSC ONS SW CWDM CWDM SW CWDM CWDM SW CUDI CLARA GC, SD Bestel, TJ

12 Layer 3 3 R&E Networks and Pacific Wave 12 AARNET GEMNET GLORIAD IEEAF KREONET MIMOS (Malaysia) QATAR SINET SINGAREN TANET/TWAREN TRANSPAC2 CA*NET4 Pacific Wave CLARA CUDI ABILENE (Internet2) CALREN (HPR) DREN ESNET NASA NLR-Packetnet NREN PNWG

13 PacificWave Seattle 13 NLR-Packetnet Abilene ATTBI/Comcast CA*NET4 DREN ESnet GEMnet WIDE/TLEX (IEEAF) Does not show lightpath connections. NLR Lambda to STARLIGHT Seattle Westin CISCO 6509 NLR Lambda to LAX (via Sunnyvale) AARNet TANET2/TWAREN SingAREN PNWGP KAREN Microsoft KREONet2 1 Gigabit 10 Gigabit

14 Pacific Wave - Sunnyvale 14 NLR TO SEATTLE PWAVE ESNET PAIX L3 SVL 6509 CENIC SVL HPR NREN Does not show lightpath connections NLR TO LA PWAVE 1 Gigabit 10 Gigabit

15 Pacific Wave - Los Angeles 15 Mimos Berhad (Malaysia) 10 GE NLR Lambda To Seattle PWave (via Sunnyvale) Qatar Foundation Abilene Los Nettos 1 Wilshire W 7th W 7th 6509 TWAREN NII/SINET (3) Cinegrid AARNet Singaren CUDI TRANSPAC2 CLARA Does not show lightpath connections CalREN-HPR NLR Packetnet 1 Gigabit 10 Gigabit

16 Overall PW Exchange Traffic 16 Live link to current stat Live link to pw stat page The data provided here is an aggregate of inbound and outbound IP packets on Participant ports.

17 Pacific Wave Lightpath Interconnect 17 Primary focus has been on Layer 3 interconnect There is a lot of interest in Layer 2 ( lightpaths ) and Layer 1 ( waves and lambdas ) interconnect. [GLIF, etc] SXTransport(S) is configured as 8x1GE PW has deployed additional OC192 from LA to SEA configured as 8x1GE to allow interconnect for AARNet and other nets as demand grows. Linking the Translight projects: 10G link from PW-Seattle to Starlight (Chicago) available (CRW) further enhancing layer 3 and lightpath interconnect capability

18 Lightpath Networks and PW 18 CA*NET4 Gloriad Cinegrid TRANSPAC (?) AARNET (S) (to TλEX) IEEAF Others in the planning stages Pacific Wave TransLight SEA-CHI (CRW) NLR Waves NLR (Layer 2) CALREN-XD HOPI, Internet2 (newnet) PNWG

19 AARNet SX-Transport (S) 19 Oahu (Planned) Los Osos (Morro Bay) SCCN STM-64 Fiber IRU & optics to Cal Poly SLO Spencer Beach (Big Island of Hawaii) Spencer Beach to Waimea Waimea to Hilo Optics to carry new OC192 lambda over CENIC from SLO to LA AARNet SCCN STM-64 Hilo to Mauna Kea Alexandria (Sydney) Pacific Wave LA

20 AARnet SX-Transport S. Link 20 Seattle, Washington Maunalani, Hawai`i Nortel HDXc to Australia local Gig-E add/dr op Spencer Beach Hawai`i Cisco Time Warner backhaul Southern Cross OC-192 CENIC backhaul OC-192 Los Osos California Los Angeles, California Cisco To Canada, New York, Chicago, Korea CENIC and NLR OC-192 local Gig-E add/dr op

21 AARNet S Path PW Lightpath Interconnect PW-L2X (8x1G) LAX-SNY-SEA to SLO to SNY, SEA 21 PW CENIC CENIC AARnet Router Abilene Singaren Twaren PW-L3X-LA NLR Packetnet CalREN Router PW-L3X:10G LAX-SNY CENIC to SD

22 Operational Status 22 Backhaul from Los Osos landing through SLO to LA has been implemented and tested End to end testing (light) from CA to AU Wave between LA and SEA tested including interoperability between CISCO and Nortel HDXc Pending for Installation of equipment in Sydney (AARnet) Final cross-connects in Hawaii

23 23 Prospective Users of AARNet SX-Transport (S)

24 Trends in High Speed R&E Networking 24 Faster transport - 10Gbps is standard now with multiple links deployed on single and diverse fiber paths Not just layer 3 routed networks any more Assignable waves, mostly GbE for now Moving to 40Gbps transport & denser WDM on expensive links (soon) Global end-to-end performance: ~7 Gbps (IPV6 & V4) Greater international collaboration, but the importance of geography (and politics) hasn t disappeared yet Importance of (open) exchanges (GOLES)

25 PacificWave GOLE Diagram 25

26 PacificWave Plans 26 As we see increasing demand for lightpath services, PW plans to automate its handling of these dedicated connections. Also, as the new Internet2 network is deployed, PacificWave needs to have automated hand-off to dynamic scheduling mechanisms are used. Continued participation in GLIF will require that certain technical standards are met. Additional capacity between PW PoP s will soon be necessary to handle the lightpath demands. Demand for 40G (and later 100G) services may also require upgrades in equipment. We can anticipate this in Explore partnerships with other International networks to help rationalize trans-pacific R&E networking.

27 27 Thank you John Silvester,