VIRL 1.1.1 (April 2016 Release)

     

    IMPORTANT - Start Here

    VIRL 1.1.1 release is an upgrade building on the VIRL 1.0.x release.

    NOTE - If you have VIRL 1.0.11 or 1.0.26 installed today, you can perform an in-place upgrade.

    In-place upgrade from VIRL versions below 1.0.11 is NOT supported. If you are running an earlier release, a new installation image MUST be downloaded and installed. Please refer to http://community.virl.info/t/virl-1-0-11-december15-release-now-available-for-download-and-upgrade/65173 for more information.

    Installation images are available for VMware Workstation, Workstation Player, Fusion Pro, ESXi and Bare-metal systems now.

    Please see the section below on Self-Service Downloads for instructions on how to obtain the appropriate installation image.

    NOTE - SUPPORT FOR VIRL v1.0.11 and v.1.0.26 WILL END ON 13th May. PLEASE UPGRADE AS SOON AS POSSIBLE!

    Online training material is available - this is designed to help get you started and productive quickly - http://virl-dev-innovate.cisco.com/tutorial.php - NOTE, this includes video walkthroughs - ensure that your browser supports H.264 video and any plugins are enabled.

     

    New Features

     

    NAT Enabled on PC Images

    Users who run VIRL on Vmware Workstation or Fusion are now able to use the native NAT functionality offered by Vmware's 'host networking' setting. The gateway IP address 'l2_network_gateway' and 'l2_network_gateway2' settings that relate to the Flat and Flat1 networks are now set to the 172.16.x.2 address. Devices configured with a default route to that address, or using DHCP to get a default route, will have Internet access via the NAT function.

    Online Resource Requirements Calculator

    The new web page at VIRL - http://virl.cisco.com/resource/ provides you with a quick resource calculator for any topology that you may be thinking of using. Simply enter in desired node amount in numbers under the field 'Enter # of Nodes' to see the estimated hardware requirement that's needed to run the simulation.

    Please note that this tool is for estimation purposes only. The actual hardware requirements to run certain simulations may vary depending on many factors including the over-commit ratios that you're using on your system.

    System Software Upgrade Simplification

    This version of VIRL introduces a new System software upgrade method. Once running VIRL 1.0.x, future upgrades will be driven via the 'System Upgrade' panel in the User Workspace Manager (UWM) page.

    2016-04-11 06.23.00 pm.png2555x627 88.5 KB

     

    The System Upgrade page will offer users three modes of upgrade:

      • Core - upgrades the key components of the VIRL system as well as the Linux operating system.
      • Full - upgrades the key components of the VIRL system, the Linux operating system and updates all of the available Virtual Machine and LinuX Container images.
      • Advanced - upgrades the key components of the VIRL system, the Linux operating system and offer you the ability to choose which VM Maestro packages, Virtual Machine and Linux Container images will be upgraded.

    When an upgrade is performed, the function will also manage any necessary reboots and Linuxbridge kernel patches (required for Layer 2 simulation operations) without the need to issue any CLI commands.


    Real-Time Traffic Visualization

    When a simulation is running, users can log into the UWM page as the user under which the simulation was launched. When clicking on 'My Simulations' and selecting the simulation of interest, a new 'Show Traffic' button is offered on the right-hand side of the page just above the 'Interfaces' table.

    Clicking on the button presents the user with a table of all of the interfaces in the simulation, with traffic counters showing the amount of traffic sent and received on each interface.

    traffic.gif1706x1072 1.61 MB

     

    You can select a subset of interface that you wish to 'graph', resulting in a graph showing the data from the last 1, 5 or 10 minutes, or the of a 'Live' graph.

    traffic2.gif1706x1072 2.22 MB

     

    NOTE - if you encounter a situation where the RX/TX packet & byte counters report 'loading' and do not populate with value when you have a simulation running, flush your browser's cache.


    Git Repository Browser Enhancement

    If you have a GIT repository 'added' to your VIRL server, you're now able to browse, search and select topologies from your GIT repository when using the UWM 'Launch new simulation' interface. Log in to UWM as a user such as 'guest' and select 'My Simulations'. Press the 'Launch new simulation' button and then click the radio button to 'Select .virl file from git repository'. The new browser function provides an 'explorer-like' view of the git repository contents as well as providing a search function.

    git_browser.gif1551x951 984 KB

     

    Syslog Data Export

    The Live Visualisation function includes the ability to set up a central syslog server to which all network devices can be configured to send syslog messages to. The Syslog function now offers the ability to export the syslog data to a .CSV file that can be downloaded for subsequent usage. To set up all network devices to send messages to the syslog server, start the Live Visualisation view, then select 'Setup Syslog' from the 'Action' menu. Messages will now be collected. To export the data, press the 'Syslog' button on the menu bar, press the 'Actions' button on the Syslog panel and select 'Download CSV' to start the download.

    syslog.gif1551x951 648 KB

     

    Ostinato Lxc Name Change

    The Ostinato LXC instance has changed name from 'LXC-Ostinato' to 'LXC-Ostinato-drone'. If you have an existing topology using the LXC-Ostinato subtype, you will be able to start your simulation but you will be advised to update the type to 'LXC-Ostinato-drone'. If you run 'Build initial configurations', it too will warn you if it detects an LXC-Ostinato instance, as per the recording below. To change the subtype, select the LXC-Ostinato instance in your topology and change the 'subtype' to 'LXC-Ostinato-drone' using the drop-down list in VM Maestro under 'Node properties'.

    ostinato.gif1636x1058 835 KB

     

    VIRL Server Cluster

    We're delighted to introduce VIRL running on Openstack clusters! Using Openstack's clustering capability means that you can now run simulations across multiple computers, with a single point of control. In this release, the system will support up to five computers operating within a cluster. The current supported cluster configuration includes, one controller node (required), and up to four compute nodes. VIRL on Openstack Clusters is available on the Packet.net hosting platform as well as being available for local installation on either VMWare ESXi or on Bare-metal systems. No special licenses are required in order to operate a VIRL Cluster. The maximum number of Cisco VMs that you can run will be subject to the following:

      1. VIRL License key (node count)
      2. Hardware resources that are have available within the set of computers.

    NOTE - Cluster installation and operation have only been tested on Vmware ESXi and on Cisco UCS C-series systems. Installation issues MAY be encountered when using other types of hardware.

    Clusters on Packet.net - please see the video at https://www.youtube.com/watch?v=PjIGuJzkUbY.
    Note, this requires you to have established an account on Packet.net and to have a valid VIRL license key. No additional license keys are required but there will be an increased cost since you're running additional servers on the Packet.net platform.

    Clusters - local installation - One computer (bare-metal or virtual machine) will be brought up as a 'controller' node, with up to four additional computers (bare-metal or virtual machines) being brought up and configured as 'compute' nodes. You will need to establish the required network connectivity between all of the computers in your cluster, either using virtual networking as offered by Vmware ESXi or using physical networking equipment.

    Specific OVA and ISO images are required to be installed on compute nodes. Converting an existing 'single-node' VIRL system to operate as a cluster 'controller' is NOT recommended. You should install a fresh image of VIRL on your designated 'controller' node.

    Full instructions on Cluster installations can be found at http://virl-dev-innovate.cisco.com/virl.cluster.php

     

    Updated

     

    Virtual Machines and Container Images

    IOSv 15.6(2)T - An updated IOSv virtual machine is now available and becomes the default IOSv instance.

    NX-OSv 7.3.0.1 - An updated NX-OSv virtual machine is now available and becomes the default NX-OSv instance.

    ASAv 9.5.2 - An updated ASAv virtual machine is now available and becomes the default ASAv instance.

     

    How to Upgrade

     

    Self-Service Download

    Every registered VIRL user is now able to download the OVA and ISO images from https://virl.mediuscorp.com/my-account. The new 'Download VIRL' link on this page will take you through to a self-service selection page where you are able to select the image you would like.