When using Open Daylight (ODL), two open standards for configuration are OpenFlow & NETCONF. Which is the better choice ? Is there an option for both ? A use case on when to use OpenFlow and NETCONF protocols in the Enterprise by using the best features of each protocol.
In this blog post, Calle Moberg (from Tail-F Systems who makes NETCONF software) highlights that the ONF has embraced NETCONF as mandatory for configuration of OpenFlow enabled devices. I didn’t know this was coming: […] OF-CONFIG1.0 requires that devices supporting OF-CONFIG 1.0 MUST implement NETCONF protocol as the transport. This in turn implies as specified […]
Over the last few months I’ve been looking at Network Management options that are not OpenFlow or SNMP based. This led to NETCONF & YANG and these are my working notes from some time spent reading and researching.
I’ve been watching NETCONF and YANG for about four years and it seems that it might be breaking through the noise to set a new standard for Network Management data exchange. In short, SNMP isn’t working and the next generation of “blah blah Cloud” will require more sophisticated communication than SNMP can handle. In the last four years, NETCONF has matured and slowly percolated its way through the industry. Now that is has teamed up with YANG we have something that looks like it’s about to burst into the mainstream.