معرفی شبکه های مبتنی بر نرم افزار software defined networks...

معرفی شبکه های مبتنی بر نرم افزارSoftware Defined Networks

دانشگاه علم و صنعت ایران

دانشکده مهندسی کامپیوتر

دکتراحمد اکبری – دکتر محمود فتحی – دکتر حسین غفاریان

مهندس شتابی

1393بهمن

دانشکده مهندسی کامپیوتر دانشگاه علم و صنعت ایران 3

دانشگاه علم و صنعت ایراندانشکده مهندسی کامپیوتر

:1368تاسیستعداد اعضای هیات علمی

2استاد تمام

10دانشیار

8استادیار

4کارشناس آموزش

:بکهQوعات شQا موضQاتی بQاهای تحقیقQداد فضQ9تع آزمایشگاه تحقیقاتی

مرکز تحقیقات فناوری اطالعات +


زمینه های همکاریهای گذشته و فعلی با توانیر

فاز نخست بازطراحیWAN( 1388-1389 صنعت برق) بکهQرح کالن شQه طQارائWAN ایQه نیازهQه بQا توجQرق بQنعت بQداده ص

فعلی )در حال اجرا( گاهیQاور دانشQوان مشQه عنQرق بQنعت بQه داده صQویت در کمیتQعض

کمیته


فناوریهای نوین حوزه شبکه های کامپیوتری

Cloud computing

Software Defined Network


Cloud computing رایانش ابری


سرویس های رایانش ابری


مجمQوع رشQد رونQد از سیسQکو بیQنی پیش 2018 تQا 2013ترافیQک مراکQز داده در سQالهای


رشد ابزارهای متصل به اینترنت

Internet of things ( Cloud Networks Fog Networks)


SDNاهداف شبکه های مبتنی بر نرم افزار

کاهش هزینه های عملیاتی شبکهانعطاف پذیری در حوزه مدیریت شبکهکاهش زمان بروز رسانی در مجموعه ابزارهای شبکهمدیریت سراسری و یک پارچه شبکهکاهش هزینه های سخت افزارهای ارتباطی شبکه


معماری مسیریابها و سوئیچهای فعلی

Specialized Packet Forwarding Hardware

OperatingSystem

Feature

Feature


توزیع شدگی روندهای کنترلی در معماری فعلی ابزارهای شبکه


چهره جدید شبکه

14

Kernel OS+

Specialized Packet Forwarding Hardware

Feature Feature

Closed Platform

Standard hardware

OS / Controller

3rd party App

Open Platform

Proprietary interface

3rd party App

Public APIs

اختصاصی 1. افزار سخت

اختصاصی 2. رابط

کند 3. نواوری سرعت

استاندارد 1. افزار سخت

پویا – 2. سیستم باز استانداردهای

سریع 3. نواوری سرعت

های شبکه SDNمعماری

کامپیوتری های شبکه معماری

سنتی های شبکه معماری

15

Unified Data and Control

Control / Data plane separation

سنتی های شبکه معماری

versus

Add feature here?!?!

Control + Data Separation

Controller

DataControl

هستند / کنترل و داده سطوح گیری تصمیم مسئول روتر سوئیچ سنتی، روشدارد را دیتا ارسال کار سوئیچ و شود می انجام کنترلر توسط یابی مسیر و گیری وتصمیم شده جدا هم از دیتا و کنترل .سطوح

AppApp App

های شبکه SDNمعماری

16

Custom Hardware

Custom Hardware

Custom Hardware

Custom Hardware

Custom Hardware

OS

OS

OS

OS

OS

Network OS

Feature Feature

Feature Feature

Feature Feature

Feature Feature

Feature Feature

Feature Feature

The network is changing

17

Feature Feature

Network OS

1. Open interface to packet forwarding

3. Consistent, up‐to‐date global network view2. At least one Network OS

probably many.Open- and closed-source

Software Defined Network (SDN)

PacketForwarding

PacketForwarding

PacketForwarding

PacketForwarding

PacketForwarding

Network OS

Network OS Examples

18

Network OS

Network OS Examples

19

Software Defined Network (SDN)

20

SDN - Layered Abstraction

Infrastructure Layer

SD

N A

rchit

ect

ure

Control Layer

Application Layer

Separate control and data plane; abstract control plane of many devices to one

Open standard-based programmatic access to infrastructure

Deliver open programmable interfaces to automate orchestration of network services



Open standard-based programmatic access to infrastructure





Open standard-based programmatic access to infrastructure Network Device Network DeviceNetwork Device

Control & Data Plane Programmable Interface )e.g., OpenFlow(

Network ApplicationsNetwork ApplicationsSDN Applications

Business ApplicationsBusiness ApplicationsBusiness Applications

)e.g., OpenStack, CloudStack(

Cloud Orchestration

SDN Controller

Programmable Open APIs

Infrastructure Layer

SD

N A

rchit

ect

ure

Control Layer

Application Layer


23

OpenFlow Basics

OpenFlow Basics

25

OpenFlow Basics

26

OpenFlow Basics

OpenFlow Flow Table Entry

27

OpenFlow Basics

Flow Table Examples

28

OpenFlow Basics

Flow Table Examples

29

OpenFlow Basics

How a packet is processed and forwarded in an OpenFlow switch

30

OpenFlow Basics

31

OpenFlow Basics

32

OpenFlow Basics

33

OpenFlow Basics

OpenFlow-only switches: support only OpenFlow operation

34

OpenFlow Basics

Comparison of OpenFlow Specifications

35

OpenFlow Basics

Industry Standards and Forums

36

OpenFlow Basics

Example of OpenFlow-Compliant Switches

37

SDN Applications Scenarios


• Scenario 1: Load balancing for better network usage o Use cases - Google

• Before using SDN/OpenFlow, network utilization rate ~ 30% • After adopting SDN/OpenFlow, network utilization rate above 90% • Reason: Without global network information, many flows may be unevenly routed to certain segments of the

network causing network congestion • SDN based network can route flows based on the global NIB to intelligently distribute the flows evenly on all

available segments – increased network utilization • Google applied SDN/OpenFlow in their WAN and data center network

39


Current network taking long time for propagate events to every network nodes SDN/OpenFlow adjusting network updates at much faster (milliseconds) speed – maximizing network

usability and throughputs

• Scenario 2: Fast network adaption and traffic allocation o Use case: Different time using different links for better network usage and OPEX (Policy based

routing) • At day time work hours, route traffic to shortest, low latency path (SLIP), and route the traffic to longer

(cheaper) alternative path (LAP) during the night and off working hours

40


• Scenario 3 o Use case A: Energy saving network (Green network)

• Distribute network traffic evenly for maximum throughputs/low latency during day time working hours, • Distribute network traffic to certain segments and shut-down others for energy saving during late night off

peak hours • Dynamically activate network segments when network traffic picking up

o Use case B: Application Driven network • Adjusting on-demand to match application needs • With less number of applications running, the network traffic can be concentrated to few links and

intelligently re-distribute the network traffic when needed for better QoS • Dynamically configure network to fit applications with application dependent flow based routing policy for

optimal performance

41


• Scenario 4: Unified network control and network flattening

– SDN/OpenFlow routing vector dimension increased from 15 (OF 1.0) to 36 (OF1.3) and extensible, covering routing parameters on multiple layers (L2/L3/L4/etc.)

– Data networking could be flattened – one path may achieve routing on multiple layers – reducing network complexity/COPEX, increasing network efficiency, etc.

42


• Scenario 5: Open and programmable network, optimized for applications – SDN provides southbound API for data forwarding and northbound API do network applications – allowing

network be changed by application programs as software to optimally support applications

o Use case A: Programmable network resources • Network resources can be programmed to allocate/release , e.g. on-demand bandwidth, etc. allocated

and adjusted • Applications can programmability optimize their resource utilization

o Use case B: Automated network management • Programmable network can reduce the complexity and cost of network deployment and management,

increase the speed of service deployment, reduce human involvement and error, make network management more automatic, etc.

43


• End-to-End QoS o SDN is based on logically centralized network control and can achieve globally optimized control

– making end-to-end QoS possible

• Fast network adjustment and recovery o SDN can timely provide alternative optimal path, avoid network trouble spots with fast network

recovery at the speed of milliseconds

• Multi-network federation o SDN/OpenFlow based core network can normalize and synchronize network signaling in multi-

network federation (e.g. tagging normalization, etc. ）

44


Software Defined Networking coursehttps://www.coursera.org

• Dr. Nick Feamster• Georgia Institute of Technology• Starts in 3 months• Eligible for Verified Certificate

• 8 weeks of study• 7-10 hours/week• English

https://www.coursera.org/instructor/feamster

https://www.coursera.org/instructor/feamster

https://www.coursera.org/gatech

https://www.coursera.org/gatech


Software Defined Networkinghttps://www.coursera.org/course/sdn

• Course Syllabus• This course will cover 8 modules (one per week).• Module 1: History and evolution of SDN• Module 2: Control and data plane separation• Module 3: Control Plane• Module 4: Network Virtualization• Module 5: Data Plane• Module 6: Programming SDNs• Modules 7: Verification and Debugging• Module 8: Use Cases and Looking Forward


با تشکر از حسن توجه شما

معرفی شبکه های مبتنی بر نرم افزار software defined networks...

Documents

actual network

network osprobably

software defined network

open interface

multiple devices

unified data

uptodate global network

programmatic access