1/22/2024 0 Comments Gns3 tutorial step by step![]() ![]() So, in Google, I'm gonna do a search for Python 3 Telnet. The focus of this course is Network Automation. I could so something such as X equals one, Y equals two, X plus Y equals three but that's not really the focus of this course. So, again I could run Python version 3 and print something such as Network Automation or hello world within the NetworkAutomation container. You could install a later release of Python if you want to but for our examples, Python 3.5 suffices, in other words, it's good enough but if you wanna install a later release of Python, such as 3.6 or later, you can do that but for our examples, Python 3.5 is good enough. One of the reasons for using the NetworkAutomation container is that it comes pre-installed with both Python version 2.7 as well as Python 3. ![]() So, I would recommend the use of the NAT Cloud and the NetworkAutomation container in GNS3. And I can also ping sites on the internet. The NAT Cloud also gives us internet access, so I can use commands such as apt-get update to update references on the NetworkAutomation container. ![]() You could configure your Cisco router as a DHCP server but to keep things simple, and to get started, I've used the NAT Cloud as the DHCP server. You don't have to use the NAT Cloud if you don't want to. The NAT Cloud runs a DHCP server and has allocated an IP address to the NetworkAutomation container. As you can see here, it's obtained an IP address, so ifconfig shows us the IP address of the NetworkAutomation container. I'm gonna stop the NetworkAutomation container and start it up again and open up a console to the NetworkAutomation container. Now, in the pre-built topology that I've given you, that's already been done for you so you can simply import the topology and that configuration would have already been completed for you. So, again, I've used nano, a simple text editor to uncomment these two lines and I've saved the file. So, cat /etc/network/interfaces shows us that these lines have been commented out, so I'm gonna use nano /etc/network/interfaces and I'm going to uncomment these two lines and press control X and Y to save the file and I'm gonna overwrite the file. What I'm gonna do initially, however, is configure the NetworkAutomation container to use DHCP. We not going to manage the Ethernetswitch through the console. Ifconfig shows us that the NetworkAutomation container only has an IP Version Six address, it doesn't have an IP Version Four address. As you can see here, the IOSv layer two switch is booting and so is the IOSv router, the NetworkAutomation container has already booted up. So, I'll start up the network devices and open up consoles to them. But we'll expand this topology and make it more complex as we go through the course but initially I wanna get you started automating as quickly as possible. I'll change the switch name to switch one, router name to router one. So, we'll start off with a simply topology. Connect the GNS3 Ether switch to the IOSv Layer Two switch and connect the switch to the router. I'm gonna connect the Ethernetswitch to the NAT Cloud. So, rather than building the topology, you can simply download it and import it into GNS3. You don't have to do that if you don't want to, you can download the pre-configured topology that I've shared. Now, in this video, I'm going to build the topology from scratch. So, in this example, I'm going to a Viral Images and a NetworkAutomation container. You could use other devices but please note that you may encounter issues when using Dynamips images. Cisco Viral images are recommended for use in GNS3. The devices I'm going to automate, however, are Cisco Viral IOSv Layer Two Switches and CiscoIOSv routers. So, I wanna have the ethernet switch in the topology which will allow the Docker container to get an IP address from the NAT Cloud and also have internet connectivity. The NetworkAutomation container boots up very quickly. ![]() In my example, I'm running all the devices on the GNS3 VM. What I'll also do is drag an ethernet switch to the GNS3 workspace and run that on the GNS3 VM. In my example, I already have the NetworkAutomation container installed, so I'm gonna drag it to the GNS3 workspace. If you don't have this device as an installed device, look under Available Devices in GNS3 and drag the NetworkAutomation container to your workspace to install it in GNS3. One of the best devices to use in GNS3 is the NetworkAutomation container. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |