A focus on Cisco’s SD-WAN has been added to the plan of CCE Enterprise. Network engineers require extensive hands-on expertise with the various solutions to do well on the lab exam. Conversely, getting hands-on experience with a lab in a practise setting outside of the workplace can be challenging.
Get EVE-NG Ready
It’s important to note that Cisco SD-WAN places heavy requirements on system resources. For a simple practise topology with a single controller of each kind and three to four virtual edges, the EVE-NG virtual machine requires at least 8 virtual CPUs and 16 GB of RAM. Yet, you’ll need a lot of processing power to set up a complex architecture with multiple controllers and many vEdge nodes.
Photographs of a Cisco Software-Defined Wide Area Network
You will require the following images of Cisco SD-WAN in order to set up this EVE-NG sd-wan lab setting on EVE-NG:
Once you have the photographs, you may organise them into individual folders and upload them to EVE-NG with a file transfer programme. Once the images have been transferred to the correct EVE-NG folders, you’ll need to change the ova files to qcow2 format. Please be aware that we need a new virtual disc added to the vManage software. To achieve this, use the green-highlighted command.
Topology in Physics: A Study in Space and Time
In the following, we’ll describe the physical topology that will underpin our approach. To replicate it in EVE-NG would be ideal. If you want to copy and paste sections of the configurations, make sure you’re using the same interfaces while building the topology on EVE-NG.
Determine how many vEdge nodes you’ll need, and then add them in the same way you added vEdge-1. The technique for building the EVE-NG sd-wan lab is based on the Cisco SD-WAN version 16.3.2. Upgrading to a newer version of the software will prevent you from adding any new vEdges to your network.
The universally-used default credentials are “admin/admin.” vManage will first ask what kind of storage device it should be put on during the first boot process. You must now make use of the virtual disc you created in the previous procedure.
Setting up the Bootstrap
After all the devices have finished booting, it’s time to allow them to communicate with each other on the most fundamental level by enabling communication between the controllers and all of the WAN edge devices. The following bootstrap code snippets show the absolute minimum settings required to get basic connectivity.