building a router
TRANSCRIPT
RtBrick positioning
Mission & Vision: Interwork Applications & Network
Southbound APIForwarding State, Policy
Northbound APITelemetry, Topology
Data
Our view of the network: HYBRID
Controller:Southbound API
Routing Protocols:IGP, BGP, SR
• Our Toolkits (=Bricks) are enabler for DevOps models• Accelerated Adoption, rather than building software from scratch
• Our Toolkits (=Bricks) are purpose-build for:• Flexibility• Speed of deployment
• Eliminate the “old” Network paradigm• No closed-systems, no curated release model
• Fast Forward IETF Network Apps (BGP, IS-IS, Segment-Routing …) • Create your own Network Apps by your needs
• Or let us customize the Applications for you• Open Source Network Test environment
• Leverage our work for acceptance testing
RtBrick = acceleration for building network devices
What Problem does RtBrick solve ?
Time to Revenue (TTR) O(months)
Development SQA-Test Acceptance-Test
Deploy
Vendor Service Provider
Dev Test Deploy
Time to Revenue (TTR) O(days)
Vendor & Service Provider
How ?
Databasecentric
ModularCode
OpenTest
OpenHardware
1. Database centric / Distributed Data Store
bds://local/bgp.neighbor
bds://local/isis.adj
bds://local/isis.lsdb.l2
bds://217.160.181.216/bgp.rib-in
PUBSUB
2. Modular Code
IS-ISBGP
RSVP
LDPNetflo
wSflow
OSPF
Trill
STP
PIM
L3VPN
L2VPN
Core infra (BDS, IPC, DPKG)
IS-IS Netflow
SRBGP
SR
Statically CompiledMonolithic NOS
Dynamic Loaded LibraryModular NOS
3. Open Test, Pull
3. Open Test, Push
4. Open Hardware / White Boxes
• Economy of scale will ultimately render custom-ASICs obsolete• Cost/Bit favorable on Merchant Silicon
• FY2016 systems shipping:• 3TBit/s, > 128K FIB entries• 800 Gbit/s, > Full Tables, Large Buffers, MPLS, indirection
• Feature Gap gets closed• Cannibalizing Edge Router Business …
• RtBrick “Full Stack” makes no Hardware assumptions• Unbounded Configuration Possibilities:• Single Switch, Cluster of Switches, Co-located x86 Rack Servers ….• Large FIBs, Small FIBs, SW-based forwarders & Combos thereof
System ArchitectureRoute Reflector
• Control plane server• 24 Core Dual Socket Intel XEON 3.3 Ghz• 256 GB RAM• 512 GB SSD for Snapshots for “antifragile” daemon restart• 2 Port 10 GBit/s (Intel XL710) DPDK compatible NIC card
SYSTEM LAYOUT
System ArchitecturePeering router
PEERING ROUTER
FWDD PLUGIN ARCHITECTURE
FORWARDING CAPABILITIES
• Forward transit traffic from the NPU• Import / Export ACLs• Punt host path traffic using GRE/MPLS from NPU to server
• Dynamic Control Plane Protection on NPU for host traffic• Data plane policies installed on the NPU for transit traffic via
firewall filters• Fwdd on NPU-CPU to have:
• VPP based software forwarder to interface with backstore• Chipset specific plug-in that programs the ASIC
• Bypass NPU-CPU processor for packet processing
System ArchitectureSpine router
• Three Levels of Routing• BGP (eBGP, iBGP)• IGP (IS-IS)• Fabric Discovery Protocol
(=Multi Instance IS-IS, Instance-ID 0xfabd)
• Use multi-level route resolution to tie it all together
• Three Levels of Forwarding• Inter-domain: IPv4 / IPV6 /
MPLS• Intra-domain: MPLS (Segment
Routing)• Intra-Fabric: MPLS Segment
Routing
RECURSIVE ARCHITECTURE
DISCRETE SPINE ROUTER
System ArchitectureSuper Spine router
• Embedded Control Board• Control Plane hosting control
plane, user interface & Policy• Multi linecard switch
• OCP 800 (26 Tbit/s)• OCP 1600 (52 Tbits/s) • Linux container (LXC) containing
etc, sample, fwd• Fwd: chipset specific adaptation
Tomahawk
SPINE ROUTER
Licencing Options
• Consumer / Developer License• Consumer: Access to package binaries• Developer: Access to Protocol (BGP, OSPF) code• Full-Stack Developer: Access to Protocol and Infrastructure code
• Annual / Perpetual License• Per Node / Enterprise (All you can eat) license
• Pay as you grow, vs. one off• Maintenance & Support
PROPOSED LICENCING OPTIONS
WE’LL BE ANSWERING QUESTIONS NOW
Q A&
THANK YOU FOR YOUR TIME
Q & A SESSION