Cisco Modeling Labs ISO Installation

Cisco Modeling Labs ISO Disk Image Installation

This chapter details the ISO disk image installation procedure for a bare metal environment.

A bare metal implementation is a computer system in which the software for a virtual machine is installed directly on hardware rather than as a virtual machine on top of a hypervisor system, such as VMware ESXi, within the host operating system. The term bare metal refers to a hard disk, the usual medium on which a computer's operating system is installed.

The following bare metal implementations are described:

Note
These hardware configurations are for example purposes only; you can deploy the server implementation that best suits your requirements.

Prepare for an ISO Disk Image Installation

Using an ISO disk image to install Cisco Modeling Labs is required when installing to bare metal servers.

There is a number of key prerequisites that must be in place in order to use an ISO disk image to successfully install Cisco Modeling Labs.

These prerequisites are:

  • 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 and must not contain any irreplaceable data, as it will be repartitioned and erased.

  • There must be five network interfaces.

  • If static IP addressing and/or proxies are required, see the section (Optional) Configure Static IP.

  • For installations to bare-metal, you must create a DVD from the ISO disk image or, alternatively, attach the ISO disk image via an integrated management interface (such as UCS or Cisco Integrated Management Controller.)

  • For installations to a virtual machine, the following hypervisors are supported:

    • VMware vSphere ESXi 5.1 U2 (Build 1483097) or later.

    • VMware vSphere ESXi 5.5 U1 (Build 1623387) or later.

    • VMware vSphere ESXi 6.0 (Build 2494585).


      Note
      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 the minimum version will result in a failed deployment that will return an error stating that nested virtualization is not supported.

    Note
    Oracle VirtualBox is not supported due to its lack of support for nested virtual machines.

  • You must configure five virtual network interfaces and map them to separate port groups. The port groups mapped to the second and third network interfaces must be set to Promiscuous Mode. See the applicable hardware documentation for details and examples of how to configure network interfaces.

  • When creating virtual machines, the guest operating system type must be set to Other Linux 64-Bit or Other Linux 3.x Kernel 64-Bit. The following table outlines how to set the guest operating system type for each hypervisor.

    Hypervisor

    Instructions

    VMware Workstation

    Select the new Cisco Modeling Labs virtual machine and choose Edit Settings > Options > General. Set the guest operating system to Linux and version to Other Linux 3.x Kernel 64-Bit.

    VMware vSphere Client

    Select the new Cisco Modeling Labs virtual machine and choose Edit Settings > Options > General Options. Set the guest operating system to Linux and version to Other Linux 3.x Kernel 64-Bit.

    VMware vSphere Web Client

    Select the new Cisco Modeling Labs virtual machine and choose Edit Settings > VM Options > General Options. Set guest operating system to Linux and version to Other Linux 3.x Kernel 64-Bit.

  • Time synchronization must be disabled for the Cisco Modeling Labs virtual machine in the Advanced or Options panel of the virtual machine settings. The following table outlines how to disable time synchronization for each hypervisor.

    Hypervisor

    Instructions

    VMware Workstation

    Select the new Cisco Modeling Labs virtual machine and choose Edit Settings > Options > General. Uncheck the Synchronize Guest Time with Host check box.

    VMware vSphere Client

    Select the new Cisco Modeling Labs virtual machine and choose Edit Settings > Options > VMware Tools. Uncheck the Synchronize Guest Time with Host check box.

    VMware vSphere Web Client

    Select the new Cisco Modeling Labs virtual machine and choose Edit Settings > VM Options > VMware Tools. Uncheck the Synchronize Guest Time with Host check box.


Note

Failing to set the guest operating system to Other Linux 64-Bit or Other Linux 3.x Kernel 64-Bit will prohibit you from setting the hostname during the installation process, resulting in a failed installation.

Depending on Internet speed and target platform performance, an installation can take between 30 and 60 minutes.

Download the Cisco Modeling Labs ISO Disk Image

You must download the Cisco Modeling Labs ISO disk image using the link provided in your purchase confirmation email.

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 ISO disk image is provided along with the download link on the download website. You must calculate and verify that the hash sum of the downloaded ISO disk image matches the source file:

  • On OS X, use the command md5 <filename>.
  • On Linux, use the command md5sum <filename>.
  • On Windows, use FCIV or another tool of your choice.

Cisco UCS B-Series Server Installation

The following sections describe how to install the Cisco Modeling Labs ISO disk image on a Cisco UCS B-Series Server.

Log In to the Cisco UCS Manager Interface

The default HTTPS weblink for the Cisco UCS Manager interface is https://UCSManager_IP, where UCSManager_IP represents the IP address assigned to Cisco UCS Manager.

    Step 1   Open a browser window and enter the IP address of the Cisco UCS Manager interface in the format https://UCSManager_IP.

    Step 2   If a Security Alert dialog box appears, click Yes to accept the security certificate and continue.
    Step 3   In the Cisco UCS Manager launch page, click Launch UCS Manager.

    Depending on the web browser you use to log in, you may be prompted to download or save the JNLP file.

    Figure 1. Cisco UCS Manager Login Window



    Step 4   If the Cisco UCS Manager displays a pre-login banner, review the message and click OK to close the dialog box.
    Step 5   If a Security dialog box appears, perform the following tasks:
    1. (Optional) Check the check box to accept all content from Cisco.
    2. Click Yes to accept the certificate and continue.
    Step 6   In the Login dialog box, perform the following tasks:
    1. Enter your username and password.
    2. If your Cisco UCS implementation includes multiple domains, choose the appropriate domain from the Domain drop-down list.
    3. Click Login.

    Map the Cisco Modeling Labs ISO Disk Image on a Cisco UCS B-Series Server


    Note
    This procedure requires you to have downloaded the Cisco Modeling Labs ISO disk image and to ensure it is accessible from the computer that you are using to log in to the Cisco UCS Manager interface.
    When the Cisco UCS Manager launches, the pane on the left provides an equipment inventory of the Cisco UCS.
    Figure 2. Cisco UCS Equipment Inventory



    You can see a physical view of the server under the Physical Display pane.
    Figure 3. Cisco UCS Physical Display



    To map the Cisco Modeling Labs ISO disk image, complete the following steps:

      Step 1   Under the General tab, click KVM Console to launch the KVM Console and connect to the KVM server.
      Figure 4. KVM Console



      Step 2   In the KVM Console, click the Virtual Media tab. In the KVM Console, the ISO disk image is mapped to the server so that at boot time, the server boots from the ISO disk image.
      Step 3   Click Add Image.
      Figure 5. Virtual Media Tab



      Step 4   From the dialog box that is displayed, navigate to the location of the Cisco Modeling Labs ISO disk image, click the corresponding image and click Open.
      Figure 6. ISO Disk Image File



      Step 5   The path to the ISO disk image is visible in the Client View of the Virtual Media tab. Check the Mapped check box to allow the disk image to be accessed by the server. Uncheck the check box to disconnect the server from the drive or disk image.
      Figure 7. ISO Disk Image Mapped to Server



      Step 6   Click the KVM tab. The No Signal window is displayed.

      The No Signal window indicates that the server is not powered on.

      Figure 8. No Signal Window



      Click Boot Server in the icon bar. The server boots up momentarily and the Cisco menu is displayed. There are three options available:

      • <F2>—Enter the setup menu.

      • <F6>—Boot menu

      • <F12>—Network boot

      Figure 9. Cisco Setup Menu



      Step 7   Press <F6> to access the Boot menu. The server boots from the virtual machine and the VIRL Installer window appears.
      Step 8   There are five options available:

      • Live - Boot the Live System

      • xforcevesa - Boot Live in safe graphics mode

      • Install - Start the installer directly

      • Memtest - Run memtest

      • Hd - Boot the first hard disk

      Figure 10. VIRL Installer Window



      Important: You must choose the first option Live - Boot the Live System using the [tab] key. The installation process starts and installs the Ubuntu (14.04.2 LTS Cloud-init) operating system and Cisco Modeling Labs.
      Note    The option Install - Start the installer directly is currently unavailable.
      Step 9   Log into the virtual machine using username virl and password VIRL.
      Figure 11. VIRL Login Window



      Step 10   On the main menu, double-click Install system to HDD to begin the installation
      Figure 12. Main Menu



      Cisco UCS C-Series Server Installation

      The following sections describe how to install the Cisco Modeling Labs ISO disk image on a Cisco UCS C-Series Server.

      Log In to the Cisco Integrated Management Controller Interface

      The default HTTPS web link for CIMC is https://ip-address.

        Step 1   Open a browser and enter the IP address of the CIMC interface in the format https://ip-address.

        Step 2   If prompted, click OK to open Java viewer.jnlp.
        Step 3   If a security dialog box is displayed, perform the following tasks:
        1. (Optional) Check the check box to accept all content from Cisco.
        2. Click Yes to accept the certificate and continue.
        3. Confirm any additional security certificate exceptions.
        Step 4   In the CIMC login window, enter the username and password for the CIMC interface.
        Tip   

        The default credential is admin and password. If you changed the password during server setup, use the password that you configured.

        Figure 13. Cisco Integrated Management Controller Login Window



        Step 5   Click Log In.

        Map the Cisco Modeling Labs ISO Disk Image on a Cisco UCS C-Series Server


        Note
        This procedure requires you to have downloaded the Cisco Modeling Labs ISO disk image file and to ensure it is accessible from the computer that you are using to log in to the Cisco Integrated Management Controller (CIMC) interface.

        To map the Cisco Modeling Labs ISO disk image, complete the following steps:

          Step 1   Under the General tab, click KVM Console to launch the KVM Console and connect to the KVM server.
          Tip   

          You can also click the keyboard icon in the icon bar at the top of the console to launch the KVM console.

          Figure 14. KVM Console



          Step 2   If a security dialog box is displayed, perform the following tasks:
          1. (Optional) Check the check box to accept all content from Cisco.
          2. Click Yes to accept the certificate and continue.
          Step 3   At the Cisco KVM Virtual Console confirmation box, perform the following tasks:
          1. (Optional) Check the check box to accept all content from Cisco.
          2. Click Run.
          3. Confirm any additional security certificate exceptions.
          Step 4   In the KVM Console, click the Virtual Media tab. In the KVM Console, the ISO disk image is mapped to the server so that at boot time, the server boots from the ISO disk image.
          Step 5   Click Add Image.
          Figure 15. Virtual Media Tab



          Step 6   From the dialog box that is displayed, navigate to the location of the Cisco Modeling Labs ISO disk image, click the corresponding image and click Open.
          Figure 16. ISO Disk Image Location



          Step 7   The path to the ISO disk image is visible in the Client View. Check the Mapped check box to allow the image file to be accessed by the server. Uncheck the check box to disconnect the server from the drive or disk image.
          Figure 17. ISO Disk Image Mapped to Server



          Step 8   Click the KVM tab. The No Signal window is displayed.

          The No Signal window indicates that the server is not powered on.

          Figure 18. No Signal Window



          Click Boot Server in the icon bar. The server boots up momentarily and the Cisco menu is displayed. There are five options available:

          • <F2>—Setup

          • <F6>—Boot Menu

          • <F7>—Diagnostics

          • <F8>—CIMC Config

          • <F12>—Network Boot

          Figure 19. Cisco Setup Menu



          Step 9   Press <F8> to access the CIMC Config menu.
          Figure 20. CIMC Configuration Utility



          Set the following parameters:

          Under NIC mode, enable Dedicated. Under IPV4 (Basic), provide values for your network for CIMC IP, Subnetmask, and Gateway. Under NIC Redundancy, enable None.

          Step 10   When completed, select <ESC> to exit the utility and return to the Cisco setup menu.
          Figure 21. Cisco Setup Menu



          Step 11   Press <F6> to access the Boot Menu. Click the applicable boot device.
          Figure 22. Boot Device Details



          Step 12   Reboot the server using the CTRL-ALT-DEL macro as shown.
          Figure 23. Reboot the Server



          Step 13   On the Power cycle the server? confirmation dialog box, click OK.
          Figure 24. Power Cycle the Server



          The server boots from the virtual machine and the VIRL Installer window appears.

          Step 14   There are five options available:

          • Live - Boot the Live System

          • Xforcevesa - Boot Live in safe graphics mode

          • Install - Start the installer directly

          • Memtest - Run memtest

          • Hd - Boot the first hard disk

          Figure 25. VIRL Installer Window



          Important: You must choose the first option Live - Boot the Live System using the [tab] key. The installation process starts and installs the Ubuntu (14.04.2 LTS Cloud-init) operating system and Cisco Modeling Labs.
          Note   
          Note    The option Install - start the installer directly is currently unavailable.
          Step 15   Log into the virtual machine using username virl and password VIRL.
          Figure 26. VIRL Login Window



          Step 16   On the desktop, double-click Install system to HDD to begin the installation
          Figure 27. Desktop Main Menu



          Install the Cisco Modeling Labs ISO Disk Image

          To install the Cisco Modeling Labs ISO disk image, complete the following steps:

            Step 1   In the Welcome window, choose the applicable language and click Continue.
            Figure 28. Welcome Window



            Step 2   In the Preparing to Install window, ensure that you have adequate resources to install the ISO disk image and click Continue.
            Note   

            We recommend a minimum of 8 GB disk.

            Note   

            If you are connected to the internet, you can check the Download updates while installing check box to enable update downloads during the installation.

            Figure 29. Preparing to Install System Window



            Step 3   In the Installation type window, click the Erase disk and install System radio button and check the Use LVM with the new system installation check box, to setup Logical Volume Management.
            Figure 30. Installation Type Window



            Click Install Now.

            Step 4   In the Where are you? window, enter the applicable time zone, and click Continue.
            Figure 31. Where are you? Window



            Step 5   In the Keyboard layout window, choose the applicable locale-specific keyboard layout to use by clicking the corresponding option from the Choose your keyboard layout list, and click Continue.
            Figure 32. Keyboard Layout Window



            Step 6   In the Who are you? window, enter values for the fields exactly as described here:

            • In the Your name field, enter the value cml or a name of your choice.

            • In the Your computer's name field, enter the value: cml

            • In the Pick a username field, enter the value: virl

            • In the Choose a password field, enter the value: VIRL
              Note    The password VIRL should be capitalized.

            • In the Confirm your password field, enter the value: VIRL

            • Uncheck the Log in automatically radio button if it is checked.

            • Click the Require my password to log in radio button.

            • Uncheck the Encrypt my home folder check box if it is checked.

              Caution   

              No variations on these values are permitted.

            Click Continue to start the installation.

            Figure 33. Who are you? Window



            Note    You must eject or unmount the ISO disk image before proceeding.
            Step 7   In the Installation Complete window, click Restart Now to restart the server.
            Figure 34. Installation Complete Window



            (Optional) Prepare for an Interface-Constrained Installation

            For complete functionality, Cisco Modeling Labs requires five network interfaces. These are:

            Network Interface

            Description

            eth0

            For management access with an IP address assigned via DHCP or via manual static IP address configuration.

            eth1

            For external layer-2 management and data-plane access (Flat) with a default IP address of 172.16.1.254/24.

            eth2

            For external layer-2 management and data-plane access (Flat1) with a default IP address of 172.16.1.254/24.

            eth3

            For external layer-3 management and data-plane access (SNAT) with a default IP address of 172.16.1.254/24.

            eth4

            To anchor OpenStack services and for inter-host communications with a default IP address of 172.16.10.250/24.

            Whenever the virtual machine is missing one or more of these interfaces, it is necessary to first create an alias for the missing OpenStack services IP address and then create dummy interfaces that can be used by Cisco Modeling Labs in place of the missing interfaces.

            The steps described in this section are for a virtual machine with only two network interfaces (eth0 and eth1) available. Therefore, three dummy interfaces (dummy1, dummy2, and dummy3) must be configured.

            If in your implementation, your virtual machine has more or less interfaces, adapt the number of required dummy interfaces accordingly. Otherwise, if your virtual machine has the required five network interfaces, skip this section.

              Step 1   Start the virtual machine and log in using username virl and password VIRL.

              Note    The Ubuntu Software Updater may start automatically upon login. It is safe to close the Updater and continue with the installation.

              Step 2   Click the xterm icon to open a terminal window.
              Step 3   Open the network configuration file for editing: sudo nano /etc/network/interfaces
              Step 4   Add a new line in the eth0 section and enter up ip addr add 172.16.10.250/24 dev eth0 to create a new alias for the missing OpenStack services address. For example: 
              iface eth0 inet dhcp
        dns-nameservers 8.8.8.8 8.8.4.4
        up ip addr add 172.16.10.250/24 dev eth0

              Step 5   Enter Ctrl-X to exit nano.
              Step 6   Enter Y and Enter to confirm saving the network configuration file and exit.
              Step 7   Open the configuration file for editing: sudo nano /etc/virl.ini
              Step 8   Change the hostname to ubuntu. This can be modified later during customization if desired.
              Step 9   Enter Ctrl-W and search for 'l2_port:'.

              Note    If the host has only one network interface, 'l2_port' would need to be set to a dummy interface, starting with dummy1 and incrementing sequentially for additional interfaces. In this case, it is left as eth1.

              Step 10   Enter Ctrl-W and search for 'l2_port2:'. In this example, since interface eth2 is missing, l2_port2: must be mapped to interface dummy1. Replace eth2 with dummy1.
              Step 11   Enter Ctrl-W and search for 'l3_port:'. In this example, since interface eth3 is missing, l3_port: must be mapped to interface dummy2. Replace eth3 with dummy2.
              Step 12   Enter Ctrl-W and search for 'internalnet_port:'. In this example, since interface eth4 is missing, internalnet_port: must be mapped to interface dummy3. Replace eth4 with dummy3.
              Step 13   Enter Ctrl-W and search for 'dummy_int'. Since dummy interfaces are required dummy_int must be set to True.
              Step 14   Enter Ctrl-X to exit nano.
              Step 15   Enter Y and Enter to confirm saving the configuration file and exit.
              Step 16   Enter sudo reboot now to reboot the virtual machine.
              Step 17   Once rebooted, log in again using username virl and password VIRL.
              Step 18   Click the xterm icon to open a terminal window.
              Step 19   Confirm that the OpenStack services IP address is reachable: ping -c 4 172.16.10.250

              Note    If no replies are received, check that the interfaces were updated correctly.

              Step 20   Enter nova service-list to display the status of the Nova services. Verify that the status for each Nova service is enabled and that the state for each is up.

              Note    If the Nova services are not enabled and up, verify the changes to the network configuration file, reboot, and try again.

              Step 21   Enter neutron agent-list to display the status of the OpenStack Neutron agents. Verify that the status for the Metadata, DHCP, and L3 agents is :-).

              Note    If the Metadata, DHCP, or L3 agents are not alive, verify the changes to the network configuration file, reboot, and try again.

              (Optional) Configure Static IP

              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 before proceeding.

              This section 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 this section.

                Step 1   Start the virtual machine and log in using the username virl and the password VIRL.

                Note    The Ubuntu Software Updater may start automatically upon login. It is safe to close the Updater and continue with the installation.

                Step 2   Click the xterm icon to open a terminal window.
                Step 3   Change to the network interfaces configuration directory: cd /etc/network
                Step 4   Open the interfaces configuration file for editing: sudo nano interfaces
                Step 5   Change the eth0 addressing method to static: iface eth0 inet static
                Step 6   Provide the static IP address: address n.n.n.n
                Step 7   Provide the static IP address netmask: netmask mmm.mmm.mmm.mmm
                Step 8   Provide the default IP gateway address: gateway g.g.g.g
                Step 9   Provide valid reachable DNS name-server addresses: dns-nameservers a.a.a.a b.b.b.b
                Step 10   Enter Ctrl-X to exit.
                Step 11   Enter Y and Enter to confirm saving the interfaces file and exit.
                Step 12   Enter sudo reboot now to reboot the virtual machine in preparation for the remaining installation steps.

                (Optional) Configure Internet Proxies

                Access to Internet servers is required for the configuration and customization of Cisco Modeling Labs as outlined in this section. If Cisco Modeling Labs is being deployed in a location where proxies are used then they must be configured, as described, using your site-specific parameters. Otherwise, if no proxies are being used, skip this section.

                  Step 1   Start the virtual machine and log in using the username virl and the password VIRL.

                  Note    The Ubuntu Software Updater may start automatically upon login. It is safe to close the Updater and continue with the installation.

                  Step 2   Click the xterm icon to open a terminal window.
                  Step 3   Open the file for editing: nano .bashrc
                  Step 4   Add in a number of new lines, enter a description for the proxy block # Add proxy configuration and enter the following: For example: 
                  export http_proxy=http://proxy.domain.tld:port/
export https_proxy=http://proxy.domain.tld:port/
export HTTP_PROXY=$http_proxy
export HTTPS_PROXY=$https_proxy

                  Note    'proxy' is the name of the required proxy server and port, 'domain' is the site-specific domain name, and 'tld' is the top-level domain identifier. For example 'http://proxy-server.domain.com:80/'.

                  Step 5   Enter Ctrl-X to exit nano.
                  Step 6   Enter Y and Enter to confirm saving the .bashrc file and exit.
                  Step 7   Open the file for editing: sudo nano /etc/apt/apt.conf
                  Step 8   Define the proxy configuration for use by APT: Acquire::http::proxy "proxy.domain.tld:port/";

                  Note    Enter the above statement using the exact format but substitute your proxy information. For example, Acquire::http::proxy "proxy.domain.com:80/";

                  Step 9   Enter Ctrl-X to exit nano.
                  Step 10   Enter Y and Enter to confirm saving the apt.conf file and exit.
                  Step 11   Enter exit to close the terminal window,

                  Customize the Cisco Modeling Labs Configuration

                  Many aspects of Cisco Modeling Labs can be customized to suit specific and unique deployment requirements by modifying the configuration settings file (/etc/settings.ini).

                  In general, Cisco Modeling Labs configuration settings can be left as default values. However, in some situations Cisco Modeling Labs must be customized to meet deployment-specific requirements. For example:

                  • When using static IP addressing or Internet proxies.

                  • When there is a need to connect and integrate the Cisco Modeling Labs Layer 2 or Layer 3 networks with existing external networks.

                  • When the virtual machine has >16GB of memory and there is a desire to enable RAMdisk to decrease simulation startup times.

                  • When the virtual machine to which Cisco Modeling Labs is being installed has fewer than five network interfaces.

                  The most commonly used parameters are described here. To use a configuration parameter, remove all of the comment markers '#' from the start of the line.

                  Note
                  If static IP or Internet proxies were specified in previous sections then they must also be specified during this installation step.

                    Step 1   Start the virtual machine and log in using the username virl and the password VIRL.

                    Note    The Ubuntu Software Updater may start automatically upon login. It is safe to close the Updater and continue with the installation.

                    Step 2   Click the 0. Edit settings.ini icon.
                    Step 3   Update the Cisco Modeling Labs configuration to meet site-specific requirements using the following configuration statements:

                    • Cisco Modeling Labs by default uses DHCP. If you are using static IP, you must set the variable using_dhcp_on_the_public_port to False.

                    • If using static IP, set the address parameters to match those defined previously in the /etc/network/interfaces file.

                    • If behind a proxy, change proxy to True and set the proxy server URL.

                    • Valid, unique, and reachable DNS name server addresses must be provided.

                    • The Flat connection provides a means to link Cisco Modeling Labs simulated nodes to external devices via a common Layer 2 domain/IP subnet. Therefore:

                      • When the subnet connected to eth1 differs from the default (172.16.1.0/24) the Flat parameters must be modified.

                      • The Flat port can be modified to something other than eth1 if necessary, to match hardware configurations.

                      • Update the Flat network, mask, and gateway settings as necessary to match the subnet on eth1 (or other interface if revised previously).

                      • Coordinate the DHCP allocation pool (addresses from which are offered to simulated nodes) with any external DHCP pools or address restrictions.

                      • l2_address is used to provide an interface into the Flat subnet on the Cisco Modeling Labs virtual machine; update as required to reflect other changes to Flat.

                      • Update the Flat DNS name servers to match those used on the attached external subnet, as necessary.

                    • Flat1 is a second Layer 2 domain/IP subnet linked via eth2 which can be adapted and used in the same fashion as Flat.

                    • SNAT is an IP subnet linked via eth3 which can be adapted in the same manner as Flat and Flat1 to match an external subnet.
                      Note    SNAT external addresses are statically mapped internal IP addresses that are connected to Cisco Modeling Labs simulated nodes.

                    • If your virtual machine has more than 16GB of memory, enabling RAMdisk will accelerate boot-times; set ramdisk to True.

                    • If your host has fewer than five network interfaces, you must set dummy_int to True.
                      Note    If dummy_int is set to True, a dummy interface must be mapped for each missing interface where listed earlier in the file. For example, for four missing interfaces, the interface-specific settings are: 
                      l2_port: dummy1
l2_port2: dummy2
l3_port: dummy3
internalnet_port: dummy4

                      For three missing interfaces: 
                      l2_port2: dummy1
l3_port: dummy2
inernalnet_port: dummy3

                    Step 4   Save the changes to the settings.ini file and exit the editor.
                    Step 5   On the desktop, click the 1. Upgrade or Rehost icon to start a standard installation process to configure the customizations entered previously.
                    Step 6   When completed, click the 2. REBOOT icon to reboot the virtual machine.
                    Step 7   Log in with the username virl and the password VIRL.
                    Step 8   Enter the command ifconfig eth0 to view the IP address assigned.

                    You will use this IP address to access the User Workspace Management interface.

                    Determine License Key Requirements

                      Step 1   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 35. CML Server Options



                      Step 2   Click User Workspace Management and log in to the interface using the username uwmadmin and the password password and switch to Admin mode.
                      Figure 36. User Workspace Management Login



                      Step 3   In the left pane, click Licenses.
                      Step 4   In the Licenses page, click Register Licenses.
                      Step 5   Record the Host Name and Mac Address for license key registration.
                      Figure 37. Information for License Key Registration



                      Use this information when completing the Register Claim 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 Types
                      License Type Description
                      Base Subscription 15-node capacity for initial deployment.
                      Capacity Subscription 10-node, 50-node, and 100-node bundles available.
                      Note    You 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.

                      Step 6   Open the attachment in a text editor and copy all the details.
                      Step 7   Return to the Register Licenses page.
                      Step 8   Repeat Step 1 and Step 2, and paste the details into the Licenses text area.
                      Step 9   Click Register to register the license key.
                      Note   

                      We recommend that you add the Base Subscription license first.

                      Under Licenses, you will see the license that is added, the number of nodes permissible, and an expiry date for the license.
                      Step 10   Click Log Out to exit the User Workspace Management interface.