SeGW function offload 1/4 SeGW VNF SmGW VNF Virtual Switch Other VNF VNFs NFVI Network Processor Offload “programming” 1)VNF need to talk to Packet Processor.

Slides:



Advertisements
Similar presentations
IP Router Architectures. Outline Basic IP Router Functionalities IP Router Architectures.
Advertisements

© 2003, Cisco Systems, Inc. All rights reserved..
Fluffy’s Safe Right? If you want to limit a user’s functionality, don’t make them an administrator.
OpenFlow overview Joint Techs Baton Rouge. Classic Ethernet Originally a true broadcast medium Each end-system network interface card (NIC) received every.
Ing. Tomáš Halagan.  Today’s network infrastructure  NFV in nutshell  Terms and definitions of NFV  NFV High Level Architecture  Benefits of NFV.
NFV Network and Compute Intensive H/W Acceleration NFV PoC (Proof of Concept) #21
ODL Release Vehicles. Base Network Service Functions Management GUI/CLI Controller Platform Southbound Interfaces & Protocol Plugins OpenDaylight APIs.
V1.0 | 1©6WIND 2015 NON Network Video transcoding Pattern matching Network L2-L4 related Filtering IPSec NAT L4 load balancing Network L7 related HTTP.
Keith Wiles DPACC vNF Overview and Proposed methods Keith Wiles – v0.5.
1 Version 3.0 Module 8 Virtual LANs. 2 Version 3.0.
CIS 235: Networks Fall, 2007 Western State College Welcome to CIS 235 Computer Networks Fall, 2007 Prof Peterson.
Virtual Private Networking Karlene R. Samuels COSC513.
NFVRG Dallas Verification of NFV Services : Problem Statement and Challenges draft-shin-nfvrg-service-verification-01 M-K. Shin, ETRI.
Data Center Virtualization: Open vSwitch Hakim Weatherspoon Assistant Professor, Dept of Computer Science CS 5413: High Performance Systems and Networking.
dpacc framework discussion data plane
Hardware & Software Needed For LAN and WAN
Router Architectures An overview of router architectures.
Jennifer Rexford Princeton University MW 11:00am-12:20pm SDN Software Stack COS 597E: Software Defined Networking.
Router Architectures An overview of router architectures.
What's New in Windows Server 2012 Hyper-V, Part 2 Jeff Woolsey Windows Server & Cloud Microsoft Corporation VIR309.
QTIP Version 0.2 4th August 2015.
NETWORKING COMPONENTS Zach Avis. Hub A hub is a low cost way to connect two computers. A hub can also act as a repeater. When a signal comes from one.
Basic Networking Components
NETWORKING COMPONENTS By Cleve Rosser. Hubs allow large numbers of computers to be connected on a single or multiple LAN. Each computer plugs into the.
What’s new in Hyper-V in Windows Server 2012 (Part 2) Stu Fox Technical Specialist, Microsoft NZ VIR315.
Internet Addresses. Universal Identifiers Universal Communication Service - Communication system which allows any host to communicate with any other host.
1.4 Open source implement. Open source implement Open vs. Closed Software Architecture in Linux Systems Linux Kernel Clients and Daemon Servers Interface.
Acceleration descriptors requirements discussion based on China Mobile Smallcell GW Chen Wei China Mobile
25-Oct-15Network Layer Connecting Devices Networks do not normally operate in isolation.They are connected to one another using connecting devices. The.
Garrett Drown Tianyi Xing Group #4 CSE548 – Advanced Computer Network Security.
CS 4396 Computer Networks Lab Router Architectures.
Networking and internetworking devices. Repeater.
BoF: Open NFV Orchestration using Tacker
Networking Components BY: JOSON ABRAHAM LTEC 4550.
Planning and Implementing a Basic SOHO Network using Network Segmentation COMP 316.
 A hub is a central connecting device in a network.  Each node is connected directly to the hub.  They receive a data packet from one node and send.
Virtio-IPsec-LA PoC Implementation
Ryu Overview 2014/11/25 晁鍾義 Tony. What is Ryu ? Component and Ryu What is component ? Component and libraries in the Ryu and description Ryu Architecture.
Sponsored by the National Science Foundation A Virtual Computer Networking Lab Mike Zink, Max Ott, Jeannie Albrecht GEC 20, March 24 th 2015.
Network Virtualization Sandip Chakraborty. In routing table we keep both the next hop IP (gateway) as well as the default interface. Why do we require.
Networking Components Quick Guide. Hubs Device that splits a network connection into multiple computers Data is transmitted to all devices attached Computers.
VIRTUAL NETWORK PIPELINE PROCESSOR Design and Implementation Department of Communication System Engineering Presented by: Mark Yufit Rami Siadous.
SDN and Beyond Ghufran Baig Mubashir Adnan Qureshi.
Course Description/001 Objectives in This Course 1. Understanding components in computer networks - What are the major network hardware components? - What.
Network Virtualization Ben Pfaff Nicira Networks, Inc.
VPN’s Andrew Stormer COSC 356 Fall What is a VPN? Acronym – Virtual Private Network Acronym – Virtual Private Network Connects two or more private.
Chen Wei China Mobile Acceleration descriptors requirements discussion based on China Mobile Smallcell GW Chen Wei China Mobile.
SDN challenges Deployment challenges
Chapter 4 Introduction to Network Layer
VDP extension for SR-IOV
April 28, 2017 SUMIT MAHESHWARI INES UGALDE
TLS Receive Side Crypto Offload to NIC
Cisco Latest Real Exam Study Questions - Cisco Dumps
Virtio Inline Accelerator
Chapter 4 Introduction to Network Layer
Firewalls Routers, Switches, Hubs VPNs
Open vSwitch HW offload over DPDK
Data collection methodology and NM paradigms
Network Hardware and Protocols
Reprogrammable packet processing pipeline
Graph 2x + 4y = 16 by finding the x and y intercepts.
Chapter 15. Connecting Devices
Update Summary of DPACC docs
Networks Hardware.
Your Programmable NIC Should Be a Programmable Switch
Flow Processing for Fast Path & Inline Acceleration
Update Summary of DPACC docs
Latest Update DPACC Use-cases
Latest Update DPACC Use-cases
Figure 3-2 VIM-NFVI acceleration management architecture
Presentation transcript:

SeGW function offload 1/4 SeGW VNF SmGW VNF Virtual Switch Other VNF VNFs NFVI Network Processor Offload “programming” 1)VNF need to talk to Packet Processor to do the job on its behalf 2)Protocol can be OpenFlow or Netconf or…. 3)HW independent API can probably be defined 4)Should happen without checking if hardware supports it

SeGW function offload 2/4: path change SeGW VNF SmGW VNF Virtual Switch Other VNF Network Processor VNFs NFVI 1)If hardware fully supports program then full offload 2)If partial offload, offload whatever hardware supports, complements in software in vSwitch 3)Is it a Forwarding Graph change ? 4)Lawfull intercept in hardware ?

SeGW function offload 3/4 SeGW VNF SmGW VNF Virtual Switch Other VNF VNFs NFVI Network Processor Offload “programming” 1)VNF need to talk to Packet Processor to do the job on its behalf 2)Protocol can be OpenFlow or Netconf or…. 3)HW independent API can probably be defined 4)Should happen without checking if hardware supports it Virtual Switch

SeGW function offload 4/4 SeGW VNF SmGW VNF Virtual Switch Other VNF VNFs NFVI Network Processor 1)VNF need to talk to Packet Processor to do the job on its behalf 2)Protocol can be OpenFlow or Netconf or…. 3)HW independent API can probably be defined 4)Should happen without checking if hardware supports it Virtual Switch

SeGW Crypto offload: with or without HW SeGW VNF SmGW VNF Virtual Switch Other VNF VNFs NFVI NIC 1)VNF receives encrypted IPSec, leverages synthetic device for decryption 2)Crypto front end passes to backend 3)Backend implements in hardware or software Decrypted IPSec traffic Crypto Accel Crypto Accel Crypto Accel-Bk Crypto Accel-Bk

SeGW Crypto by cpu instructions SeGW VNF SmGW VNF Virtual Switch Other VNF VNFs NFVI NIC Decrypted IPSec traffic Crypto Accel-Bk Crypto Accel-Bk 1)At startup, crypt Accel back-end sends crypto plugin to front end 2)VNF receives encrypted IPSec, leverages synthetic device for decryption 3)Crypto front end does the decryption in VNF Crypto Accel Crypto Accel

vRouter Forwarding Graph SmGW VNF Virtual Router Other VNF IPSec Packet Processor VNFs NFVI 1)No need of a SecGW VNF 2)VNFD describes the need of IPSec termination for SmGW 3)If hardware fully supports program then full offload 4)If partial offload, offload whatever hardware supports, complements in software in vSwitch 5)No need for standardization