NFV and SD-WAN Multi vendor deployment Pablo Ramirez Sevilla, 29.05.2019

What does NFV means? s

Catalogue of Network Functions Virtualization NFV Routing Firewall DPI (Deep Packet Inspection) Intrusion Detection WAN Acceleration VPN Gateway Content Caching … Load Balancer Traffic Management Encryption Residential Gateway Deep Packet Inspection Intrusion Detection Network Address Translation Network Firewall Digital PBX Content Delivery/ Cache Encryption Load Balancer Basic Traffic Management Traffic Management Application Acceleration Session Border Controller SIP Gateway Test Set Router

An open virtualization platform is essential Key trends for telcos Carriers demand open, multi-vendor virtualized solutions to support their cloud vision SD-WAN is hot and migrating from appliance to NFV uCPE architecture Security and encryption are critical for marketplace acceptance COTS technology becoming optimized for edge NFV deployment Need consistent virtualization technology across L2, L3, LTE, Wi-Fi networks Carriers require simplified, automated deployment and operations An open virtualization platform is essential

The cloud migration should include SD-WAN Services should be flexible and optimized for the customer’s needs Monolithic SD-WAN Application: Hybrid WAN, VPN, WAN Opt, FW, etc. running bare metal VNF2 VPN VNF3 FW VNF1 Hybrid WAN NFVI Single-vendor SD-WAN appliance Single-vendor SD-WAN monolithic software running on white-box Multi-vendor SD-WAN software components running in VMs on uCPE with standard software NFVI Implement SD-WAN as a set of network functions - not a vertically integrated app

This is not what we had in mind… Edge NFV: round 1 Fall from grace Gray box edge Solutions from IP players…as in “what’s the point” Most operators rushed SD-WAN appliances to market SD-WAN vendors “reluctantly” ship boxes Neo-lockin providers saying “buy all the apps from me and I can host my competition if you force me” This is not what we had in mind…

Choice of platforms and choice of apps on the platform uCPE allow choices… NFVI hardware Variety of hardware options from operator chosen vendors or customer supplied COTS NFVI software Network OS convergence layer Security Management VNFs Multiple options per function Multiple functions Customer functions … NFVI (HW) Network OS NFVI (SW) Firewall #1 Firewall SD-WAN VNFs App Router Choice of platforms and choice of apps on the platform

uCPE the perfect place

Multiple cloud management models Centralized OpenStack controller Standard cloud model and APIs Only agents on compute nodes – minimizes resource requirements on uCPE Embedded cloud Provides distributed, wholly contained uCPE cloud deployment Address security, scaling and upgrade concerns of centralized OpenStack controller Consistent virtualization API at customer premises and data center Local management Eliminates OpenStack controller and agent resource requirements on uCPE Faster startup Suitable for direct control via scripts or third-party managers

Zero touch provisioning MANO Overview of operation ZTP Auth Orch Network OS is packaged with operator defaults. Golden image is mated by hardware provider with target COTS. COTS suppliers drop ship platform pre-loaded with Ensemble Connector and operator defaults to end customer. Customer site data is captured and a private authorization key is generated Customer receives device, power is applied and the authorization key is entered. Ensemble Connector calls home and authenticates. ZTP and orchestration deliver site-specific service configuration and applications. No inventory, no truck roll, no time to revenue

Benefits of NFV Immediate & easy deployment Selection of technology Future growth Progressiveness Virtualization Possibility of technology change without hardware change