ch 05 --- nfv basics

NDI Communications - Engineering & Training

Software Defined Networking (SDN)

Chapter 5 – NFV Basics

Chapter Content

Basics & Network architecture

NFV Infrastructure

NFV Management and Orchestration (MANO)

Common Systems & Vendors

Motivation for NFV

Software Implementation of the Network

Network Function Modules

Implementation in Virtual Machines

Standard APIs Between Modules

NFV Architecture

Virtualized Network Functions (VNFs)

VNF VNF VNF VNF VNF

NFV Infrastructure (NFVi)

VirtualComputing

VirtualStorage

VirtualNetwork

Virtualization Layer

Hardware Resources

VirtualComputing

VirtualStorage

VirtualNetwork

NFVManagement

and Orchestration

End-to-End Network Service

NF1 NF2 NF3EndPoint1

EndPoint2

InfrastructureNetwork 1



Network Function Forwarding Graph (NF-FG)

End to End Network Service

End-to-End Network Service

VNF2A

VNF-FG-2


VNF2B

VNF2A

VNF2A

EndPoint1

EndPoint2

VNF2C

HDHD

HDHD

HD NFVI-PoP

Physical Link

Logical Link

Virtualization

Chapter Content


NFV Infrastructure



Architectural Functional Blocks


Hardware Resources

VirtualComputing

VirtualStorage

VirtualNetwork

OSS/BSS

NFV Managementand Orchestration

Orchestrator

OrchestratorOrchestratorOrchestratorVNFManager(s)

Virtual Infrastructure

Manager(s)


Manager(s)


Manager(s)


Manager(s)


VNF1 VNF2 VNF3

EMS1 EMS2 EMS3

VirtualComputing

VirtualStorage

VirtualNetwork

Service, VNF & Infrastructure Descryprion

NFVI

Vn-Nf

VI-Ha

Os-Ma

Se-Ma

Ve-Vnfm

Nf-Vf

Or-Vnfm

Vi-VnfmOr-Vi

Virtualized Network Function (VNF) & Element Management System

A Virtual Network Function

(VNF) is a virtualization of

a network function in a

legacy non-virtualized

network.

A VNF can be composed of multiple internal components. For

example, one VNF can be deployed over multiple VMs, where

each VM hosts a single component of the VNF.

The Element Management System (EMS) performs the typical

management functionality for one or several VNFs.

NFV Infrastructure

The NFV Infrastructure is the

totality of all hardware and

software components which build up

the environment in which VNFs are

deployed, managed and executed.

NFV differentiates the following two types of networks:

NFVI-PoP network: the network that interconnects the computing

and storage resources contained in an NFVI-PoP.

Transport network: the network that interconnects NFVI-PoPs,

NFVI-PoPs to other networks owned by the same or different

network operator

The Virtualization Layer

The virtualization layer is

responsible for:

Abstracting and logically

partitioning physical

resources, commonly as a

hardware abstraction

layer.

Enabling the software that

implements the VNF to use

the underlying virtualized

infrastructure.

Virtualized Infrastructure Manager(s)

Resource management, in charge of:

Inventory of software

Allocation of virtualisation enablers

Management of infrastructure resource

Operations, for:

Visibility into and management of the NFV

infrastructure.

Root cause analysis of performance issues from

the NFV infrastructure perspective.

Collection of infrastructure fault information.

Collection of information for capacity planning,

monitoring, and optimization.

Orchestrator & VNF Manager(s)

The Orchestrator is in charge of the

orchestration and management of NFV

infrastructure and software resources, and

realizing network services on NFVI

A VNF Manager is responsible for VNF

lifecycle management (e.g. instantiation,

update, query, scaling, termination).

Reference Points (1)


Hardware Resources

VirtualComputing

VirtualStorage

VirtualNetwork

OSS/BSS


Orchestrator



Manager(s)


Manager(s)


Manager(s)


Manager(s)


VNF1 VNF2 VNF3

EMS1 EMS2 EMS3

VirtualComputing

VirtualStorage

VirtualNetwork


NFVI

Vn-Nf

VI-Ha

Os-Ma

Se-Ma

Ve-Vnfm

Nf-Vf

Or-Vnfm

Vi-VnfmOr-Vi

Virtualisation Layer - Hardware Resources -(Vl-Ha):• Create an execution environment for

VNFs• Collect relevant hardware resource state

information for managing the VNFs

VNF - NFV Infrastructure (Vn-Nf):• This reference point represents the execution environment

provided by the NFVI to the VNF. • It is in the scope of NFV in order to guarantee hardware

independent lifecycle, performance and portability requirements of the VNF.

Orchestrator - VNF Manager (Or-Vnfm):• Resource related requests, e.g. authorization,

validation, reservation, allocation, by the VNF Manager(s).

• Sending configuration information to the VNF manager, so that the VNF can be configured appropriately to function within the VNF Forwarding Graph in the network service.

• Collecting state information of the VNF necessary for network service lifecycle management.



Hardware Resources

VirtualComputing

VirtualStorage

VirtualNetwork

OSS/BSS


Orchestrator



Manager(s)


Manager(s)


Manager(s)


Manager(s)


VNF1 VNF2 VNF3

EMS1 EMS2 EMS3

VirtualComputing

VirtualStorage

VirtualNetwork


NFVI

Vn-Nf

VI-Ha

Os-Ma

Se-Ma

Ve-Vnfm

Nf-Vf

Or-Vnfm

Vi-VnfmOr-Vi

NFVI - Virtualized Infrastructure Manager (Nf-Vi): • Specific assignment of virtualized resources in response

to resource allocation requests. • Forwarding of virtualized resources state information. • Hardware resource configuration and state information

(e.g. events) exchange.

Virtualised Infrastructure Manager - VNF Manager (Vi-Vnfm) • Resource allocation requests by the VNF Manager.• Virtualised hardware resource configuration and state

information (e.g. events) exchange.

Orchestrator - Virtualised Infrastructure Manager (Or-Vi): • Resource reservation and/or allocation requests by

the Orchestrator. • Virtualised hardware resource configuration and

state information (e.g. events) exchange.



Hardware Resources

VirtualComputing

VirtualStorage

VirtualNetwork

OSS/BSS


Orchestrator



Manager(s)


Manager(s)


Manager(s)


Manager(s)


VNF1 VNF2 VNF3

EMS1 EMS2 EMS3

VirtualComputing

VirtualStorage

VirtualNetwork


NFVI

Vn-Nf

VI-Ha

Os-Ma

Se-Ma

Ve-Vnfm

Nf-Vf

Or-Vnfm

Vi-VnfmOr-Vi

Service, VNF and Infrastructure Description - NFV Management and Orchestration (Se-Ma):• retrieving information

regarding the VNF deployment template,

• VNF Forwarding Graph, service-related information, and NFV infrastructure information models.

OSS/BSS - NFV Management and Orchestration (Os-Ma):• Requests for network service lifecycle management. • Requests for VNF lifecycle management. • Forwarding of NFV related state information. • Policy management exchanges. • Data analytics exchanges. • Forwarding of NFV related accounting and usage records.

NFVI capacity and inventory information exchanges VNF/EMS - VNF Manager (Ve-Vnfm):• Requests for VNF lifecycle management. • Exchanging configuration information.• Exchanging state information necessary for network

service lifecycle management.

Chapter Content


NFV Infrastructure



MANO - Management and Orchestration

General Management and Orchestration Requirements

VNF requirements:

General Management and Orchestration Requirements Related to

VNF

Management and Orchestration Requirements Related to VNF

Maintenance Tasks

Management and Orchestration Requirements Related to Scaling

Requirements for VNFD and VNF-FGD Template

General Requirements Related to VNF Forwarding Graphs

Requirements Related to VNF Creation and Termination

Requirements Related to Scaling

Functional Requirements on Infrastructure

Generic Domain Requirements

Hypervisor Requirements

Compute Resource Requirements

Network Resources Requirements

Chapter Content


NFV Infrastructure



VNF Manager(s)y

VNF Manager(s)y

OSS/BSS

EMS 1

VNF 1

EMS N

VNF N

Virtual Virtual Comput

e

Virtual Storage

Virtual Network

Compute, Storage & Network Hardware

Service, VNF and Infrastructure Description

NFVOrchestrator

Management and Orchestration (MANO)

NFVI


VNF Manager(s)

Virtualized Infrastructure

Manager(s)

. . .

. . .

Vendor’s

OSS/BSS ProvidersOSS/BSS Providers

Orchestrator Providers

Orchestrator ProvidersVNF ProvidersVNF Providers

NFV Platform Providers

NFV Platform ProvidersServer Hardware

ProvidersServer Hardware

Providers

OPEN DAYLIGHT

Open vSwitch

Open vSwitch, sometimes abbreviated to OVS, is a production-quality open

source implementation of a distributed virtual multilayer switch.

The main purpose of Open vSwitch is to provide a switching stack for hardware

virtualization environments, while supporting multiple protocols and standards

used in computer networks

OpenStack

OpenStack is a cloud operating system that controls large

pools of compute, storage, and networking resources

throughout a datacenter, all managed through a dashboard

that gives administrators control while empowering their

users to provision resources through a web interface.

FloodLight

Floodlight Is an Open SDN Controller

WINDRIVER

Wind RiverCarrier Grade

CommunicationsServer (CGCS)

Carrier Grade Linux

Open Virtualization Profile

Carrier Grade Accelerated vSwitch

Carrier Grade Middleware

Carrier Grade OpenStack

VNFs

OSS / BSS

vEPCvBRAS vCPE Other

Overture Ensemble OSA™ Orchestration and Control

Ensemble Service Orchestrator (ESO)Ensemble Service Orchestrator (ESO)Ensemble Network Controller (ENC)Ensemble Network Controller (ENC)

Service Provider Access Network

Big Switch Controller

Big Network Controller is a

commercial OpenFlow

controller based on Project

Floodlight that is the

foundation for Open

Software Defined Networks

(SDN),

Use Cases

Cloud:

NFV infrastructure as a service (NFVIaaS) like IaaS

Virtual Network Functions (VNFs) as a service (VNFaaS) like SaaS

VNF forwarding graphs (Service Chains)

Virtual Network Platform as a Service (VNPaaS) like PaaS

Mobile:

Virtualization of the Mobile Core Network and IMS

Virtualization of Mobile Base Station

Data Center:

Virtualization of CDNs

Access/Residential:

Virtualization of the Home environment

Fixed Access NF

Summary

Yoram Orzach

[email protected]

Thank You!!!

Coming soon LIVE on our NEW e-Learning portal

ch 05 --- nfv basics

Internet