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. |
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.
Contact Us