- Overview
- Product Documentation
- CML 2.6 Release Notes
- CML 2.6 Installation Guide
- CML 2.6 User Guide
- CML 2.6 Admin Guide
- CML Administrator's Guide
- Cisco Modeling Labs System Overview
- System Defaults
- Creating a New Node Definition
- Custom VM Images
- Clustering
- CML Admin Tools
- System Settings
- Networking
- Resources
Bootstrap Configuration Building¶
CML provides basic stub configurations for simulated nodes. Depending on the node type, it generates configurations for:
setting the hostname
activation of interfaces
creation of default configuration like users, logins, etc.
It does not currently create IP address plans, dynamic/static routing or other advanced configurations.
Note
The configuration generation tool generates configurations only for clean nodes or nodes that have been wiped and not started yet. The tool doesn’t generate configurations for running or stopped nodes.
Note
Nodes can have “default configurations” as defined in the provisioning section of the corresponding node definition. The default configurations of nodes will be auto populated in the Config` tab of each node. In the Workbench, when you click the Bootstrap Lab button in the Lab menu, the CML will generate configurations for nodes only in these cases:
The Config` tab of the node is empty. If you want to force-generate node configuration, you need to delete the configuration and save the empty configuration for each node you want to generate configuration for.
The Config` tab contains the default configurations from the provisioning section of the corresponding node definition. If you want to ensure that the default configuration is not overwritten by the configuration generator, you have to modify it e.g., append an empty line.
In all other cases, node configuration will not be overwritten.
Supported Node Types
The hostname and usernames are configured for all of the supported node types. In addition, interface and line configuration is done for non-Linux supported node types. For more information about supported node types, see Reference Platforms and Images.
Additional node type specific configured properties are:
ASAv: Access lists for management access.
Nexus 9300v: VDC, SNMP server, RMON.
WAN Emulator: Latency (100ms) and bandwidth (512Kbps).
Ubuntu and Core OS nodes can leverage “cloud-init” configurations. Please refer to cloud-init configuration examples.
Related Information