Synchronizing Multi Controllers For Software Defined Network Guided by MR T Senthilkumar
Synchronizing Multi Controllers For Software Defined Network Guided by MR T Senthilkumar
Difficult to perform real world experiment Closed systems(Black Box) Slow innovation & reduced flexibilty Vendor specific software Innovation is limited to vendor/ vendor partners Barriers to new ideas
Separate Control plane and Data plane entities Execute or run Control plane software on general purpose hardware Decouple from specific networking hardware Have programmable data planes Maintain, control and program data plane state from a central entity An architecture to control not just a networking device but anentire network.
SDN controller
components
Control plane-OS and application (to manage the network) that run on top of it. Forwarding plane contains switches,routers and other network elements. OFP-Protocol-communicates both the planes(n/w controller interface) NOX-binds n/w elements and the abstractions to the applications OF swithes-simple switces with flow table communicates the controller using OF.
Project Requirement
SDN originally created for routing(controlling) within enterprise networks. Our solution enhances the SDN capability to route across enterprise networks. Each enterprise networks are associated with one or more SDN controllers. To achieve routing across enterprise networks, the SDN controllers need to be synchronized.
We are using Mininet to simulate the network topology. Development work is required We are building a new application on POX for synchronization (sync-component)
Synchronization component
Messenger- enables communication between several pox comtrollers When the destination is not part of the network switch invokes the component The component returns the next hop to the switch if a route is available.
OFSWITCH
OFS
OFS
OFS
Thank you