The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
In the build phase, you build the configurations for each node. After selecting the options for the overall topology and each node, you create the configuration files. Alternatively, you can use AutoNetkit to create the configuration files.
You can modify and save configuration files for the topology and for each node in your topology.
While AutoNetkit is useful for generating configuration files for all the nodes in the topology, you can bypass AutoNetkit and enter node configuration information directly.
You can enter configuration information in either of the following ways:
During the design phase, copy and paste configuration commands for each node.
During the simulation phase, connect to a node console and change its configuration when the topology is running. See the chapter Simulate the Topology for more information on how to modify, extract, and save a running configuration.
While in the Design perspective, any changes you manually make to a node configuration are saved in the current filename.virl file. Before you launch a simulation from the Design perspective, a notification window advises you to save the changes or cancel the simulation launch.
The topology design should be complete.
Launch a simulation to observe the changes.
You can use an existing configuration file to create a node configuration in Cisco Modeling Labs.
The topology design should be complete.
Launch a simulation to observe the changes.
You can import a topology from an existing Cariden MATE file, version 5.2.0 or later. Cisco Modeling Labs client will accept site imports up to two layers deep. Any Cariden MATE file that has a topology with more than two layers of sites will not import correctly.
A valid Cariden MATE file is available on your file system.
Cisco Modeling Labs client is running.
Your license allows Cariden MATE file import.
Step 1 | Choose File > Import A window appears, prompting you to Import topology from the Cariden MATE file. |
Step 2 | Choose Import Cariden MATE File then click Next. The license is checked. When confirmed, click Next. |
Step 3 | Choose the From data fileCariden MATE file to import. Use Browse to select the directory and file to import. |
Step 4 | Choose the location Into target folder for the Cariden MATE file. Use Browse to select the target Project folder. |
Step 5 | Enter a filename
for the imported Cariden MATE file.
|
Step 6 | In the Projects view, expand the project folder where you saved the imported file. |
Step 7 | Right click on the imported file, for example Lab_import.virl and choose Open With > Topology Editor. A topology canvas opens and displays the topology. |
Visualize the configuration.
Run the simulation.
The topology design should be complete.
Step 1 | Verify the
configuration for each node in the topology.
| ||
Step 2 | Generate a configuration for the topology. Click Update Router Configurations from the toolbar. Alternatively, from the menu bar, choose Run > Update Router Configurations. You are prompted to save any changes made since the previous configuration update. If the Auto-generate check box is checked for a node, the configuration updates are generated by AutoNetkit. | ||
Step 3 | AutoNetkit
displays a notification after it generates the configuration. Click
No to skip
a comparison of configuration changes. Click
Yes to
open a comparison view of the configuration changes.
| ||
Step 4 | When you close
the comparison view, a notification is displayed, and you can choose whether or
not to open AutoNetkit visualization.
|