Software Defined Networking - 2
-
Upload
t-s-pradeep-kumar -
Category
Engineering
-
view
68 -
download
4
Transcript of Software Defined Networking - 2
![Page 1: Software Defined Networking - 2](https://reader034.fdocuments.us/reader034/viewer/2022042611/587f59581a28ab0d378b6e35/html5/thumbnails/1.jpg)
SOFTWARE DEFINED NETWORKING
T S Pradeep Kumarhttp://www.nsnam.com
![Page 2: Software Defined Networking - 2](https://reader034.fdocuments.us/reader034/viewer/2022042611/587f59581a28ab0d378b6e35/html5/thumbnails/2.jpg)
NEED FOR SDN
![Page 3: Software Defined Networking - 2](https://reader034.fdocuments.us/reader034/viewer/2022042611/587f59581a28ab0d378b6e35/html5/thumbnails/3.jpg)
REQUIREMENTS FOR SDN• ODCA (open Data Centre Alliance)
suggested the requirements
• Adaptability
• Automation
• Maintainability
• Model Management
• Mobility
• Integrated Security
• On Demand Scaling
![Page 4: Software Defined Networking - 2](https://reader034.fdocuments.us/reader034/viewer/2022042611/587f59581a28ab0d378b6e35/html5/thumbnails/4.jpg)
SDN ARCHITECTURE
![Page 5: Software Defined Networking - 2](https://reader034.fdocuments.us/reader034/viewer/2022042611/587f59581a28ab0d378b6e35/html5/thumbnails/5.jpg)
SDN ARCHITECTURE
![Page 6: Software Defined Networking - 2](https://reader034.fdocuments.us/reader034/viewer/2022042611/587f59581a28ab0d378b6e35/html5/thumbnails/6.jpg)
SDN ARCHITECTURE
• Open interfaces are defined so that the switching hardware presents a uniform interface regardless of the details of internal implementation
• They enable networking applications to communicate with the SDN controllers.
![Page 7: Software Defined Networking - 2](https://reader034.fdocuments.us/reader034/viewer/2022042611/587f59581a28ab0d378b6e35/html5/thumbnails/7.jpg)
SDN ARCHITECTURE
![Page 8: Software Defined Networking - 2](https://reader034.fdocuments.us/reader034/viewer/2022042611/587f59581a28ab0d378b6e35/html5/thumbnails/8.jpg)
SDN ARCHITECTURE
• Data plane is simply responsible for the relaying or forwarding of packets
• Control plane provides intelligence in designing routes, setting priority, routing policy parameters to meet QoS and QoE and to cope with the shifting traffic patterns.
![Page 9: Software Defined Networking - 2](https://reader034.fdocuments.us/reader034/viewer/2022042611/587f59581a28ab0d378b6e35/html5/thumbnails/9.jpg)
SOFTWARE DEFINED ARCHITECTURE
![Page 10: Software Defined Networking - 2](https://reader034.fdocuments.us/reader034/viewer/2022042611/587f59581a28ab0d378b6e35/html5/thumbnails/10.jpg)
![Page 11: Software Defined Networking - 2](https://reader034.fdocuments.us/reader034/viewer/2022042611/587f59581a28ab0d378b6e35/html5/thumbnails/11.jpg)
SDA• Data plane consists of virtual and physical switches.
• both the switches are responsible for forwarding the packets.
• Buffer, priority parameters and other data structures can be vendor dependent.
• But each switch must use open API that should be used between the control and data plane.
• OpenFlow is one such example (SouthBound API) from control to data plane.
![Page 12: Software Defined Networking - 2](https://reader034.fdocuments.us/reader034/viewer/2022042611/587f59581a28ab0d378b6e35/html5/thumbnails/12.jpg)
SDN CHARACTERISTICS• Control plane is separated from the data plane
• control plane is implemented in a central controller or a set of coordinated centralised controllers
• open interfaces are defined between the devices in the control plane and those in the data plane
• the network is programmable by applications running on top of the SDN controllers
![Page 13: Software Defined Networking - 2](https://reader034.fdocuments.us/reader034/viewer/2022042611/587f59581a28ab0d378b6e35/html5/thumbnails/13.jpg)
SDN DATA PLANE FUNCTIONS
• Control support functions
• interacts with SDN Control layer
• the switch communicates with the controller via openflow switch protocol
• data forwarding functions
![Page 14: Software Defined Networking - 2](https://reader034.fdocuments.us/reader034/viewer/2022042611/587f59581a28ab0d378b6e35/html5/thumbnails/14.jpg)
SDN DATA PLANE
![Page 15: Software Defined Networking - 2](https://reader034.fdocuments.us/reader034/viewer/2022042611/587f59581a28ab0d378b6e35/html5/thumbnails/15.jpg)
Data plane Network Device
![Page 16: Software Defined Networking - 2](https://reader034.fdocuments.us/reader034/viewer/2022042611/587f59581a28ab0d378b6e35/html5/thumbnails/16.jpg)
• The above figure shows 3 I/O Ports• One - providing control communication with the
SDN controller• Other two for the input and output of data
packets• It can have multiple ports also to communicate
with SDN controllers and might have more number of ports for input and output.
DATA PLANE NETWORK DEVICE
![Page 17: Software Defined Networking - 2](https://reader034.fdocuments.us/reader034/viewer/2022042611/587f59581a28ab0d378b6e35/html5/thumbnails/17.jpg)
OPENFLOW LOGICAL NETWORK DEVICE
![Page 18: Software Defined Networking - 2](https://reader034.fdocuments.us/reader034/viewer/2022042611/587f59581a28ab0d378b6e35/html5/thumbnails/18.jpg)
• For practical SDN, two requirements are needed,
• there must be a logical architecture in all switches, routers and other network devices to managed by an SDN controller.
• a standard, secure protocol is needed between the controller and the network device
![Page 19: Software Defined Networking - 2](https://reader034.fdocuments.us/reader034/viewer/2022042611/587f59581a28ab0d378b6e35/html5/thumbnails/19.jpg)
OPENFLOW SWITCH
![Page 20: Software Defined Networking - 2](https://reader034.fdocuments.us/reader034/viewer/2022042611/587f59581a28ab0d378b6e35/html5/thumbnails/20.jpg)
OPENFLOW SWITCHES• it defines three ports
• physical ports
• hardware interface of a switch.
• logical ports
• higher level abstractions ports
• defined using non openflow methods (Ex. loopback interfaces)
• reserved ports
• defined by openflow specification
• generic forwarding actions like receiving from or sending to controller, flooding, etc
![Page 21: Software Defined Networking - 2](https://reader034.fdocuments.us/reader034/viewer/2022042611/587f59581a28ab0d378b6e35/html5/thumbnails/21.jpg)
OPENFLOW SWITCH
![Page 22: Software Defined Networking - 2](https://reader034.fdocuments.us/reader034/viewer/2022042611/587f59581a28ab0d378b6e35/html5/thumbnails/22.jpg)
OPENFLOW TABLE STRUCTURE
![Page 23: Software Defined Networking - 2](https://reader034.fdocuments.us/reader034/viewer/2022042611/587f59581a28ab0d378b6e35/html5/thumbnails/23.jpg)
SDN CONTROL PLANE
![Page 24: Software Defined Networking - 2](https://reader034.fdocuments.us/reader034/viewer/2022042611/587f59581a28ab0d378b6e35/html5/thumbnails/24.jpg)
SDN CONTROL PLANE
North bound interface
Shortest path forwarding
Notification Manager
Security mechanisms
Technology Manager Statistics Manager Device Manager
Southbound interfaceEast/Westbound interface
East/Westbound Mechanisms
![Page 25: Software Defined Networking - 2](https://reader034.fdocuments.us/reader034/viewer/2022042611/587f59581a28ab0d378b6e35/html5/thumbnails/25.jpg)
SDN CONTROL PLANE• shortest path forwarding (routing information collected from
the switches)
• notification manager (alarm notifications, security alarms, etc)
• security mechanisms (provides isolation and security)
• topology manager
• statistics manager (collects data on traffic)
• device manager (manages flow tables)
![Page 26: Software Defined Networking - 2](https://reader034.fdocuments.us/reader034/viewer/2022042611/587f59581a28ab0d378b6e35/html5/thumbnails/26.jpg)
• NOS(Network Operating Systems)
• a server based OS for networking.
• it provides directory services, network management, network monitoring, network policies, user group management, network security and other network related functions.
![Page 27: Software Defined Networking - 2](https://reader034.fdocuments.us/reader034/viewer/2022042611/587f59581a28ab0d378b6e35/html5/thumbnails/27.jpg)
SDN CONTROLLERS• Commercial and open source implementation of SDN controllers
• OpenDaylight
• open source and java based,
• may run one or more cluster servers in the network
• Open Network Operating Systems (ONOS)
• open source SDN NOS
• multiple distributed controllers
• POX
• open source
• Web based GUI written in python
• shortens is experimental and developmental cycles.
![Page 28: Software Defined Networking - 2](https://reader034.fdocuments.us/reader034/viewer/2022042611/587f59581a28ab0d378b6e35/html5/thumbnails/28.jpg)
SDN CONTROLLERS• Beacon
• Open source developed by Stanford.
• Written in Java, integrated with Eclipse
• It is the first SDN Controller
• Floodlight
• Open source. based on beacon initially.
• Web based and java based GUI is available
• Ryu
• Open source developed by NTT, written in Python
• Onix
• distributed controller developed by Google,, VMWare, and NTT.
• It is Commercial