Cisco Modeling Labs Troubleshooting Guide, Release 1.0.1
Updated: November 14, 2014
Chapter: Troubleshooting Cisco
Troubleshooting Cisco Modeling Labs
issues in Cisco Modeling Labs, you should follow the guidelines described in
the following table.
Table 1 Troubleshooting
Node shuts down immediately after initial boot up.
No VT-X extension support in the underlying hardware, VT-X
extensions are not being enabled in BIOS, or VT-X extensions are not being
enabled in the .vmx file.
Enable nested virtualization. See
Enabling Nested Virtualization for more information.
Java Runtime Environment (JRE) or Java Development Kit (JDK)
error is displayed.
Java executable is missing or not set in the PATH environment
Install Java or add the Java executable to the PATH environment
Java Issues for more information.
Error when applying multiple Cisco Modeling Labs licenses.
Licenses have been applied in the incorrect order.
Re-apply the licenses in the correct order. See
Applying Licenses for more information.
Missing node subtypes (images) under the Nodes tab in the
Fetch from server option not run.
Fetch available node subtypes from the Cisco Modeling Labs
Fetching Node Subtypes from the Cisco Modeling Labs Server for more information.
To use Cisco Modeling
Labs, you must enable nested virtualization in your newly deployed nodes.
In the ESXi client,
VT-x/EPT check box. Additionally, several updates must be made to the
applicable configuration/vmx file for your particular vSphere version.
For ESXi 5.0
virtualization, add the following string to /etc/vmware/config:
vhv.allow = “TRUE”
Edit the .vmx file
associated with the new virtual machine and add the following commands to
enable support for nested hypervisors by the virtual machine:
monitor.virtual_mmu = "hardware"
monitor.virtual_exec = "hardware"
vcpu.hotadd = "FALSE"
A reboot is not
required for the change to take effect.
For ESXi versions 5.1 and 5.5
virtualization, add the following strings to the .vmx file associated with the
vhv.enable = “TRUE”
virtualHW.version = "9"
Verify that the string
“FALSE” is also present in the file. You also need to enable
promiscuous mode on the port group that will be used for network connectivity.
Cisco Modeling Labs Corporate Edition System Administrator
Installation Guide, Release 1.0.1 for more information on planning
your network configurations.
When installing the
Cisco Modeling Labs client, ensure that you have the appropriate Java version
installed and that the PATH environment variable contains the path for the Java
architecture versions of Java 6 or Java 7 and the Cisco Modeling Labs client
are installed, a Java runtime error is returned and the installation fails.
starting your installation, ensure that:
If you are
installing a 32-bit build of the Cisco Modeling Labs client, a 32-bit version
of Java must be installed.
If you are
installing a 64-bit build of the Cisco Modeling Labs client, a 64-bit version
of Java must be installed.
Where the Java binary
is not on the PATH, you can update the CML.ini file to point to the full path
of the Java binary (javaw.exe) file, as follows:
Open the CML.ini
in a text editor.
Add the following
two lines immediately before the
<path to javaw.exe file>, for example C:\Program Files\Java\jre7\bin\javaw.exe
The order in which you
apply your Cisco Modeling Labs license is important.
To resolve this issue,
remove all licenses and then re-apply them starting with your base license
Subtypes from the Cisco Modeling Labs Server
To fetch new node
subtypes from the Cisco Modeling Labs server, perform the following tasks:
Server Confirm dialog box is displayed.
the list of node subtypes.
Figure 1. Fetch
Nodes Subtypes from Server
The updated list of node
subtypes is available for use in the
Figure 2. Updated List
of Node Subtypes Visible in the Palette View
Contact your system administrator if a specific node subtype is
missing from the list, as the system administrator is responsible for adding
new node subtypes to the Cisco Modeling Labs server.