Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.
Building a Router
Hannes Gredler
hannes@rtbrick.com
Pravin S Bhandarkar
pravin@rtbrick.com
RtBrick positioning
Hyper Scale
Routing
Protocols
Bare Metal
hardware
Full API
programmability
Mission & Vision: Interwork Applications & Network
Southbound API
Forwarding State, Policy
Northbound API
Telemetry, Topol...
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
...
What Problem does RtBrick solve ?
Time to Revenue (TTR) O(months)
Development SQA-Test Acceptance-
Test
Deploy
Vendor Serv...
How ?
Database
centric
Modular
Code
Open
Test
Open
Hardware
1. Database centric / Distributed Data Store
bds://local/bgp.neighbor
bds://local/isis.a
dj
bds://local/isis.lsdb.l2
bds:/...
2. Modular Code
IS-IS
BGP
RSVP
LDP
Netflow
Sflow
OSPF
Trill
STP
PIM
L3VPN
L2VPN
Core infra (BDS, IPC, DPKG)
IS-IS NetflowS...
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 Mer...
System Architecture
Route Reflector
• Control plane server
• 24 Core Dual Socket Intel XEON 3.3 Ghz
• 256 GB RAM
• 512 GB SSD for Snapshots for “antifragile” ...
System Architecture
Peering router
PEERING ROUTER
FWDD PLUGIN ARCHITECTURE
Brick daemon "fwdd" on NPU
VPP
REST APIbackstore CLI
Tomahawk Jericho Netlink
Brick daemon "fwdd"...
FORWARDING CAPABILITIES
• Forward transit traffic from the NPU
• Import / Export ACLs
• Punt host path traffic using GRE/M...
System Architecture
Spine router
• Three Levels of Routing
• BGP (eBGP, iBGP)
• IGP (IS-IS)
• Fabric Discovery Protocol
(=Multi Instance IS-IS,
Instance-ID...
DISCRETE SPINE ROUTER
System Architecture
Super Spine router
LXC
Control Board
LXC
fwd
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 M
M
N2N1
etc
etc isis
bgp
isis
bgp.
ipv4
bgp.
ipv6
sample...
Licencing Options
• Consumer / Developer License
• Consumer: Access to package binaries
• Developer: Access to Protocol (BGP, OSPF) code
• F...
WE’LL BE ANSWERING QUESTIONS NOW
Q A&
THANK YOU FOR YOUR TIME
Q & A SESSION
Upcoming SlideShare
Loading in …5
×
Upcoming SlideShare
Applying Hyper-scale Design Patterns to Routing
Next
Download to read offline and view in fullscreen.

3

Share

Download to read offline

Building a Router

Download to read offline

Start building your own routers on bare-metal hardware using our "Full-Stack" light-weight routing and messaging toolkits

Related Books

Free with a 30 day trial from Scribd

See all

Related Audiobooks

Free with a 30 day trial from Scribd

See all

Building a Router

  1. 1. Building a Router Hannes Gredler hannes@rtbrick.com Pravin S Bhandarkar pravin@rtbrick.com
  2. 2. RtBrick positioning Hyper Scale Routing Protocols Bare Metal hardware Full API programmability
  3. 3. Mission & Vision: Interwork Applications & Network Southbound API Forwarding State, Policy Northbound API Telemetry, Topology Data
  4. 4. Our view of the network: HYBRID Controller: Southbound API Routing Protocols: IGP, BGP, SR
  5. 5. • 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
  6. 6. 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
  7. 7. How ? Database centric Modular Code Open Test Open Hardware
  8. 8. 1. Database centric / Distributed Data Store bds://local/bgp.neighbor bds://local/isis.a dj bds://local/isis.lsdb.l2 bds://217.160.181.216/bgp.rib-in PUBSUB
  9. 9. 2. Modular Code IS-IS BGP RSVP LDP Netflow Sflow OSPF Trill STP PIM L3VPN L2VPN Core infra (BDS, IPC, DPKG) IS-IS NetflowSRBGP SR Statically Compiled Monolithic NOS Dynamic Loaded Library Modular NOS
  10. 10. 3. Open Test, Pull
  11. 11. 3. Open Test, Push
  12. 12. 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
  13. 13. System Architecture Route Reflector
  14. 14. • 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 1RU Server LXC M N2N1 etc isis bgp isis bgp. ipv4 bgp. ipv6 fwd conf policy
  15. 15. System Architecture Peering router
  16. 16. PEERING ROUTER
  17. 17. FWDD PLUGIN ARCHITECTURE Brick daemon "fwdd" on NPU VPP REST APIbackstore CLI Tomahawk Jericho Netlink Brick daemon "fwdd" on Server VPP REST APIbackstore CLI Tomahawk Jericho Netlink
  18. 18. 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
  19. 19. System Architecture Spine router
  20. 20. • 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
  21. 21. DISCRETE SPINE ROUTER
  22. 22. System Architecture Super Spine router
  23. 23. LXC Control Board LXC fwd 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 M M N2N1 etc etc isis bgp isis bgp. ipv4 bgp. ipv6 sample fwd conf policy LXC fwd 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 M etc sample LXC fwd 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 M etc sample LXC fwd 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 M etc sample LXC fwd 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 M etc sample LXC fwd 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 M etc sample LXC fwd 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 M etc sample LXC fwd 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 M etc sample • 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
  24. 24. Licencing Options
  25. 25. • 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
  26. 26. WE’LL BE ANSWERING QUESTIONS NOW Q A& THANK YOU FOR YOUR TIME Q & A SESSION
  • BlakeWillis

    Dec. 16, 2016
  • talkmebhabani

    Oct. 23, 2016
  • louisyoung7911

    Oct. 21, 2016

Start building your own routers on bare-metal hardware using our "Full-Stack" light-weight routing and messaging toolkits

Views

Total views

20,551

On Slideshare

0

From embeds

0

Number of embeds

18,536

Actions

Downloads

89

Shares

0

Comments

0

Likes

3

×