This lab can be completed if you have access to the server infrastructure in a private lab or if you are at an event such as Cisco Live!
Introduction to Standard Device Interfaces
- Why were NETCONF and YANG envisioned and developed
- RFC 3535 and requirements for network management protocols
- NETCONF and YANG to the rescue!
- Developing 101 Topic Review
- Clients and Servers
- Transport Protocol vs Data Model
- Data Format Options
Why do we need another protocol
Current Status of Network Management/Configuration
Despite being more than 50 years since ARPANET, the most common technologies leveraged for network management include:
- Copy and Paste
- Text Editors
- Spreadsheets and Formulas
- CLI Commands
In recent years we have seen an massive increase in the number of applications running on networks, the importance those applications have to organizations, and the rate at which these applications are changing. This has lead to pressure on network architects, engineers, and operators to support these changes.
Network No Longer Isolated
Network Engineers leveraging CLI are no longer the only parties and methods interested in configuring and monitoring the network.
DevOps as an approach to development and operations has proven successful for many organizations, and these teams are quickly looking at how they can expand their reach into the network.
New Web Applications leveraging Micro-Service architectures are building overlay container networks, but as the model matures, these applications look to integration with the underlying network for performance and segmentation.
And the "Cloud" is no longer a destination, but rather a complete approach to delivering IT Services and Applications. This approach demands fully programmatic (i.e. through APIs) access to services. Consumers aren't interested in individual devices and feature configuration, but rather the capabilities that the network can provide.