UNIT:I

SDN:INTRODUCTION

Evolving Network Requirements –

The SDN Approach – SDN
architecture - SDN Data Plane ,
Control plane and Application Plane.
 SDN:INTRODUCTION
• Software-Defined Networking (SDN) is an
innovative approach to network management
that separates the control plane from the data
plane, allowing centralized and programmable
control over network traffic. This decoupling
enables more agile, scalable, and efficient
network operations.
• Key Components of SDN:
• Application Layer – Consists of applications
that communicate network requirements.
• Control Layer – The SDN controller acts as the
brain, making intelligent decisions about
traffic routing.
• Infrastructure Layer – Comprises physical or
virtual network devices (switches, routers)
that forward data based on the controller’s
instructions.
• Benefits of SDN:
• Centralized Control – Provides a global view of the
network, making management easier.
• Improved Automation – Reduces manual configuration
through programmability.
• Better Resource Utilization – Optimizes network
performance and traffic flow.
• Scalability & Flexibility – Easily adapts to changing
network demands.
• Enhanced Security – Centralized policies can detect
and mitigate threats more effectively
• SDN Protocols:
• OpenFlow – The most common protocol for
communication between SDN controllers and
switches.
• NETCONF/YANG – Used for configuration
management.
• REST APIs – Enables integration with external
application
• Applications of SDN:
• Data Centers – Simplifies network
management in cloud environments.
• 5G Networks – Enables dynamic network
slicing.
• Enterprise Networks – Enhances security and
optimizes bandwidth.
• IoT Networks – Manages massive device
connections efficiently.
 The SDN Approach
• Adaptability
• Automation
• Maintainability
• Model management
• Mobility
• Integrated security
• On-demand scaling
Software-DefinedNetworking
(SDN)
 SDN Architecture

Fig: The Modern Approach to Computing and Networking

Fig: Control and Data Planes
Fig: Software-DefinedArchitecture
 Unit II
SDN DATA PLANE AND CONTROL PLANE

Data Plane functions and protocols – OpenFLow

Protocol – Flow Table – Control Plane Functions -
Southbound Interface, Northbound Interface – SDN
Controllers – Ryu, OpenDaylight, ONOS –
Distributed Controllers
Data Plane functions and protocols –
OpenFlow Protocol – Flow Table
Control Plane Functions -Southbound
Interface, Northbound Interface
SDN Controllers – Ryu, OpenDaylight, ONOS –
Distributed Controllers
Centralized and Distributed controller
 Unit III
SDN APPLICATIONS

SDN Application Plane Architecture – Network

Services Abstraction Layer – Traffic Engineering –
Measurement and Monitoring – Security – Data
Center Networking
Traffic Engineering:

Process of optimising the flow of data

traffic across a network.
Reasons to deploy traffic engineering

1. Congestion in the network due to

changing traffic patterns
2. Election news, online trading/major
sports events.
3. Better utilization of available
bandwidth.
4. Route on the path that is not the
shortest
5. Route around failed links/nodes
SDN APPLICATION
SECURITY
 LOCAL SERVERS
• Owned by organization in early 2000s, for
email, file storage, and also for data.
• Ensures system can still even run during
internet outages
• Example: to store citizen biometrics, tax
records, building permits, etc.
• Data stored in on-premises
 CLOUD SECURITY
• Used by organizations needing data control,
security, or specific performance.
• It is adopted around 2006-2008.
• It is used to protect data, applications, user
accounts and identity, networks, etc.
• Example: data, applications, workloads,
resources
• Data stored in remote data centers managed by
cloud providers.
 CLOUD SECURITY IN SDN
APPLICATION
• It is a centralized control, enhances security,
provides faster response to security threats.
• It started appearing around 2014-2015, but
become solid research and industry focus from
2016 onwards.
• It includes threat detection, segmentation,
provides quick responses.
• Example: user authentication, secure network
devices, cloud infrastructure.
 THREE MAIN COMPOENENTS
• CONFIDENTIALITY: keeps information in secret
manner.
• INTEGRITY: maintains consistency, data cannot
be altered without authorization.
• AVAILABILITY: accessible when needed by
authorized user.
 DESIGNED TO PROTECT:

• DATA
• SDN CONTROLLER
• DATA PLANE
• COMMUNICATION CHANNEL
• CLOUD SERVICE PROVIDERS
• NETWORK DEVICES
 SECURITY CHALLENGES

• Lack of security protocols

• Dynamic cloud
• Problem araises in communication channel
• Centralized control vulnerability
• API vulnerability
 CLOUD SERVICE AS SERVICE

• Also called as Security as a Service(SECaas).

• Includes services like identity and access
management(IAM), data encryption, threat
intelligence, firewall protection, and intrusion
detection.
• Reduces burden over network or data.
 EXAMPLE:

Netflix uses cloud infrastructure like(AWS) and

SDN to manage and optimize the delivery of
video content to million users.
Spotify uses Google cloud app engine for user
authentication, recommendations and content
management.
Snapchat uses Lambda function to process and
apply filters to images.
Data Center
Networking
 Data Center Supports the following
• things:
Processing of users business transactions
• Hosting of Company Website
• Process and store intellectual property
• Maintain financial records
• Route electronic mails
 Key Management Activities include:
1. Monitoring
2. Reporting
3. Provisioning
Big Data Over SDN
 Cloud Networking over SDN
• CloudNaaS stands for Cloud Network as
a service.
• Where users can design their own
network using cloud and SDN technology.
• It uses SDN to let users create custom
networks in the cloud easily and
automatically.
CloudNaaS Framework
CloudNaaS Architecture
 NFV CONCEPTS
Benefits and Requirements

85
87
NFV
REFERENCE
ARCHITECTUR
E
 • NFV Reference Arch
• NFV Management an
Orchestration
Agenda • Reference Points
• Implementation

89
NFV REFERENCE ARCHITECTURE
 BLOCKS OF REFERENCE ARCHIT

• NFV Infrastructure(NFVI)

• VNFs /EMS

• NFV Management and Orchestration(NFV-

MANO)
• OSS/BSS

92
 NFV MANAGEMENT AND ORCHEST

• NFV Orchestrator

• VNF Manager

• Virtualized Infrastructure Manager

93
 REFERENCE POINTS

• Vi-Ha
• Vn-Nf
• Nf-Vi
• Or-Vnfm
• Vi-Vnfm
• Or-Vi
• Os-Ma
• Ve-Vnfm
• Se-Ma
94
95