software defined network

Software Defined NetworkBy:

Deeptiman MallickIT135018

7th SemesterInformation Technology

Contents

• The need for a new Network Architecture• Introducing Software Defined Network (SDN)• Understanding the Technology• Looking at the benefits and Use Cases of SDN• Key SDN Consideration and Requirements• Important facts about Evaluating SDN solution• Conclusion

The need for a new Network Architecture

• Changing traffic patterns• The “Consumerization of IT”• The rise of Cloud Service• Big Data means more Bandwidth

Introducing Software Defined Network

• SDN means, Networks are controlled by software application and SDN controller • It removes the use of traditional network management consoles and

commands• The traditional Networking requires a lot of administrative overhead

which can’t be managed on large scale• So, the software based automated control of SDN is much more

flexible than old rigid management consoles and CLIs.• It’s an open technology focusing mostly on integrations and extensions


Image downloaded from: www.cisco.com/go/sdn


SDNTraditional Rigid N/W

Complexity Inconsistent policy Inability to Scale

S/W Defined N/W

Server virtualization and cloud n/w

Policy based automation


Image downloaded from: www.cisco.com/go/sdn

Understanding the Technology

SDN CONTROLER

SDN APPS

SDN DATAPATH

This is the thing that performs specified operation.

Programmatically communicates n/w behavior to controller

The heart of the SDN.The thing which is

being programmedSDN CDPI

A program that acts as logical

Networking Device

Provides programmatic control, statistic reporting

and event notification

SDN NBI

Enables direct expression of network behavior and

requirements


• An SDN Controller is the central repository of policy and control instructions for the network or application infrastructure.• It integrates the features of different components of SDN with API and

provides network information and analytics across all network resources• When we are writing the control software to manage different

resources and operations in a n/w, we are actually programming the controller by using the APIs integrated to it.


• The OpenFlow protocol is the fundamental element for building an SDN solution.• According to OpenFlow an SDN Architecture needs to be:

Directly Programmable Centrally Managed Programmatically Configured Open standard-based and vendor-neutral

Looking at the benefits and Use Cases of SDN

• SDN automation leads to Business Agility• A new approach to network policy, which is:• An easier, application-focused way of expressing Policy• Improved automation• Consistency• Extensible Policy model • Centralized Policy management with distributed control points

Looking at the benefits and Use Cases of SDN

• Some popular use cases of SDN are• DevOps• Big Data and Everything-as-a-Service• Mobility app and Internet of Things (IoT)

Key Considerations and Requirements

• The SDN promises a new era of centrally managed, policy based automation tools that could accelerate network management and optimization• So, to reach those goals we need to be aware about certain

considerations and requirements, like• Focusing on Applications• Keeping Things Open (using open protocols, Open APIs, Open Architecture

and open source technology)

Important facts about Evaluating SDN solution• Programming rather than managing manually• Making for easier policy implementation• Supporting Multivendor Ecosystem• Understanding the Importance of the Controller• Making use of Cloud Automation Tools• Considering Extensible Architecture• Choosing an Open Source SDN Platform carefully

Conclusion

This is a new and advanced as well as very useful technology. Not much research are done on this field. So there are vast opportunities for Research Scholars, Network Programmers and Cloud Application developer.

Reference

Reference• “Reactive, Proactive, Predictive: SDNModels|F5DevCentral”. Devcentral.f5.com. Retrieved2014-01-23.• Wikipedia, “Software Defined Networking” [https://en.wikipedia.org/wiki/software-defined_networking] • Kreutz, Diego and Ramos, Fernando and Verissimo, Paulo(2013). “Towards secure and dependable software defined

networks”. Proceedings of the second ACM SIGCOMM workshop on Hot topics in software defined networking. pp. 50–60.

• Scott-Hayward, Sandra and O'Callaghan, Gemma and Sezer, Sakir (2013). “SDN security: A survey”. Future Networks and Services (SDN4FNS), 2013 IEEE SDN for. pp. 1–7.

• Benton,Kevinand Camp,Ljean and Small,Chris(2013). “Openflow vulnerability assessment”. Proceedings of the second ACM SIGCOMM workshop on Hot topics in software defined networking. pp. 151–152.

• Giotis,Kand Argyropoulos,Christosand Androulidakis, Georgios and Kalogeras, Dimitrios and Maglaris, Vasilis (2014). “Combining OpenFlow and sFlow for an effective and scalable anomaly detection and mitigation mechanism on SDN environments”. Computer Networks 62: 122–136.

• Braga,Rodrigoand Mota,Edjardand Passito,Alexandre (2010). “Lightweight DDoS flooding attack detection using NOX/OpenFlow”. Local Computer Networks (LCN), 2010 IEEE 35th Conference on. pp. 408–415.

• Feamster, Nick(2010). “Outsourcing home network security”. Proceedings of the 2010 ACM SIGCOMM workshop on Home networks. pp. 37–42.

Thank YouAny Queries??