[SDN Protocols] Part 5 – NETCONF
For those that followed my SDN Protocols series last summer, you might have noticed a missing entry: NETCONF. This protocol has actually existed for some time (the original now-outdated specification was published in 2006), but is appearing more often, especially in discussions pertaining to network automation. The current, updated specification – RFC6241 - covers a fairly large amount of material, so I will attempt to condense here.
NETCONF operates at the management layer of the network, and therefore plays a role similar to that of OVSDB. This is in contrast to protocols like OpenFlow which operate at the control plane.
A key difference between NETCONF and other management protocols (including SNMP) is that NETCONF is built around the idea of a transaction-based configuration model. The NETCONF specification provides for some optional device capabilities aimed at assisting operators with the lifecycle of configuring a network device, such as rolling back a configuration upon an error. Unfortunately, not all network devices support such capabilities, but the protocol was built to make it easier to discover what kind of capabilities a network device can support.
Configuration Datastores
Before getting into the semantics Continue reading
You’ve hit brain freeze. It seemed like such a great idea at the time, but now that it’s 2am, the application is down, and you can’t find the problem, maybe it wasn’t after all. Or maybe it’s 4pm, and you’re sitting at your desk trying to figure out how to resolve a problem, or build a system. You’re completely stuck, and you’ve no idea what to do next.

