This document provides an overview of a course on Software Defined Networking (SDN). It discusses:
1. The course format which includes assignments on using SDN environments and writing controller applications, as well as a course project.
2. An introduction to SDN which describes how SDN decouples the network control and forwarding planes using a southbound API. This allows for a global view of the network and programmatic control.
3. Some of the key sections that will be covered in the course, including OpenFlow, network virtualization use cases, and SDN challenges related to controller availability.
SDN basics and OpenFlow
The document discusses SDN and OpenFlow. It defines SDN as an approach that separates the network control plane from the forwarding plane, allowing for centralized control over the network. OpenFlow is introduced as an open standard protocol that enables communication between the control and forwarding planes. Key concepts covered include the control and data planes, SDN architecture, OpenFlow switch operation and flow tables, and OpenFlow protocol messages. The relationship between SDN and OpenFlow is established, with OpenFlow providing an API that enables SDN.
Here are the key steps to run the Ryu controller with a sample application on the Mininet virtual machine topology:
1. Ensure no other controllers are running with `killall controller`
2. Clear any existing Mininet components with `mn -c`
3. Start the Ryu controller with `ryu-manager --verbose ./simple_switch_13.py`
4. In a new terminal, start the Mininet topology with `mn --controller remote`
5. Use Mininet commands like `pingall` and `net` to test connectivity and explore the network
6. You can install additional Ryu applications and restart the controller to add new functionality
7. Use
Here are the key steps:
1. Kill any existing controllers running on the system
2. Clear out any existing Mininet topology using mn -c
3. Start the Ryu OpenFlow controller by running:
ryu-manager --verbose ./simple_switch_13.py
This starts the Ryu controller with the simple_switch_13.py application, which provides basic OpenFlow switch functionality. The --verbose flag prints debug information from the controller. We have now initialized the SDN environment with Ryu acting as the controller.
The document provides an overview of Software Defined Networking (SDN). It discusses the history and disadvantages of traditional networking approaches. It then defines SDN, describing its architecture and key components like the data plane, control plane, and management plane. It outlines the needs and benefits of SDN, such as virtualization, orchestration, programmability, and automation. It also covers SDN concepts like the OpenFlow protocol and SDN controllers.
The Challenges of SDN/OpenFlow in an Operational and Large-scale NetworkOpen Networking Summits
Jun Bi
Professor & Director
Tsinghua University
Outline
• Intra-AS (campus level) IPv6 source address validation using OpenFlow (with extension)
– Good for introducing new IP services to network
• Planning next step if we run SDN as a common infrastructure for new services and architectures
– Some personal viewpoints and thoughts on design challenges
– Forwarding abstraction for Post-IP architectures
– Control abstraction for scalable NOS and programmable/manageable virtualization platform
– Inter-AS policies negotiation abstraction
ONS2015: http://bit.ly/ons2015sd
ONS Inspire! Webinars: http://bit.ly/oiw-sd
Watch the talk (video) on ONS Content Archives: http://bit.ly/ons-archives-sd
Andreas Wundsam
Big Switch Networks
Research Track Part 2
ONS2015: http://bit.ly/ons2015sd
ONS Inspire! Webinars: http://bit.ly/oiw-sd
Watch the talk (video) on ONS Content Archives: http://bit.ly/ons-archives-sd
This document provides an introduction to software defined networking (SDN). It discusses the history and disadvantages of traditional networking approaches. SDN aims to address these issues by separating the network control and forwarding functions, and enabling programmability of the network. The key components of an SDN architecture are described, including the OpenFlow protocol for communication between the control plane and data plane. Several SDN controllers and their programming languages are also mentioned. The document concludes with the objectives of running an SDN demonstration lab using Mininet to experiment with OpenFlow and SDN controllers like Ryu.
SDN basics and OpenFlow
The document discusses SDN and OpenFlow. It defines SDN as an approach that separates the network control plane from the forwarding plane, allowing for centralized control over the network. OpenFlow is introduced as an open standard protocol that enables communication between the control and forwarding planes. Key concepts covered include the control and data planes, SDN architecture, OpenFlow switch operation and flow tables, and OpenFlow protocol messages. The relationship between SDN and OpenFlow is established, with OpenFlow providing an API that enables SDN.
Here are the key steps to run the Ryu controller with a sample application on the Mininet virtual machine topology:
1. Ensure no other controllers are running with `killall controller`
2. Clear any existing Mininet components with `mn -c`
3. Start the Ryu controller with `ryu-manager --verbose ./simple_switch_13.py`
4. In a new terminal, start the Mininet topology with `mn --controller remote`
5. Use Mininet commands like `pingall` and `net` to test connectivity and explore the network
6. You can install additional Ryu applications and restart the controller to add new functionality
7. Use
Here are the key steps:
1. Kill any existing controllers running on the system
2. Clear out any existing Mininet topology using mn -c
3. Start the Ryu OpenFlow controller by running:
ryu-manager --verbose ./simple_switch_13.py
This starts the Ryu controller with the simple_switch_13.py application, which provides basic OpenFlow switch functionality. The --verbose flag prints debug information from the controller. We have now initialized the SDN environment with Ryu acting as the controller.
The document provides an overview of Software Defined Networking (SDN). It discusses the history and disadvantages of traditional networking approaches. It then defines SDN, describing its architecture and key components like the data plane, control plane, and management plane. It outlines the needs and benefits of SDN, such as virtualization, orchestration, programmability, and automation. It also covers SDN concepts like the OpenFlow protocol and SDN controllers.
The Challenges of SDN/OpenFlow in an Operational and Large-scale NetworkOpen Networking Summits
Jun Bi
Professor & Director
Tsinghua University
Outline
• Intra-AS (campus level) IPv6 source address validation using OpenFlow (with extension)
– Good for introducing new IP services to network
• Planning next step if we run SDN as a common infrastructure for new services and architectures
– Some personal viewpoints and thoughts on design challenges
– Forwarding abstraction for Post-IP architectures
– Control abstraction for scalable NOS and programmable/manageable virtualization platform
– Inter-AS policies negotiation abstraction
ONS2015: http://bit.ly/ons2015sd
ONS Inspire! Webinars: http://bit.ly/oiw-sd
Watch the talk (video) on ONS Content Archives: http://bit.ly/ons-archives-sd
Andreas Wundsam
Big Switch Networks
Research Track Part 2
ONS2015: http://bit.ly/ons2015sd
ONS Inspire! Webinars: http://bit.ly/oiw-sd
Watch the talk (video) on ONS Content Archives: http://bit.ly/ons-archives-sd
This document provides an introduction to software defined networking (SDN). It discusses the history and disadvantages of traditional networking approaches. SDN aims to address these issues by separating the network control and forwarding functions, and enabling programmability of the network. The key components of an SDN architecture are described, including the OpenFlow protocol for communication between the control plane and data plane. Several SDN controllers and their programming languages are also mentioned. The document concludes with the objectives of running an SDN demonstration lab using Mininet to experiment with OpenFlow and SDN controllers like Ryu.
Software-defined networking (SDN) uses an approach that allows network administrators to programmatically control network behavior dynamically. OpenFlow is an open standard that defines the communication between the control and forwarding layers of the SDN architecture, allowing the network control to be programmed and managed through open source software rather than proprietary hardware switches. OpenFlow switches use flow tables and groups tables that can be populated and manipulated by an OpenFlow controller using the OpenFlow protocol to determine how packets are forwarded through the network.
The document discusses the limitations of existing networks and introduces the concept of software-defined networking (SDN) as a solution. Some key limitations of traditional networks include slow innovation, closed systems, and difficulty experimenting on large production networks. SDN is described as separating the control plane and data plane, making the network programmable from a central controller. This allows for greater flexibility, innovation, and experimentation. The architecture of SDN is explained including layers for infrastructure, control, and applications. OpenFlow is discussed as an open protocol that allows the controller to remotely program the forwarding behavior of switches.
Software Defined Networking(SDN) and practical implementation_truptitrups7778
This document provides an overview of software defined networks (SDN) and OpenFlow protocol. It discusses the limitations of traditional networks and how SDN addresses these issues by decoupling the control plane from the data plane. The key components of the SDN architecture are described, including the control layer with SDN controllers, the infrastructure layer with OpenFlow switches, and the application layer. The document also covers the OpenFlow protocol for communication between controllers and switches, including message types. Examples of SDN controllers like NOX and POX are also mentioned.
This document discusses the limitations of existing networks and introduces the concept of software-defined networking (SDN) as a solution. It outlines that current networks have separate control and data planes, making them difficult to program and innovate on. SDN is proposed to separate the control and data planes, making the network programmable through open interfaces and allowing for centralized control. This enables experimentation, flexibility, and easier integration of new applications and services. The key aspects of SDN architecture include the infrastructure, control, and application layers that communicate through the OpenFlow protocol to enable remote programming of forwarding rules in switches.
The document discusses the transport SDN framework and APIs. It provides an overview of the transport SDN toolkit, including the SDN framework, APIs, and a global transport SDN prototype demonstration. The framework uses a three-layer model with an infrastructure layer containing network elements, a control layer with multiple controllers, and an application layer. Transport SDN APIs are being developed to standardize the southbound and northbound interfaces. The demonstration showed a multi-domain, multi-vendor transport SDN deployment across five carrier labs and nine system vendors.
This document discusses Software Defined Networking (SDN). It describes how traditional networks have tight coupling between the control and data planes, which causes challenges. SDN separates the control and data planes, making the network programmable. The control plane software can run on general hardware. OpenFlow is the communication interface that allows the control plane to program the data plane switches and routers. This gives operators more flexibility and control over how the network functions.
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
- 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)
Inter-controller Traffic in ONOS Clusters for SDN Networks Paolo Giaccone
In distributed SDN architectures, the network is controlled by a cluster of multiple controllers. This distributed ap- proach permits to meet the scalability and reliability requirements of large operational networks. Despite that, a logical centralized view of the network state should be guaranteed, enabling the simple development of network applications. Achieving a consis- tent network state requires a consensus protocol, which generates control traffic among the controllers whose timely delivery is crucial for network performance.
We focus on the state-of-art ONOS controller, designed to scale to large networks, based on a cluster of self-coordinating controllers, and concentrate on the inter-controller control traffic. Based on real traffic measurements, we develop a model to quan- tify the traffic exchanged among the controllers, which depends on the topology of the controlled network. This model is useful to design and dimension the control network interconnecting the controllers.
SDN models can be categorized as canonical/OpenFlow, broker/API-based, proactive/declarative, overlay, and hybrid models. The canonical model uses a logically centralized controller and "dumb" switches. Broker models use an API to interact between applications and the network. Proactive models use a compiler to translate high-level network definitions. Overlay models program edge devices to manage tunnels. Hybrid models combine centralized and distributed control. Future work is needed to maximize the benefits of combining models while limiting complexity.
Software Defined Optical Networks - Mayur ChannegowdaCPqD
This document discusses software defined optical networks using SDN. Key points include:
- SDN and OpenFlow can decouple the data and control planes in optical networks for automated provisioning and unified control.
- There are challenges in applying SDN to optical networks including switching constraints, physical impairments, multi-domain/multi-technology operation, and network virtualization.
- OpenFlow extensions are needed to abstract optical network elements and account for characteristics like flexible grid networks, impairment awareness, and multi-dimensional resource allocation.
- Proof-of-concept demonstrations have shown the potential for media-aware SDN, packet and optical convergence, and virtualization across multiple domains.
Software Defined Optical Networks - Mayur ChannegowdaCPqD
This document discusses software defined optical networks using SDN. Key points include:
- SDN and OpenFlow can decouple the data and control planes in optical networks for automated provisioning and unified control.
- There are challenges in applying SDN to optical networks including switching constraints, physical impairments, multi-domain/multi-technology operation, and network virtualization.
- OpenFlow extensions are needed to abstract optical network elements and account for characteristics like flexible grid networks, impairment awareness, and multi-dimensional resource allocation.
- Proof-of-concept demonstrations have shown the potential for media-aware SDN, packet and optical convergence, and virtualization across multiple domains.
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.
Understanding network and service virtualizationSDN Hub
This document discusses network and service virtualization technologies. It begins with an overview of challenges with current network architectures and how virtualization addresses them. It then covers three key trends: 1) network virtualization using SDN to program networks dynamically, 2) service virtualization using NFV to virtualize network functions, and 3) new infrastructure tools like Open vSwitch, OpenDaylight, and Docker networking. Finally, it discusses approaches to deploying network and service virtualization and provides a vendor landscape.
DEVNET-1175 OpenDaylight Service Function ChainingCisco DevNet
This tutorial will overview the OpenDaylight Service Function Chaining (SFC) architecture, implementation and operation. A description of the SFC components and the Network Service Header (NSH) will be presented. This talk will conclude with a step-by-step demonstration of SFC configuration and operation using the GUI and REST interfaces.
This document provides an overview of software defined networking (SDN), including its evolution from traditional router architectures, the seminal Clean Slate project and OpenFlow protocol, and the current SDN architecture. It discusses key SDN concepts like the separation of the control and data planes, standardization bodies, example applications like VOLTHA and ONOS, and related technologies like NFV and P4.
The document provides an overview of software-defined networking (SDN) fundamentals, including:
- In traditional networks, the control plane and data plane are logically coupled within each network device, whereas SDN separates these planes and centralizes the control plane in an SDN controller.
- The SDN controller holds the entire network description as a graph and can perform optimization calculations. It programs flow entries into forwarding devices using the OpenFlow protocol.
- OpenFlow defines a standard interface that gives access to the forwarding plane of network switches or routers. It separates the data and control planes and allows the control logic to be implemented separately in the SDN controller.
The document discusses security issues in software-defined networking (SDN). It outlines how SDN architectures separate the control plane from the data plane and use centralized controllers. However, this introduces new security threats, such as attacks on controllers, control plane communication, and applications. The document analyzes threats across the different SDN layers and proposes some mitigation approaches, concluding that while SDN was not initially designed with security in mind, it could potentially improve network security when properly implemented.
btNOG 9 presentation Introduction to Software Defined NetworkingAPNIC
SDN evolved from the Clean Slate project which sought to redesign the internet using a clean slate approach. This led to the development of OpenFlow, which separated the control plane and data plane of network devices. SDN is defined as the separation of the network control plane from the forwarding plane, with a control plane controlling several devices. It provides network agility and flexibility through enhanced programmability, disaggregation of the control plane from hardware, and centralized network control with visibility. Key SDOs developing SDN standards include ONF, IETF, and IEEE.
Lecture 1 - Introduction to Course & Course outline.pptxSameer Ali
This document provides an introduction and course outline for a Wireless Communications course. It outlines 5 sections that will be covered: Basics of Wireless Communications, Radiowave propagation characteristics, Fundamentals of Cellular Communication, Mobile Communication Systems (2G-4G), and Wireless Communications of the future. It discusses why wireless communication is important and provides an overview of the history and applications of wireless technologies. It also highlights the growth of mobile data usage and the increasing importance of wireless networks. Students will complete an independent study project on an application of wireless communications.
Software-defined networking (SDN) uses an approach that allows network administrators to programmatically control network behavior dynamically. OpenFlow is an open standard that defines the communication between the control and forwarding layers of the SDN architecture, allowing the network control to be programmed and managed through open source software rather than proprietary hardware switches. OpenFlow switches use flow tables and groups tables that can be populated and manipulated by an OpenFlow controller using the OpenFlow protocol to determine how packets are forwarded through the network.
The document discusses the limitations of existing networks and introduces the concept of software-defined networking (SDN) as a solution. Some key limitations of traditional networks include slow innovation, closed systems, and difficulty experimenting on large production networks. SDN is described as separating the control plane and data plane, making the network programmable from a central controller. This allows for greater flexibility, innovation, and experimentation. The architecture of SDN is explained including layers for infrastructure, control, and applications. OpenFlow is discussed as an open protocol that allows the controller to remotely program the forwarding behavior of switches.
Software Defined Networking(SDN) and practical implementation_truptitrups7778
This document provides an overview of software defined networks (SDN) and OpenFlow protocol. It discusses the limitations of traditional networks and how SDN addresses these issues by decoupling the control plane from the data plane. The key components of the SDN architecture are described, including the control layer with SDN controllers, the infrastructure layer with OpenFlow switches, and the application layer. The document also covers the OpenFlow protocol for communication between controllers and switches, including message types. Examples of SDN controllers like NOX and POX are also mentioned.
This document discusses the limitations of existing networks and introduces the concept of software-defined networking (SDN) as a solution. It outlines that current networks have separate control and data planes, making them difficult to program and innovate on. SDN is proposed to separate the control and data planes, making the network programmable through open interfaces and allowing for centralized control. This enables experimentation, flexibility, and easier integration of new applications and services. The key aspects of SDN architecture include the infrastructure, control, and application layers that communicate through the OpenFlow protocol to enable remote programming of forwarding rules in switches.
The document discusses the transport SDN framework and APIs. It provides an overview of the transport SDN toolkit, including the SDN framework, APIs, and a global transport SDN prototype demonstration. The framework uses a three-layer model with an infrastructure layer containing network elements, a control layer with multiple controllers, and an application layer. Transport SDN APIs are being developed to standardize the southbound and northbound interfaces. The demonstration showed a multi-domain, multi-vendor transport SDN deployment across five carrier labs and nine system vendors.
This document discusses Software Defined Networking (SDN). It describes how traditional networks have tight coupling between the control and data planes, which causes challenges. SDN separates the control and data planes, making the network programmable. The control plane software can run on general hardware. OpenFlow is the communication interface that allows the control plane to program the data plane switches and routers. This gives operators more flexibility and control over how the network functions.
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
- 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)
Inter-controller Traffic in ONOS Clusters for SDN Networks Paolo Giaccone
In distributed SDN architectures, the network is controlled by a cluster of multiple controllers. This distributed ap- proach permits to meet the scalability and reliability requirements of large operational networks. Despite that, a logical centralized view of the network state should be guaranteed, enabling the simple development of network applications. Achieving a consis- tent network state requires a consensus protocol, which generates control traffic among the controllers whose timely delivery is crucial for network performance.
We focus on the state-of-art ONOS controller, designed to scale to large networks, based on a cluster of self-coordinating controllers, and concentrate on the inter-controller control traffic. Based on real traffic measurements, we develop a model to quan- tify the traffic exchanged among the controllers, which depends on the topology of the controlled network. This model is useful to design and dimension the control network interconnecting the controllers.
SDN models can be categorized as canonical/OpenFlow, broker/API-based, proactive/declarative, overlay, and hybrid models. The canonical model uses a logically centralized controller and "dumb" switches. Broker models use an API to interact between applications and the network. Proactive models use a compiler to translate high-level network definitions. Overlay models program edge devices to manage tunnels. Hybrid models combine centralized and distributed control. Future work is needed to maximize the benefits of combining models while limiting complexity.
Software Defined Optical Networks - Mayur ChannegowdaCPqD
This document discusses software defined optical networks using SDN. Key points include:
- SDN and OpenFlow can decouple the data and control planes in optical networks for automated provisioning and unified control.
- There are challenges in applying SDN to optical networks including switching constraints, physical impairments, multi-domain/multi-technology operation, and network virtualization.
- OpenFlow extensions are needed to abstract optical network elements and account for characteristics like flexible grid networks, impairment awareness, and multi-dimensional resource allocation.
- Proof-of-concept demonstrations have shown the potential for media-aware SDN, packet and optical convergence, and virtualization across multiple domains.
Software Defined Optical Networks - Mayur ChannegowdaCPqD
This document discusses software defined optical networks using SDN. Key points include:
- SDN and OpenFlow can decouple the data and control planes in optical networks for automated provisioning and unified control.
- There are challenges in applying SDN to optical networks including switching constraints, physical impairments, multi-domain/multi-technology operation, and network virtualization.
- OpenFlow extensions are needed to abstract optical network elements and account for characteristics like flexible grid networks, impairment awareness, and multi-dimensional resource allocation.
- Proof-of-concept demonstrations have shown the potential for media-aware SDN, packet and optical convergence, and virtualization across multiple domains.
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.
Understanding network and service virtualizationSDN Hub
This document discusses network and service virtualization technologies. It begins with an overview of challenges with current network architectures and how virtualization addresses them. It then covers three key trends: 1) network virtualization using SDN to program networks dynamically, 2) service virtualization using NFV to virtualize network functions, and 3) new infrastructure tools like Open vSwitch, OpenDaylight, and Docker networking. Finally, it discusses approaches to deploying network and service virtualization and provides a vendor landscape.
DEVNET-1175 OpenDaylight Service Function ChainingCisco DevNet
This tutorial will overview the OpenDaylight Service Function Chaining (SFC) architecture, implementation and operation. A description of the SFC components and the Network Service Header (NSH) will be presented. This talk will conclude with a step-by-step demonstration of SFC configuration and operation using the GUI and REST interfaces.
This document provides an overview of software defined networking (SDN), including its evolution from traditional router architectures, the seminal Clean Slate project and OpenFlow protocol, and the current SDN architecture. It discusses key SDN concepts like the separation of the control and data planes, standardization bodies, example applications like VOLTHA and ONOS, and related technologies like NFV and P4.
The document provides an overview of software-defined networking (SDN) fundamentals, including:
- In traditional networks, the control plane and data plane are logically coupled within each network device, whereas SDN separates these planes and centralizes the control plane in an SDN controller.
- The SDN controller holds the entire network description as a graph and can perform optimization calculations. It programs flow entries into forwarding devices using the OpenFlow protocol.
- OpenFlow defines a standard interface that gives access to the forwarding plane of network switches or routers. It separates the data and control planes and allows the control logic to be implemented separately in the SDN controller.
The document discusses security issues in software-defined networking (SDN). It outlines how SDN architectures separate the control plane from the data plane and use centralized controllers. However, this introduces new security threats, such as attacks on controllers, control plane communication, and applications. The document analyzes threats across the different SDN layers and proposes some mitigation approaches, concluding that while SDN was not initially designed with security in mind, it could potentially improve network security when properly implemented.
btNOG 9 presentation Introduction to Software Defined NetworkingAPNIC
SDN evolved from the Clean Slate project which sought to redesign the internet using a clean slate approach. This led to the development of OpenFlow, which separated the control plane and data plane of network devices. SDN is defined as the separation of the network control plane from the forwarding plane, with a control plane controlling several devices. It provides network agility and flexibility through enhanced programmability, disaggregation of the control plane from hardware, and centralized network control with visibility. Key SDOs developing SDN standards include ONF, IETF, and IEEE.
Lecture 1 - Introduction to Course & Course outline.pptxSameer Ali
This document provides an introduction and course outline for a Wireless Communications course. It outlines 5 sections that will be covered: Basics of Wireless Communications, Radiowave propagation characteristics, Fundamentals of Cellular Communication, Mobile Communication Systems (2G-4G), and Wireless Communications of the future. It discusses why wireless communication is important and provides an overview of the history and applications of wireless technologies. It also highlights the growth of mobile data usage and the increasing importance of wireless networks. Students will complete an independent study project on an application of wireless communications.
This document discusses security and privacy challenges in cloud computing. It begins with an introduction to cloud computing models and background. It then outlines some of the core security issues like loss of control over data, lack of trust in third party providers, and risks from multi-tenancy. The document proposes a threat model approach and taxonomy of fears related to confidentiality, integrity, availability and privacy. Overall, the core issue discussed is the difficulty of trusting other customers and providers in a shared cloud infrastructure.
This document provides an overview of an introductory computer security class. It outlines administrative details such as staff, grading, and communication. It then discusses key topics that will be covered including the components of computer security, threats, vulnerabilities, attacks, controls, security policy, and assurance. Example topics that will be covered in lectures are also listed.
This document discusses security challenges in mobile networks and proposes solutions for fault-tolerant authentication. It introduces two schemes: 1) a virtual home agent scheme that uses a master home agent and backup home agents to provide uninterrupted service when failures occur. 2) A hierarchical authentication scheme that organizes home agents in a tree structure and assigns keys based on priority to select an alternative agent. It also discusses using clusters of front-end and back-end servers to scale authentication in a distributed manner. Future work involves quantifying priority factors and simulating the proposed approaches.
Data centers are large physical facilities that house servers, networking equipment, and other infrastructure to deliver computing resources and services. They provide utilities like power, cooling, security and shelter. Typical data centers range from 500-5000 square meters and consume 1-20 MW of power on average. Modern cloud-based data centers are designed with multiple regions and availability zones to provide redundancy and prevent failures across entire regions. They use software-defined infrastructure to dynamically allocate resources based on workload demands and improve utilization of servers. Managing the scale and complexity of data centers remains an ongoing challenge due to their growth and the massive amounts of data generated each day.
The document provides an introduction to computer security concepts including examples of security breaches from an FBI report, definitions of key security pillars like confidentiality, integrity and availability, and descriptions of vulnerabilities, threats and controls. It discusses different types of threats like interception, interruption and modification of assets, and levels of vulnerabilities from hardware to software to data to people. Examples of software threats include trojan horses, viruses, logic bombs and trapdoors.
- SDN is defined as separating the network control plane from the forwarding plane, allowing a single control plane to control multiple forwarding devices. (Paragraph 1)
- Key dimensions of SDN include disaggregating the control and data planes, having a centralized vs decentralized control plane, and using fixed-function vs programmable data planes. SDN has progressed through phases of network operators taking more control. (Paragraph 2)
- SDN enables use cases like network virtualization, SD-WAN, traffic engineering, bare metal switching, and in-band network telemetry. (Paragraph 3)
SINDH SALES TAX ON SERVICES ACT 2011.pdfSameer Ali
This document outlines the Sindh Sales Tax on Services Act of 2011 which establishes a tax on services provided in Sindh province, Pakistan.
The Act defines key terms related to taxable services and establishes a scope of tax that applies to both residents and non-residents providing taxable services in Sindh. It exempts certain services and allows the Board to amend schedules of tax rates.
The Act requires registration of service providers, establishes rules for record keeping, audits, and tax returns. It appoints authorities to administer the tax and establishes offenses and penalties for non-compliance. The Act also outlines procedures for appeals, recovery of tax arrears, and holds agents responsible for collection and payment
Starting a business is like embarking on an unpredictable adventure. It’s a journey filled with highs and lows, victories and defeats. But what if I told you that those setbacks and failures could be the very stepping stones that lead you to fortune? Let’s explore how resilience, adaptability, and strategic thinking can transform adversity into opportunity.
The Steadfast and Reliable Bull: Taurus Zodiac Signmy Pandit
Explore the steadfast and reliable nature of the Taurus Zodiac Sign. Discover the personality traits, key dates, and horoscope insights that define the determined and practical Taurus, and learn how their grounded nature makes them the anchor of the zodiac.
Discover timeless style with the 2022 Vintage Roman Numerals Men's Ring. Crafted from premium stainless steel, this 6mm wide ring embodies elegance and durability. Perfect as a gift, it seamlessly blends classic Roman numeral detailing with modern sophistication, making it an ideal accessory for any occasion.
https://rb.gy/usj1a2
AI Transformation Playbook: Thinking AI-First for Your BusinessArijit Dutta
I dive into how businesses can stay competitive by integrating AI into their core processes. From identifying the right approach to building collaborative teams and recognizing common pitfalls, this guide has got you covered. AI transformation is a journey, and this playbook is here to help you navigate it successfully.
Unlocking WhatsApp Marketing with HubSpot: Integrating Messaging into Your Ma...Niswey
50 million companies worldwide leverage WhatsApp as a key marketing channel. You may have considered adding it to your marketing mix, or probably already driving impressive conversions with WhatsApp.
But wait. What happens when you fully integrate your WhatsApp campaigns with HubSpot?
That's exactly what we explored in this session.
We take a look at everything that you need to know in order to deploy effective WhatsApp marketing strategies, and integrate it with your buyer journey in HubSpot. From technical requirements to innovative campaign strategies, to advanced campaign reporting - we discuss all that and more, to leverage WhatsApp for maximum impact. Check out more details about the event here https://events.hubspot.com/events/details/hubspot-new-delhi-presents-unlocking-whatsapp-marketing-with-hubspot-integrating-messaging-into-your-marketing-strategy/
NIMA2024 | De toegevoegde waarde van DEI en ESG in campagnes | Nathalie Lam |...BBPMedia1
Nathalie zal delen hoe DEI en ESG een fundamentele rol kunnen spelen in je merkstrategie en je de juiste aansluiting kan creëren met je doelgroep. Door middel van voorbeelden en simpele handvatten toont ze hoe dit in jouw organisatie toegepast kan worden.
Part 2 Deep Dive: Navigating the 2024 Slowdownjeffkluth1
Introduction
The global retail industry has weathered numerous storms, with the financial crisis of 2008 serving as a poignant reminder of the sector's resilience and adaptability. However, as we navigate the complex landscape of 2024, retailers face a unique set of challenges that demand innovative strategies and a fundamental shift in mindset. This white paper contrasts the impact of the 2008 recession on the retail sector with the current headwinds retailers are grappling with, while offering a comprehensive roadmap for success in this new paradigm.
Zodiac Signs and Food Preferences_ What Your Sign Says About Your Tastemy Pandit
Know what your zodiac sign says about your taste in food! Explore how the 12 zodiac signs influence your culinary preferences with insights from MyPandit. Dive into astrology and flavors!
The Genesis of BriansClub.cm Famous Dark WEb PlatformSabaaSudozai
BriansClub.cm, a famous platform on the dark web, has become one of the most infamous carding marketplaces, specializing in the sale of stolen credit card data.
Profiles of Iconic Fashion Personalities.pdfTTop Threads
The fashion industry is dynamic and ever-changing, continuously sculpted by trailblazing visionaries who challenge norms and redefine beauty. This document delves into the profiles of some of the most iconic fashion personalities whose impact has left a lasting impression on the industry. From timeless designers to modern-day influencers, each individual has uniquely woven their thread into the rich fabric of fashion history, contributing to its ongoing evolution.
Storytelling is an incredibly valuable tool to share data and information. To get the most impact from stories there are a number of key ingredients. These are based on science and human nature. Using these elements in a story you can deliver information impactfully, ensure action and drive change.
How are Lilac French Bulldogs Beauty Charming the World and Capturing Hearts....Lacey Max
“After being the most listed dog breed in the United States for 31
years in a row, the Labrador Retriever has dropped to second place
in the American Kennel Club's annual survey of the country's most
popular canines. The French Bulldog is the new top dog in the
United States as of 2022. The stylish puppy has ascended the
rankings in rapid time despite having health concerns and limited
color choices.”
Call8328958814 satta matka Kalyan result satta guessing➑➌➋➑➒➎➑➑➊➍
Satta Matka Kalyan Main Mumbai Fastest Results
Satta Matka ❋ Sattamatka ❋ New Mumbai Ratan Satta Matka ❋ Fast Matka ❋ Milan Market ❋ Kalyan Matka Results ❋ Satta Game ❋ Matka Game ❋ Satta Matka ❋ Kalyan Satta Matka ❋ Mumbai Main ❋ Online Matka Results ❋ Satta Matka Tips ❋ Milan Chart ❋ Satta Matka Boss❋ New Star Day ❋ Satta King ❋ Live Satta Matka Results ❋ Satta Matka Company ❋ Indian Matka ❋ Satta Matka 143❋ Kalyan Night Matka..
𝐔𝐧𝐯𝐞𝐢𝐥 𝐭𝐡𝐞 𝐅𝐮𝐭𝐮𝐫𝐞 𝐨𝐟 𝐄𝐧𝐞𝐫𝐠𝐲 𝐄𝐟𝐟𝐢𝐜𝐢𝐞𝐧𝐜𝐲 𝐰𝐢𝐭𝐡 𝐍𝐄𝐖𝐍𝐓𝐈𝐃𝐄’𝐬 𝐋𝐚𝐭𝐞𝐬𝐭 𝐎𝐟𝐟𝐞𝐫𝐢𝐧𝐠𝐬
Explore the details in our newly released product manual, which showcases NEWNTIDE's advanced heat pump technologies. Delve into our energy-efficient and eco-friendly solutions tailored for diverse global markets.
Unveiling the Dynamic Personalities, Key Dates, and Horoscope Insights: Gemin...my Pandit
Explore the fascinating world of the Gemini Zodiac Sign. Discover the unique personality traits, key dates, and horoscope insights of Gemini individuals. Learn how their sociable, communicative nature and boundless curiosity make them the dynamic explorers of the zodiac. Dive into the duality of the Gemini sign and understand their intellectual and adventurous spirit.
3. Administrative Details
• Course Format
– Student Engagement (30%)
• Class Participation (20%)
• Paper Reviews (10%)
– Course Assignments (20%)
• Learning to use SDN environments
• Writing Controller Applications
– Course Project (60%)
• Deep dive into an SDN topic
4. Outline
• Section 1: SDN Ecosystem
– SDN Motivation
– SDN Primer
– Dimensions of SDN Environments
– Dimensions of SDN Applications
• Section 2: OpenFlow Primer
• Section 3: Demo/Use-cases
– Network Virtualization
• Section 4: SDN Challenges
– SDN Challenges
6. Network Today…
• Vertical integrated stacks
– Similar to PC in 1980s
IBM’s Mainframe
Cisco Routers
D.B.
O.S
CPU
COBOL Apps. VLANS
Switch O.S.
ASIC
L3 Routing
7. Implications of Networking…
• Restricted to ill defined vendor CLI
– Provisioning is slow….
• VM provisioning: 1min
• Virtual network provisioning: 1-3 weeks
8. Software Defined Networking
• Southbound API: decouples the switch hardware from
control function
– Data plane from control plane
• Switch Operating System: exposes switch hardware
primitives
Network O.S.
Applications
Applications
Applications
Southbound
API
SDN
Switch Operating System
Switch Hardware
Network O.S.
ASIC
Applications
Applications
Current Switch
Vertical stack
SDN Switch
Decoupled
stack
9. Implications Of SDN
Controller (N. O.S.)
Applications
Applications
Applications
Southbound
API
Switch O.S
Switch HW
Switch O.S
Switch HW
Switch O.S
Switch HW
Global View
Programmatic
Control
Current Networking SDN Enabled Environment
Network O.S.
ASIC
Applications
Applications
Network O.S.
ASIC
Applications
Applications
Network O.S.
ASIC
Applications
Applications
10. Implications Of SDN
Current Networking SDN Enabled Environment
Controller (N. O.S.)
Applications
Applications
Applications
Southbound
API
Switch O.S
Switch HW
Switch O.S
Switch HW
Switch O.S
Switch HW
• Distributed protocols
• Each switch has a brain
• Hard to achieve optimal
solution
• Network configured indirectly
• Configure protocols
• Hope protocols converge
• Global view of the network
• Applications can achieve optimal
• Southbound API gives fine grained control
over switch
• Network configured directly
• Allows automation
• Allows definition of new interfaces
Network O.S.
ASIC
Applications
Applications
Network O.S.
ASIC
Applications
Applications
Network O.S.
ASIC
Applications
Applications
11. How SDN Works
Controller (N. O.S.)
Applications
Applications
Applications
Southbound
API
Switch H.W
Switch O.S
Switch H.W
Switch O.S
12. How to Pick an SDN Environment
Network O.S.
Applications
Applications
Applications
Southbound
API
SDN
Switch Operating System
Switch Hardware
What is the Southbound AP!?
Is the switch hardware
and OS closed?
Is the switch virtual or
physical?
How easy is it to develop
on for the
Controller platform?
13. Dimensions of SDN Environments:
Vendor Devices
Vertical Stacks
• Vendor bundles switch and
switch OS
– Restricted to vendor OS and
vendor interface
• Low operational overhead
– One stop shop
Whitebox Networking
• Vendor provides hardware
with no switch OS
• Switch OS provided by third
party
– Flexibility in picking OS
• High operational overhead
– Must deal with multiple
vendors
14. Dimensions of SDN Environments:
Switch Hardware
Virtual: Overlay
• Pure software implementation
– Assumes programmable virtual
switches
– Run in Hypervisor or in the OS
– Larger Flow Table entries (more
memory and CPU)
• Backward compatible
– Physical switches run traditional
protocols
• Traffic sent in tunnels
– Lack of visibility into physical network
Physical: Underlay
• Fine grained control and visibility into
network
• Assumes specialized hardware
– Limited Flow Table entries
16. Dimensions of SDN Environments:
Controller Types
Modular Controllers
• Application code manipulates
forwarding rules
– E.g. OpenDaylight, Floodlight
• Written in imperative
languages
– Java, C++, Python
• Dominant controller style
High Level Controllers
• Application code specifies declarative
policies
– E.g. Frenetic, McNettle
• Application code is verifiable
– Amendable to formal verification
• Written in functional
languages
– Nettle, OCamal
17. BigSwitch
• Controller Type
• Modular: Floodlight
• Southbound API: OpenFlow
• OpenFlow 1.3
• SDN Device: Whitebox
• (indigo)
• SDN Flavor
• Underlay+Overlay
18. Juniper Contrail
• Controller Type
• Modular: OpenContrail
• Southbound API: XMPP/NetConf
• BGP+MPLS
• SDN Device: Vertical Stack
• Propriety Junos
• SDN Flavor
• Overlay
19. SDN EcoSystem
Arista
OF + proprietary
Underlay
Vertical Stack
Broadcom
OF + proprietary
Underlay
Vertical Stack
HP
OF
Underlay
Vertical Stack
Cisco
OF + proprietary
Underlay+Overlay
Vertical Stack
FloodLight
OF
Underlay+Overlay
Whitebox
Dell
OF
Underlay
Vertical Stack
HP
OF
Underlay
Vertical Stack
Alcatel
BGP
Overlay
Vertical Stack
Juniper
BGP+NetConf
Overlay
Vertical Stack
20. SDN Stack
• Southbound API: decouples the switch hardware from
control function
– Data plane from control plane
• Switch Operating System: exposes switch hardware
primitives
Controller (Network O.S.)
Applications
Applications
Applications
Southbound
API
SDN
Switch Operating System
Switch Hardware
22. OpenFlow
• Developed in Stanford
– Standardized by Open Networking Foundation (ONF)
– Current Version 1.4
• Version implemented by switch vendors: 1.3
• Allows control of underlay + overlay
– Overlay switches: OpenVSwitch/Indigo-light
PC
23. How SDN Works: OpenFlow
Controller (N. O.S.)
Applications
Applications
Applications
Southbound
API
Switch H.W
Switch O.S
Switch H.W
Switch O.S
OpenFlow
OpenFlow
24. OpenFlow: Anatomy of a Flow Table
Entry
Switch
Port
MAC
src
MAC
dst
Eth
type
VLAN
ID
IP
Src
IP
Dst
IP
Prot
L4
sport
L4
dport
Match Action Counter
1. Forward packet to zero or more ports
2. Encapsulate and forward to controller
3. Send to normal processing pipeline
4. Modify Fields
When to delete the entry
VLAN
pcp
IP
ToS
Priority Time-out
What order to process the rule
# of Packet/Bytes processed by the rule
25. OpenFlow: Types of Messages
Asynchronous (Controller-to-Switch)
Send-packet: to send packet out of a specific port on a switch
Flow-mod: to add/delete/modify flows in the flow table
Asynchronous (initiated by the switch)
Read-state: to collect statistics about flow table, ports and individual flows
Features: sent by controller when a switch connects to find out the features supported by a switch
Configuration: to set and query configuration parameters in the switch
Asynchronous (initiated by the switch)
Packet-in: for all packets that do not have a matching rule, this event is sent to controller
Flow-removed: whenever a flow rule expires, the controller is sent a flow-removed message
Port-status: whenever a port configuration or state changes, a message is sent to controller
Error: error messages
Symmetric (can be sent in either direction without
solicitation)
Hello: at connection startup
Echo: to indicate latency, bandwidth or liveliness of a controller-switch connection
Vendor: for extensions (that can be included in later OpenFlow versions)
26. Dimension of SDN Applications:
Rule installation
Proactive Rules Reactive Rules
Controller (N. O.S.)
Applications
Applications
Applications
Switch H.W
O.S
Controller (N. O.S.)
Applications
Applications
Applications
Switch H.W
O.S
27. Dimension of SDN Applications:
Rule installation
Proactive Rules
• Controller pre-installs flow
table entries
– Zero flow setup time
• Requires installation of rules
for all possible traffic patterns
– Requires use of aggregate rules
(Wildcards)
– Require foreknowledge of
traffic patterns
– Waste flow table entries
Reactive Rules
• First packet of each flow
triggers rule insertion by the
controller
– Each flow incurs flow setup
time
– Controller is bottleneck
– Efficient use of flow tables
28. Dimensions of SDN Applications:
Granularity of Rules
Microflow WildCards (aggregated rules)
Controller (N. O.S.)
Applications
Applications
Applications
Switch H.W
O.S
Controller (N. O.S.)
Applications
Applications
Applications
Switch H.W
O.S
29. Dimensions of SDN Applications:
Granularity of Rules
Microflow
• One flow table matches one
flow
• Uses CAM/hash-table
– 10-20K per physical switch
• Allows precisions
– Monitoring: gives counters for
individual flows
– Access-Control: allow/deny
individual flows
WildCards (aggregated rules)
• One flow table entry
matches a group of flow
• Uses TCAM
– 5000~4K per physical switch
• Allows scale
– Minimizes overhead by
grouping flows
30. Dimensions of SDN Applications:
Granularity of Rules
Distributed Controller Centralized Controller
Controller (N. O.S.)
Applications
Applications
Applications
Switch O.S
Switch HW
Switch O.S
Switch HW
Switch O.S
Switch HW
Controller (N. O.S.)
Applications
Applications
Applications
Switch O.S
Switch HW
Switch O.S
Switch HW
Switch O.S
Switch HW
Controller (N. O.S.)
Applications
Applications
Applications
Controller (N. O.S.)
Applications
Applications
Applications
35. Controller Availability
“control a large force like a small force: divide and conquer”
--Sun Tzu, Art of war
47
• How many controllers?
• How do you assign switches to controllers?
• More importantly: which assignment reduces
processing time
• How to ensure consistency between
controllers
Controller (N. O.S.)
Applications
Applications
Applications
Controller (N. O.S.)
Applications
Applications
Applications
Controller (N. O.S.)
Applications
Applications
Applications
36. SDN Reliability/Fault Tolerance
48
Controller (N. O.S.)
Applications
Applications
Applications
Controller: Single point of control
• Bug in controller takes the whole
network down
Existing network survives failures or
bugs in code for any one devices
37. SDN Reliability/Fault Tolerance
49
Controller (N. O.S.)
Applications
Applications
Applications
Controller: Single point of control
• Bug in controller takes the whole
network down
• Single point of failure
Existing network survives failures or
bugs in code for any one devices
38. SDN Security
50
Controller (N. O.S.)
Applications
Applications
Applications
Controller: Single point of control
• Compromise controller
If one device in the current networks
are compromised the network may
still be safe
39. SDN Security
51
Controller (N. O.S.)
Applications
Applications
Applications
Controller: Single point of control
• Compromise controller
• Denial of Service attack the
control channel
40. Data-Plane Limitations
• Limited Number of TCAM entries
– Currently only 1K
• Networks have more than 1K flows
– How to fit network in limited entries?
• Limited control channel capacity
– All switches use same controller interface
– Need to rate limit control messages
• Prioritize certain messages
• Limited switch CPU
– Less power than a smartphone
– Limit control messages and actions that use
CPU
Controller (N. O.S.)
Applications
Applications
Applications
Switch H.W
O.S
41. Debugging SDNs
• Problems can occur
anywhere in the SDN
stack
– How do you diagnose
each type of problem?
Network O.S.
Applications
Applications
Applications
Switch Operating
System
Switch Hardware
Buggy
App
Buggy
NOS
Switch Operating
System
Switch Hardware
Buggy
Switc
h
H/W
Buggy
Switc
h