implementing a programmable service edge - update...our current prototype bm switch with broadcom...
TRANSCRIPT
Implementing a Programmable Service Edge - updateONF Connect 2019S. Szuppa & the A4 Fun(ctions) Team, H.J. Kolbe, Deutsche Telekom
2
We develop a cost-efficient, lean-to-operate and scalable access platform to deliver Gigabit products.
„
„
Access4.0 is a mini data center at the network edge(AKA DT’s seBA incArnATion)
Sept 2019 3– Access 4.0 | ONF Connect 2019 –
IP-CORE
WHOLE SALE
CPEFTTH GPON LT
Central Management Layer
Spine-Switch
WDM
WDM
GPON LT
GPON LT
GPON LT
Leaf/ToR Service Edge
GPON LT
GPON LT
GPON LT
XGS-PON LT
XGS-PON LT
Leaf/ToR Service Edge
GPON LT
GPON LT
XGS-PON LT
XGS-PON LT
Leaf/ToR Service Edge
Spine-Switch
x86Control & local Mgmt.
GPON LT
x86Control & local Mgmt. x86Control &
local Mgmt.
MERCHANT SILICONBARE METAL
HW / SW SPLIT (CUPS, …)
COMMUNITY & OPEN SOURCE
HORIZONTALLY & VERTICALLY SCALABLE
CPE DPUFTTB
CPE MSANFTTC
Bng: subscriber-aware ip edge & a split personality
4
Access Device Access Node Aggregation BNG IP Routers
BNG service edge part
terminates subscribers
Tunnel protocols
Services
BNG routing part
Full PE router
protocols
interfaces
Architecture first: where to put the BNG (=SE+router)As always, ça depend…
Internal appliance
SE and Routing can be split
Hairpin routing
Part of the SDN fabric and management
External monolith
SE and router external
Possible migration scenario
Lots of things to be implemented twice
Embedded
SE and Routing split
Service Edge (SE) in TOR switch
Router in fabric Using devices that are anyway in
the data path
5
SDN Control App shall support all three. SEBA does, too. Our target architecture is embedded SE
Our current prototype BM switch with Broadcom Qumran, rtbrick control plane,
DT PAO controller
Routing happens in fabric
A bng/se on bare metal switches
6
PPPoE on bare metal switch
Basic SE feature set Termination of Q-in-Q tagged Ethernet frames (S-VLAN, C-VLAN)
Termination of PPPoE session (including LCP, IPCP, IPv6CP)
Authentication, Authorization and Accounting (RADIUS) (control plane only)
Subscriber IP address management (control plane only)
Customer specific IP packet filter, for instance anti-spoofing filters
Hierarchical (aka per subscriber) Quality of Service for various
services (e.g. VoIP, IPTV, etc.)
Multicast Replication
Termination of L2TP tunnel for wholesale
Subscriber-aware counting and statistics for both operation as well as billing
Legal intercept
Uplink encap/decap to MPLS-based fabric
Thoughts on cp/up split
7
chip / merchant silicon
Device ODM
Open Network Linux
SE control plane
PAO / Radius
Common API
Common API
Owned by DTOpenclosed
CP local per deviceSwicthes run containers, too ☺Less delay, less distributed stateLess synch issues – no additional abstraction like with PFCPLocal packet handling via host path short cut
Programmable chipsetsOpen APIs to allow SW companies provide SE functionality
Learnings, challenges, etc
8FPGAs are also interesting devices
CPU 150pin Connector
1588,
SyncE
Circuit
Broadcom
J2C/Q2C
PM25
PM25
PCIe
Broad
SyncLPC
BMC
AST2520
CPLD
I2C
I2C
Flash
Flash
DDR4
I210
PCIe x1
NCSI
UARTMGMT
USB
PCIe
x4
10G KR
x4
10G
Serdes 25G
Serdes
25G
Serdes
KBP
or
TAP
48 x SFP28 25G
10 x QSFP28 100G
4 x SFP+ 10G
Statistic
4 x 50G
Search
8 x 50G
MGMT
Console
USB
Mux
UART
Mux
BCM82758SFI
1pps_out
BITS
Ecosystem view wrt current prototypeAPIs decouple proprietary components
chip / merchant silicon
Device ODM
Open Network Linux
Routing / SE control plane
PAO
Common API
Common API
Owned by DTOpenclosed
Pioneers
Long term
Dec
ouplin
g v
ia A
PIs
selected proprietary components Ecosystem and
“new kids on the block”9
Your logos here
Your logos here
Core Technologies in SEBA and Access 4.0
10
• SDN Control & Apps (incl. DT PAO)• Open Hardware • OLT, Switch, DPU, …• Automation, CI/CD• Network Management & IT
Abstraction • “Las Vegas Principle“ at DT• Service Edge & Router (BNG)
Moving on!
11
Deutsche Telekom @ ONF Connect 2019deep dives on Access4.0 and much more
12
Dr. Hans-Joerg Kolbe, 2:30pmImplementing the
Programmable Service Edge
Manuel Paul, 11:55AmPanel: Technical
Leadership Team (TLT)
Manuel Paul, 4:30pmCOMAC and OMEC at DT
Bjoern Nagel, 2:15pmVOLTHA Roadmap
Dr. Fabian Schneider, 5:30pmSEBA Reality Check! How to Take
the Design to the Next Level?
Jochen Appel, 10:00AmKeynote: Access Network
Transformation
Robert Soukup, 4:30pmAccess4.0 Program update
Dr. Hans-Joerg Kolbe, 11:00AmInside View Into Operator
Business Cases
Michal Sewera, 5:30pmopen source epc
Michal Sewera, 11:45Am5g and open source
Additional material
13
Towards a common subscriber edge
14
Platform Compatibility Framework with standard set of APIs▪ avoids hardware lock-in▪ provides compatibility to apps/features
through common protocol and data model for forwarding▪ provides compatibility of management tools and practices
Anything south of the line to be provided by hardware vendor
Design paradigm: Control plane / user plane splitno frAgmenTATion, pleAse…
15
Forwarding Plane
Control Plane
CP/UP Mediation LayerDrivers
D1 D2 D4D3
D1 D2 D4D3
App1 App2 App3 Fixed / mobile or converged control applications (usually on x86)
Programmable hardware on bare metal(Differentiate through performance & exposed feature sets)
fin
16