- Overview
- Product Documentation
- Release Notes
- Getting Started
- CML 2.0 User Guide
- CML 2.0 Admin Guide
- Resources
New and Changed Information¶
There are some product features that will not be supported until a future 2.x release. There are also some new features and changes that may impact your workflow in the product.
Configuration generation. The 1.x releases used AutoNetkit (ANK) to generate detailed configurations, including IP Addresses and routing protocols, for the nodes in your topology. CML 2.0 only uses ANK to generate a basic configuration for most node types.
Node types. The following node types have been replaced or removed:
Ostinato is replaced by Cisco’s TRex. TRex requires two interfaces and can be managed using a GUI application that you can download separately. The TRex node’s console and the node type description provide additional details.
RouteM and iPerf are now installed on the Alpine Linux node type.
Docker containers now run inside CoreOS, which is included as a node type and VM image.
Ubuntu and CoreOS nodes require a proper Cloud-Init configuration. Cloud-init takes longer when there is no IP connectivity. Cloud-init on Ubuntu takes about 30 seconds to be applied beyond the point when the “login” prompt is shown.
WAN emulation is achieved via a new WAN Emulator node type. In the 1.x releases, you could add packet loss and latency by setting properties on a connection in a running simulation. In the 2.0 release, you will instead add a Wan Emulator to your lab on the connection that you want to affect. The WAN Emulator node is basically a two-port bridge or “bump in the wire” that can be controlled via its console.
Clustering. CML 2.0 does not support clustering. Adding support for clustering is on the CML-Enterprise roadmap and will be added in a future release. The architecture supports clustering, and the current CML server is effectively a “cluster of one compute.”
System management. The old User Workspace Management (UWM) web interface is no longer part of the product. The system administrator can manage the CML server via the System Administration Cockpit, which runs on port 9090 by default.
Note
You may still import CML 1.x topologies that contain one or more of the node types that have been replaced or removed, but the imported lab may not function as expected.