+ All Categories
Home > Documents > Network Virtualization Sandip Chakraborty. In routing table we keep both the next hop IP (gateway)...

Network Virtualization Sandip Chakraborty. In routing table we keep both the next hop IP (gateway)...

Date post: 18-Jan-2018
Category:
Upload: byron-oneal
View: 213 times
Download: 0 times
Share this document with a friend
Description:
R1-eth0 R1-eth1 R2-eth0 R3-eth0 R4-eth0 1.A router may have multiple interfaces ! 2.An interface may have multiple routers connected to it ! 1.A router may have multiple interfaces ! 2.An interface may have multiple routers connected to it ! Finding a next hop essentially means finding a L3 device along with its L2 connectivity – The policies and access control get added up when we talk about routing in ISP domains! Essentially, the routers need to do a lots of “CONTROL” operations! Finding a next hop essentially means finding a L3 device along with its L2 connectivity – The policies and access control get added up when we talk about routing in ISP domains! Essentially, the routers need to do a lots of “CONTROL” operations! The Life of a Network Administrator is very tough !!!
19
Network Virtualization Sandip Chakraborty
Transcript
Page 1: 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.

Network Virtualization

Sandip Chakraborty

Page 2: 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.

• In routing table we keep both the next hop IP (gateway) as well as the default interface. Why do we require both?

Page 3: 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.

R1-eth0

R1-eth1

R2-eth0

R2-eth0 R3-eth0

R4-eth0

1. A router may have multiple interfaces !2. An interface may have multiple routers

connected to it !

Finding a next hop essentially means finding a L3 device along withits L2 connectivity – The policies and access control get added upwhen we talk about routing in ISP domains! Essentially, the routers need to do a lots of “CONTROL” operations!

The Life of a Network Administrator is very tough !!!

Page 4: 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.

Can we get a simple view of networking system?

Page 5: 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.

Logical Similarity between Networks and Operating System

Applications

OS Functionalities

Hardware ResourcesMemory, CPU, I/O Devices

System Calls

Applications – Process Communications

Network Services

Hardware ResourcesPhysical Links, NICs, Switches

Service Primitives

Operating Systems Networks

Page 6: 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.

Networks and Operating System – Where they Differ?

Applications

CENTRALIZEDOS Functionalities

Hardware ResourcesMemory, CPU, I/O Devices

System Calls

Applications – Process Communications

Network Services

Hardware ResourcesPhysical Links, NICs, Switches

Service Primitives

Operating Systems Networks

Page 7: 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.

Networks and Operating System – Where they Differ?

Applications

OS Functionalities

Hardware ResourcesMemory, CPU, I/O Devices

System Calls

Applications – Process Communications

Network Services

Hardware ResourcesPhysical Links, NICs, Switches

Service Primitives

Operating Systems Networks

DISTRIBUTEDCONTROLLED

Page 8: 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.

Networks and Operating System – Where they Differ?

Applications

OS Functionalities

Hardware ResourcesMemory, CPU, I/O Devices

System Calls

Applications – Process Communications

Hardware ResourcesPhysical Links, NICs, Switches

Service Primitives

Operating Systems Networks

DISTRIBUTEDCONTROLLED

Network isCompletely Distributed andUnsynchronized

Page 9: 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.

How OS Manages Centralized Control over Distributed Architecture?

Page 10: 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.

Network Virtualization – Decoupling Infrastructure and Service Providers

Infrastructure Providers:

Maintains routers, links, data centres, and other physical infrastructure

Service Providers:

Offer end-to-end services to users

Page 11: 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.

Example from Other Sectors

• Airport authority provides the infrastructure, Airline operators “rent” it and provide end-to-end services.

Page 12: 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.

Solution – Network VirtualizationA

A

A

A

A

AB

B

B B

B B

Page 13: 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.

Packet Forwarding with Network Virtualization

Competing ISPs with different goals must coordinate

Single service provider controls end-to-end path

Today’s Network Network Virtualization

Page 14: 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.

Network Function Virtualization (NFV)

• Network Functions:– Routing / Forwarding– Access Control– Traffic shaping – …

• Implement network functions in software• Load the software functions on-demand to the

hardware

Page 15: 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.

SOFTWARECONTROLLER

Switch A Switch B Switch C

Flow 1VOICE

Flow 2VIDEO

Policy VOPolicy VOPolicy VO Policy VIPolicy VIPolicy VI

Page 16: 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.

Putting These All Together – Software Defined Networking (SDN)

Page 17: 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.

SDN Architecture – Control and Data

Page 18: 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.

Control Logic

Page 19: 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.

Network Administration – Things are Much Simple Now !!

• Fed the control logic (routing logic like routing policies, QoS control, Access control list etc) to the controller

• Controller will convert that logic to switch configuration (through Network virtualization)


Recommended