Validation of the Interface to the Routing System (I2RS) - PowerPoint PPT Presentation

Chair for Network Architectures and Services Technical University of Munich (TUM) Validation of the Interface to the Routing System (I2RS) intermediate talk Kerem Saka June 15, 2016 Chair for Network Architectures and Services Department of Informatics Technical University of Munich (TUM) Kerem Saka – Validation of I2RS 1

Chair for Network Architectures and Services Technical University of Munich (TUM) Motivation What is I2RS Approach Mininet and MiniNext Quagga Netconf and Yang Next Steps Kerem Saka – Validation of I2RS 2

Chair for Network Architectures and Services Technical University of Munich (TUM) Motivation ◮ I2RS new Protocol from IETF , which is still under development ◮ Only specification of the Protocol and no implemantation ◮ Realtime/Event driven interaction with routing system ◮ Allows to add and retrive parameters/information in to/from the routing system Kerem Saka – Validation of I2RS 3

Chair for Network Architectures and Services Technical University of Munich (TUM) What is I2RS Kerem Saka – Validation of I2RS 4

Chair for Network Architectures and Services Technical University of Munich (TUM) Approach ◮ First understanding I2RS and set up the development and testing Environment ◮ Vm includes Mininet, Mininext, Quagga ◮ After that add own I2RS Daemon to Quagga Kerem Saka – Validation of I2RS 5

Chair for Network Architectures and Services Technical University of Munich (TUM) Approach - Mininet and miniNExT ◮ Mininet emulates a virtual network ◮ 2 different kind of nodes: switch and host ◮ Provides OpenFlow VSwitch(OVS) ◮ Limitation of Mininet: no native routing protocol Kerem Saka – Validation of I2RS 6

Chair for Network Architectures and Services Technical University of Munich (TUM) Approach - Mininet and miniNExT ◮ Solution to add routing protocol to Mininet: miniNExT ◮ Extention to Mininet ◮ Hosts have own configuration ◮ Hosts can run Quagga software Kerem Saka – Validation of I2RS 7

Chair for Network Architectures and Services Technical University of Munich (TUM) Approach - Development Network Kerem Saka – Validation of I2RS 8

Chair for Network Architectures and Services Technical University of Munich (TUM) Approach - Quagga ◮ Software Router ◮ Runs in virtual network ◮ Supports different routing protocols (OSPF , BGP , etc.) ◮ Has an interface for the different daemon allowing the creation of a custom daemon ◮ But no support for NETCONF and YANG Kerem Saka – Validation of I2RS 9

Chair for Network Architectures and Services Technical University of Munich (TUM) Approach - Quagga ◮ Build own Deamon as I2RS Agent ◮ Communicate with the ZEBRA daemon to manipulate Network ◮ Combine daemon with ConfD to support NETCONF and YANG ◮ Use NETCONF and YANG models to build I2RS protocol Kerem Saka – Validation of I2RS 10

Chair for Network Architectures and Services Technical University of Munich (TUM) Approach - NETCONF and YANG ◮ Network Configuration Protocol ◮ Provides mechanisms to install, manipulate and delete configurations ◮ YANG data modeling language ◮ Model configuration data and state data of network elements ◮ Data model for I2RS is implemented in YANG Kerem Saka – Validation of I2RS 11

Chair for Network Architectures and Services Technical University of Munich (TUM) Next Steps ◮ Implement an I2RS daemon for Quagga ◮ Combining I2RS daemon with ConfD ◮ Build I2RS Client with YANG Cli pro or OpenDaylight ◮ Establish communication with I2RS Agent and I2RS Client Kerem Saka – Validation of I2RS 12

Chair for Network Architectures and Services Technical University of Munich (TUM) Questions? ◮ Thank you Kerem Saka – Validation of I2RS 13