VIRL 1.2.64 (July 2016 Release)

     

    IMPORTANT - Start Here

    VIRL July (1.2.64) release is an upgrade building on the VIRL 1.0.x and 1.1.x releases.

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

    In-place upgrade from VIRL versions below 1.0.26 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-26-february-16-release-now-available-for-download/7126 for more information.

    Availability:

    Installation images for VMware Workstation, Workstation Player, Fusion Pro, ESXi and Bare-metal systems (ISO) are available now. Cluster compute nodes will continue to use the 1.1.1 images.

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

    NOTE - SUPPORT FOR VIRL v1.1.1 and v.1.0.26 WILL END ON 6th Aug. 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


    Docker Support

    This release of VIRL introduces the ability to integrate Docker nodes into VIRL topologies. For more information on 'Docker' containers and their operation, please see https://blog.docker.com/2015/03/docker-tutorial-1-installing-docker/.

    Users are able to select Docker images from public repositories (such as hub.docker.com) or private repositories. Once downloaded to your VIRL server, you are able to design a network topology that will include your Docker node. Basic configuration information (interface and routing details) are provided by AutoNetkit using the 'build initial configurations' function. The simulation can then be started. As part of the simulation launch, the Coreos virtual machine will be spun up and the Docker node started within it. The Docker node will appear as if it were directly connected to the other nodes within your simulation. The neighboring devices are unaware of the presence of the Coreos VM that is hosting the Docker nodes. The Coreos VM is configured to run with 2Gb RAM and 2vCPUs. If the amount of memory is insufficient, it can be adjusted using the 'Node Resources/Flavors' function in UWM.

    There are thousands of Docker images available on public repositories. Not all images will run on VIRL (or any other Docker deployment), so care must be taken when selecting the image. A video 'Docker on VIRL' has been produced (CLICK HERE) which will help you run Docker images.

     

    NOTE:

    In order to use the Docker functionality, you MUST install the Coreos virtual machine image. This is available for installation from the 'VIRL Server' / 'VIRL Software' page in UWM.

     

    CoreOS Virtual Machine

    The implementation in VIRL makes use of the Coreos virtual machine as a 'launch platform', hosting your Docker instances. A thorough tutorial on Coreos and Docker is available from https://coreos.com/os/docs/latest/getting-started-with-docker.html.

     

    System Configuration Workflow

    The 'System Configuration' panel under the 'VIRL Server' menu in UWM has been revised. The new progress line helps guide you through the various steps while keeping you informed of the current stage in the system configuration process. As part of this feature, system messages like maintenance mode and required reboots are now clearly alerted to the user; even when navigating away from the page. When a reboot is required, a reboot button will now appear on the page. You no longer need to interact with your VIRL server directly, when a reboot is required after making system changes.

     

    2016-07-06 13_52_44-UWM __ System Configuration - Jobs.png

     

     

    Remote Server Panel

    VIRL currently supports cloud deployments to Packet.net only. For more information about VIRL on the cloud, please visit our web page http://virl.cisco.com/cloud.

    The 'Remote Server' panel under the 'VIRL Server' menu in UWM, provides a simple and convenient method for launching a VIRL server instance to a cloud provider.

    Packet Deployment

    Once you've registered with Packet.net and obtained an API Key, you are now ready to prepare your remote server. Select your target location (San Jose, New York or Amsterdam), your server type* and the time for which you want your server to be operational. Then, press 'Generate Passwords' or create your own for the services listed.  Pressing the 'Launch' button then controls the process of starting up your remote VIRL server and provide you with the connection information once your remote VIRL server is ready. The 'Terminate' button can be used to shut down the remote VIRL server instance and remove the server (Project) from your Packet.net account.

     

    A full walk-through tutorial is available from  VIRL on Packet - Web launcher interface from your local VIRL server - YouTube

     

    *The 'Baremetal_2' (currently in Beta) server type is NOT available from packet at this time.

    2016-07-06 14_16_29-.png

     

     

    Adding Graphics To Your Diagrams

    Using either VM Maestro or the Web Editor in UWM, you are now able to augment your topology diagrams by adding graphic elements.

     

    2016-06-27 12.40.31 pm.png

    2016-06-27 12.43.10 pm.png

    You're able to use a set of drawing tools to add rectangles, ellipses, line and text elements to your diagram. Controls enable to you to change fonts, text size, borders, fills etc.

    The annotations that you create when you're designing the topology, are then visible when your simulation is up and running. They can also be hidden to leave just your nodes and links visible.

     

    ezgif.com-optimize.gif

    CLICK ON THE PICTURE ABOVE TO WATCH VIDEO CLIP

     

    annotations_2.gif

    CLICK ON THE PICTURE ABOVE TO WATCH VIDEO CLIP

     

    VM Maestro Unified Editor

    VM Maestro now provides the ability to see the interfaces associated with a node, directly in the design or simulation canvas without needing to open up another panel. Double-click on a node to 'expand' in order to see the interfaces and connection mappings. Double-click once more to 'collapse' the node. The 'View/Expand All/Collapse All' menu option can be used to 'expand' and 'collapse' all nodes in your diagram.

     

    unified.gif

    CLICK ON THE PICTURE ABOVE TO WATCH VIDEO CLIP

     

    VM Maestro 'node' Menu Options

    VIRL has previously provided users with a series of 'extensions' that could be applied to VIRL topologies in order to control aspects such as the Mgmt-IP address assigned to a node or the static_ip address to be applied to a data-interface. For an expanded list of the various extensions, take a look at VIRL Topology Extensions Reference.

     

    VM Maestro now provides node-type appropriate menu options, enabling users to set these values more easily, without the need to the use the 'extensions' function.

     

    extensions.gif

    CLICK ON THE PICTURE ABOVE TO WATCH VIDEO CLIP

     

    VM Maestro and Web Editor Icon Set

    The icons used in both VM Maestro and UWM Web Editor have been updated. No user actions are required to use the new icons for new or existing topologies.

    NOTE

    The 'cloud' icons previously used for FLAT and SNAT network objects have been replaced with a 'Hub' icon and a 'Gateway' icon respectively.

     

    2016-06-27 02.16.32 pm.png

    No functionality has changed as a result of this update.

     

    Liveness Detection

    When a simulation is started, the nodes will go through a number of states before their configuration has been applied and are deemed fully operational. In previous releases, a node would be marked as 'ACTIVE' as soon as the virtual machine has started its boot-up cycle. in some cases, it can take many minutes before the node is truly operational. Users who have used the 'Live Visualisation' functionality will have seen its ability to detect when a node is responsive to commands. This functionality has now been adapted and expanded such that a new 'state' is now reported in VM Maestro and in UWM.  reporting when a node has reached the point where its configuration has been applied and the node is now 'pingable' on its management interface.

     

    2016-06-27 04.09.13 pm.png

     

    In the example above, the log messages indicate when the nodes have transitioned from booting to the point where configuration has been applied and the node is now 'reachable'. The state is also reflected in the state marker shown in the simulations panel.

    If the management interface is not configured, or is placed into shutdown state, the node will be shown as 'ACTIVE - UNREACHABLE'.

     

    Coordinated Packet Capture

    When inspecting traffic passing across the network, it can be valuable to be monitoring more than one interface at a time and also to start the packet-capture at the same time. The 'coordinated packet capture' capabilities is provided in the UWM interface. When a simulation is up and running, you're able to select one or more interfaces and 'mark' them for traffic capture. You're then able to specify the traffic capture parameters including the packets to match (using PCAP filter syntax), the time to run the capture, or number of packets to capture. You can either start the capture on the marked interfaces immediately, or do so at a later point in time.

    Once complete, you can either download the per-interface .PCAP files or get a .ZIP file containing the .PCAP files for each interface.

     

    A demo of this function is posted at #VIRL Personal Edition June 2016 Webinar Recording - YouTube

     

    Topology Capacity Requirements Check

    Users are able to take an existing VIRL file and get a report of the resource requirements that the topology will need versus the resources available on the VIRL server. Log in to UWM as a user (not as 'uwmadmin') and select 'My Simulations'. Select 'Launch new simulation'. Now select the VIRL file that you'd like to check, using one of the available options (local file, remote file, file from GIT repository). Now press the 'Calculate requirements' button. A table will be generated showing the CPU and memory requirements for the topology.

     

    capacity_check.gif

    CLICK ON THE PICTURE ABOVE TO WATCH VIDEO CLIP

     

    Topology Node Count Changes

    In previous releases of VIRL, the capacity calculation rules were applied on a 'per-simulation' basis. This meant that if you have a 20-node license, the largest topology that you could theoretically launch would be one with up to 20 Cisco virtual-machines (not including 3rd party VMs or containers. A topology with more than 20 nodes would be rejected.

    Changes introduced in this release mean that the capacity calculation is now performed on a per-node basis. This means that you are now able to launch up to 20-nodes (assuming a 20-node license) of a much larger topology. For example, if you have a 40 node topology, you are able to mark 20 out of the 40 as 'excluded from launch'. Where as with previous releases, this would still be rejected on the basis of the size of the overall topology, the simulation start will now take place since you have chosen to start up to your license node-count capacity.

    Once started, you are able to stop nodes and start other nodes in the topology, as long as you remain within the total node-count capacity of your license.

     

    UWM System Console

    System administrator occasionally need access to the command-line of the VIRL server. Using the UWM interface, System Console provides users with administrative privilege, the ability to access the command line shell through a web-page. SSH clients such as Secure-CRT, PuTTY etc. are no longer needed for simple tasks.

     

    IMPORTANT: The communication channel used for the CLI session is NOT secure. The username and password is sent in clear-text. If you have security concerns about this connection method, do NOT use this feature.

     

    cli_console.gif

    CLICK ON THE PICTURE ABOVE TO WATCH VIDEO CLIP

     

    Enhancements

     

    Virtual Machine and Container Images

     

    • IOS XRv 6.0.1 - An updated IOS XRv virtual machine is now available and becomes the default IOS XRv instance.
    • IOS XRv 9000 6.0.1 - An updated IOS XRv 9000 virtual machine is now available and becomes the default IOS XRv 9000 instance.
    • CSR1000v 16.2.2 - An updated CSR1000v virtual machine is now available and becomes the default CSR1000v instance.
    • Coreos - The Coreos virtual machine provides a launch 'platform' for Docker images. The VM should be considered as a VIRL infrastructure virtual machine and is not a virtual machine that can be designed into a simulation. Please see the section on 'Docker support' for more details.

    Notice:

    • Cisco IOL LXC - Inclusion of the IOL LXC image has been postponed. This image is NOT included at this point in time. All questions are to be directed to Nour Abueshsheikh (mailto:noabushe@cisco.com) and Scott Anderson (mailto:scander2@cisco.com). This release introduces support for the IOL router image in LinuX Containter format. IOL is a light-weight implementation of the Cisco IOS operating system requiring ~100Mb RAM to run. An additional icon will be provided from the 'node palette' in the VM Maestro and Web-based Editor tools. The node can be placed into your topology in exactly the same manner as other network elements. The AutoNetkit configuration engine is able to configure the IOL instance, creating an appropriate bootstrap configuration in order the device to boot and then participate in your network simulation. It must be noted that there is no 'serial console' present on the IOL instance. A maximum of 16 Ethernet interfaces are provided.
    • Cisco IOL-L2 LXC - Inclusion of the IOL LXC image has been postponed . This image is NOT included at this point in time. All questions are to be directed to Nour Abueshsheikh (mailto:noabushe@cisco.com) and Scott Anderson (mailto:scander2@cisco.com). This release introduces support for the IOL-L2 switch image in LinuX Containter format. IOL-L2 is a light-weight implementation of the Cisco IOS operating system requiring ~100Mb RAM to run. An additional icon will be provided from the 'node palette' in the VM Maestro and Web-based Editor tools. The node can be placed into your topology in exactly the same manner as other network elements. The AutoNetkit configuration engine is able to configure the IOL-L2 instance, creating an appropriate bootstrap configuration in order the device to boot and then participate in your network simulation. It must be noted that there is no 'serial console' present on the IOL-L2 instance. A maximum of 16 Ethernet interfaces are provided.

     

    System Upgrade Workflow

    The 'System Upgrade' panel under the 'VIRL Server' menu in UWM has been revised. The new progress line helps guide you through the various steps while keeping you informed of the current stage in the upgrade process.

    NOTE - The progress line will become available as you upgrade your VIRL server to version 1.2.5. It is normal to see a disconnection error from UWM during the upgrade as some services will restart.

    2016-07-06 13_28_09-UWM __ System Upgrade.png

     

     

    Other Updates

    • VM Maestro 'Geo-map' - The Geographic Map function that was present in previous version of VM Maestro has been deprecated. The function is no longer available.
    • VM Maestro validation change - VM Maestro will now permit topologies with an IOSvL2 node linked to a FLAT or SNAT connector to launch.  A warning marker will be shown on the link instead of an error marker.  You will also receive a warning dialog when you click "Launch Simulation."
    • VIRL .XSD Schema Change - the Schema version for VIRL XML documents has changed from Version 0.9 to Version 0.95. The full .XSD is available from https://raw.githubusercontent.com/CiscoVIRL/schema/v0.95/virl.xsd

     

    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.

    self-service.png

    Please note that the downloads are large. The use of download manager application is strongly recommended.

     

    In-Place Upgrade Instructions

    NOTE - you must have communication to a Cisco salt-master and have a valid license key in order to perform the upgrade.

    Known Issues:

    • Upgrade fails due to unknown version - From UWM, overview reports 'Release' as N/A. If this happens, you need to run the commands from your VIRL server console as outlined in the answer of this post: VIRL Upgrade Problem; once you have verified that UWM is reporting the appropriate version, you may continue with the in-place upgrade.

     

    Existing VIRL 1.0.26 Users

    READ THIS - You are able to upgrade to the latest release by logging into the User Workspace Managment (UWM) interface as 'uwmadmin'.

    From the menu on the left-hand side of the page, select 'VIRL Server'/'VIRL Software'. After a ~60 seconds a list of available images will be presented. New packages will be shown as available for installation with a tick-box present in the 'Install Y/N' column. Select the package and press the 'Start installation' button. The system will now perform the first stage of the upgrade.

    Once completed, from the menu on the left-hand side of the page, select 'VIRL Server'/'System Upgrade'. A list of available upgrade options (Core, Full or Advanced) will be presented. At a minimum, select the 'Core' upgrade, enable maintenance mode and press the 'Start installation' button.

    Updated Virtual machine images are available for installation, either by using the 'Full' or 'Advanced' upgrade options or by selecting from the 'Cisco VM image upgrades' section of the VIRL Software package.

    The upgrade will not only install the latest VIRL software set but will also update critical components of the Ubuntu operating system. The time taken will depend on your network connectivity.

    Progress can be monitored by expanding the 'vinstall upgrade' panel on the 'System Upgrade' page.

     

    Watch the video: VIRL 1.0 to 1.2 Upgrade - YouTube

     

    Existing VIRL 1.1.x Users

    READ THIS - You are able to upgrade to the latest release by logging into the User Workspace Managment (UWM) interface as 'uwmadmin'. From the menu on the left-hand side of the page, select 'VIRL Server'/'System Upgrade'. A list of available upgrade options (Core, Full or Advanced) will be presented. At a minimum, select the 'Core' upgrade, enable maintenance mode and press the 'Start installation' button.

    Updated Virtual machine images are available for installation, either by using the 'Full' or 'Advanced' upgrade options or by selecting from the 'Cisco VM image upgrades' section of the VIRL Software package.

    The upgrade will not only install the latest VIRL software set but will also update critical components of the Ubuntu operating system. The time taken will depend on your network connectivity.

    Progress can be monitored by expanding the 'vinstall upgrade' panel on the 'System Upgrade' page.

     

    Watch the video: VIRL 1.0 to 1.2 Upgrade - YouTube

     

    Existing VIRL 1.1.x Cluster Users

    READ THIS - You are able to upgrade to the latest release by logging into the User Workspace Managment (UWM) interface as 'uwmadmin' on the Cluster CONTROLLER node. From the menu on the left-hand side of the page, select 'VIRL Server'/'System Upgrade'. A list of available upgrade options (Core, Full or Advanced) will be presented. At a minimum, select the 'Core' upgrade, enable maintenance mode and press the 'Start installation' button.

    Updated Virtual machine images are available for installation, either by using the 'Full' or 'Advanced' upgrade options or by selecting from the 'Cisco VM image upgrades' section of the VIRL Software package.

    The upgrade will not only install the latest VIRL software set but will also update critical components of the Ubuntu operating system. The time taken will depend on your network connectivity.

    Progress can be monitored by expanding the 'vinstall upgrade' panel on the 'System Upgrade' page.

     

    At the end of the upgrade process, the cluster controller will be rebooted. Once it has rebooted, you need to reboot each one of the compute nodes within your cluster. To do this:

      1. Log in to UWM on the Cluster Controller node as 'uwmadmin'
      2. Navigate to the 'VIRL Server / System Tools' panel and select 'System console'
      3. For each one of the compute servers in your cluster, issue the following command sequence:
        1. ssh virl@compute[1-4]
        2. sudo reboot
      4. Once all compute nodes have rebooted, issue the following command in the 'System console' window:
        1. nova service-list | grep compute
        2. The following output should be reported:

    2016-07-01 11.13.59 am.png

     

    Performing a New Installation

    Please use the installation guides posted at http://virl-dev-innovate.cisco.com/ and select the instructions appropriate for your platform.

     

     

    Upgrade VIRL Client (VM Maestro) required

    You must update VM Maestro to version 1.2.7 Dev-423 or later. Older releases are not supported with VIRL 1.2.5. Download the new VM Maestro client from "http://your.VIRL.server.IP/download". Once installed, update the available node types as follows:

    1. Launch VM Maestro
    2. Select 'File / Preferences / Node Subtypes'
    3. Press 'Fetch From Server'
    4. Press 'Apply'

     

     

     

    VIRL Server Component Versions

    This release contains the following component versions:

    • Openstack Kilo
    • VM Maestro 1.2.7 Build Dev-423 (NEW)
    • AutoNetkit 0.23.2/0.23.7 (NEW)
    • Live Network Collection Engine 0.11.6 (NEW)
    • VIRL_CORE 0.10.27.8 (NEW)

     

    Cisco Platform VMs

     

    Linux Container Images

    • Ubuntu 14.4.2 LXC
    • iPerf LXC
    • Routem LXC
    • Ostinato-drone LXC

     

    Important Notes

     

    Bare-Metal Installation Image (.ISO)

    The .ISO installer image will install the Ubuntu 14.4.3 operating system as well as all of the software stack for VIRL. Due to space issues, the CSR1000v image is not included in the .ISO installation image. Once VIRL has been installed, your salt-key has been applied and communication established to the Cisco salt-masters, you will be able to install the CSR1000v 3.17 image from the VIRL Software panel in the User Workspace Management interface. Use a Web-browser to log into the User Workspace Management interface and select the 'VIRL Software' tab from the panel on the left. Select the CSR1000v and then press 'Start Installation'.

    Salt Master Settings

    Once you have installed VIRL, apply for VIRL license key as per the installation instructions. You should enter at least two hosts picking a number between 1 and 4. Do not enter the same number twice! You can list up to four salt-masters. When specifying multiple salt masters, separate each one with a comma followed by a space; as shown below. Update you salt-master list if needed.

    US

    us-1.virl.info, us-2.virl.info, us-3.virl.info, us-4.virl.info

    EU

    eu-1.virl.info, eu-2.virl.info, eu-3.virl.info, eu-4.virl.info

     

     

    Caveats

    • VM Maestro build dev-423 fails to run on OS X.
      The initial VM Maestro 1.2.7 build included with this release (build dev-423) failed to run on OS X unless the machine already had a Java 8 JDK installed.
      Solution: Upgrade to the latest VM Maestro 1.2.7 build dev-434 or higher.
    • CSR1000v 16.2.1 - this image CANNOT be used with VIRL due to a defect CSCuz09110.
      Workaround: none
    • VIRLDEV-2299 - Connection creation in VM Maestro does not work on some Windows 10 machines if the Topology Editor preference is set for selecting interfaces manually. 
      For a summary of this problem, see Windows 10 - Cannot select interfaces while creating a connection.
      Workaround: Disable touchscreen and pen HID devices:detailed instructions for workaround.
    • VIRLDEV-3525 - Scroll bar on Preferences > Node Subtypes dialog doesn't work on OS X 10.11
      When using VM Maestro on Mac OS X 10.11.x, the scroll-bar that should be displayed inside the Node Subtype list panel, may be missing.
      Workround: Open the Mac System Preferences pane. Under 'General' select 'Show scroll bars' and set to 'Always'.
    • VIRLDEV-3998 - UWM : Preview is not working after AutoNetkit webserver port change
      In the VIRL server's System Configuration panel, if the AutoNetkit webserver port is changed from its default value (19401), when you subsequently use the UWM interface and select 'My simulations' to start a simulation, the preview function will not work and will instead report 'can't establish a connection to the server at x.x.x.x:19401.'.
      Workaround: Use the AutoNetkit protocol visualisation function in VM Maestro to view your topology.
    • VIRLDEV-4006 - Link parameters on compute nodes not operating correctly
      When using VIRL in cluster mode, if link-parameters (latency, jitter, packet-loss) are applied to a link where the VM is operating on a Compute node (vs the Controller node), the link parameters are not applied.
      Workaround: none
    • Bare-metal installation (ISO) - when following the installation instructions and selecting 'LVM' for partition management, the system will report that there is insufficient disk space and that you should increase the size of the /boot partition. THIS MESSAGE CAN BE IGNORED. Press the 'continue' button. The installation will proceed without issue.
    • Following an upgrade from 1.0.11 to 1.0.26, the following message may be observed when trying to start up a simulation:
      (ERROR) [Feb/04/2016 21:14:51] Failed to start simulation "LXC_demo-clsv9_": local variable 'message' referenced before assignment
      Workaround: Reboot your VIRL server and please try to start your simulation once more.
    • IOSv 15.6(2)T - On boot-up the following message may be observed:%SYS-3-CPUHOG: Task is running for (1997)msecs, more than (2000)msecs (0/0),process = TTY Background.-Traceback= 114ECF8z 130425z 15E20Ez 15DF30z 15DD3Dz 157D75z 158A2Bz 1589BFz 159B67z 153672z 3C9740Az 3C868CEz 3C89BEFz 5125F91z 491D86Cz 492E540z - Process "Crypto CA", CPU hog, PC 0x00157D2C
      Workaround: This is cosmetic and can be ignored.
    • IOSv 15.6(1)T / IOSvL2 15.2(4055) DSGS - CSCuv77089 - CVAC: day0 configuration only partially saved
      When booting an IOSv or IOSvL2 instance within VIRL, it will insert the bootstrap configuration into running-config and report the following message:

    Aug 10 15:06:08.555: %CVAC-4-CONFIG_DONE: Configuration generated from file flash3:/ios_config.txt was applied and saved to NVRAM. See 'show running-config' or 'show startup-config' for more details.

    The running-config is fully applied. However, the startup configuration only contains partial content.
    Workaround: issuing the command 'copy run start' after the device has fully booted, will copy the running-configuration content to the startup-configuration as expected.Note: VIRL's configuration extraction function performs a 'copy run start' operation as part of its execution.

    • VIRLDEV-3140 - Live Visualization - ping with 50% packet loss - timeout reported
      Configured a link with 50% packet loss and use the 'ping from' 'ping to' function. The ping 'failed' reporting the following:
      ping 192.168.0.6 source 192.168.0.5 Timeout exceeded.

    This issue impacts the ping function within the Live Visualisation system but does not impact the regular operation of pings from the VMs themselves.
    Workaround: reduce the packet loss on the selected link.

    • VIRLDEV-3119 - Rehost operation - changing the internalnetport IP address from 172.16.10.250 results in broken system_
      Changing the internalnet_port IP address from the default (172.16.10.250) value and then performing the 'vinstall rehost' operation results in an VIRL system which is not operational.
      Workaround: None. Changing the internalnet_port IP address is NOT supported.
    • VM Maestro - terminal preference for detached internal terminals - this function has been deprecated in VM Maestro 1.2.4 onwards.
      Workaround: you can manual 'tear' the terminal pane from the main VM Maestro window. Use this in conjunction with the VM Maestro preference (Cisco terminal) - "multiple tabs for one simulation".
    • VIRLDEV-4517: No VM Maestro splash screen on Windows
      On Windows, when VM Maestro starts, the splash screen is not being shown.
      Workaround: none.  Wait approximately 10 minutes after starting VM Maestro, and then the main VM Maestro window should appear.

     

    Community Found Defects; Resolved

    VIRL is a community supported and community shaped application. As VIRL grows and evolves, the feedback received from the community shapes and enhances the user experience. The following resolved defects were reported by our community and users:

    • VIRLDEV-4138 STD - data-interface range correction for IOS XRv 9000 -
    • VIRLDEV-4173 UWM - specialize subtype - rejects names with spaces with invalid input
    • VIRLDEV-4293 STD - TypeError: argument must be an int, or have a fileno() method.