Deploying Virtualized Services Over Legacy Networks

Network Virtualization and SDN EuropeJune 1, 2016

Deploying Virtualized Services Over Legacy Networks

© 2016 ADVA Optical Networking. All rights reserved. Confidential.2

NFV: A Narrow DefinitionReplacing closed appliances with software virtual network functions (VNFs) that can be hosted anywhere in the network on any open hardware


Broad Definition of NFV

Bring the cloud to the network.Use the cloud to deliver the cloud.

Are we doing that with NFV today?How cloudy is NFV?


NIST Definition of Cloud Computing

Five essential characteristics:• On-demand self-service• Broad network access• Resource pooling• Rapid elasticity• Measured service

Are we doing that with NFV today? NO.Could we? YES!


The Goal: Cloudy NFV

• Hosted centrally• Available on demand• Integrated with network • Integrated with OSS/BSS• Pay-as-you-grow model


Some Obstacles1. Integrated with network:

How to leverage existing infrastructure?

2. Integrated with OSS/BSS:How much work is required?

3. Hosted centrally:How to provide dynamic connections?

4. Available on demand:Access via customer portal?


Can we cross the gap to NFV?

And do so while minimizing impact?

There Must Be a Way!


Answer: Build on Today’s MPLS VPNs

Service providers have deployed layer 3 VPNs everywhere, built on fast and reliable MPLS backbones

Layer 3VPN

MPLS Backbone


… and add NFV in the Cloud

Centralized NFV optimizes pooling of compute resources, maximizing resilience, minimizing cost

Layer 3VPN

MPLS Backbone

Data Center


But how do we connect the VNFs to the VPNs?

Need a dynamic method to inject VNFs at the PE router

Layer 3VPN

MPLS Backbone

Data Center


Solution – Use BGP to Signal

Specific VNFs can be tied to specific VPNs

Layer 3VPN

MPLS Backbone

Data Center


Details of VNF InsertionSequence:1. Customer makes

request at portal2. OSS generates service

order for orchestrator3. Orchestrator

instantiates VNFs via OpenStack

4. Orchestrator signals eBGP engine

5. eBGP engine signals route insertion

6. VPN traffic redirected to VNF(s) – service is live!

OSS/BSS

eBGP only(no data)

Customer Portal

MPLS Backbone

Layer 3VPN

Orchestrator

1

23

45

OpenStack


Benefits of Using Existing Infrastructure

• Layer NFV on top of existing infrastructure and OSS systems• Offer customers dynamic incremental virtualized services• No change to existing CEs, PEs or L3 VPNs• Centralized NFV offers lowest TCO• Scalability is very high – easy to add more servers• Very distributed approach – can add a few servers in

multiple locations• Starting cost at each point of instantiation is very low • Required integration to OSS/BSS is limited to service order


We Can Make NFV More Cloudy!

… and we can get started today!

Thank You

IMPORTANT NOTICEThe content of this presentation is strictly confidential. ADVA Optical Networking is the exclusive owner or licensee of the content, material, and information in this presentation. Any reproduction, publication or reprint, in whole or in part, is strictly prohibited.

The information in this presentation may not be accurate, complete or up to date, and is provided without warranties or representations of any kind, either express or implied. ADVA Optical Networking shall not be responsible for and disclaims any liability for any loss or damages, including without limitation, direct, indirect, incidental, consequential and special damages, alleged to have been caused by or in connection with using and/or relying on the information contained in this presentation.

Copyright © for the entire content of this presentation: ADVA Optical Networking.

http://www.linkedin.com/company/adva-optical-networking

http://twitter.com/ADVAOpticalNews

http://www.facebook.com/pages/ADVA-Optical-Networking/37630238931?ref=ts#!/pages/ADVA-Optical-Networking/37630238931?v=wall

http://www.youtube.com/user/ADVAOptical

http://advaopticalnews.tumblr.com/

http://www.slideshare.net/ADVAOpticalNetworking

Technology

Deploying Virtualized Services Over Legacy Networks