OpenFlow vs NETCONF

OpenFlow provides controllers of the network to determine the flow of network packets over a network of switches. Controllers are separate from switches. The Internet Engineering Task Force created and standardized the NETCONF network management protocol. NETCONF offers processes for installing, modifying, and deleting network device configurations.

What is OpenFlow?

OpenFlow is a communications protocol that allows remote access of a network to a network switch or router’s forwarding plane. Controllers are separate from switches. It was initially defined as the communication protocol in SDN architectures that allowed the SDN controller to communicate directly with the forwarding plane, which consists of network devices such as switches and routers, both physical and virtual (hypervisor-based), so it is more responsive to changing business requirements.

Why Do We Need OpenFlow?

OpenFlow originally defined the communication protocol in SDN architectures, allowing the SDN controller to interact directly with the forwarding plane of network devices such as switches and routers, both physical and virtual (hypervisor-based), allowing it to better adapt to changing business requirements. Division of hardware and software, control plane and forwarding, and physical and logical settings.

What is NETCONF?

NETCONF is a network device protocol that allows it to be remotely configured and operated. This enables a network management system to send, edit, and remove network devices. Standard application programming interfaces (APIs) are accessible on network devices, allowing the NMS to handle them via NETCONF.

Why Do We Need NETCONF?

NETCONF is one of the primary requirements for networks in the cloud is network automation, which includes quick and on-demand service delivery as well as autonomous operations and maintenance. Conventional network management solutions, such as the command-line interface (CLI) and the Simple Network Management Protocol (SNMP), cannot meet this requirement so NETCONF comes in, which is becoming popular in network automation.

Difference Between OpenFlow and NETCONF

OpenFlow	NETCONF
OpenFlow is a remote access protocol that allows a network switch or router’s forwarding plane.	NETCONF is a network management protocol enabling a network management system to send, edit, and remove network devices.
OpenFlow-created forwarding table entries are, by definition, temporary. They do not appear in the device setup and are lost upon device reload or connection loss.	NETCONF protocol adjusts device configuration. Whatever you configure using NETCONF shows in the device configuration and can be saved from running to permanent (or startup) when you choose to save the changes.
It is much simpler when compared to Netconf, especially because it is vendor and device-independent.	It is not separate from and follows the standard vendor and device-dependent process while installing route maps based on policy-based routing, static MPLS in/out label mappings, access lists, etc.
Effectively helpful to SDN since it can simply execute the separation of the control and the data planes.	Netconf is inconsistent with the separation of the control and data planes.
It allows you to install the same type of forwarding entries via OpenFlow onto any of the OpenFlow-enabled switches.	You can create an ACL over a Junos switch, or router but the actual data of the relevant Netconf message is going to be vendor-specific.

Conclusion

In this article, we have learned about OpenFlow and NETCONF. OpenFlow is much simpler when compared to Netconf, especially because it is vendor- and device-independent and Netconf is inconsistent with the separation of the control and data planes.

Frequently Asked Questions on OpenFlow and NETCONF – FAQs

What is the limitation of OpenFlow?’

One drawback is that the currently specified match fields only apply to the packet header. Thus, a conventional OpenFlow does not enable deep packet inspection (DPI), which uses fields in the packet’s content to differentiate flows.

What is the purpose of OpenFlow?

The main purpose of OpenFlow is to forward packets to a single or more port.

What layer is OpenFlow?

Layer 2 of the OSI model is the OpenFlow that allows the SDN controller to interact directly with the forwarding plane of network devices.

What is the purpose of NETCONF?

NETCONF provides an interface to install, modify, and remove the configuration of network devices.

Which transport method is used by NETCONF?

NETCONF widely uses Secure Shell (SSH) as the transport layer between network devices. The port number 830 is a customizable option.