ONOS/VirNOS-C 2015/12/10 CTO Tetsuya Murakami [email protected] Advanced Software Solutions for

Carrier Ethernet & MPLS • Enterprise Switching & Routing • Data Center • Provider Edge • IPTV & VOD

© 2014 IP Infusion Inc. All rights reserved.

1

Problem Definition §  Provide the traditional networking services such as MPLS-VPN on top of SDN network

© 2014 IP Infusion Inc. All rights reserved.

2

MPLS VPN Service iBGP

IP/MPLS Network eBGP or OSPF VRF OSPF, LDP Provider Edge Router Customer Edge Router

eBGP or OSPF OSPF, LDP VRF Provider Edge Router Customer Edge Router

Enterprise network

§  §  § 

Enterprise network

MPLS VPN service requires many protocols to carry/isolate the routing information for a given customer. Even though replacing the IP/MPLS network, still the provider edge router/switch needs to support the routing protocols in order to communicate the customer’s edge routers. In order to isolate each customer, VRF must be supported at the provider edge router/switch.

© 2013 IP Infusion Inc. All rights reserved.

3

MPLS VPN service with SDN network ONOS

IGP information

VirNOS-C VRF

OpenFlow

VirNOS-C Virtual network

VRF

OpenFlow BGP or OSPF

BGP or OSPF

OF OF

OF

SDN network OF

Enterprise Network

Enterprise Network

§ 

VirNOS-C is taking care of the following §  §  §  §  § 

§ 

Take care of only EGP information by using BGP or OSPF over VRF interfaces. Trap any control packets by using PKT-IN/PKT-OUT. Provide VRF functionality in order to isolate each enterprise network. Acquire the IGP information from ONOS. Translate the EGP information into the flow entries after combining EGP information with IGP information.

ONOS is taking care of the following. §  § 

Manage the IGP information fully. Provide the IGP information to VirNOS-C (IGP information is needed to generate the flow entries based on the EGP information).

© 2013 IP Infusion Inc. All rights reserved.

4

Network Topology ONOS

OpenStack API

Deploy/Undeploy/Configuration Need to define. OF, REST or other?

VirNOS-C

•  Control Plane is physically separated from User Plane.

VirNOS-C

OF

ARP/ ICMP/ BFD/ BGP/ OSPF/ etc

OF

Control Plane OF

U-Plane

U-Plane

•  C-Plane (VirNOS-C) •  No need to use any special hardware. •  Working on the hypervisor system on the general x86 platform. •  Easy deploy/undeploy from OpenStack. •  Support ARP/Neighbor Discovery/BGP/OSPF/LDP/BFD/ ICMP/etc. Layer •  Southbound interface •  All control packets can be handled by C-Plane via PKT-IN/PKT-OUT defined in OpenFlow. •  IP routing/LSP information can be translated to the OpenFlow message. •  Northbound interface •  ONOS can provision IGP information to VirNOS-C via OpenFlow or other.

U-Plane

•  U-Plane •  Any devices supporting OpenFlow can be available. •  No need to support any routing/signaling protocols.

User Plane Layer Router

Router

© 2014 IP Infusion Inc. All rights reserved.

5

On-Demand Control ONOS

OpenStack API

VirNOS-C

Step.3 Step.2

•  Step.1 VirNOS-C receives routing updates from the customer edge router. VirNOS-C

OF

OF

•  Step.2 VirNOS-C request a corresponding IGP information to ONOS via REST or other API.

Control Plane Layer OF

Step.4

•  Step.3 ONOS provides the corresponding IGP information to VirNOS via OF, REST or other API

U-Plane

•  Step.4 VirNOS calculates EGP information with IGP information provided by ONOS, translates EGP information into flow entries and provision the flow entries to the U-Plane devices.

Step.1

U-Plane

U-Plane

User Plane Layer Router

Router

© 2014 IP Infusion Inc. All rights reserved.

6