Transcript 20070212-reese-transitrail

TransitRail:
Nationwide Commodity
Peering Program
February 12, 2007
Minneapolis, MN
Copyright 2007 CENIC and PNWGP
Premise
Successful large-scale commodity
Peering can...
Decrease commodity costs and result in
overall savings
Reduce reliance on commercial vendors
Increase routing efficiency and flexibility
Copyright 2007 CENIC and PNWGP
TransitRail Is...
NATIONWIDE
Multiple exchange locations around the US;
COMMODITY
packet-agnostic
Connections at commercial peering exchange
points;
PEERING
Direct network-to-network bilateral IP Packet
exchange
Copyright 2007 CENIC and PNWGP
TransitRail Goals
Build a robust and reliable network
focused on serving the commodity
demands of research and education
networks;
Reduce the overall cost and reliance on
traditional Internet transit services;
Operate on a cost-recovery, sustainable
basis.
Copyright 2007 CENIC and PNWGP
What to Expect
TransitRail participants are likely to
experience anywhere from a 25% to
60+% reduction in the overall traffic
that normally goes over their
commodity ISP circuits.
Copyright 2007 CENIC and PNWGP
CENIC Experience
9000
Commodity only - no R&E
8000
7000
6000
Peering Volume
Transit Volume
Aggregate
Linear (Aggregate)
Linear (Peering Volume)
5000
4000
3000
2000
1000
0
04 04 04 04 04 04 05 05 05 05 05 05 06 06 06 06 06 06 07 07 07
n- ar- ay- ul- ep- ov- an- ar- ay- ul- ep- ov- an- ar- ay- ul- ep- ov- an- ar- aya
J S
J S
J S
J
J
J
J
M M
M M
M M
M M
N
N
N
Copyright 2007 CENIC and PNWGP
Who
 CENIC and Pacific Northwest Gigapop are
jointly developing, and implementing the
TransitRail facility;
 These groups have significant individual and
joint experience with peering facilities and
prospective peering partners;
 Working with NLR who is providing the
underlying network infrastructure.
Copyright 2007 CENIC and PNWGP
Trial Phase Success
 Phase 0 (trial) success
No cost to participants
CENIC, PNWGP shared subset of peers
Helped FRGP defer/avoid adding additional
transit capacity, noticeably improved latency
Helped OneNet relieve severe congestion on
transit links, estimated ~200Mbps, actual
~500Mbps
Copyright 2007 CENIC and PNWGP
Current Status
West Coast peering transition complete
Los Angeles, Sunnyvale, Seattle on-line
12 Gbps of peering capacity
Washington DC connected
14 Gbps of additional peering capacity in
provisioning
Chicago - Signing IRU contract
Equipment received and waiting
Copyright 2007 CENIC and PNWGP
TransitRail Participants
 Seven participants connected
CENIC
Front Range GigaPOP (UCAR)
LEARN (North Texas GigaPOP and Univ of Texas)
OneNet
Pacific Northwest GigaPOP
Pittsburgh Super Computer
 Three participants in progress
ENA, MERIT, NCREN
Copyright 2007 CENIC and PNWGP
TransitRail Growth
FRGP is adding 2nd GE to TransitRail
Copyright 2007 CENIC and PNWGP
Infrastructure
 Equipment (CISCO 7600s)
 Maintenance - 4 hr on site
 10GE WaveNet between routers
 Redundant loops to exchange facilities
 FrameNet backup links between routers
 New autonomous system (11164)
 Restrictive peering policy to maximize return
Copyright 2007 CENIC and PNWGP
Seattle (Westin Bldg)
Equinix
DC
Chicago
Equinix Ashburn
Sunnyvale
PAIX
TransitRail - Phase 1
Los Angeles
(Equinix LAP)
Equinix LAX
1 Wilshire
Copyright 2007 CENIC and PNWGP
Routing Policies
What TransitRail requires of its peers
3-5 locations throughout US
Large amount of traffic exchanged per
peer
Reliable Operations
Copyright 2007 CENIC and PNWGP
Routing Policies
What TransitRail requires of its peering
participants
Structured local preference
Maintained IRR object
Willingness to tune announcements to
L3/Wiltel/C&W (to attain highest amount
of usage)
Copyright 2007 CENIC and PNWGP
Business Side
Cost recovery model
NOC support through PNWGP & CENIC
Future upgrades, additional peering
locations, will be decided with
participants
Per port pricing model
Copyright 2007 CENIC and PNWGP
TransitRail Support Model
Operational Engineering
Peer Relationships:
• Level1 support to peers
• Maintenance Events
• Interconnect Outages
• DoS Response
• Peer contacts
Troubleshooting:
• Level2 to Customer Support
• Testing and Data collection
• Problem Mitigation
• TR Access Links
Customer Support
Call Center:
• Customer contacts
• Trouble Ticket System
• Detailed Problem Description
• Abuse Handling
Network Outage Monitoring:
• Customer connections
• Customer Maintenance Events
• NLR FrameNet Links
• TR Backbone Links
Tools
Customer Facing:
• PacificWave Speedometer
• Backbone Interface Trends
• Ping and Traceroute Looking Glass
Internal:
• Inventory/Asset Tracking
• TACACS, RANCID
• Syslog, Swatch, Cricket
• TR Planning Tools
Customer Reporting:
• Netflow capture
• Data processing
• Report generation
Configuration/Design:
• Address assignment
• Router configuration
• Change control
• TR Access Changes
Network Architecture
• Sr. Technical Staff
• Technical Escalation Point
• Capacity Planning
• Architecture
• Long term:
• Routing Changes
• Customer and
Peer Relations
Copyright 2007 CENIC and PNWGP
Management
• Collocation contracts
• Peer contracts
• Customer contracts
• Customer billing
• Accts Payable/Receivables
Thank you
http://www.transitrail.net
[email protected]
Copyright 2007 CENIC and PNWGP