Transcript The HOPI Testbed and the new Internet2 Network

Dynamic Lightpath Services on the
Internet2 Network
Rick Summerhill
Director, Network Research, Architecture, Technologies, Internet2
TERENA 2007
20 May 2007
Copenhagen, Denmark
Agenda
• Motivation
• HOPI Project Review
• Infrastructure
•
•
•
•
•
DWDM wave system
Circuit system
HOPI Testbed
IP network
Observatory
• Dynamic Circuit Services (DCS)
2
Why Dynamic Lightpath Services?
• Connection oriented services, circuits, “light path” services,
etc. do bring value to the application community
• Guaranteed bandwidth (predictable, repeatable, dependable
performance between collaborating sites)
• Traffic segregation (policy reasons, traffice engineering)
• Cost/capability tradeoffs (general purpose L3 router blades cost
more than L2 ports which cost more than L1 or L0 interfaces)
• Dynamic circuit capabilities allows these circuit services to
be provisioned efficiently and correctly using automated
tools.
• Establishing end to end light paths is a non-trivial task that when
done manually consumes substantial man-power and is error prone
• Dynamic and automated tools allow for rapid provisioning and
efficient utilization of capital investment
• Automated reservation, allocation, and provisioning enables coscheduling of network and non-network resources.
3
HOPI Project - Overview
•How does one effectively use a richer set of
capabilities available to network designers and end
users?
•
•
Core IP packet switched networks
A set of optically switched lightpaths available for dynamic provisioning
•Fundamental Question: How can we build an
network to efficiently utilize these capabilities?
•
More Generally, how will the Internet architecture evolve as lower layer
capabilities become available?
•Examine a hybrid of shared IP packet switching
and dynamically provisioned circuits
•HOPI Project – Hybrid Optical and Packet
Infrastructure - how does one put it all together?
•
•
4
Dynamic Provisioning - setup and teardown of optical paths
Hybrid Question - how do end hosts use the combined packet and
circuit switched infrastructures?
Infrastructure
5
6
7
8
9
Nodes
10
Nodes
11
Nodes
12
Nodes
13
Nodes
14
Nodes
15
Nodes
16
Internet2 Network: Infrastructure with Multiple Services
Routed IP
Network”
Router Layer
Ethernet Layer
Switched SONET
Layer (vcat, lcas)
Provisioned
Services
“SONET
Switched
Network”
Switched WDM
Optical Layer
Multi-Layer GMPLS
Controlled Networks
17
“Ethernet
VLAN
Switched
Network (i.e.,
HOPI)”
Services
• Circuit Services
• Static Services
• Dynamic Services
• HOPI Testbed Experimentation
• IP Services
• Research Traffic
• Commodity Peering Services
• Commodity Transit Services (under discussion)
• Research Services
• Observatory
• Experimental Architectures
18
Circuit Service Types
• Static Services - Configured by our NOC
• Ethernet or SONET Framed Lambda - Directly on the
Infinera wave equipment through client interface
• Connections can be through a dense set of locations across
the US
• SONET Circuits through the Ciena equipment
• Ethernet Framed tagged or untagged circuits under
SONET via GFP
• Dynamic Circuit Service
• Create Circuits in seconds for periods of hours to days
• Only through the Ciena equipment at the start, eventually
evolving to the full platform
19
Circuit System
• Uses Ciena Core Director and CIs
• Standard Architecture (implemented on a variety of
different vendor equipment)
• Used by many carriers in the US
• Used by GEANT2, CANARIE, UltrascienceNet, USLHC
net, and SURFnet!
• Provides circuits with either Ethernet or SONET
framing
• Connectors likely to use Ethernet, international
connections from Europe or Asia likely to be SONET
• One of the fundamental reasons for supporting this
architecture
• Deterministic capabilities is another
• Provides a variety of SONET or other types of
protection
20
Dynamic Circuit Services
• Current infrastructure and deployment
• The HOPI testbed - uses a single wave on the wave platform
• Is a breakable platform for experimentation
• VLAN based, modeling a circuit infrastructure
• Uses Force10 switches
• A single wave connected to the Ciena platform
• Working toward a persistent set of services to support real
applications
• Separation of development services from production services
• Eventually would like a unified control plane to control
all aspects of the network
21
Dynamic Circuit Services Development
• Current Development involves two main areas: Intradomain and Inter-domain capabilities
• Intra-domain work
• HOPI - has been working for a long time
• The Ciena Network - now working
• Have a small Ciena testbed between Bloomington and
Indianapolis
• Inter-domain work
• Collaborations with other networks
• Following and participating in various standards bodies
22
Intra-Domain work
• Challenges
• Multi-vendor environment
• Multi-layer environment
• Uses DRAGON GMPLS control plane for both HOPI
and the Ciena network
• HOPI has been in place for several years, and
functions as a test-bed
• Ciena Implementation should support a large number
of platforms, eventually
• Evolving to a UNI-2.0 interface at this time
• It is currently using the TL-1 interface
• Software platform should be extensible and vendor
independent
• Lot of support from Ciena on all aspects of this project
23
Inter-Domain Development
• Collaborations with many different group
• For example, the DICE group - Dante (GEANT2),
Internet2, CANARIE, and ESnet
• Working closely with ESnet on interfacing OSCARS and
HOPI - involves AAA work, using OSCARS interface
• Reporting back progress to the GLIF and other
organizations
• For example, Phosphorus, in coordination with the SURFnet
and University of Amsterdam participants
• Meetings with Terapaths
• Coordinating with OGF on various schema - topology,
path computation, signaling, ASTs
24
DRAGON Control Plane - Key Components
• Network Aware Resource Broker – NARB
• Intradomain listener, Path Computation, Interdomain Routing
• Virtual Label Swapping Router – VLSR
• Open source protocols running on PC act as GMPLS network element
(OSPF-TE, RSVP-TE)
• Control PCs participate in protocol exchanges and provisions covered
switch according to protocol events (PATH setup, PATH tear down, state
query, etc)
• Client System Agent – CSA
• End system or client software for signaling into network (UNI or peer
mode)
• Application Specific Topology Builder – ASTB
• User Interface and processing which build topologies on behalf of users
• Topologies are a user specific configuration of multiple LSPs
25
Inter-Domain Topology Abstraction
Full Topology
Partial (edge nodes only)
Maximum Summarization
- Each network defines their own summarization level and is
able to maintain privacy and security
- Summarization impacts optimal end-to-end path
computation, but allows the domain a high degree of
flexibility in internal resource planning within the scope of the
service request
26
Multi-Domain Control Plane
GEANT
•
•
•
•
•
Multi-Domain Provisioning
Interdomain ENNI (Web Service and OIF/GMPLS)
Multi-domain, multi-stage path computation process
AAA
Scheduling
Internet2
Network
RON
RON
Dynamic Ethernet
Dynamic Ethernet
TDM
ESNet
Domain Controller
Ctrl Element
Ethernet
SONET Switch
Router
Data Plane
Control Plane Adjacency
LSP
IP Network (MPLS, L2VPN)
27
Workshops
• Two day workshop
• Provide a working knowledge of how to
design and deploy a GMPLS based
dynamic services network
• Overview of GMPLS architecture
• RSVP and OSPF protocols
• Basic Control Plane Concepts
• Routing, Path Computation, Signaling
28
Workshops, continued
• Hands-on workshop, attendees will:
• Implement a dynamic services test-bed (Ethernet based),
using the DRAGON GMPLS Software Suite
• Schedule:
• First day will focus on concepts and basic control plane design
and implementation
• Second day will explore inter-domain dynamic services and
provisioning
• Target Audience: Senior Network Engineers familiar with
current R&E network infrastructure, IP architectures, and
ethernet switching.
• See http://events.internet2.edu/2007/DCS/
29
Questions?
[email protected]
30