Abilene Engineering - PowerPoint PPT Presentation

1 / 16
About This Presentation
Title:

Abilene Engineering

Description:

Sacramento, Kansas City, Indianapolis. Seattle, Los Angeles. Denver, Houston, Cleveland ... Sacramento. Los Angeles. Abilene Architecture: Access. Access Nodes ... – PowerPoint PPT presentation

Number of Views:100
Avg rating:3.0/5.0
Slides: 17
Provided by: Greg8
Category:

less

Transcript and Presenter's Notes

Title: Abilene Engineering


1
Abilene Engineering
  • Guy AlmesInternet2 Project
  • San Francisco
  • 28 September 1998

2
Overview
  • Abilene Engineering and Goals
  • 1998 Schedule
  • Launch Network Expectations
  • Early 1999 Expectations
  • Planning a Connection

3
Abilene Network
Abilene Demo Network September 1999
Seattle
Eugene
Minneapolis
Westfield
New York
New Haven
Cleveland
Newark
Detroit
Trenton
Salt Lake City
Philadelphia
Wilmington
Pittsburgh
Lincoln
Columbus
Sacramento
Indianapolis
Washington
Denver
Oakland
Kansas City
Raleigh
Albuquerque
Oklahoma City
Nashville
Los Angeles
Atlanta
Anaheim
Phoenix
Dallas
Abilene
New Orleans
Access Node
Router Node
Star Tap
Houston
Miami
4
Launch Directly Connected Participants
Seattle
Eugene
Minneapolis
Westfield
New York
New Haven
Cleveland
Newark
Detroit
Trenton
Salt Lake City
Philadelphia
Wilmington
Pittsburgh
Lincoln
Columbus
Sacramento
Indianapolis
Washington
Denver
Oakland
Kansas City
Raleigh
Albuquerque
Oklahoma City
Nashville
Los Angeles
Atlanta
Anaheim
Phoenix
Dallas
Abilene
New Orleans
Directly Connected Participant
Access Node
Router Node
Houston
Miami
28 Total Access Nodes
17 Directly Connected Participants
5
Abilene Engineering and Goals
  • Very High Speed Connectivity
  • Among Internet2 GigaPoPs, including vBNS
  • Other federal NGI networks
  • Non-US advanced networks
  • Qualities Stressed
  • Reliability
  • Low latency
  • Effective NOC and Engineering teamwork

6
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
  • Sacramento, Kansas City, Indianapolis
  • Seattle, Los Angeles
  • Denver, Houston, Cleveland
  • Atlanta, New York City

7
(No Transcript)
8
Launch Core Architecture
Seattle
New York
Cleveland
Sacramento
Indianapolis
Denver
Kansas City
Los Angeles
Atlanta
Abilene
Router Node
Houston
9
Abilene Architecture Access
  • Access Nodes
  • Located at Qwest PoPs
  • Sonet Connects Local to Long-distance
  • Initially, about 120 Access Nodes
  • This list grows as the Qwest Sonet plant grows

10
Launch With 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
Denver
Oakland
Kansas City
Raleigh
Albuquerque
Oklahoma City
Nashville
Los Angeles
Atlanta
Anaheim
Phoenix
Dallas
Abilene
New Orleans
Access Node
Router Node
Houston
Miami
11
Abilene NOC
  • Located at Indiana University
  • Excellent Operations and Engineering Skills
  • Commitment evidenced in Abilene Rollout

12
Schedule
  • Design work Mar-98 and ongoing
  • Rack design May-98 to Jul-98
  • Initial assembly / testing Jul-98 to Aug-98
  • Router Nodes / Interior Lines Jul-98
  • Demo network installed Sep-98
  • Remainder installed Oct-98
  • Beta Period 1-Nov-98
  • Production begins 1-Jan-99

13
Launch Network Expectations
  • Some Sonet Rings not completed
  • Mix of OC-12 and OC-48 Interior Lines
  • NOC fully operational
  • Measurements of Delay, Loss, Utilization
  • Some Access Lines not completed
  • Multicast support
  • Connections at two NGIXes

14
Early 1999 Expectations
  • Gradual increase in OC-48 Interior Lines
  • Gradual completion of Sonet Rings
  • Gradual smoothing of NOC procedures
  • Gradual improvement of access to measurements and
    other engineering data
  • Participation in QBone
  • Connection to remaining NGIX
  • Gigabit Ethernet?

15
Access Line Process
  • Qwest personnel dedicated
  • Issues
  • Access Node
  • OC-3 vs OC-12
  • IP/ATM vs IP/Sonet
  • Choice of Local Carrier
  • Sonet ring vs Dark fiber vs ATM cloud

16
Thanks
  • (ATT/TCG) Sam Yuen, Phil Lordo, Michael Rabin,
    (Qwest) Debbie Montano, Kelly Kermode, (PacBell)
    Greg Wong, Hal Bray, (Nortel) Costa Fitopolous,
    Jean Noel, Brian McFadden, Steve Mariano, The IU
    Abilene NOC, (MCI/vBNS) Kevin Thompson, The vBNS
    Engineering Team, (Cisco) Roy Brooks, John
    Cavanaugh, Samir Parikh, Jeff Barret, David
    Meyer, Chris Buja, Michael Turzanski, (3com) Matt
    Mauss, Matt Rockwell, Harley Reed, (Advanced
    Network Services) David Sutherland, Bill
    Cervany, Matt Zekauskas, (Indiana Univ) Brent
    Sweeny, Rick Wood (Univ California) Kyung Huang,
    Russ Hobby, John Hess, Ken Lindahl, David Wasley,
    (Hyatt Embarcadero) Arnel Cruz, (California State
    Univ) Brian Court
Write a Comment
User Comments (0)
About PowerShow.com