Abstract Software defined networking is a new concept that redefined the current network device architecture and the way they behave. Due to the exponential growth of the Internet and services attached to this worldwide infrastructure, a number of issues have cropped up in modern day networks. This paper discusses a few of these limitations and how the software defined networking approach tries to alleviate them. OpenFlow, released in the year 2008, is a commercially viable implementation of this concept that is being well received by the networking industry at large. The paper also discusses the OpenFlow protocol, its implementation and the challenges facing its widespread acceptance 1. Introduction …show more content…
This is because, to implement any change to the network policies, the network engineers have to reconfigure each device individually to ensure a consistent set of access, security and QoS parameters. Further, with the evolution of Internet and enterprise data centers, the nature of data circulating on the Internet has also undergone a tremendous change. Data transfer in the form of video and audio is increasing at a tremendous pace[2]. Moreover, different sources of data (e.g.- mobile, tablet PCs) have placed considerable pressure on modern networks. The current capacities of network switches do not support the transfer of these mass amounts of data. Moreover, with advent of social media, amount of data generated on websites such as Facebook and LinkedIn has reached humungous levels. As this demand for dynamic and unpredictable data grows, more and more devices have to be added to existing networks and configured accordingly. The need of the hour is to regulate networks centrally and as a whole rather than configure individual network devices and gain more control to achieve flexibility in existing networks. 3. Software Defined Networking Software defined networking is a concept born out of the need to control network devices centrally, wherein the service offered by a device is decoupled from the device in a way that
amid this configuration we tend to look for guidance from them as data, control, and application planes. At base, the data plane is included system segments, whose SDN Data ways uncover their abilities through the Control-Data-Plane Interface (CDPI) Agent. On top, SDN Applications exist inside of the application plane, and impart their needs by means of northward Interface (NBI) Drivers. inside of the centre, the SDN Controller interprets these needs and applies low-level administration over the SDN Data ways, while giving pertinent data up to the SDN
* Opengear supports the OpenFlow/SDN Interoperability Lab. This Software Defined Networking (SDN) technology from the Open
Held, G. (1999). Data communications networking devices: Operation, utilization, and LAN and WAN internetworking. Chichester: Wiley.
Brocade is fully invested in making SDN completely modular to deliver New IP networks based on an open ecosystem. The Brocade SDN Controller is continuously built from the OpenDaylight code, with a virtuous cycle of contributions back to the OpenDaylight community. Physical and virtual networks from multiple vendors can be managed within the Brocade SDN Controller, and organizations can gradually introduce ever-larger portions of their existing networks into the controller domain with single-source technical support for the entire
Networking is not new; it has been around for a long time. The way networking is done changes all the time; let’s look briefly at the past and how networking has changed over the years.
The major goal of Software Defined networks is separate the control plane and the data plane and passing the control to a SDN controller for the programmability of the network resources. The SDN architecture consist of basically 3 layers- (i) the infrastructure layer (ii) the control layer and (iii) the application layer (from top to bottom). The connecting interface between the control and application layer is termed as the NorthBound Interface while between the control layer and the infrastructure layer is termed as SouthBound Interface. The SouthBound Interface uses the Open Flow Protocol to communicate with the lower level switches. The Controller is the main intelligent device present in the architecture that offers a centralized view of the whole network [1].
Many vendors have realized this and have developed some solutions that will be able to address these issues. Most approaches to this solution focus on the overlay solution, simply because the re-design of the enterprise network would be a massive undertaking. With this solution it allows for the organization to have a path of migration that will be able to be followed in the future. Other solutions include changes to the network, as well as the end-point elements. Some of these network access control candidates are: posture based, Cisco network, Microsoft NAP, Juniper NAP, and in-line traffic inspection.
The architecture of SDN allows the controller to control data plane resources. SDN simplifies the configuration of the wide range of resources that are available. SDN must be applicable within systems that already exist which contain many organizations with the need for security of the information that is being shared. Limitations in the real world include the need to exist with the present support systems, administrative or technology fields. Functional subsets maybe summarized from the SDN architecture if the environment is not as complex. Standardization, validation and integration are minimized whenever required, using simple mechanisms. A complex system is partitioned into modular parts in architecture. This helps in managing the level of complexity and reusing the components in order to meet other practical or business goals. Component partitioning is an added advantage when it comes to the type of services delivered to the end user.
The purpose of this report is to assess Computer Dynamic’s current data and communication network. The objective of the report is to offer a proposed solution for a modern network that meets the organisation’s needs.
In the SDN architecture, the control and data planes are decoupled, network intelligence and state are logically centralized, and the underlying network infrastructure is abstracted from the applications [1]. This is the definition of SDN given by Open Network Foundation (ONF).
The current solution as TCP/IP becomes inefficient and subjects to certain problems. An example of this, to search for content, the content must be mapped to a host, and then DNS translates the host name to the location i.e. IP address. The two-step mapping incurs access overhead. Security is an issue since the security coupled to the host. The host becomes a target for security attacks. Also IP is stateless so they cannot be caching capability; the same request would be made times, this lead to unnecessary bandwidth usage. This prompted the research into move the architecture from a host-centric to information-centric.
SDN topology should be designed to provide support to existing traditional applications and at the same time, offer better network control, performance, and reliability.
A simple model of virtual network, subnet, and port abstractions to define network resources are the base for creating OpenStack Networking component. Similar to a VLAN in the physical networking world, network in OpenStack is an isolated layer-2 segment. Subnet is a block of IP version 4 or version 6 addresses, set as an address pool from which OpenStack can assign IP addresses to virtual machines (VMs). Each subnet is stated as a Classless Inter-Domain Routing range[13].
network is flexible enough to reprogram its operation and adapt its configuration to a specific
RakNet is a flexible networking engine that treats the users time as precious, keeping ‘bookkeeping’ to a minimum, such as storing connected IP’s, storing a GUID for connected users, pings, dropouts. This frees development time to work on the project. Alongside the minimal approach for users, the engine is well documented with explanations and examples of how to set up certain situations a user may need. This includes plugins designed alongside the general development of RakNet, to give them a superior level of function then something that people may make to work alongside RakNet.