Looking at Figure 1, there are three key takeaways to remember. The diagram below highlights the major components involved in a NETCONF transaction. These RPCs contain well-defined XML messages that are very easy to handle inside software applications. It allows network devices to be managed through Remote Procedure Calls (RPCs). The NETCONF protocol solves this problem. And CLI commands and outputs are usually just strings of data without much structure.
For software to be robust, there is a requirement for strict data structures. When it comes to automation, however, the CLI is not the best choice. The CLI is the most human-friendly interface. Most network engineers are familiar with the CLI (Command Line Interface). Network devices may be managed through several options. If you'd like to do a deep dive on NETCONF, check them out. In these posts, we explained the NETCONF protocol in detail. You may have read some of our previous blog posts on NETCONF.
