DEMO

Evolving the IP routing landscape with OpenFlow/SDN

RouteFlow Control Platform

Marcelo Ribeiro Nascimento, Christian Esteve Rothenberg,Marcos R. Salvador and Maurício F. Magalhães

Telecommunications Research and Development Center (CPqD)University of Campinas (Unicamp), Brazil

- Develop an open-source framework for virtual IP routing solutions in OpenFlow-enabled networks.

Expected results

- Control plane successfully working between OpenFlow and legacy switches. - Routes from Quagga FIB are properly converted into flow entries.- Data plane packets are correctly forwarded

Tiny daemon listening to Linux Netlink events- Monitors Linux routing and ARP tables and informs the RF-Server- To extract additional routing information (e.g. all learned paths), it may hook or peer with the routing engine(s).

RouteFlow-Client

Simple "proxy" application in OpenFlow controller of choice - Registers to events (e.g., PacketIn, DatapathJoin)- Handles control plane packets betw. OF switches & VMs- Manages flow entries as commanded by the RF-Server

RouteFlow-Proxy

Open issues & Outlook

Demo

- Deployment on hardware testbed at Indiana University- User Interface: Towards holistic network administration- SNMP agent for rx/tx port traffic- Aggregated BGP (aBGP) Routing Service:Unified AS-wide routing logic (i.e. business policy)

- RouteFlow (RF) is implemented as a NOX controller application (RF-C) and one slave daemon (QF-S) per VM running Quagga.

- QF replicates the physical topology by configuring and "stitching" the VMs into a virtual topology running the Quagga control plane.

- RF sets the OpenFlow tables according to Quagga FIB updates and dispatches routing control messages to from/to legacy subnets

Your GroupHere

- Cheap IP forwarding gear with minimal embedded software- Migration path from traditional IP to native/hybrid SDN - Support different flavours of IP network virtualization (e.g., logical routers, router aggregation / multiplexation).- IP Routing/Network-as-a-Service models of networking- Simplified intra- and inter-domain routing interoperable with legacy equipments.

The "brain" implementing advanced Routing Services- Discovers and maps virtual to physical devices/ports- Handles OF events and routing info from RF-Clients- Commands flow modification messages

RouteFlow-Server

Use Cases- Engineered path selection- Optimal best path reflection- Path protection with prefix independent convergence- Data plane security- Secure inter-domain routing- Simplifying customer multi-homing and IPv6 migration

http

://go

.cpq

d.co

m.b

r/rou

teflo

w

Match: EthDst, IP+MASK, Actions: Set(EthSrc, EthDst), PortOut, (TTL--, Chksum+)

Overview

Benefits- Simplified edge architecture (no BGP state on the edge)- Lower cost and increased edge speed- Power of innovation leads to differentiation + revenues- BGP security, stability, monitoring, policy management

Work Ahead- Implementation of Use Cases and Pilots focusing in the under-served mid market (SMEs and regional ISPs)- Load-balancing services for multi-homed networks- Integration of OF v1.1, v1.2 and v1.3- LDP / MPLS support towards open-source LSR

- Embodiments of Network Information Base (NIB) and Knowledge Information Base (KIB)- Backend of JSON-based RouteFlow IPC

Distributed NoSQL Database

Topology and Statistics

RouteFlow Protocol

Resource Status and Mapping

OpenNMS SNMP

DEMO

Architecture

DEMODEMO

DEMO http://go.cpqd.com.br/routeflow

Controller-based Hybrid Networking

 

           http://go.cpqd.com.br/routeflow  

 

Overview    RouteFlow:  Integrating  IP  routing  services  with  OpenFlow  networks     RouteFlow   is   composed   by   an  OpenFlow  Controller   application,   an   independent  RouteFlow   Server,   and   a  virtual  network  environment  that  runs  arbitrary  IP  routing  engines  (e.g.  Quagga).  The  resulting  forwarding  information  base  (FIB)  from  running  the  configured  IP  routing  protocols  (e.g.,  OSPF,  BGP)  is  collected  along  the  ARP  tables  are  collected  by  RouteFlow  Slave  processes  and  then  translated  into  OpenFlow  entries  that  are  finally  installed  in  the  associated  OpenFlow-­‐enabled  datapaths.  

Project  Objective    The  main  goal  of  RouteFlow  is  to  develop  an  open-­‐source  framework  for  virtual  IP  routing  solutions  over   commodity   hardware   implementing   the  OpenFlow  API.  RouteFlow  aims  at  a   commodity   routing  architecture   that   combines   the   line-­‐rate  performance  of   commercial  hardware  with   the   flexibility  of   open  source  routing  stacks  (remotely)  running  on  general  purpose  computers.  As  an  outcome  of  this  point  in  the  design  space  of  routing  solutions,  we  expect:  

• Controller-­‐centric  hybrid  networking  model  enabling  a  migration  path  from  legacy  IP  deployments  to  purely  software-­‐defined  networks.    

• Open-­‐Source  framework  to  support  the  different  flavors  of  network  virtualization  (e.g.,  logical  routers,  router  aggregation  /  multiplexation).  

• IP  Routing-­‐as-­‐a-­‐Service  models  of  networking.  • Simplified  intra-­‐  and  inter-­‐domain  routing  configuration  integrated  with  legacy  equipments.  

RouteFlow  Control  Platform  Demo  

New   Prototype   Implementation:   The   evolution   from   previous   prototype   designs   to   a   better   layered,  distributed  system  design,  is  based  on  a  NoSQL  datastore  (MongoDB)  that  centralizes  (i)  the  RFCP  core  state,  (ii)   the  network  view   ,   and   (iii)   additional  knowledge   information  base  used   to  develop  advanced  routing  applications.    In  addition,  the  datastore  acts  as  the  pubsub-­‐like  message  queuing  IPC  that  loosely  couples  the  modules   via   a   JSON-­‐based   implementation   of   the   RouteFlow   protocol,   facilitating   extensibility,   fault-­‐management,  debugging,  and  monitoring.    A  newly  developed  SNMP  subagent  will  be  demonstrated  with  a  legacy  NMS  that  monitors  the  RFCP-­‐controlled  port  traffic.  

Aggregated   BGP   Routing   Service:   Using   the   configurable   mapping   of   virtualized   routing   engines   to  OpenFlow  switches,  the  routing  service  provides  unified  AS-­‐wide  routing  criteria  (i.e.  business  policy)  in  an  abstraction   level  which  does  not   require   individual   configuration  of  multiple   routing  processes.  The  RFCP  runs  a  single  BGP  engine  that  talks  eBGP  to  the  neighbouring  domain  routers.  

Hardware  Deployment:  To  demonstrate  how  a  RouteFlow  network  can  be  deployed  we  have  constructed  a  sample   RouteFlow   topology   using   hardware   switches   (Pronto   3290).   The   configuration   simulates   a  backbone   networks   with   an   OSPF   mesh   between   RouteFlow   routers   and   BGP   peerings   to   external   non-­‐RouteFlow  routers.  

User   Interface:   Another   recent   addition   to   RouteFlow   is   a   web-­‐based   UI   to   simplify   the   basic   tasks   of  network   administration.   The   goal   of   the   UI   is   to   administer   networks   in   a   holistic   manner   instead   of  configuring   individual   network   elements.   Error   prone   configuration   details   are   by   default   automatically  configured  using  templates,  relieving  load  on  network  operators  of  repetitive  details.  The  RFCP  architecture  allows   for   the   integration   of   tools   and   data   sources   into   the   network   provisioning   process.   Filter   list  creation,  IP  selection,  topology  discovery,  etc..,  can  be  automated.