Transcript HC Packet Rings

100G Packet Ring Architectures
Gady Rosenfeld
VP Marketing
Corrigent Confidential
Copyright © 2007 Corrigent Systems
October 2007
[email protected]
The need for 100G
 Cox – "100GE needed for broadband customer aggregation urgently in the
core by 2009 and across the board by 2011", John Weil, Apr'07
 Comcast – “There is a market need for 100GE”, Vik Saxena, Jan’07
 Equinix – Requirements for “100 Gbps or greater”, Louis Lee, Jan’07
 Level 3 – Using 8x10 GbE LAG today
 Yahoo! – Using 4x10 GbE LAG today
Corrigent Confidential
Copyright © 2007 Corrigent Systems
2
Corrigent Confidential
Copyright © 2007 Corrigent Systems
3
Corrigent Confidential
Copyright © 2007 Corrigent Systems
4
Generic Triple-Play Network Architecture
MGW
Metro Node
NHO
Video
Acquisition
System
National
Video Content
Distribution Network
(IP Multicast)
NHO
VoIP
Digital
Video
Server
Local IPTV Video
Distribution Network
Metro Node
ISP1
ISP2
BRAS
ISP3
VoIP
Digital
Video
Server
IP Core Network
(Tier 1 aggregation network)
National
Content
Insertion
Regional
Content
Insertion
Local IPTV Video
Distribution Network
Metro Transport Network
(Tier 2 aggregation network)
Local
Distribution
Corrigent Confidential
Copyright © 2007 Corrigent Systems
5
Triple-Play Network – Metro Transport
Local Content
Insertion
Metro Node
DSLAM
PTS
PA
Nx10GE
PTS
PTS
Digital ER
Video
Server
Nx10G
PTS
10G metro rings
Metro Node
Nx10GE
PTS
PA
PA
Digital ER
Video
Server
PTS
PTS
KEY
ER : Edge Router (Layer-3)
PA : Packet Aggregator (Layer-2)
Customer Premises
PTS
Packet transport switch
Fiber
Copper
Corrigent Confidential
Copyright © 2007 Corrigent Systems
6
Bandwidth Requirements
 IPTV
• 2007 – 300 channels, 10% HD: 1.1-1.4 Gbits/s (MPEG-4/MPEG-2)
• 2010 – 300 channels, 50% HD: 2.0-3.2 Gbits/s
 VoD (2500 subscribers per node)
• 2007 – 5% VoD penetration: 0.5-0.6 Gbits/s
• 2010 – 30% VoD penetration: 5.0-8.0 Gbits/s (MPEG-4/MPEG-2)
 Total bandwidth requirements – 6 nodes per ring
• 2007 – 3.5-4.5 Gbits/s
• 2010 – 32-51 Gbits/s
Corrigent Confidential
Copyright © 2007 Corrigent Systems
7
IEEE 802.3 HSSG Status
 IEEE 802.3 HSSG
• Agreed on PAR for 40GE and 100GE, July’07
• Identify bandwidth-hungry applications: data centers, internet
exchanges, high-performance computing and video on demand
 Parallel optics for 100GE (4x25G, 10x10G) discussed for dedicated
fiber and limited distances applications. Serial options for MAN/WAN
applications still under evaluation
• Polarization multiplexing, Phase coding
 Standard is still at least 4 years away
Corrigent Confidential
Copyright © 2007 Corrigent Systems
8
Alternative for Network Scalability
 Add separate rings
• Complex network operation – multiple networks, Traffic Engineering
• No redundancy between rings
• Limited statistical multiplexing
 Upgrade to 40 Gbits/s
• Disruptive and costly process
• High equipment cost – optics, network processors, traffic
management
• Limited capacity
Corrigent Confidential
Copyright © 2007 Corrigent Systems
9
High-Capacity Packet Rings


High-capacity (HC) packet
rings are achieved through
advanced bonding techniques
100G MAC Layer
PTS
PTS
PTS
Multiple 10G RPR instances
are combined to create a single
logical ring
PTS
nx10G PHY

40G links can also be added to
the bundle
PTS
PTS
PTS
PTS
Hashing
User
Interface

Flow-aware hashing for load balancing and
distributing packets over parallel physical links

Guarantees traffic integrity, by uniquely identifying
and classifying each individual flow over the same
physical link, avoiding re-ordering
RPR#2
RPR#1
Corrigent Confidential
Copyright © 2007 Corrigent Systems
10
HC Packet Rings – Traffic Distribution
 No mis-ordering within a flow
• Each flow is consistently delivered on the same channel
• Packet ordering is maintained even if each channel is carried in
different route with different length
• Flexible combinations of fields used for hashing to provide load
balancing in different applications
Link Failure
Transmitted packets
over 4 channels
6 flows
4
3
2
1
4
3
2
1
4
3
2
1
4
3
2
1
4
3
2
1
4
3
2
1
3
2
1
3
2
2
1
1
3
2
2
1
1
4
3
2
1
4
After the failure packets are
distributed over 3 channels
Corrigent Confidential
Copyright © 2007 Corrigent Systems
11
HC Packet Rings Survivability
RPR Steer
protection
TDM
Flow
Data
Flow
RPR Steer
protection
- Logical port
- Physical RPR MAC
Corrigent Confidential
Copyright © 2007 Corrigent Systems
12
HC Packet Rings Enhanced Survivability
TDM
Flow
Data
service
RPR Link#2
is Down
- Logical port
- Physical RPR MAC
Corrigent Confidential
Copyright © 2007 Corrigent Systems
13
Example – Growth of Existing Services (1/3)

L2-VPN service to interconnect
between enterprise's branches

VPLS over ring network

Can be infrastructure service to
multiple end-user services
Customer C
Customer A
Customer B
Customer C
Customer A
Customer C
Customer B
Customer B
Network Capacity
Network
Capacity
Customer AA––3G
Customer
3G
Customer BB––3G
Customer
4G
Customer CC––4G
Customer
4G
Total net
Total
netcapacity
capacity: 10G
: 11G
Customer B
Customer A
Customer C
Corrigent Confidential
Copyright © 2007 Corrigent Systems
14
Example – Growth of Existing Services (2/3)
Option 1 – Multi-ring configuration

Add additional ring instance – ringlet #2

Disconnect all CustomerB locations from
ringlet #1

Re-provisioning Customer B service on
ringlet #2
Customer C
Customer A
Customer B
Customer C
Customer A
Customer C
Customer B
Customer B
Customer B
Customer A
Customer C
Corrigent Confidential
Copyright © 2007 Corrigent Systems
15
Example – Growth of Existing Services (3/3)
Option 2 – HC-RPR

Increase RPR ring capacity to 20G

Connect Customer B 4th location to
the existing L2-VPN service
Customer C
Customer A
Customer B
Customer C
Customer A
Customer C
Customer B
Customer B
Customer B
Customer A
Customer C
Corrigent Confidential
Copyright © 2007 Corrigent Systems
16
Multi-Phy HC Packet Rings

Description
• Allow combination of RPRoSTM64 and RPRo10GE in the same HC-RPR
group.

Motivation
• Reduce cost while maintaining ring synchronization.
• Clock distribution across the ring via SONET/SDH interface
• Data and TDM traffic will run on top of both Ethernet and SONET/SDH
interfaces – full flexibility

Implementation aspects
• Eliminate miss-order by per flow hashing
• Fine flow granularity to assure equal load sharing between RPR instances
• Flow granularity: MAC ( S+D) + IP (S+D) + Port
• No issue of equal load sharing between different Phy layers
• OC192 payload rate (net rate): 9.51Gbps
• 10GE tri-model average payload rate: 9.5Gpbs
Equal net rates
Corrigent Confidential
Copyright © 2007 Corrigent Systems
17
Asymmetric Operation (AHC-RPR) and Management
 Best for incremental network growth
 Install RPR blades and optics only
PTS
S5
S4
S1
PTS
PTS
as node capacity demand increases
2x10G
HC-RPR
 At least one ring must be common to
all stations
 Each station is represented by
HC (group) MAC and physical MAC
PTS
PTS
S2
S3
• HC MAC is used for data forwarding and IP level
• Physical MAC used for topology
 Reference topology has group entity and per ring entities
Corrigent Confidential
Copyright © 2007 Corrigent Systems
18
The CM4000 Packet Transport Switch Layer
Monitoring, Survivability
and multiplexing
Transport Plane


TDM
Ethernet
Classification
Marking
IP/MPLS
Queuing
Point to point
Tagging
OTN (G.709)
Policing
Multipoint
FC
Interworking
Point to Multipoint
MPLS LSP
SONET/SDH Path
SONET/SDH Line
PPP
HDLC
1 GE
10 GE
SONET/SDH
Nx10GE
NxRPR
RPR
Ethernet
Packet-based Path/Link Technologies
Packet-based Multiplexing, Survivability and Monitoring at the
Path/Link layers
Corrigent Confidential
Copyright © 2007 Corrigent Systems
19
Summary
 HC Packet Transport
• Network scalability up to 100 Gbits/s for high bandwidth
applications is required today
• 100GE is at least 4 years away
• Cost effective network migration path is required
• In-service network scalability in 10G or 40G increments
• Resiliency to fiber and equipment failures
• Implemented with available low-cost optical components
Corrigent Confidential
Copyright © 2007 Corrigent Systems
20
Questions?
Thank You
Corrigent Confidential
Copyright © 2007 Corrigent Systems