This repository is configured to run arista.cvp
& arista.avd
ansible collections against the Arista Test Drive (ATD) Topology.
To access an Arista Test Drive topology, please contact your Arista representative.
The DC1 portion of the Level 5 lab topology consists of 3 Spines, 6 Leafs and 2 Hosts.
Device | IP Address |
---|---|
spine1-DC1 | 192.168.0.11 |
spine2-DC1 | 192.168.0.12 |
spine3-DC1 | 192.168.0.13 |
leaf1-DC1 | 192.168.0.21 |
leaf2-DC1 | 192.168.0.22 |
leaf3-DC1 | 192.168.0.23 |
leaf4-DC1 | 192.168.0.24 |
Make sure to reset your lab to the default configlet assignments (BASE configlets and ATD-INFRA). You can use the ATD-Reset-Level5 repo to do this: https://github.com/tonybourkesdnpros/ATD-Reset-Level5
(For Level5 ATD Linux Server)
> ansible-galaxy collection install arista.cvp --force
Make sure you're in the persist directory, then clone this repository:
git clone https://github.com/tonybourkesdnpros/AVD-Level5
edit credentials in vscode: atd-inventory/inventory.yml
(put your lab password in for ansible_password and ansible_ssh_pass)
ansible-playbook playbooks/CVP-lab-reset.yml
We can make use of tags in AVD to execute a portion of the playbook, in this case generating all the configuration.
ansible-playbook playbooks/atd-fabric-deploy.yml --tags=generate
View the generated configuration files:
ls atd-inventory/intended/configs
Look at leaf1-DC1.cfg, and note the loopback0 IP address. It should be in the 192.0.200.0/24 address space (as a /32).
You can try changing the loopback_ipv4_pool parameter in atd-inventory/group_vars/ATD_FABRIC.yml from 192.0.200.0/24 to 192.198.200.0/24
loopback_ipv4_pool: 192.168.200.0/24
Rerun the configuration generation
ansible-playbook playbooks/atd-fabric-deploy.yml --tags=build
This will re-create the configuration files. Note that loopback0 has changed to the 192.198.200.0/24 address space.
Run the fabric deploy playbook
ansible-playbook playbooks/atd-fabric-deploy.yml
This will take about 2-3 minutes, and will create a series of tasks in CloudVision. When the playbook is complete, create a change control from these tasks and execute it (you may see some errors, that's OK).
Verify the fabric is configured show ip bgp summary show bgp evpn summary
The BGP sessions may not be in Established, but that's OK. The key is the configuration was pushed from AVD.
ansible-playbook playbooks/atd-validate-states.yml
ansible-playbook playbooks/atd-snapshot.yml
Project is published under Apache License.