Acronym Soup

2 © 2013 Emulex Corporation

Network Function Virtualization (NFV)

Network Function Virtualization (NFV) – an alternative design approach for building complex telecom or service provider solutions that virtualizes entire classes of functions into building blocks that may be connected, or chained, together to create services and deployed on industry standard hardware. Examples include border gateways and routers, session controllers and voice services, security appliances and application delivery systems.

NFV

3 © 2013 Emulex Corporation

Building NFV SolutionsIndustry Call to Action for Telecom Networking

Source: AT&T, BT, CentryLink, China Mobile, Colt, Deutsche Telekom, KDDI, NTT, Orange, Telefonica, Telecom Italia, Telstra, Verizon

4 © 2013 Emulex Corporation

High Performance Packet Processing for Network Function Virtualization

New paradigm for carrier networks

Industry trends towards NFV– Commercial off-the-shelf IT platforms can host

a variety of network applications– New virtualization technologies allows

abstraction and automation– Software Defined Networking benefits NFV

New products for– Mobile network nodes– Virtualized home environments– Tunneling– Traffic analysis– Converged network-wide functions– Application-level optimization– Security functions

Reduced network costs, increased time to market, platform for innovation

Co

ntr

ol P

lan

e A

pp

lian

ce

Hypervisor

x86 Serversor MicroServers

Da

ta P

lan

e A

pp

lian

ce 1

…

Da

ta P

lan

e A

pp

lian

ce n

Ne

xt G

en

Se

rvic

es

1

…

Se

rvic

es

on

De

ma

nd

Emulex NVeX

SU

RF

Hyper-V

5 © 2013 Emulex Corporation

Network Function Virtualization (NFV)

Software defined networking (SDN) – an emerging software architecture for networking infrastructure that separates the data plane, control plane and application plane and centralizes their management for greater flexibility, lower cost, improved process efficiency and simplified management.

SDN

6 © 2013 Emulex Corporation

Software Defined Network (OpenFlow)

The controller acts as an interface between the physical network and the SDN layer

7 © 2013 Emulex Corporation

SDN versus/with OVN

• Affects the Network infrastructure and how traffic is forwarded

• Switch Vendors already invested a lot

• Users need specialized Hardware and a SDN Controller

• Admins can easily manage traffic flows from a single GUI

• Affects the Hypervisor and how VMs communicate with each other

• VXLAN = VMware• NVGRE = Windows• No special Hardware

needed but Emulex/Skyhawk boosts performance

• Emulex is lead Vendor for HW offload for both Microsoft and VMware

Software Defined Networking

Virtual Network FunctionsOverlay Networks

8 © 2013 Emulex Corporation

Ecosystem Overview – SDNVirtual Networks Vs. OpenFlow

SDN is the network hypervisor layer

SDN manages two classes of devices– Standard network object (forwarding tables in switches, routers, etc.)– New VNF objects such as servers, vSwitches, and VNF NICs– Emulex provides VNF NICs

Standard Network Objects

Net

wor

kO

bjec

ts

FlowDatabase

Player n

QuantumOpenStack

Servers, vSwitches, VEB, NICs

Ope

nFlo

w

VN

F A

PI

Net

wor

kH

yper

viso

rLa

yer

9 © 2013 Emulex Corporation

Virtual Network Functions

Virtual Network Functions (VFN) or Overlay Networks (OVN) – a layered networking protocol that virtualizes a network on top of one or more other networks typically using encapsulation and tunneling techniques to increase scalability, portability of devices or offer features/services not available in the original network. Examples include SST, NV-GRE, VxLAN and the internet protocol (IP)

VNF=OVN

10 © 2013 Emulex Corporation

Virtual Network Functions/Overlay Networks

Having the VM Identifier equal to the identifier makes it difficult to have a true virtual environment

Current Networks

Problem: VM Identifier = LocationSubnet B

10.10.11.XSubnet A10.10.10.X

192.168.3.25 192.168.3.23192.168.3.24

Hypervisor

Need to scale beyond the 4,096 VLAN limitation

As virtual environments grow, limiting VM mobility to a single segment creates inefficiencies

Currently VMs can be easily moved inside a network segment

Overlay Networks

192.168.3.23192.168.3.25192.168.3.23 192.168.3.24

Solution: VXLAN, NVGRE, and/or…

Overlay Network 192.168.3.X

Hardware offload in the server is required for lower cost overlay network designs

No complex network reconfigurations or vendor lock-in

Scales to millions of unique identifiers

Preserves all investment in networking engineering & design

11 © 2013 Emulex Corporation

Where the OCe14000 “Fits In”

Outer MAC DA

Outer MAC SA

Outer 801.1Q Tag

Outer IP DA

Outer IP SA

Outer UDP

VNI VXLAN ID (24 bits)

Inner MAC DA

Inner MAC SA

Optional Inner 802.1Q Tag

Optional Ethernet L2

Frame

Outer MAC

Outer IP Header (DA)

GRE Header (Includes 24 Bit TNI)

Inner MAC

Inner IP Header (CA)

TCP Header TCP User Data

Emulex OCe14000 Encapsulates VXLAN & NVGRE Packets

12 © 2013 Emulex Corporation

SDN and Overlay Network Collateral

White papers:– Overlay Networks – VMware VXLAN– Overlay Networks – Microsoft NVGRE

Tech Brief:– VMware VXLAN compatible hardware offload and integrated API technology—

scalable, secure and L3 support

Adobe Acrobat Document

Adobe Acrobat Document

Adobe Acrobat Document

Click Here To Open

Click Here To Open

Click Here To Open