I have been using Cisco Virtual Internet Routing Lab (VIRL) to create virtual network models for my customers. I like that VIRL provides a tool for engineers such as myself to perform “what-if” tests on a model of a customer’s network without needing physical hardware, or impacting a production network.
Models of a customer’s network may need multiple devices to illustrate the design fully. I have previously found that loading issues can be encountered when more than a few devices are created in a VIRL model.
An issue that I found is when I launched a simulation with several IOSv2 switches as well as several Layer 3 IOS devices, the saved VLAN database of each switch did not always load. This seemed to be pretty random – some switches would work, others would fail. My work-around was to manually add back in the defined VLANs because they simply disappeared – even though they were in the saved configuration.
After an email exchange with the VIRL development team, they suggested the issue might be a temporary capacity/resource issue on the PC when starting a larger simulation. I have a fairly new PC, with 32 MB of RAM and Intel i7-4700 processor, so I thought I had enough resources to run the simulation – but maybe not to launch the simulation.
I tested out this premise, and I found that this issue was indeed a capacity/resource issue. The lost VLAN database issue on IOSv2 switches can be avoided by loading the devices in a staged fashion. What worked for me was to exclude some of the nodes from being launched initially. After the allowed nodes have successfully launched, I could then manually launch the remaining nodes with their complete VLAN configuration.
Here is the process I followed to stage the launch order of nodes in my model with 17 devices.
From VM Maestro, open the VIRL topology from the Projects pane. From the top menu, select the Design tab that will open the Design pane. At the bottom of your topology, the Properties pane should be displayed. (If the Properties pane is not displayed at the bottom of your topology, from the top menu select Window/Show View/Properties.)
The below figure illustrates what my screen looked like.
Highlight the nodes in your topology that you would like to exclude from launching when the simulation is launched. The method I utilize to highlight the nodes is to hold down the CTRL key and left click each node with your mouse to highlight. (I selected all of the IOSv2 switches.)
Once the nodes are highlighted, select the Nodes tab from the Properties tab, and check Exclude node from simulation launch.
The below figure illustrates what my screen looked like after these steps were followed.
From the top menu, select File/Save to save changes for this topology.
You should notice that the nodes which have been selected to be excluded from launching have an amber circle next to them. If the amber circles do not appear in your topology from the top menu select View/Topology Labels/Excluded from Launch.
For example, the below figure illustrates what my topology looked like when some nodes are excluded from launch.
You can now launch your simulation, and you should notice that all nodes which are not excluded from launch should obtain a status of [ACTIVE].
Nodes that have been excluded from the initial launch will have a status of [ABSENT].
The below figure illustrates this behavior on my simulation.
After all the initially launched devices are active, I then manually launched the [ABSENT] devices one at a time. Highlight node from the Simulation pane and right click with your mouse and select Start this node to manually start each node. I can now consistently run the VIRL model using the staged node launch process – the IOSv2 devices come up correctly, with their VLAN databases intact! It appears that the VLAN database is loaded just fine when the IOSv2 nodes did not have to compete for resources at the initial launch time.
I hope this VIRL tip helps you with your modeling! I plan to post some additional VIRL tips in the future.
Some QoS Gotchas
DNS Security: The First Layer in the Cybersecurity Fight
Nick has over 20 years of experience in Security Operations and Security Sales. He is an avid student of cybersecurity and regularly engages with the Infosec community at events like BSides, RVASec, Derbycon and more. The son of an FBI forensics director, Nick holds a B.S. in Criminal Justice and is one of Cisco’s Fire Jumper Elite members. When he’s not working, he writes cyberpunk and punches aliens on his Playstation.
Virgilio “Bong” has sixteen years of professional experience in IT industry from academe, technical and customer support, pre-sales, post sales, project management, training and enablement. He has worked in Cisco Technical Assistance Center (TAC) as a member of the WAN and LAN Switching team. Bong now works for Tech Data as the Field Solutions Architect with a focus on Cisco Security and holds a few Cisco certifications including Fire Jumper Elite.
John is our CTO and the practice lead for a talented team of consultants focused on designing and delivering scalable and secure infrastructure solutions to customers across multiple industry verticals and technologies. Previously he has held several positions including Executive Director/Chief Architect for Global Network Services at JPMorgan Chase. In that capacity, he led a team managing network architecture and services. Prior to his role at JPMorgan Chase, John was a Distinguished Engineer at Cisco working across a number of verticals including Higher Education, Finance, Retail, Government, and Health Care.
He is an expert in working with groups to identify business needs, and align technology strategies to enable business strategies, building in agility and scalability to allow for future changes. John is experienced in the architecture and design of highly available, secure, network infrastructure and data centers, and has worked on projects worldwide. He has worked in both the business and regulatory environments for the design and deployment of complex IT infrastructures.