CML 2.1.1 Release Notes

CML 2.1.1 is a maintenance and bug fix release for CML 2.1.0. It does not contain any new features or functionality. This page lists the changes included in the 2.1.1 release. If you are upgrading from CML 2.0.x, be sure to read the entire CML 2.1 Release Notes to understand all of the changes since that release.

Bug Fixes in CML 2.1.1

In addition to the fixes in CML 2.1.0, the 2.1.1 release fixes the following bugs:

Bug Description

Resolution

Under certain circumstances, the command channel between CML’s controller and compute components could become disconnected. No re-connection was attempted.

The symptoms of this disconnect included the inability to start new labs (i.e., nodes would get stuck in QUEUED state) and no more updates to the system health statistics in the status bar of the CML UI.

Remediated. If the command channel becomes disconnected, CML 2.1.1 will automatically re-instantiate the connection.

The refplat-20201020-fcs.iso released with CML 2.1.0 included new versions of many of the reference platforms, but the non-crypto image of the new IOSv version was used by mistake.

The Ubuntu node definition included with refplat-20201020-fcs.iso used a version string that referred to the older version. That is, the Ubuntu image was correct, but the node definition label still referenced the old version.

Fixed. The refplat-20201020-fcs.iso file has been replaced by refplat-20201110-fcs.iso.

The new ISO file replaces the IOSv image with the correct crypto image.

The image and node definitions have been updated for Alpine Desktop, WAN Emulator, TRex and Ubuntu nodes. Specifically, Ubuntu nodes now reference the correct version. The other image definitions have been updated to use more specific names that include a OS version string.

In CML-Personal, the messages in the CML UI that explain how to deregister an instance from the Smart Licensing servers included an out-of-date URL.

Fixed. Updated the URL and improved the phrasing and clarity of the message in the CML UI.

The Tools ‣ Licensing page had some hard-coded text that incorrectly reported the export-controlled state of the software: Export-Controlled Functionality: Not Allowed.

Fixed. The hard-coded message did not reflect the current state of the software and has been removed.

The true state can be seen in the CML UI under Tools ‣ System Administration in the Licensing Tech Support section. On that page, it should normally show Export-Controlled Functionality: ALLOWED.

In CML 2.1.0, the copy-refplat-iso-to-disk.sh script required you to wipe all existing labs on the CML server before the script would succeed.

Fixed. The script no longer requires labs to be wiped. All labs should be stopped before running the script, and the script now stops the controller services before the copying starts and re-starts the services after the copying is done.

In CML 2.1.0, the Build Initial Bootstrap Configurations button in the lab’s Design pane would only generate configurations for nodes that had a completely empty configuration in their Edit Config pane in the CML UI.

Many node definitions have an initial boilerplate config, and when you add a node of that type to the lab, it will have a non-empty config. Therefore, you had to clear each node’s boilerplate config manually before using Build Initial Bootstrap Configurations. Otherwise, the configuration for those nodes would not be updated.

Fixed. In CML 2.1.1, configurations will only be generated and overwritten for a particular node if either

  • the node configuration is empty, or

  • the node configuration is identical to the configuration in the node definition template

In all other cases, the configuration will not be changed. As part of this fix, the text in the associated tab in the UI has been updated to match the new behavior.

Some CML-Enterprise customers who were using the Specific License Reservation (SLR) licensing option experienced virl2-controller.service crashes.

Fixed. Improvements have been made to the SLR feature in CML 2.1.1.

Known Issues in CML 2.1.1

In addition to the unresolved issues in CML 2.1.0, the 2.1.1 release has the following known issue:

Bug Description

Notes

Ubuntu images will use a different interface name than what was defined in the node definition.

This problem is mostly cosmetic. In the definitions, the interfaces are named enp0s2, enp0s3, etc. With changed VM definitions, the interface names are ens2, ens3, etc. Note: you may need to change the cloud-init scripts for your Ubuntu nodes if they specifically reference the interface names.

Reference Platform ISO

The 20201020-fcs reference platform ISO image from CML 2.1.0 has been replaced with an updated ISO image: 20201110-fcs. The new reference platform ISO contains new node and image definitions and the crypto version of the IOSv image. See also Reference Platforms and Images.