![]() ![]() name: PLAY 3 - deploy spoke configuration name: PLAY 2 - deploy hub configuration name: PLAY 1 - deploy common configuration Here’s our playbook: cat deploy_dmvpn.yml All these roles are called by a single playbook that provisions the whole network, and then tests connectivity. The ‘test’ role performs basic ping tests from each router to all of the loopback addresses in the topology. ‘Crypto’ takes care of the Tunnels, ‘Interfaces’ looks after the interfaces, and the ‘hub’ and ‘spoke’ roles handle configuration that is specific to the device role. The ‘ACL’ role applies an access control list to the WAN interface. You can find the all code in my Git repo.Īs per best practice we are using Ansible Roles to break the deployment up into smaller chunks. The DMVPN network is dual-hub, with 3 spokes, using EIGRP as the WAN routing protocol, and based on this Cisco validated design. I’ve tested this in GNS3 on IOSv 15.6 routers and the Network Automation appliance from the GNS3 marketplace, with Ansible v2.5 installed. I use this as a lab for testing, but with a few tweaks you could use this to deploy a production DMVPN network. In this post we will automate the deployment of a Cisco DMVPN network. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |