Skip to content
Welcome To Charanjit Cheema Blog

Welcome To Charanjit Cheema Blog

An Open Source and Cloud Blog

Menu
  • Home
  • About Me!
  • Way to my Technical Blog
  • Contact me
  • Privacy Policy
Menu

What is SDN?

Posted on May 18, 2018 by Charanjit Cheema

SDN or Software-defined networking is a new technology which will soon replace the traditional Data Center networking architecture specially after introduction of Virtulization and Cloud. This term comprises of several kinds of network technologies which aimed at making the network as agile and flexible for virtualized server and storage infrastructure of the modern Data Center.

The opennetwork.org defined SDN as “The physical separation of the network control plane from the forwarding plane, and where a control plane controls several devices.”

The SDN enable network engineers and administrators to meet the volatile requirements of business. Software-Defined Network, gives flexibility to a network administrator to shape traffic from a centralized control console without touching individual switches, and can deliver services to wherever they are needed in the network, regardless to what specific equipment like server, network or other hardware are connected. SDN technology has below key points:
1. Functional separation,
2. Network virtualization and
3. Automation through programmability.

Figure: SDN High level Architecture
According to ciena.com there are four critical areas in which SDN technology can make a difference for an organization.
1) Network programmability: SDN enables network behavior to be controlled by the software that resides beyond the networking devices that provide physical connectivity. As a result, network operators can tailor the behavior of their networks to support new services, and even individual customers. By decoupling the hardware from the software, operators can introduce innovative, differentiated new services rapidly—free from the constraints of closed and proprietary platforms.

2) Logically centralize intelligence and control: SDN is built on logically centralized network topologies, which enable intelligent control and management of network resources. Traditional network control methods are distributed. Devices function autonomously with limited awareness of the state of the network. With the kind of centralized control an SDN-based network provides, bandwidth management, restoration, security, and policies can be highly intelligent and optimized—and an organization gains a holistic view of the network.

3) Abstraction of the network: Services and applications running on SDN technology are abstracted from the underlying technologies and hardware that provide physical connectivity from network control. Applications will interact with the network through APIs, instead of management interfaces tightly coupled to the hardware.

4) Openness: SDN architectures usher in a new era of openness—enabling multi-vendor interoperability as well as fostering a vendor-neutral ecosystem. Openness comes from the SDN approach itself. The open APIs support a wide range of applications, including cloud orchestration, OSS/BSS, SaaS, and business-critical networked apps. In addition, intelligent software can control hardware from multiple vendors with open programmatic interfaces like OpenFlow. Finally, from within the SDN, intelligent network services and applications can run within a common software environment.

A key advantage of SDN technology is the ability for network operators to write programs that utilize SDN APIs and give applications control over network behavior. SDN allows users to develop network-aware applications, intelligently monitor network conditions, and automatically adapt the network configuration as needed.

Reference Sources:
https://searchsdn.techtarget.com/definition/software-defined-networking-SDN
http://www.ciena.com/insights/what-is/What-Is-SDN.html
https://www.opennetworking.org/sdn-definition/

  • Author
  • Recent Posts
Charanjit Cheema
Follow him
Charanjit Cheema
Charanjit is currently working as a Cloud Architect at Mphasis, with 17 years of experience in IT infrastructure projects, implementation, and support. While his main role is as a DevOps engineer, he holds a Cloud Architect position and has strong skills in cloud technologies and automation. His expertise includes Terraform, Ansible, AWS, Azure DevOps, Azure Cloud, VMware, and Linux systems.

Charanjit is passionate about automating tasks and improving processes. He uses tools like Terraform and Azure DevOps to build and manage cloud infrastructure and streamline deployment. He also enjoys using Shell scripts and Ansible playbooks to make systems run more efficiently.

In his free time, Charanjit enjoys learning about new technologies and sharing his knowledge through his blog. When he’s not working, he likes listening to music, having a cup of coffee, and relaxing in nature.

You can connect with Charanjit on Twitter, Facebook, LinkedIn, or email him at charanjit.cheema@cjcheema.com.
Charanjit Cheema
Follow him
Latest posts by Charanjit Cheema (see all)
  • How to optimize the performance of Ansible Automation Platform or Ansible Tower - July 16, 2023
  • How to fix code and text file linting errors with the help of Visual Studio Code - June 27, 2023
  • How to migrate existing WordPress blog from AWS EC2 instance to Amazon Lightsail - May 29, 2023

Like this:

Like Loading...

Related

Leave a ReplyCancel reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Tags

AWS Cloud Computing Dockers Networking Open Networking OpenSource RHEL-CentOS SDN Server Hardware SLES tcpdump Ubuntu WSL

Follow me @

Subscribe to Blog via Email

Enter your email address to subscribe to this blog and receive notifications of new posts by email.

Join 2 other subscribers

Recent Posts

  • How to Deploy Docker Containers with NGINX on AWS EC2 Using Ansible and GitHub Actions
  • No More DynamoDB! Use Native S3 locking for Terraform State
  • How to Bring and Manage Manually Created AWS Resources Under Terraform Management
  • Iterating Cloud Resource Provisioning Using Terraform Count and For_Each Meta-Arguments
  • Terraform and Ansible Collaboration for AWS Cloud Deployment

Recent Comments

  1. Charanjit Singh on Terraform and Ansible Collaboration for AWS Cloud Deployment
  2. christinatodd2020aeaa798563 on Terraform and Ansible Collaboration for AWS Cloud Deployment
  3. Charanjit Singh on How to Set password policy in CentOS or RHEL system
  4. SAURABH on How to recover or rebuild initramfs in CentOS 7 Linux
  5. Sangita on How to Set password policy in CentOS or RHEL system

Archives

  • April 2025
  • February 2025
  • January 2025
  • August 2024
  • July 2024
  • June 2024
  • January 2024
  • August 2023
  • July 2023
  • June 2023
  • May 2023
  • September 2022
  • August 2022
  • July 2020
  • May 2020
  • February 2020
  • November 2019
  • June 2019
  • May 2019
  • March 2019
  • February 2019
  • December 2018
  • November 2018
  • October 2018
  • September 2018
  • August 2018
  • June 2018
  • May 2018
  • April 2018

Categories

  • Automation
  • Cloud Computing
  • Coding
  • CyberSecurity
  • Networking
  • OpenSource
  • RHEL-CentOS
  • Server Hardware
  • SLES
  • Technical Blog
  • Ubuntu
  • WSL

Blog Stats

  • 18,353 hits
Privacy & Cookies: This site uses cookies. By continuing to use this website, you agree to their use.
To find out more, including how to control cookies, see here: Cookie Policy
  • Home
  • About Me!
  • Way to my Technical Blog
  • Contact me
  • Privacy Policy
© 2025 Welcome To Charanjit Cheema Blog | Powered by Superbs Personal Blog theme
 

Loading Comments...
 

    %d