Ravi Namboori - Software Defined Network Presentation

Views:
 
     
 

Presentation Description

A Presentation by Ravi Namboori,a Cisco Evangelist about Software Defined Networking.Ravi Namboori explains Software Defined Networking is not a mechanism. It is a framework to solve a set of problems. The physical separation of network control plane from the forwarding plane, and where a control plane controls several devices.

Comments

By: mblogger (43 month(s) ago)

Looking out for networking and Big data related articles, got more information at single place. Thanks!!

Presentation Transcript

Software Defined Networking:

Software Defined Networking By Ravi Namboori

Overview:

Overview Origins of SDN. What is SDN ? Original Definition of SDN. What = Why We need SDN ? Conclusion. 2

Origins of SDN:

Origins of SDN SDN Originated from Open Flow Centralized Controller Easy to Program. Change routing policies on the fly. Software Defined Networking (SDN). Initially , SDN = Separation of Control and Data Plane. Centralization of Control. Open Flow to talk to the data planes. Now the definition has changed significantly. 3

What is SDN ?:

What is SDN ? All of these are mechanisms. SDN is not a mechanism. It is a framework to solve a set of problems => Many solutions. 4

Original Definition of SDN:

Original Definition of SDN “ What is SDN ? The physical separation of network control plane from the forwarding plane, and where a control plane controls several devices. ” Directly Programmable . Agile : Abstraction control from forwarding. Centrally managed. Programmatically configured. Open standards-based vendor neutral. 5

What = Why we need SDN ?:

What = Why we need SDN ? Virtualization : Use network resource without worrying about where it is physically located, how much it is , how it is organized , etc. Orchestration : Should be able to control and manage thousands of devices with one command. Programmable : Should be able to change behavior on the fly. Dynamic Scaling : Should be able to change size , quantity . Automation : To lower OpEx minimize manual involvement Troubleshooting Reduce downtime Policy enforcement Provisioning / Re-provisioning / Segmentation of resources Add new workloads, sites, devices, and resources. 6

What = Why we need SDN ?(cont..):

What = Why we need SDN ?(cont..) Visibility : Monitor resources, connectivity Performance : Optimize network device utilization Traffic engineering / Bandwidth management Capacity optimization Load balancing High utilization Fast failure handling Multi-tenancy : Tenants need complete control over their addresses, topology, and routing , security. Service Integration : Load balancers , firewalls, Intrusion Detection System(IDS), provisioned on demand and placed appropriately on traffic path. 7

What = Why we need SDN ?(cont..):

What = Why we need SDN ?( cont..) Openness : Full choice of “how” mechanisms Modular plug-ins Abstraction : Abstract = Summary = Essence = General Idea => Hide the details. Also, abstract is opposite of concrete => Define tasks by APIs and not by how it should be done. E.g ., send from A to B. Not OSPF. 8

Conclusion:

Conclusion SDN is a framework to allow network administrators to automatically and dynamically manage and control a large number of network device, services , topology, traffic paths, and packet handling ( quality of service) policies using high-level language and APIs. Management includes provisioning, Operating, monitoring , optimizing, and managing FCAPS( faults, Configuration , accounting , performance , and security ) in a multi-tenant environment. Key : Dynamic => Quick Legacy approaches such as CLI were not quick particular for large networks. 9

PowerPoint Presentation:

10 Thank you

authorStream Live Help