![]() Netconf-yang cisco-odm actions parse Interfaces The VMs containing the two devices are deployed within a single hypervisor and connected with one interface to the management network and back-to-back with the second pair of interfaces for BGP peering.Įach device contains some basic initial configuration to allow it be reachable from the Ansible server. The test environment will consist of a single instance of CSR1000v running IOS-XE version 16.4.1 and a single instance of vMX running JUNOS version 17.1R1.8. I hope this promise is exciting enough so without further ado, let’s get cracking. To demonstrate the model-agnostic behaviour I will use a mixture of vendor’s native, IETF and OpenConfig YANG models. ![]() All configuration and operational state will be based on a couple of YAML files.State verification will be done with no pattern-matching or screen-scraping.All changes will be pushed through a single, vendor and model-independent Ansible module.I will not use any templates and absolutely no XML/JSON for device config generation. ![]() However the approach I’m going to demonstrate in this post, using YANG and NETCONF, will have a few notable differences: The idea of using Ansible for configuration changes and state verification is not new. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |