Upgrade Limitations

Upgrading from Previous Releases

Cisco Modeling Labs 2.0 is a brand-new platform. In-place upgrades from the 1.6 release to the 2.0 release are not supported. If you have an existing 1.x installation of CML or Cisco VIRL Personal Edition, you will have to migrate to a new installation of CML-Enterprise or CML-Personal 2.0.

System Settings

There is no automated migration of system settings or users from 1.x to 2.0. Because of the scope of changes between the 1.6 and 2.0 releases, many of the system settings from the 1.6 release are no longer applicable. The initial set-up wizard will prompt you for required settings during the CML 2.0 installation. During the installation process, you will also create a system administrator account and an initial application user account with application administrator privileges. You can apply additional system settings in the new System Administration Cockpit after you complete the installation process using the system administrator account. You can create and manage application user accounts using the application administrator account. From the Lab Manager page of the UI, select Tools ‣ System Administration.

Topology Files

CML 2.0 supports backward compatibility for .virl topologies from the 1.6 release with some limitations. You can import your legacy .virl files from your local machine to the CML server from the Lab Manager page in the new UI. In the 1.6 release, topology files generally reside on the local machine under the GUI’s workspace folder. To find the local path to a particular topology file, right-click on the file in the Project view of VM Maestro or the CML UI and select Properties from the pop-up menu. The Resource ‣ Location property provides the file location.

Upgrades to Future 2.x Releases

While upgrades from 1.x releases are not supported, in-place upgrades within the 2.x train will be supported for both CML-Enterprise and CML-Personal.