There is a number of
key prerequisites that must be in place in order to successfully install Cisco
Modeling Labs using an OVA file.
The host must
support Intel VT-x/EPT virtualization extensions, and these extensions must be
enabled in the BIOS.
The target disk
must be at least 250 GB.
installations to a VM, the following hypervisors are supported:
vSphere ESXi 5.1 U2 (Build 1483097) or later.
vSphere ESXi 5.5 U1 (Build 1623387) or later.
vSphere ESXi 6.0 (Build 2494585).
Additionally, you must verify that you are using vSphere Client
v5.5 Update 2 (Build 1993072) or later before deploying Cisco Modeling Labs.
Failure to use this minimum version will result in a failed deployment that
returns an error stating that nested virtualization is not supported.
VirtualBox VM is not supported due to its lack of support for nested virtual
network speed and target platform performance, an installation can take between
30 and 60 minutes.
Download the Cisco
Modeling Labs OVA File
You must download the
Cisco Modeling Labs OVA file using the link provided in your purchase
The OVA files are
large (~4 GB), so rather than HTTP downloads using a web browser, the use of a
download manager for Mac or Windows is recommended.
An MD5 hash sum for
the OVA file is provided along with the download link on the download website.
You must calculate and verify that the hash sum of the downloaded OVA file
matches the source file:
On OS X, use the command 'md5 <filename>'.
On Linux, use the command
On Windows, use Microsoft
File Checksum Integrity Verifier (FCIV).
and Network Settings
You must enable
Intel VT in the BIOS for Cisco Modeling Labs to operate correctly.
The Cisco Modeling
Labs virtual machine requires connections to five unique virtual network port
groups, the first of which is for management and is site unique. It is, by
The other four port-groups areFlat,
are used by Cisco Modeling Labs for external Layer 2 and Layer 3 connectivity
and are created as described in this section.
Ensure that you have
administrator access to the VMware ESXi server in which you plan to deploy the
Cisco Modeling Labs OVA in order to enable nested virtualization.
Log in as
administrator to the remote VMware ESXi server using the VMware vSphere Client.
Software > Security
edit the properties associated with security services.
Services Properties dialog box is displayed. Enable
UI as follows:
Start and Stop with
Host radio button.
Figure 1. Services Properties
To add the four
additional port groups—Flat,
are required for external Layer 2 and Layer 3 connectivity and configure
network settings, choose
Networking > Properties.
Network wizard, choose the
Figure 2. Connection Type
Properties, in the
assign a site-relevant VLAN ID, for example, 19, in the
are unique for each port group. A VLAN ID is used to identify which VLAN a
packet belongs to; specifically, switches use the VLAN ID to determine which
port(s), or interface(s), to send a broadcast packet to.
If you have
previously installed Cisco Modeling Labs version 1.0, you will only need to add
Figure 3. Flat
Next. The new
port group is assigned.
add the port group.
Repeat Step 7
through Step 13 to add the remaining port groups.
Figure 4. SNAT
Port Group Assigned
Figure 5. Flat1
Port Group Assigned
Figure 6. INT Port
the port groups to allow promiscuous mode:
Hardware > Networking and click
the port group for which you want to enable promiscuous mode, for example,
port group and click
Promiscuous Mode check box, and from the
Promiscuous Mode drop-down list, choose
that the values for
Address Changes and
Transmits are also set to their default value of
Figure 7. Promiscuous Mode for the Flat1 Port Group
mode permits traffic to flow between Cisco Modeling Labs simulated nodes and
other virtual machines running on the ESXi host.
15a through Step 15e to set the promiscuous mode for all port groups.
Figure 8. Available Port Groups
Deploy the Cisco
Modeling Labs OVA
Before You Begin
you have configured the necessary security and network settings.
you know where the OVA file resides.
To install the
OVA, log in to the VMware ESXi server.
From the vSphere
Client menu, choose
File > Deploy OVF
Figure 9. Deploying OVA
Source screen, click
navigate to the OVA package.
In the dialog
box displayed, click
Next to review
the OVA details.
Figure 10. OVF
Information about the OVA you are about to deploy is displayed.
Location screen, confirm or provide a new name for the virtual
machine, for example,
Labs, and click
Figure 11. Name and
Format screen, confirm that the
Provision Lazy Zeroed radio button is selected and click
Figure 12. Disk
Mapping screen, confirm the source and destination network mappings
Network must be mapped to a valid site-relevant network port group used for
virtual machine management.
Figure 13. Network
Complete screen, ensure that the
Power On After
Deployment check box remains unchecked to allow the virtual
machine settings to be updated before it is powered on.
Finish to start
the OVA deployment.
Figure 14. Final
OVA deployment starts.
Figure 15. Deploying the OVA
the deployment completes, click
Edit the Virtual
In the vSphere
Machine Properties dialog box is displayed.
required for your environment.
Figure 16. Updated
Virtual Machine Properties
confirm that the network adapters have been setup correctly.
ensure that the setting
is set to
Expose Nx flag
to guest as shown.
Figure 17. CPUID Mask
If using the
vSphere web client, under the
Hardware tab, locate the
Virtualization option. Ensure that
is set to
flag to guest and that the setting
Hardware Assisted Virtualization to the Guest OS is enabled as shown.
Figure 18. Enable
the Hardware Virtualization Option
OK to save
Start the Cisco
Modeling Labs Server for the First Time
In the vSphere
Power On the
virtual machine starts up.
Open a console
window by right-clicking on
Labs 1.1 and choose
from the list.
Console window you can see the virtual machine starting up.
Figure 19. Virtual
Machine Starting Up
When the virtual
machine has started, the login screen is displayed.
Log in with the
username virl and the password VIRL.
Figure 20. Cisco
Modeling Labs Server Log In
Modeling Labs desktop is displayed.
Figure 21. Cisco
Modeling Labs Desktop
On the desktop,
xterm icon and
enter the CLI command
ensure that the installation worked correctly, confirm that you received the
acceleration can be
used, indicating that the images will work.
Figure 22. Run the
There are a
number of default settings in the settings.ini file. Values edited in this file
are used to configure the Cisco Modeling server for your environment.
0. Edit settings.ini
file icon on the desktop.
Scroll down the
file and update the following:
If you are
installing the Cisco Modeling Labs server behind an HTTP Proxy server,
uncomment the proxy parameter to allow the client to communicate with the
server. For example, the two entries are
#proxy="False". If your installation is not behind an
HTTP proxy server, the two entries are
since a static address will be defined (if applicable for your deployment). To
do this, add the comment sign (#) to the start of the line
dhcp on the public port? = "True"" and remove the comment sign (#)
from the start of the line "using dhcp on the public
port? = "False"".
set your Nameserver entries if you are not using DHCP.
Static IP, public_network, public_netmask, and public_gateway parameters by
removing the comment sign (#) in front of the parameter.
If you are
using more than 16 GB of memory, set the ramdisk parameter.
values for the Flat, Flat1, SNAT and INT interfaces as required for your
port values for ANK web server, VIRL web services, and VIRL user management as
required for your installation.
additional user accounts. The default user account is
to the users list as required.
file and exit.
update the hostname at this time.
On the desktop,
1. Upgrade or
Rehost icon to start a standard installation process.
2. REBOOT icon
to reboot the virtual machine.
Log in with
the username virl and the password VIRL.
eth0 to view the IP address assigned.
You will use
this IP address to access the User Workspace Management interface.
Where there is no
DHCP addressing facility on the subnet to which the Cisco Modeling Labs virtual
machine is connected via eth0, it is necessary to assign a static IP address
describes the configuration steps to use when Static IP addressing is required.
However, if DHCP is being used to configure the eth0 IP address, you may skip
virtual machine and log in using the username virl and the password VIRL.
Software Updater may start automatically upon login. It is safe to close the
Updater and continue with the installation.
xterm icon to
open a terminal window.
Change to the
network interfaces configuration directory:
interfaces configuration file for editing:
Change the eth0
addressing method to static:
static IP address:
static IP address netmask:
default IP gateway address:
reachable DNS name-server addresses:
dns-nameservers a.a.a.a b.b.b.b
Enter Ctrl-X to
Enter Y and
Enter to confirm saving the interfaces file and exit.
now to reboot the virtual machine in preparation for the remaining
Determine License Key
In a web browser, use the IP address or hostname of your Cisco
Modeling Labs server to access the
CML Server interface, in the format
http://<IP address | hostname>.
Figure 23. CML Server
Management and log in to the interface using the username
Figure 24. User
Workspace Management Login
In the left
Licenses page, click
Host Name and
Mac Address for
license key registration.
Figure 25. Information
for License Key Registration
information when completing the
Certificates instructions in the eDelivery Order Notification email to
request your license key for use with the Cisco Modeling Labs server.
Two types of
licenses are available, as shown in the following table.
Table 1 License
15-node capacity for initial deployment.
10-node, 50-node, and 100-node bundles available.
can have any number or type of licenses. Licenses are determined by the node
capacity you want to deploy.
You will receive
your license key as an attachment via an email.
attachment in a text editor and copy all the details.
Return to the
Repeat Step 1 and
Step 2, and paste the details into the
register the license key.
that you add the Base Subscription license first.
you will see the license that is added, the number of nodes permissible, and an
expiry date for the license.
Log Out to exit