Network Functions Virtualization (NFV)
Santanu Dasgupta
Sr. Consulting Engineer –Service Provider Network Architecture
2
“Network Functions” in SP Network Architecture Landscape
LTE
SmartphoneAccess
xDSL
WiFi
Smartphone PC RNC2G 3G
EthernetCE
NodeB eNodeB APSmall Cell
FAPGateways /
Service Edge
OSS/BSS
Subsystems and Control
Data Plane
Voice
Video
Data
Core Network Infrastructure
IMS
xDSL
HFC
PGW SGW 2/3G GGSN 2/3G SGSN MME ePDG eWAG PEMetro Network
Infrastructure
NAT FW IPSec DPI CGN Caching Opt MSC-S MGW A-SBC I-SBC BGCF MGCF PS / RLS DRA Video ingestion DRMVideo
Network
EMS Provisioning Analytics Billing
Radius DNS DHCP S-CSCF P-CSCF I-CSCF Trans-
coding Control Cache
Policy Parental control HLR HSS ENUM TAS SMS-C
Services
OCS MMS-C RMS HCSxDSL
DSLAMDSL/ FTTX
BNG Core Routing Metro Ethernet Biz CPE Consumer CPE Cable Modem CMTS Capacity Planning WLC SecGW HNB-GW Policy SDN Controller BGP server MetroVirtualization of “Network Functions”
Existing Hardware / Appliance
based Network Functions (NFs)
VM on x86 Server Platform
Virtualized NFs running as
Step 1: Decouple software
from underlying hardware
Step 2: Port it as a VM on
x86 Server platform running
as a Network Function
Ethernet Switches
Storage
Hypervisor
Telco Service
Providers
$$
$$
Service
Consumers
Enterprises
Public
Sector
Consumer
$$
$$
Cloud / OTT Service
Providers
IaaS
PaaS
SaaS
OTT
$$
many
networks,
technologies
and systems
massive growth
of IP traffic
$
$$
$$
$$
$$
converged and
private networks
PPPoE
IPv4
IPv6
MPLS
MPLS-TP
OTN
DWDM
ATM
SDH
xGE
tunnel
VPN
MP-BGP
ISIS/OSPF
MPLS-TE
DHCP
EOAM
IPOAM
LACP
SNMP
CLI
XML
t revenue cost $1.
Lean & Agile OTT players with
economies of scale
2.
Highly-‐automated operaEons
3.
Fast-‐paced innovaEon
1.
Complex and silo’d networks
2.
High cost to operate
3.
Lack of agility, huge Eme required to create new services
4.
ExponenEal growth of bandwidth
1.
User Experience
2.
Cloud Centric
ConsumpEon Models /
Pay-‐as-‐you-‐go
SP’s Expectation from NFV
§
NFV will help them to reduce cost (TCO)
§
NFV will bring the much needed agility in the Service Creation & delivery process
§
On-boarding a new service will be much easier with NFV
§
SP’s can now afford to go wrong – decommissioning a failed service wont be expensive
§
Services now can be scaled up and down elastically
§
NFV –
It is a Service Provider driven Initiative.
§
Initiative announced at
“SDN and OpenFlow World Congress”
, Darmstadt, Oct 2012
§
Industry Specification Group (ISG) group within ETSI
§
Not defining standards -deliver white papers and liaising with standards bodies
§
First ETSI meeting was held in January, 2013
§
Technically not related to SDN, conceptually different
§
But may utilize SDN concepts – Programmability, Orchestration
§
Type of network function mostly determine where virtualization makes sense
§
Careful analysis is required on Network Function by Network Function
NFV = Transition of network infrastructure services to run on
virtualised compute platforms – typically x86
Key Factors To Determine Potential Virtualization Targets
Packet / Data Plane Performance Requirements
Control Plane Performance Requirements
Deviation from Standard Server build (e.g. interface type, density)
Economics of On-boarding if Virtualized
Power Efficiency requirement of the System
Development, Ease of Integration, Service Elasticity Needs
1
2
3
4
5
6
8
The Fundamental Electrical Building Blocks
General Purpose Processors (x86, ARM, PPC)
•
Wide range of capabilities (including packet processing)
•
Evolving multi-core capability (10+ processors per die)
•
Support virtualization and easy to program
Network Processor Units (NPUs)
•
Designed for flexible packet processing
•
Multi-threaded (100s) / n/w acceleration / integrated memory
•
Programmable in high level languages
Fixed function ASICs
•
Very low cost
•
Integrated s/w, very efficient but relatively inflexible
Characteristics of Network Elements
High Capacity Plumbing:
(L0-3 : e.g. IPv4/v6, MPLS, VPNs, ACLs, optical devices
…
)
•
High throughput / BW
•
Many flows needing isolation, significant traffic management needed
•
Stateless functions
•
Mostly predictable traffic
•
Interface-specific functions (2-stage forwarding)
Network Services:
(L4+ : e.g. DPI, vFW, CGN, DDOS, BNG, mobility,
…
)
•
Throughput - varies
•
# of flows (traffic management) – varies
•
Stateful functions
•
Unpredictable traffic
•
No i/f-specific functions
Low compute + High BW
è
Good fit for NPU
è
Poor fit for x86/CPU
Poor fit for x86/CPU
Good fit for x86/CPU
Yes (%)
No (%)
High Compute +
10
Business CPE
Service
Appliances
(L4-L7)
Core Backbone Routing,
CE Access-Aggregation
and DC switching
Wireline GWs
Home CPE
Wireless
GWs
Network Functions – Requirements & today’s approaches
CPU
Reqs
0
10Mbps
100Mbps
1Gbps
10Gbps
100Gbps
1Tbps
10Tbps
100Tbps
1Pbps
High
Low
Distributed: CPUs + Lots of NPUs
Distributed: Lots of CPUs + NPUs
Centralized:
CPU + NPU
CPU
Centralized: CPU or SoC
Variable CPU / FPGA / NPU
OSS/BSS, subsystem
and N/W control
Mapping Back to the Service Provider Landscape
LTE
SmartphoneAccess
xDSL
WiFi
Smartphone PC RNC2G 3G
EthernetCE
NodeB eNodeB APSmall Cell
FAPGateways /
Service Edge
OSS/BSS
Subsystems and Control
Data Plane
Voice
Video
Data
Core Network Infrastructure
IMS
xDSL
HFC
PGW SGW 2/3G GGSN 2/3G SGSN MME ePDG eWAG PEMetro Network
Infrastructure
NAT FW IPSec DPI CGN Caching Opt MSC-S MGW A-SBC I-SBC BGCF MGCF PS / RLS DRA Video ingestion DRMVideo
Network
EMS Provisioning Analytics Billing
Radius DNS DHCP S-CSCF P-CSCF I-CSCF Trans-
coding Control Cache
Policy Parental control HLR HSS ENUM TAS SMS-C
Services
OCS MMS-C RMS HCSxDSL
DSLAMDSL/ FTTX
BNG Core Routing Metro Ethernet Biz CPE Consumer CPE Cable Modem CMTS Capacity Planning WLC SecGW HNB-GW Policy SDN Controller BGP server MetroEthernet Center Data
No
Appeal
No Appeal
High
Ap
pe
al
High
Appeal
Depends
H
ig
h Ap
pe
al
Very High Appeal
High Appeal
No
Ap
pe
12
The Role of SDN and Orchestration
Partial list, just a few main ones are mentioned here
Ethernet Switching Network Underlay
Hypervisor
Hypervisor
Hypervisor
NAT
Firewall
DPI
Orchestration and SDN Control Function
Storage
Server 1
Server 2
Server 3
NAT
Firewall
DPI
VM / VNF Lifecycle
Management in
End-to-end manner
Network Plumbing
to orchestrate
dynamic topologies
Configuration
Management
of the VNFs
Integration with
Other DC/POD
And the WAN
OAM,
Assurance,
Analytics
Computing
Hardware
Storage
Hardware
Network
Hardware
Hardware resources
Virtualisation Layer
Infrastructure
Virtualised
Manager(s)
VNF
Manager(s)
VNF 2
Orchestrator
OSS/BSS
NFVI
VNF 3
VNF 1
Other reference points
Virtual
Computing
Virtual Storage
Virtual Network
NFV Management and Orchestration
EMS 2
EMS 3
EMS 1
Service, VNF and Infrastructure Description
Or-Vi
Or-Vnfm
Vi-Vnfm
Os-Ma
Se-Ma
Ve-Vnfm
Nf-Vi
Vn-Nf
Vl-Ha
Cisco Confidential 14 © 2013-2014 Cisco and/or its affiliates. All rights reserved.
Major Service Providers Driving the ETSI NFV ISG
NFV Use Cases
•
Simple ones – Virtualized Route Reflector
•
Virtualized CPE for Business VPN services
•
Virtualized Mobile Packet Core
•
Virtualized Managed Services (CPE, FW, UTM
…
..)
•
Virtualized Home CPEs
•
Virtualized Gateways (BRAS, BNG, mobile gateways, Wi-Fi gateways)
16 DCI DCI PE Web VM DB VM FW WAAS
vCPE
vFW
vWAAS
L2 NID
Backhaul
End-to-End Orchestration
DCI DCI PE Web VM DB VM FW WAASvFW
vESA
vWAAS
L3 CPE /
vCPE
Backhaul
End-to-End Orchestration
Business VPN CPE in a Overlay Transport Model
Cloud IPVPN with FW and Remote
Access to Internet
§
vFW with NAT and Policy
§
vFW with IPSec/SSL Remote Access
including Remote End-Host posture
verification
CPE
CPE
CPE
Internet Router vFWSP CLOUD
Internet
Cloud-Hosted Management
Scalable, elastic, on-demand
Overlay Packet Tunnels
§
Keyed IPv6 tunnels - mesh, hub&spoke;
§
IPSec tunnels – mesh, hub&spoke if
keyed IPv6 tunnels not supported;
18
Where to Place the VNFs ?
§
Candidate location types in the network –
§
Centralized Data Centers à
Easier to manage
§
Fully Distributed – POP’s, Edge / Anchor Points / Peering locations à
Higher scale & performance
§
Hybrid – Mix of the above
§
Some factors that may need to be considered here –
§
The Use Case to deploy the VNFs
§
Cost of transporting traffic across core
§
Network Architecture / design
§
Chance of Sub-optimal routing, impact on SLA (e.g. delay)
DCI DCI PE
L2 Backhaul
vCPE
vCPE
DCI DCI Web VM DB VM FW WAASL2 Backhaul
Web VM DB VM FW WAASvCPE
vCPE
DCI DCI PEvCPE
vFW
vWAAS
L2 NID /
L2 Backhaul
Web VM DB VM FW WAASC
en
tra
lize
d
Higher Traffic Across Core
Sub-optimal routing
Higher e2e delay
Better performance / scale
More Complex to manage
Better performance / scale
More Complex to manage
D
ist
rib
ut
ed
D
ist
rib
ut
ed
w
ith
Se
rvi
ce
C
ha
in
20