The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
This Cisco Modeling Labs FAQ provides answers to questions concerning the use of the Cisco Modeling Labs server and client.
Question |
Answer |
---|---|
What is the minimum version of VMWare ESXi? |
See Supported VMware ESXi Versions for more information. |
What is the recommended hardware for Cisco Modeling Labs Release 1.1? |
See Recommended Hardware for Cisco Modeling Labs Version 1.2 for more information. |
Why does my installation fail with a 'No valid host was found' error? |
See Map Network Interfaces for more information. |
Why do some VMs show ACTIVE state while others show ERROR state in my running simulation? |
See Resource Issue in Cisco Modeling Labs for more information. |
Why does my configuration extraction fail? |
See Configuration Extraction Fails for more information. |
Why am I getting an error when I try to launch my simulation? |
See Problem Running Simulations for more information. |
How do I reset my secure storage password? |
See Resetting the Secure Storage Password for more information. |
How do I know which topology is currently open? |
See Topology File Information for more information. |
How do I know what active profile I am using? |
See User Profile Information for more information. |
Why did my updated configuration get overwritten? |
See Caveat When Using AutoNetkit for more information. |
Where are updated node configurations stored? |
See Storing Updated Node Configurations for more information. |
Is packet tracing in a simulated network supported? |
See Packet Tracing in a Simulated Network for more information. |
The recommended servers for use with Cisco Modeling Labs version 1.2 are the Cisco UCS C220 M4 and Cisco UCS C240 M4 servers. These are the latest dual-socket, rack-mounted servers based on Intel's Haswell CPU that support up to a maximum of 18 cores per socket. Large installations may require a 4-socket server such as the Cisco UCS C460 M4. See the following specification sheet for more information on supported rack servers http://www.cisco.com/c/dam/en/us/products/collateral/servers-unified-computing/ucs-c-series-rack-servers/c220m4-sff-spec-sheet.pdf.
Cisco Modeling Labs requires connections to five unique virtual network port groups, the first of which is for management and is site unique. It is, by default, VM Network. The other four port groups are Flat, Flat1, SNAT, and INT. These are used by Cisco Modeling Labs for external Layer-2 and Layer-3 connectivity.
Note | You must map all five network interfaces, regardless if you plan to use all of them or not. |
In Cisco Modeling Labs, each configured virtual machine in a topology has an associated operating system, such as Cisco IOSv, Cisco CSR1000v, and so on. Additionally, each virtual machine is also configured with a memory size value which is allocated when the VM starts up. For example, Cisco IOSv requests 512mb, while Cisco CSR1000v requests 3072mb. When you send a request to start a simulation, the VM management function, Openstack Icehouse, evaluates the virtual machine start request and confirms if there is sufficient memory available to support the VM.
If there is enough memory, the VM boots up and is reported as ACTIVE.
Where there is insufficient memory, the VM is reported as being in the ERROR state.
Since the requested launch is evaluated in the sequence in which the VM receives the request, you may see situations where some VMs in your topology go ACTIVE, while others go into the ERROR state.
During the configuration extraction process, the system attempts to log in using a set of default usernames and passwords. For example, the Cisco IOSv cisco default password is enable. Therefore, if you have changed this password, the configuration extraction will fail.
For virtual machines configured using AutoNetkit, the basic configuration created ensures that the configuration extraction process will succeed.
Note | The enable password is only required for virtual machines running in Cisco ASAv, Cisco IOSv, Cisco IOSvl2 and Cisco CSR100v. For Cisco IOS XRv and Linux server the username cisco and corresponding password cisco must be used. |
This section describes common errors encountered when launching your simulation.
After you have designed a topology on the Topology Editor canvas, you click Launch Simulations, and an error is returned. Possible errors are:
These errors occur when a Web Services profile has not been correctly configured for the Cisco Modeling Labs client to communicate with the Cisco Modeling Labs server, or when you try to log in as an unrecognized user or with an incorrect password.
To resolves these issues:
When the Secure Storage feature is used for the first time, it generates a master password that is used to encrypt the data. In the future, this same master password will be required to retrieve the data from secure storage. If the master password becomes unavailable, the Secure Storage feature provides optional support for password recovery.
Two methods are used to reset the password for the secure storage feature.
Method 1
Method 2
If you are unable to access the Cisco Modeling Labs client due to a lost or forgotten password for the secure storage feature, complete the following steps:
On the Cisco Modeling Labs client Topology Editor canvas, hover your mouse over the topology tab of the open topology to view the project name and file name.
In the Cisco Modeling Labs client, hover your mouse over the credentials button in the status bar at the bottom of the screen.
The tool tip shows a summary of the current Web Services Profile settings.
AutoNetkit is included with Cisco Modeling Labs to allow users to quickly generate configuration files for topologies.
Be aware of the following caveat when using AutoNetkit.
AutoNetkit is enabled by default. You must disable AutoNetkit under the following conditions:
You do not want AutoNetkit to update the configuration for a node.
You want to preserve modifications made to a running configuration.
To disable the AutoNetkit settings, select a node in the topology, then choose
. Uncheck the Auto-generate the configuration based on these attributes check box.Node configurations are stored in the topology .virl file. If you are extracting configurations from a topology that is open and launched in the current UI session, the topology .virl file is modified in place and automatically saved.
In cases where the original topology file has been updated since its last launch, a dialog box is displayed asking to overwrite the file or ignore changes made.
You can capture traffic from an interface by using tcpdump to attach to a port in a simulated network created with Cisco Modeling Labs. The procedure is done on the Cisco Modeling Labs server. You can export the packet-trace capture file to another server for examination and analysis with a tool, such as Wireshark. If VNC is enabled on the Cisco Modeling Labs server and sufficient resources are available, you can perform the capture and analysis tasks within the VNC session.
Every link and every connection in Cisco Modeling Labs is a collection of ports represented in the Neutron networking services component of OpenStack. Neutron maintains a database of the ports. The database contains the interfaces, MAC addresses, IP addresses, and so on, associated with those ports. Use the database to identify the MAC address of the interface being investigated as the starting point, to identify the correct port, and then to identify the Linux interface that the port belongs to.
To enable packet tracing, complete the tasks in this section: