My lab is build with GNS3 and the networkdevices I use, run on IOSv-Images from Cisco-virl. I use the Linux-Subsystem-Ubuntu18.04 on Windows10. If some plugins or scripts don't work in Linuxsubsystem, I run a Ubuntu Workstation in GNS3 and here I can reach all subnets over the virtual infrastructur as well. Ansible 2.7 runs on the subsystem with all my tested playbooks.
I also build a GNS3-LAB an on ESXi which I can reach from an Ubuntu-VM which runs on that ESXSi. Here Ansible is also installed. Here I have more RAM and so I can run larger Labs.
- 4 Cisco IOSv-Routers
- 4 Cisco IOSv-Switches
- 4 Alpine Linux Hosts (for simulating clienttraffic)
- 1 Ubuntu "Network Automation" Appliance from GNS3 Marketplace
I use GNS3 because I have been using it for years, when learning new stuff. I also like the possibility to take a packetcapture on every wire within the topology and simulate paketloss and jitter. It's so easy to import new Devices into GNS3 with appliances from GNS3 marketplace. ... But now I'm going to stop advertising GNS3.
-
sh_ip_int_br.yml: this will display the output of "show ip int brief"
-
get_serial.yml with this palybook the serial-numbers of the devices get printed. ios_facts is used so I get structered data
-
copy_run_init.cfg.yml saves running config on flash with the name init.cfg problems : run sometimes in timeouts..
-
cdp_nei.yml get cdp neighbours, but for switches print the error lines. (This is the banner)
-
enable_all_int.yml Enable all Interfaces on Device. Uses Napalm-Facts to get Interfaces. loops over all interfaces and enable it with ios_config. Very Slow!