- SDN separates the control plane from the data plane, with a centralized controller making decisions about how traffic is routed through the network (3 sentences)
- This improves network flexibility and programmability. The controller directs traffic flow through OpenFlow switches based on application requirements. SDN also enables network slicing to deliver customized services. (3 sentences)
- In an example, an SDN controller directs test traffic from Generator B to Consumer B instead of Consumer A by tagging the packets and instructing switches to route them accordingly, demonstrating SDN's ability to control traffic flow. (3 sentences)
Software-defined Networking (SDN)
It is an approach to computer networking that allows network administrators to programmatically initialize, control, change, and manage network behavior dynamically via:
open interfaces
abstraction of lower-level functionality
SDN is meant to address the fact that the static architecture of traditional networks doesn't support the dynamic, scalable computing and storage needs of more modern computing environments such as data centers.
This is done by decoupling or disassociating the system that makes decisions about where traffic is sent (the SDN controller, or control plane) from the underlying systems that forward traffic to the selected destination (the data plane).
Data Plane: processing and delivery of packets
Based on state in routers and endpoints
E.g., IP, TCP, Ethernet, etc.
Control Plane: establishing the state in routers
Determines how and where packets are forwarded
Routing, traffic engineering, firewall state, …
Separate control plane and data plane entities
Have programmable data planes—maintain, control and program data plane from a central entity i.e. control plane software called controller.
An architecture to control not just a networking device but an entire network
Software-defined Networking (SDN)
It is an approach to computer networking that allows network administrators to programmatically initialize, control, change, and manage network behavior dynamically via:
open interfaces
abstraction of lower-level functionality
SDN is meant to address the fact that the static architecture of traditional networks doesn't support the dynamic, scalable computing and storage needs of more modern computing environments such as data centers.
This is done by decoupling or disassociating the system that makes decisions about where traffic is sent (the SDN controller, or control plane) from the underlying systems that forward traffic to the selected destination (the data plane).
Data Plane: processing and delivery of packets
Based on state in routers and endpoints
E.g., IP, TCP, Ethernet, etc.
Control Plane: establishing the state in routers
Determines how and where packets are forwarded
Routing, traffic engineering, firewall state, …
Separate control plane and data plane entities
Have programmable data planes—maintain, control and program data plane from a central entity i.e. control plane software called controller.
An architecture to control not just a networking device but an entire network
Provide a diagram and description of the flow table entries that can.pdfarihantelehyb
Provide a diagram and description of the flow table entries that can be
modified in an OpenFlow Switch.
Provide a diagram and description of an SDN Controller and describe
how the SDN Controller works – OpenDaylight is an appropriate
example that you could use.
Solution
Open Flow Switch:
An Open Flow switch is a software program or hardware device that forwards packets in a
software-defined networking (SDN) environment. Open Flow switches are either based on the
Open Flow protocol or compatible with it.
In a conventional switch, packet forwarding (the data plane) and high-level routing (the control
plane) occur on the same device. In software-defined networking, the data plane is decoupled
from the control plane. The data plane is still implemented in the switch itself but the control
plane is implemented in software and a separate SDN controller makes high-level routing
decisions. The switch and controller communicate by means of the Open Flow protocol.
Flow table entries:
The components of flow table entries and the process by which incoming packets are matched
against flow table entries.
A flow entry consists of header fields, counters, and actions.
Header fields
Counters
Actions
Each flow table entry contains:
1. Header fields to match against packets.
2. Counters to update for matching packet.
3. Actions to apply to matching packets.
These are flow table entries are used to modified in an open flow switch.
Open Flow is an open standard that enables researchers to run experimental protocols in the
campus networks we use every day. Open Flow is added as a feature to commercial Ethernet
switches, routers and wireless access points – and provides a standardized hook to allow
researchers to run experiments, without requiring vendors to expose the internal workings of
their network devices. Open Flow is currently being implemented by major vendors, with Open
Flow-enabled switches now commercially available.
SDN controller (software-defined networking controller):
An SDN controller is an application in software-defined networking (SDN) that manages flow
control to enable intelligent networking. SDN controllers are based on protocols, such as Open
Flow, that allow servers to tell switches where to send packets.
SDN controller is a new paradigm to configure and operate computer networks through a
centralized software controller that dictates how the network behaves. The core of this new
paradigm is the SDN controller.
There are typically two sets of SDN controllers:
The controller is the core of an SDN network. It lies between network devices at one end and
applications at the other end. Any communications between applications and devices have to go
through the controller. The controller also uses protocols such as Open Flow to configure
network devices and choose the optimal network path for application traffic.
SDN controllers works:
Software Defined Networking, as it evolved from prior proposals, standards, and
implementations such as For CES,.
SDN most commonly means that networks are controlled by software applications and SDN controllers rather than the traditional network management consoles and commands that required a lot of administrative overhead and could be tedious to manage on a large scale
“What is SDN? The physical separation of the network control plane from the forwarding plane, and where a control plane controls several devices.”
The main scope of up-gradation to the advanced computer networks is to make the technical advancement in the network management and so managing the traffic control (that is the control plane and data or forwarding plane) while abridging it in the Multi-Controller Domain. SDN refers to the isolation of the network control plane from the forwarding plane, with a control plane overseeing many networking systems. This paper investigates how new improvements in SDN and the programmability of networks can be helpful to abridge tasks, improve dexterity, and encounter new task necessities within the U.S. Department of Defense (DoD) and open networks. These improvised network services across the digital network entail a multi-controller domain. This paper represents the research in SDN and multi-controller domain, aiming at OpenFlow Protocol and its upcoming challenging tasks.
In current generation where all people are obsessed with mobile device and having mentality of “always stay connected”,SDN plays a major role.
OpenFlow based SDN technologies enable IT to address the some important aspects like high bandwidth, flexible QoS ,policy information, dynamic nature of today's applications, adaption of new network approaches to ever-changing business needs, and significantly reduce operations & management complexities. A network can have multiple SDN domains,each controlled by individual SDN controller.In today’s generation where networks are moving rapidly towards cloud architecture (data centers) ,SDN plays one of the key enabler of this.To utilize the resources efficiently ,SDN controllers need to communicate with each other which is the main discuss point in this seminar.
Radisys/Wind River: The Telcom Cloud - Deployment Strategies: SDN/NFV and Vir...Radisys Corporation
Radisys and Wind River present on the evolution to the Telecom Cloud and how cloud technology and network virtualization will provide both big opportunities and challenges for operators. Important details and insights are shared on Network Function Virtualization (NFV), Software Defined Network (SDN) and Virtualization.
JMeter webinar - integration with InfluxDB and GrafanaRTTS
Watch this recorded webinar about real-time monitoring of application performance. See how to integrate Apache JMeter, the open-source leader in performance testing, with InfluxDB, the open-source time-series database, and Grafana, the open-source analytics and visualization application.
In this webinar, we will review the benefits of leveraging InfluxDB and Grafana when executing load tests and demonstrate how these tools are used to visualize performance metrics.
Length: 30 minutes
Session Overview
-------------------------------------------
During this webinar, we will cover the following topics while demonstrating the integrations of JMeter, InfluxDB and Grafana:
- What out-of-the-box solutions are available for real-time monitoring JMeter tests?
- What are the benefits of integrating InfluxDB and Grafana into the load testing stack?
- Which features are provided by Grafana?
- Demonstration of InfluxDB and Grafana using a practice web application
To view the webinar recording, go to:
https://www.rttsweb.com/jmeter-integration-webinar
"Impact of front-end architecture on development cost", Viktor TurskyiFwdays
I have heard many times that architecture is not important for the front-end. Also, many times I have seen how developers implement features on the front-end just following the standard rules for a framework and think that this is enough to successfully launch the project, and then the project fails. How to prevent this and what approach to choose? I have launched dozens of complex projects and during the talk we will analyze which approaches have worked for me and which have not.
Provide a diagram and description of the flow table entries that can.pdfarihantelehyb
Provide a diagram and description of the flow table entries that can be
modified in an OpenFlow Switch.
Provide a diagram and description of an SDN Controller and describe
how the SDN Controller works – OpenDaylight is an appropriate
example that you could use.
Solution
Open Flow Switch:
An Open Flow switch is a software program or hardware device that forwards packets in a
software-defined networking (SDN) environment. Open Flow switches are either based on the
Open Flow protocol or compatible with it.
In a conventional switch, packet forwarding (the data plane) and high-level routing (the control
plane) occur on the same device. In software-defined networking, the data plane is decoupled
from the control plane. The data plane is still implemented in the switch itself but the control
plane is implemented in software and a separate SDN controller makes high-level routing
decisions. The switch and controller communicate by means of the Open Flow protocol.
Flow table entries:
The components of flow table entries and the process by which incoming packets are matched
against flow table entries.
A flow entry consists of header fields, counters, and actions.
Header fields
Counters
Actions
Each flow table entry contains:
1. Header fields to match against packets.
2. Counters to update for matching packet.
3. Actions to apply to matching packets.
These are flow table entries are used to modified in an open flow switch.
Open Flow is an open standard that enables researchers to run experimental protocols in the
campus networks we use every day. Open Flow is added as a feature to commercial Ethernet
switches, routers and wireless access points – and provides a standardized hook to allow
researchers to run experiments, without requiring vendors to expose the internal workings of
their network devices. Open Flow is currently being implemented by major vendors, with Open
Flow-enabled switches now commercially available.
SDN controller (software-defined networking controller):
An SDN controller is an application in software-defined networking (SDN) that manages flow
control to enable intelligent networking. SDN controllers are based on protocols, such as Open
Flow, that allow servers to tell switches where to send packets.
SDN controller is a new paradigm to configure and operate computer networks through a
centralized software controller that dictates how the network behaves. The core of this new
paradigm is the SDN controller.
There are typically two sets of SDN controllers:
The controller is the core of an SDN network. It lies between network devices at one end and
applications at the other end. Any communications between applications and devices have to go
through the controller. The controller also uses protocols such as Open Flow to configure
network devices and choose the optimal network path for application traffic.
SDN controllers works:
Software Defined Networking, as it evolved from prior proposals, standards, and
implementations such as For CES,.
SDN most commonly means that networks are controlled by software applications and SDN controllers rather than the traditional network management consoles and commands that required a lot of administrative overhead and could be tedious to manage on a large scale
“What is SDN? The physical separation of the network control plane from the forwarding plane, and where a control plane controls several devices.”
The main scope of up-gradation to the advanced computer networks is to make the technical advancement in the network management and so managing the traffic control (that is the control plane and data or forwarding plane) while abridging it in the Multi-Controller Domain. SDN refers to the isolation of the network control plane from the forwarding plane, with a control plane overseeing many networking systems. This paper investigates how new improvements in SDN and the programmability of networks can be helpful to abridge tasks, improve dexterity, and encounter new task necessities within the U.S. Department of Defense (DoD) and open networks. These improvised network services across the digital network entail a multi-controller domain. This paper represents the research in SDN and multi-controller domain, aiming at OpenFlow Protocol and its upcoming challenging tasks.
In current generation where all people are obsessed with mobile device and having mentality of “always stay connected”,SDN plays a major role.
OpenFlow based SDN technologies enable IT to address the some important aspects like high bandwidth, flexible QoS ,policy information, dynamic nature of today's applications, adaption of new network approaches to ever-changing business needs, and significantly reduce operations & management complexities. A network can have multiple SDN domains,each controlled by individual SDN controller.In today’s generation where networks are moving rapidly towards cloud architecture (data centers) ,SDN plays one of the key enabler of this.To utilize the resources efficiently ,SDN controllers need to communicate with each other which is the main discuss point in this seminar.
Radisys/Wind River: The Telcom Cloud - Deployment Strategies: SDN/NFV and Vir...Radisys Corporation
Radisys and Wind River present on the evolution to the Telecom Cloud and how cloud technology and network virtualization will provide both big opportunities and challenges for operators. Important details and insights are shared on Network Function Virtualization (NFV), Software Defined Network (SDN) and Virtualization.
JMeter webinar - integration with InfluxDB and GrafanaRTTS
Watch this recorded webinar about real-time monitoring of application performance. See how to integrate Apache JMeter, the open-source leader in performance testing, with InfluxDB, the open-source time-series database, and Grafana, the open-source analytics and visualization application.
In this webinar, we will review the benefits of leveraging InfluxDB and Grafana when executing load tests and demonstrate how these tools are used to visualize performance metrics.
Length: 30 minutes
Session Overview
-------------------------------------------
During this webinar, we will cover the following topics while demonstrating the integrations of JMeter, InfluxDB and Grafana:
- What out-of-the-box solutions are available for real-time monitoring JMeter tests?
- What are the benefits of integrating InfluxDB and Grafana into the load testing stack?
- Which features are provided by Grafana?
- Demonstration of InfluxDB and Grafana using a practice web application
To view the webinar recording, go to:
https://www.rttsweb.com/jmeter-integration-webinar
"Impact of front-end architecture on development cost", Viktor TurskyiFwdays
I have heard many times that architecture is not important for the front-end. Also, many times I have seen how developers implement features on the front-end just following the standard rules for a framework and think that this is enough to successfully launch the project, and then the project fails. How to prevent this and what approach to choose? I have launched dozens of complex projects and during the talk we will analyze which approaches have worked for me and which have not.
Builder.ai Founder Sachin Dev Duggal's Strategic Approach to Create an Innova...Ramesh Iyer
In today's fast-changing business world, Companies that adapt and embrace new ideas often need help to keep up with the competition. However, fostering a culture of innovation takes much work. It takes vision, leadership and willingness to take risks in the right proportion. Sachin Dev Duggal, co-founder of Builder.ai, has perfected the art of this balance, creating a company culture where creativity and growth are nurtured at each stage.
Kubernetes & AI - Beauty and the Beast !?! @KCD Istanbul 2024Tobias Schneck
As AI technology is pushing into IT I was wondering myself, as an “infrastructure container kubernetes guy”, how get this fancy AI technology get managed from an infrastructure operational view? Is it possible to apply our lovely cloud native principals as well? What benefit’s both technologies could bring to each other?
Let me take this questions and provide you a short journey through existing deployment models and use cases for AI software. On practical examples, we discuss what cloud/on-premise strategy we may need for applying it to our own infrastructure to get it to work from an enterprise perspective. I want to give an overview about infrastructure requirements and technologies, what could be beneficial or limiting your AI use cases in an enterprise environment. An interactive Demo will give you some insides, what approaches I got already working for real.
Connector Corner: Automate dynamic content and events by pushing a buttonDianaGray10
Here is something new! In our next Connector Corner webinar, we will demonstrate how you can use a single workflow to:
Create a campaign using Mailchimp with merge tags/fields
Send an interactive Slack channel message (using buttons)
Have the message received by managers and peers along with a test email for review
But there’s more:
In a second workflow supporting the same use case, you’ll see:
Your campaign sent to target colleagues for approval
If the “Approve” button is clicked, a Jira/Zendesk ticket is created for the marketing design team
But—if the “Reject” button is pushed, colleagues will be alerted via Slack message
Join us to learn more about this new, human-in-the-loop capability, brought to you by Integration Service connectors.
And...
Speakers:
Akshay Agnihotri, Product Manager
Charlie Greenberg, Host
Let's dive deeper into the world of ODC! Ricardo Alves (OutSystems) will join us to tell all about the new Data Fabric. After that, Sezen de Bruijn (OutSystems) will get into the details on how to best design a sturdy architecture within ODC.
Epistemic Interaction - tuning interfaces to provide information for AI supportAlan Dix
Paper presented at SYNERGY workshop at AVI 2024, Genoa, Italy. 3rd June 2024
https://alandix.com/academic/papers/synergy2024-epistemic/
As machine learning integrates deeper into human-computer interactions, the concept of epistemic interaction emerges, aiming to refine these interactions to enhance system adaptability. This approach encourages minor, intentional adjustments in user behaviour to enrich the data available for system learning. This paper introduces epistemic interaction within the context of human-system communication, illustrating how deliberate interaction design can improve system understanding and adaptation. Through concrete examples, we demonstrate the potential of epistemic interaction to significantly advance human-computer interaction by leveraging intuitive human communication strategies to inform system design and functionality, offering a novel pathway for enriching user-system engagements.
State of ICS and IoT Cyber Threat Landscape Report 2024 previewPrayukth K V
The IoT and OT threat landscape report has been prepared by the Threat Research Team at Sectrio using data from Sectrio, cyber threat intelligence farming facilities spread across over 85 cities around the world. In addition, Sectrio also runs AI-based advanced threat and payload engagement facilities that serve as sinks to attract and engage sophisticated threat actors, and newer malware including new variants and latent threats that are at an earlier stage of development.
The latest edition of the OT/ICS and IoT security Threat Landscape Report 2024 also covers:
State of global ICS asset and network exposure
Sectoral targets and attacks as well as the cost of ransom
Global APT activity, AI usage, actor and tactic profiles, and implications
Rise in volumes of AI-powered cyberattacks
Major cyber events in 2024
Malware and malicious payload trends
Cyberattack types and targets
Vulnerability exploit attempts on CVEs
Attacks on counties – USA
Expansion of bot farms – how, where, and why
In-depth analysis of the cyber threat landscape across North America, South America, Europe, APAC, and the Middle East
Why are attacks on smart factories rising?
Cyber risk predictions
Axis of attacks – Europe
Systemic attacks in the Middle East
Download the full report from here:
https://sectrio.com/resources/ot-threat-landscape-reports/sectrio-releases-ot-ics-and-iot-security-threat-landscape-report-2024/
Search and Society: Reimagining Information Access for Radical FuturesBhaskar Mitra
The field of Information retrieval (IR) is currently undergoing a transformative shift, at least partly due to the emerging applications of generative AI to information access. In this talk, we will deliberate on the sociotechnical implications of generative AI for information access. We will argue that there is both a critical necessity and an exciting opportunity for the IR community to re-center our research agendas on societal needs while dismantling the artificial separation between the work on fairness, accountability, transparency, and ethics in IR and the rest of IR research. Instead of adopting a reactionary strategy of trying to mitigate potential social harms from emerging technologies, the community should aim to proactively set the research agenda for the kinds of systems we should build inspired by diverse explicitly stated sociotechnical imaginaries. The sociotechnical imaginaries that underpin the design and development of information access technologies needs to be explicitly articulated, and we need to develop theories of change in context of these diverse perspectives. Our guiding future imaginaries must be informed by other academic fields, such as democratic theory and critical theory, and should be co-developed with social science scholars, legal scholars, civil rights and social justice activists, and artists, among others.
Key Trends Shaping the Future of Infrastructure.pdfCheryl Hung
Keynote at DIGIT West Expo, Glasgow on 29 May 2024.
Cheryl Hung, ochery.com
Sr Director, Infrastructure Ecosystem, Arm.
The key trends across hardware, cloud and open-source; exploring how these areas are likely to mature and develop over the short and long-term, and then considering how organisations can position themselves to adapt and thrive.
Essentials of Automations: Optimizing FME Workflows with ParametersSafe Software
Are you looking to streamline your workflows and boost your projects’ efficiency? Do you find yourself searching for ways to add flexibility and control over your FME workflows? If so, you’re in the right place.
Join us for an insightful dive into the world of FME parameters, a critical element in optimizing workflow efficiency. This webinar marks the beginning of our three-part “Essentials of Automation” series. This first webinar is designed to equip you with the knowledge and skills to utilize parameters effectively: enhancing the flexibility, maintainability, and user control of your FME projects.
Here’s what you’ll gain:
- Essentials of FME Parameters: Understand the pivotal role of parameters, including Reader/Writer, Transformer, User, and FME Flow categories. Discover how they are the key to unlocking automation and optimization within your workflows.
- Practical Applications in FME Form: Delve into key user parameter types including choice, connections, and file URLs. Allow users to control how a workflow runs, making your workflows more reusable. Learn to import values and deliver the best user experience for your workflows while enhancing accuracy.
- Optimization Strategies in FME Flow: Explore the creation and strategic deployment of parameters in FME Flow, including the use of deployment and geometry parameters, to maximize workflow efficiency.
- Pro Tips for Success: Gain insights on parameterizing connections and leveraging new features like Conditional Visibility for clarity and simplicity.
We’ll wrap up with a glimpse into future webinars, followed by a Q&A session to address your specific questions surrounding this topic.
Don’t miss this opportunity to elevate your FME expertise and drive your projects to new heights of efficiency.
Neuro-symbolic is not enough, we need neuro-*semantic*Frank van Harmelen
Neuro-symbolic (NeSy) AI is on the rise. However, simply machine learning on just any symbolic structure is not sufficient to really harvest the gains of NeSy. These will only be gained when the symbolic structures have an actual semantics. I give an operational definition of semantics as “predictable inference”.
All of this illustrated with link prediction over knowledge graphs, but the argument is general.
Transcript: Selling digital books in 2024: Insights from industry leaders - T...BookNet Canada
The publishing industry has been selling digital audiobooks and ebooks for over a decade and has found its groove. What’s changed? What has stayed the same? Where do we go from here? Join a group of leading sales peers from across the industry for a conversation about the lessons learned since the popularization of digital books, best practices, digital book supply chain management, and more.
Link to video recording: https://bnctechforum.ca/sessions/selling-digital-books-in-2024-insights-from-industry-leaders/
Presented by BookNet Canada on May 28, 2024, with support from the Department of Canadian Heritage.
GDG Cloud Southlake #33: Boule & Rebala: Effective AppSec in SDLC using Deplo...James Anderson
Effective Application Security in Software Delivery lifecycle using Deployment Firewall and DBOM
The modern software delivery process (or the CI/CD process) includes many tools, distributed teams, open-source code, and cloud platforms. Constant focus on speed to release software to market, along with the traditional slow and manual security checks has caused gaps in continuous security as an important piece in the software supply chain. Today organizations feel more susceptible to external and internal cyber threats due to the vast attack surface in their applications supply chain and the lack of end-to-end governance and risk management.
The software team must secure its software delivery process to avoid vulnerability and security breaches. This needs to be achieved with existing tool chains and without extensive rework of the delivery processes. This talk will present strategies and techniques for providing visibility into the true risk of the existing vulnerabilities, preventing the introduction of security issues in the software, resolving vulnerabilities in production environments quickly, and capturing the deployment bill of materials (DBOM).
Speakers:
Bob Boule
Robert Boule is a technology enthusiast with PASSION for technology and making things work along with a knack for helping others understand how things work. He comes with around 20 years of solution engineering experience in application security, software continuous delivery, and SaaS platforms. He is known for his dynamic presentations in CI/CD and application security integrated in software delivery lifecycle.
Gopinath Rebala
Gopinath Rebala is the CTO of OpsMx, where he has overall responsibility for the machine learning and data processing architectures for Secure Software Delivery. Gopi also has a strong connection with our customers, leading design and architecture for strategic implementations. Gopi is a frequent speaker and well-known leader in continuous delivery and integrating security into software delivery.
2. Router
1
Router
3
Router
2
Traditional Routing
-
Internet Service Provider
Each Router Consist of Data and Control Plane. Data Plane is used to
forward the packets and control plane is used for decision making. In every
Router it will choose the path and decision making.
4. Software Defined Networking(SDN)
• In SDN there is only one Centralised administrator or control plane.All
communications based on control plane.
• SDN can improve data flows, minimize network bandwidth, and boost
latency. It can also improve network agility and flexibility.
• SDN separates a single physical network into multiple virtual networks that
share the same network infrastructure.
• This logical separation splits networks into customizable slices, enabling
operators to deliver services based on each customer's needs.
5. Networking module:
• Data plane(I/O module ):responsible for forwarding of network traffic
and moving packets from one network device to another based on the
instruction provided by control plane.
• Control plane (brain of the module):responsible for making decision
about how traffic should be routed and managed.
• Management plane(monitor all devices):network monitering, bandwidth
utilization, customer billing.
6. Seperation of control and data layer
• In SDN ,command and controll are given by the controller(central
node)
• The centalized controller decides traffic routing and data
plane(forwarding plane) is used to forward the packets from payload
to destination-DECOUPLING
• SDN provides central view of efficient resource allocation and
keeping end to end eye on network
Features of SDN
• Makes networking & IP routing flexible
• Decoupling control &data plane
• Offloads brain to centralized controller
• Programmable network,centrally managed
7. Frame work of SDN
• SDN architecture typically comprises three layers: the application layer,
the control layer, and the infrastructure layer.
• These layers communicate using northbound and southbound application
programming interfaces (APIS).
• Open flow protocol is key to entire SDN topology
8. Frame work of SDN
• Southbound APIs (Application Programming Interfaces):Interfaces between the SDN
controller and network devices (routers, switches, etc.).
• Allows the controller to communicate and manage these devices, typically using protocols like
OpenFlow
• Infrastructure Layer:
– Data Plane (Forwarding Devices):
• Physical or virtual network devices (switches, routers, etc.) that forward traffic based
on instructions received from the SDN controller.
• These devices follow the rules and policies set by the controller.
• Northbound APIs:
– Interfaces between the SDN controller and the applications or systems in the application
layer.
– Allows SDN applications to communicate with the controller, enabling network
programmability and automation.
9. Control layer
• Centralized brain of the SDN architecture responsible for making decisions
about how data should flow through the network.
• Receives information from applications and translates it into network
policies.
• Enforces policies by instructing the data plane devices.
Application layer
• These are the software applications or services that utilize the SDN
controller's capabilities to manage the network. Examples include traffic
engineering, security applications, network monitoring, etc.
11. SDN OPEARATION
• In this scenario, an SDN Controller (SDNC) is in charge of operating three
different OpenFlow Switches.
• Connected to OpenFlow Switch no. 1 are two information generators.
Generator A generates ‘production grade’ information (i.e. regular traffic)
whose destination is Consumer A, whereas Generator B is used for testing a
new protocol.
• In this example, when traffic from Generator B reaches Switch no. 1, the
Controller is contacted using the OpenFlow protocol.
• The controller, through preconfigured knowledge of the network topology,
is able to determine that the final destination for that kind of traffic should
be Consumer B, instead of Consumer A.
• The SDNC takes charge by sending a series of commands using OpenFlow.
• For Switch no. 1,The controller configures the switch via software to add a
virtual tag to all packets with origin at Generator B.
• For Switch no. 2, it instructs the switch to forward any packet with this
special tag arriving at port 12 to port 8, instead of the usual port 6.
12. SDN control for authentication
traffic redirection
• Here openflow is used to capture or inject 802.1X authentication messages
• Allowing the controller to act as a 802.1X authenticator and radius client,
in a user‐specific way.
• 802.1X – NETWORK AUTHENTICATION PROTOCOL
Remote Authentication Dial-In
User Service(Radius) Server
Request
13. Network function virtualization(NVF)
• Network Function Virtualization (NFV) refers to the virtualization of
network services traditionally performed by dedicated hardware appliances.
It aims to replace these specialized physical devices with software-based
virtual instances running on standard hardware infrastructure.
• NFV decouples network functions, such as firewalls, routers, load
balancers, and intrusion detection systems, from proprietary hardware.
Instead, these functions are implemented as software-based Network
Functions Virtual(NFV) that can run on general-purpose servers, switches,
or storage devices.
15. Network Function Virtualization
Physical resources layer:
• The operator leverages its underlying networking, processing and memory
resources
• In this layer, these resources appear as just raw aggregates of computational and
networking elements
• By using reservation interfaces, these resources can be requested, via a
virtualisation execution environment, and reserved onto the hardware
Virtual substrate layer:
• Able to employ a logic ordering on different hardware resources, made
available by the physical resources layer
16. Network Function Virtualization
• In this way, such resources can be logically aggregated into one or several
virtual machines (i.E. Composing a virtual type of computational element where
functions can be stored and operated) as well as virtual networks (i.E. Providing
the necessary structured connectivity for the virtualised machines, taking into
consideration different routing and business policies).
Virtualised function layer:
• Virtualised resources further provides a virtualisation interface, allowing
different virtualised functions to be deployed.
• As such, the core hardware provided by the operator can be virtualised into a
logical structure, both in terms of network and processing, into which different
services and functions can be virtualised.