1 / 61

Internet2: A Tutorial Part 2 of 4

Internet2: A Tutorial Part 2 of 4. 17 th Brazilian Symposium on Computer Networks Paul Love, Internet2 Chair, I2 Topology WG epl@internet2.edu. Abilene. Overview. Abilene Background Review of Abilene Architecture 1999 Schedule Launched Network First Half 1999 Expectations

kaitlin-higgins
Download Presentation

Internet2: A Tutorial Part 2 of 4

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Internet2: A TutorialPart 2 of 4 17th Brazilian Symposium on Computer Networks Paul Love, Internet2 Chair, I2 Topology WG epl@internet2.edu

  2. Abilene

  3. Overview • Abilene Background • Review of Abilene Architecture • 1999 Schedule • Launched Network • First Half 1999 Expectations • Engineering Issues • Additional information http://www.internet2.edu/abilene/

  4. Abilene: Objectives • Provide high-quality, widely available Interconnect among participating gigaPoPs/universities • IP as the bearer service • Goals • Reliability • Functionality • Latency • Capacity SBRC99 Salvador, Bahia, Brazil

  5. Abilene: Objectives cont • Additional, separate networks to • Test advanced network capabilities • Final proposals being evaluated this month • For network research - still TBD • Support advanced functionality as it evolves • Multicast, QoS, IPv6 SBRC99 Salvador, Bahia, Brazil

  6. Abilene Team • Overall direction by Internet2 • Qwest • Cisco • Nortel (Northern Telecom) • Indiana University • National Center for Network Engineering • Open to other contributors • Collaborate with related efforts in network or applications research SBRC99 Salvador, Bahia, Brazil

  7. Key Attributes • IP over Sonet initially • Qwest OC-48 Sonet capacity and collocation sites • Nortel OC-192 Sonet equipment • Cisco GSR 12000 routers including support for • QoS • Native multicast SBRC99 Salvador, Bahia, Brazil

  8. Abilene and Other Networks • Important for Abilene to interconnect with other high performance networks • First I2 backbone: vBNS • Federal Agency NGI networks (ESnet, NREN, DREN, ...) • Non-US Research & Education Networks • CANARIE, NORDUnet, SURFnet, TransPac, etc • Peering in hand or plans in process • vBNS, ESnet, CANARIE, DREN, NREN, NORDUnet, SURFnet, etc • Advanced functionality across I2 & our peers • Native multicast • QoS across multiple interconnected networks *RSN SBRC99 Salvador, Bahia, Brazil

  9. Broader Internet2, NGI, and International Advanced Nets Initial NGIX sites Possible CA*net3 peering sites StarTap StarTap Plus SBRC99 Salvador, Bahia, Brazil

  10. Notes on I2, NGI, and International Interconnections • NGIXes are the foundation for peering I2 backbones & with NGI nets • Abilene will connect with OC12 • StarTap is the foundation of international interconnections - universal solution • New York is first example of StarTap Plus • Minimize latency • Provide redundancy • Abilene doesn’t provide transit SBRC99 Salvador, Bahia, Brazil

  11. Example: New York City • SURFnet has OC-3 circuits and routers at the Teleglobe POP at 60 Hudson Street • NORDUnet the same • And each connects from New York to the StarTap with DS3 • Details on the next slides SBRC99 Salvador, Bahia, Brazil

  12. New York City Europe ISP SURFnet NORDUnet Teleglobe Qwest Abilene Chicago SBRC99 Salvador, Bahia, Brazil

  13. New York City Europe ISP SURFnet NORDUnet Teleglobe Qwest Abilene Chicago SBRC99 Salvador, Bahia, Brazil

  14. St. John’s Calgary Regina Winnipeg Charlottetown Fredericton Montreal Halifax Vancouver Ottawa Toronto Chicago CA*net3 SBRC99 Salvador, Bahia, Brazil

  15. Abilene NOC • Located at Indiana University • Publish statistics & online information resources • Coverage can be looked at in three broad areas • Administration • Engineering • Operations SBRC99 Salvador, Bahia, Brazil

  16. Administration • Security Management • Communications • Overall Management and Coordination SBRC99 Salvador, Bahia, Brazil

  17. Engineering • Configuration • Testing • Data collection • Traffic Analysis SBRC99 Salvador, Bahia, Brazil

  18. Operations • 24x7 Monitoring • Reporting • Change and Problem management • Information base • Single point of contact • Network problems • Abilene connection process SBRC99 Salvador, Bahia, Brazil

  19. Online Traffic Map

  20. For more informationon the Abilene NOC • www.abilene.iu.edu • Abilene traffic map at http://hydra.uits.iu.edu/~abilene/traffic SBRC99 Salvador, Bahia, Brazil

  21. Couple of Notes on Costs Cost recovery on UCAID’s part Set each year for following year Participant institution Connector - based on BW(can be connector and not participant) nb There is also a small Qwest access fee Long-distance part of access line is considered part of the ‘backbone’ Thus, number/location of core nodes does not affect costs borne by connecting sites SBRC99 Salvador, Bahia, Brazil

  22. Qwest Fiber Networkhttp//www.qwest.com/network/netmaps.html SBRC99 Salvador, Bahia, Brazil

  23. Schedule - part 1 • Design work: Mar-98 and ongoing • Rack design: May-98 to Jul-98 • Initial assembly / testing: Jul/Aug-98 • Router Nodes / Interior Lines: Jul/Aug-98 • Demo network installed: Sep-98 • Remainder installed: Nov/Dec-98 • Production begins: 29-Jan-99 • Launch Event in DC: 24-Feb-99 SBRC99 Salvador, Bahia, Brazil

  24. Abilene Sep 98 Demo Network Seattle Eugene Minneapolis Westfield Boston New York New Haven Cleveland Newark Detroit Trenton Salt Lake City Philadelphia Wilmington Pittsburgh Lincoln Columbus Sacramento Indianapolis Washington Oakland Denver Kansas City Raleigh Albuquerque Oklahoma City Nashville Los Angeles Atlanta Anaheim Phoenix Dallas New Orleans Houston Router Node Miami Access Node Star Tap SBRC99 Salvador, Bahia, Brazil

  25. Abilene Architecture: Core • Router Nodes located at Qwest PoPs • Cisco 12008 GSR • ICS Unix PC: IPPM and Network Mgmt • Cisco 3640 Remote Access for NOC • 100BaseT LAN and ‘console port’ access • Remote 48v DC Power Controllers • Initially, ten Router Nodes • Seattle, Sacramento, Los Angeles, Denver, Kansas City, Houston, Indianapolis, Cleveland, New York City, Atlanta • And, coming this Fall - Washington, DC • Interior lines connect core nodes • OC-12 and OC-48 Sonet • IP-over-Sonet interfaces SBRC99 Salvador, Bahia, Brazil

  26. SBRC99 Salvador, Bahia, Brazil

  27. Abilene Architecture: Access • Access Nodes • Located at Qwest PoPs • Sonet: Connects Local to Long-distance • Currently about 135 Access Nodes: • This list grows as the Qwest Sonet plant grows • Access lines connect from core node to gigaPoP or member • IP-over-Sonet or IP-over-ATM possible • OC-3 and OC-12 typical • Others as possible & appropriate • GigE, ... SBRC99 Salvador, Bahia, Brazil

  28. Abilene + some Access Nodes Seattle Boston Eugene Minneapolis Westfield New York New Haven Cleveland Newark Detroit Trenton Salt Lake City Chicago Philadelphia Wilmington Pittsburgh Lincoln Columbus Sacramento Indianapolis Washington Oakland Denver Kansas City Raleigh Albuquerque Oklahoma City Nashville Los Angeles Atlanta Anaheim Phoenix Dallas New Orleans Houston Miami Router Node Access Node SBRC99 Salvador, Bahia, Brazil

  29. Launch Network • Some Sonet Rings not completed • Mix of OC-12 and OC-48 interior Lines • NOC fully operational • Some Access Lines not completed • Connections at two NGIXes • NGIX/Central (OC3) • NGIX/West (OC12) • OC12 into Union Station for demos SBRC99 Salvador, Bahia, Brazil

  30. Schedule, part 2 • Production began: 29-Jan-99 • Launch Event in DC: 24-Feb-99 • Member Meeting: 28-Apr-99 • Native Multicast deployed in core: Jun-99 • Completion of OC-48 Core: TBD • Addition of DC Router Node: 3Q99 • Seattle Member Meeting: 11/15-Oct-99 SBRC99 Salvador, Bahia, Brazil

  31. First Half 1999 Expectations • Measurements of Delay, Loss, Utilization • Gradual • Increase in OC-48 Interior Lines • Completion of (Qwest) Sonet Rings • Accesss to measurements and other engineering data • Participation in QBone • Upgrade of NGIX/Central to OC12 • Native Multicast SBRC99 Salvador, Bahia, Brazil

  32. Second Half 1999 Expectations • Gigabit Ethernet connection(s)? • OC48 connection? • Connection to NGIX/East • Somewhere in Washington, DC, area • OC12 SBRC99 Salvador, Bahia, Brazil

  33. Seattle New York Cleveland Sacramento Indianapolis Denver Kansas City Los Angeles Atlanta Houston Abilene Core: Current SBRC99 Salvador, Bahia, Brazil

  34. OC12 still being installed OC12 OC48 OC12 Abilene: Current plus On Order Seattle New York Cleveland Sacramento Indianapolis Denver Kansas City Los Angeles Atlanta Houston OC3 SBRC99 Salvador, Bahia, Brazil

  35. Outline of Engineering Issues Routing: OSPF, BGP4, Routing Arbiter Database Multicast PIM-Sparse Mode, MBGP, MSDP Measurements Surveyor: One-way delay and loss Traffic utilization End to end flows with gigaPoP help OC3MON -- passive measurements QoS - QBone SBRC99 Salvador, Bahia, Brazil

  36. GigaPoP Architecture

  37. Acknowledgments • Steve Corbató - University of Washington & Pacific/Northwest Gigapop • Ron Hutchins - Georgia Institute of Technology & Southern CrossRoads Gigapop • Ken Lindahl - University of California, Berkeley • Rick Summerhill - Executive Director, Great Plains Network • David Wasley - CENIC Director of Projects/CalREN-2 Gigapop SBRC99 Salvador, Bahia, Brazil

  38. GigaPoP Idea • From George Strawn of NSF - Predates Internet2 • Idea was one of the catalysts for Internet2 • Aggregation point • Economies of scale • Member sites • Value added services shared by members • Not limited to university/I2 members • (High-speed) local traffic stays local • Attached networks SBRC99 Salvador, Bahia, Brazil

  39. GigaPoPs • Variety of services and styles • Technical and organizational differences • Mixture of technologies • Some things must be the same • IP as a common bearer service • Inter-GigaPoP routing policy and design • Measurement • Trouble tickets among network operation centers SBRC99 Salvador, Bahia, Brazil

  40. Customer links Robust Model Backbone nodes Peering connection Aggregation points/ GigaPoPs Agency Networks SBRC99 Salvador, Bahia, Brazil With thanks to Ron Hutchins

  41. GigaPoPs can be Hierarchical UNC Vanderbilt Duke NCSU MCNC UAH UAB SoX GigaPoP GSU GCATT UA Peachnet GT vBNS FSU, UF,Miami SBRC99 Salvador, Bahia, Brazil With thanks to Ron Hutchins

  42. Internet2 GigaPoPsAs of November 1997 Denotes GigaPoP SBRC99 Salvador, Bahia, Brazil

  43. Internet2 GigaPoPsAs of 19 May 1999 Denotes GigaPoP SBRC99 Salvador, Bahia, Brazil

  44. GigaPoPs - What Flavors Do They Come In • Two broad sets of choices • Level • Topology • Level • Layer 1 (optical) • Layer 2 (usually ATM) • Layer 3 • Topology • Star - aka Gigapoint • Distributed • Combination - figure “8” SBRC99 Salvador, Bahia, Brazil

  45. Member links ISP/HPNSP links Star or Gigapoint • Advantages • No internal transit issues • Disadvantages • Longer backhauls for both members & service providers SBRC99 Salvador, Bahia, Brazil

  46. Member links Intra-GP links ISP/HPNSP links Distributed • Advantages • Optimize backhauls • Take advantage existing connections • Politics • Disadvantages • BW between nodes can be bottleneck SBRC99 Salvador, Bahia, Brazil

  47. Member links Intra-GP link ISP/HPNSP links Combination • Advantages • Optimize backhauls • Take advantage existing connections • Politics • Minimize internal transit • Disadvantages • BW between hubs can be bottleneck • Longer backhauls SBRC99 Salvador, Bahia, Brazil

  48. Example - Non-ATMLevel 2 GigaPoP

  49. P/NW GigaPoP Design SBRC99 Salvador, Bahia, Brazil With thanks to Steve Corbató

  50. Example - Combination GigaPoP

More Related