Flattening the Network
-
Upload
jennieawalsh -
Category
Documents
-
view
219 -
download
0
Transcript of Flattening the Network
-
7/30/2019 Flattening the Network
1/16
Flattening the Network
Intro to BoF Session in Denver, June
Neil Farquharson
-
7/30/2019 Flattening the Network
2/16
Copyright 2011 Alcatel-Lucent. All rights reserved.2 | Taming | January 2011
Birds of a Feather in Denver
Please sign up for our
BoF SessionAt NewNOG52, June
-
7/30/2019 Flattening the Network
3/16
Copyright 2011 Alcatel-Lucent. All rights reserved.3 | Taming | January 2011
Data traffic predictions
MINTS Minnesota Internet Traffic Study, http://www.dtc.umn.edu/mints/home.php
Swanson-Gilder Estimating the Exaflood, 2008.
Cisco Forecast Global IP Forecast and Methodology, 2007.
2 dB/yr
10E+0110E+0210E+0310E+0410E+0510E+0610E+0710E+0810E+09
1980 1990 2000 2010 2020
Dat
aTraffic(Tb/month)
MINTS low
MINTS high
Swanson-GilderCisco forecast
Extrapolation from2007 MINTS measuredgrowth rate
All content copyright ownerships acknowledged
-
7/30/2019 Flattening the Network
4/16
Copyright 2011 Alcatel-Lucent. All rights reserved.4 | Taming | January 2011
All content copyright ownerships acknowledged
Traffic Predictions
-
7/30/2019 Flattening the Network
5/16
Star Trek copyright of Paramount
-
7/30/2019 Flattening the Network
6/16
Copyright 2011 Alcatel-Lucent. All rights reserved.6 | Taming | January 2011
Drivers for change
Traffic growth leads to more core routers being deployed, as all traffic passes througha meshed router core
Traditional delineation of Transport and IP networks results in limited operationalvisibility across domains, thus the cost of delivering services is not optimized
Core architectures are increasingly expensive and power hungry Carriers looking for higher speeds (40G, 100G) and dramatic cost efficiencies
From
High volumes of video & internettraffic negatively impacting
profitability
Growing meshes of core routers tohandle ever-increasing traffic
Separate IP & Transport domainswith minimal cross-domainoperational visibility
To
A new architecture that canaccommodate profitable growth forinternet and content distribution
Leveraging the efficiencies ofintegrating flexible OTN and of
powerful IP services
Integration of the Optical domaininto the IP domain with cross-Layervisibility and automation
-
7/30/2019 Flattening the Network
7/16
Copyright 2011 Alcatel-Lucent. All rights reserved.7 | Taming | January 2011
HO-ODU HO-ODU HO-ODU
HO-ODU
HO-ODU
level networking
HO-ODU HO-ODU
Sub- level networking
LO-ODU LO-ODU
Switching at Lambda or Sub-lambda (Port, Sub-port) Level
LO-ODU
Clear Channel
Clients
IP/MPLS
Clients
LO-ODU
HO-ODU networking used whenclient throughput does not needfurther aggregation within a
LO-ODU networking used whensub- multiplexing is needed (nostranded BW)
ODU Termination (G.709 OAM)guarantees a clear demarcation Intermediate Monitoring can
be electronic and/or photonic
Switching can be electronicand/or photonic
NE Bsub-switch
NE A switch
ODU(flex) switch
ROADM
OTN is the key convergence technology uniting current technologies with robust
OAM and FEC for reliable transport that is very high bandwidth at low cost/bit
Complete transparency forclients in flexible containers
ODU container sizes well-suited for Ethernet transport
-
7/30/2019 Flattening the Network
8/16
Copyright 2011 Alcatel-Lucent. All rights reserved.8 | Taming | January 2011
ODUflex maps any bit-rate client to a single, right-sized transport container
More flexibility for OTN
ODUflex The Flexible Data Unit
Provides for connection-orientedtransport of any variable bit-rate,leveraging its flexible-sizedcontainer (1.25 Gbps increments)
Decouples client physical interfacefrom the network transport entity
Maintains a 1:1 relation betweenclient interfaces and transportentities, reducing the # of transportentities and simplifying operations
Supports transport of variable ratepacket streams (for instance VLANswithin a 100GE port)
Similar to VCAT, but avoidsdifferential delay problem of VCAT
Enables full utilization of networkresources, avoiding capacity waste
Wavelength
HO ODU/OCh
Client
interface
Transport
entity
Physical
interface
HO ODU/OCh
HO ODU/OCh
ODUflexFlow (VLAN)
ODUflexFlow (VLAN)
HO ODU/OCh
ODUflex
ODU
Phy
Phy
Phy
ODUPhy
ODUFlow (VLAN)Phy
-
7/30/2019 Flattening the Network
9/16
Copyright 2011 Alcatel-Lucent. All rights reserved.9 | Taming | January 2011
HO ODU
VLAN #4
VLAN #3
VLAN Shapers
VLAN #2
Queue 2
Queue 1
Queue 3
Queue 4
Queue 6
Queue 5
Queue 7
Queue 8
Buffer Pool
WFQ
SP
VLAN #1
ODU-flex-1
ODU-flex-2
ODU-flex-3
ODU-flex-4
EthernetPort
Logical Flow(VLAN #4)
Logical Flow (VLAN #3)
Logical Flow (VLAN #2)
Logical Flow(VLAN #1)
Port Shaper
Routers
ROADM/OXCMore flexibility for OTN
Flexible grooming + OTN
-
7/30/2019 Flattening the Network
10/16
Copyright 2011 Alcatel-Lucent. All rights reserved.10 | Taming | January 2011
Before Flattening - Present Mode of Operation
Separate andindependent IP and optical domains
P Router
ServicePE Routers
PE Routers
P Router
P Router
P Router ServicesApplications
Gateways
IP/MPLS Backbone
OTN/DWDM
OXC/ROADM
OTNHub
OpticalTransport
-
7/30/2019 Flattening the Network
11/16
Copyright 2011 Alcatel-Lucent. All rights reserved.11 | Taming | January 2011
After Flattening, using a unified control plane
Mix of technologies to give best overall performance
IP/MPLS Backbone
Node 1
RoutersRouters
Services
ApplicationsGateways
OTN/DWDM
OXC/ROADM
OTN
Hub
Node 3Node 2
On average equates to:
lower latencyhigher bandwidthlower cost per bit
-
7/30/2019 Flattening the Network
12/16
Copyright 2011 Alcatel-Lucent. All rights reserved.12 | Taming | January 2011
Node 2
Node 1
Node 3
After Flattening, using a unified control plane
Example of one traffic stream
-
7/30/2019 Flattening the Network
13/16
Copyright 2011 Alcatel-Lucent. All rights reserved.13 | Taming | January 2011
Node 2
Node 1
Node 3
After Flattening, using a unified control plane
Example of another traffic stream
-
7/30/2019 Flattening the Network
14/16
Copyright 2011 Alcatel-Lucent. All rights reserved.14 | Taming | January 2011
Node 2
Node 1
Node 3
After Flattening, using a unified control plane
Example of a third traffic stream
-
7/30/2019 Flattening the Network
15/16
Copyright 2011 Alcatel-Lucent. All rights reserved.15 | Taming | January 2011
Belief #1: Network Flattening (NF) should be done at WDM layer, not ODU layer(via IPoDWDM with tunables on routers) to reduce complexity and the # of OXCs.
Belief #2: You dont need to protect both IP and optical layers opticalprotection works for link failures, not router failures. Emphasis should be on IPlayer protection.
Belief #3: As you make an optical device more dynamic, it tends towardsbecoming a router; with comparable capex, complexity and opex challenges.
Belief #4: Network Flattening requires more router resources for protectionpurposes. Also, you need > 100% spare to account for potential types of failures.
Belief #5: Router-OTN (mapping onto ODU layer) handoff is expensive andcomplex; and unlike the optical layer, MPLS LSPs can grow and shrink as trafficdictates.
Belief #6: The adage of switch where you can, route where you must is stillpertinent: NF leads to much worse scalability problems since meshing of PE-routers becomes an O(N2) problem rather than O(N). Also, P-routers are able tostat-mux traffic better than PE-routers. Consequently the reliance on PE-routersas aggregators requires overprovisioning of the PE-routers.
Engrained beliefs to be overcome
-
7/30/2019 Flattening the Network
16/16
Copyright 2011 Alcatel-Lucent. All rights reserved.16 | Taming | January 2011
Birds of a Feather in Denver
Utilize P-Routers for what they do best Optimize resource sharing and distribution Increase network capacity fast Will save a darn lot of money once we get it to work
Cell during NANOG51: 214 675 0660
Paramount Star Trek copyright ownership acknowledged
Please join us for our
BoF Session, NewNOG52, June