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.
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.
For this version of Cisco Modeling Labs, you are able to import configurations from a number of other file types, such as, Cariden MATE, Visio, GNS3 to name a few. These are discussed in the following sections.
You can import a topology from an existing Cariden MATE file, version 5.2.0 or later or version 6.1.0. 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.
Step 1 | Choose A window appears, prompting you to Import Cariden MATE file. . |
Step 2 | Choose Import Cariden MATE File then click Next. |
Step 3 | Choose the From data file Cariden 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.
The Cariden MATE file converts to a Cisco Modeling Labs .virl 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
The canvas
opens and displays the topology.
.
|
Step 1 | Choose A window appears, prompting you to Export to Cariden MATE file. . |
Step 2 | Choose Export Cariden MATE File then click Next. |
Step 3 | Choose the location To file for the Cariden MATE file export. Use Browse to select the target Project folder. |
Step 4 | Enter a filename for the exported Cariden MATE file, or use the default filename. For example, sample_topology.virl is converted to sample_topology.pln and saved in the target directory. |
Step 5 | Click Finish. The Cisco Modeling Labs .virl file silently converts to a Cariden MATE .pln file. |
You can import a topology from an existing Visio .vsdx file, version 2013 and later.
Step 1 | Choose The Import dialog box appears. . | ||
Step 2 | Expand the
Topology
folder, choose
Import Visio
vsdx File and click
Next.
| ||
Step 3 | Choose the From data file Visio .vsdx file to import. Use Browse to select the directory and file to import. | ||
Step 4 | Choose the
location
Into target
folder for the Visio .vsdx file. Use
Browse to
select the target Project folder.
| ||
Step 5 | Click
Finish.
The Visio
.vsdx file converts to a Cisco Modeling Labs .virl file, using the original
filename of the file and it is automatically opened on the canvas.
|
For this release of Cisco Modeling Labs, export to Visio .vsdx files is not supported. However, export to .svg files is supported, as Visio supports the use of .svg files. The Export option can be used to export .virl files as .svg files.
Step 1 | Choose A window appears, prompting you to Export to SVG file. . |
Step 2 | Choose Export to SVG file then click Next. |
Step 3 | Choose the location To file for the SVG file export. Use Browse to select the target Project folder. |
Step 4 | Enter a filename for the exported SVG file, or use the default filename. For example, sample_topology.virl is converted to sample_topology.svg and saved in the target directory. |
Step 5 | Click Finish. The Cisco Modeling Labs .virl file silently converts to a SVG .svg file. |
You can import a topology from an existing GNS3 .gns3 file.
Step 1 | Choose The Import dialog box appears. . |
Step 2 | Expand the
Topology
folder, choose
Import GNS3
File and click
Next.
The Import GNS3 File dialog box is displayed. |
Step 3 | In the From source file field, use Browse to select the directory and GNS3 .gns3 file to import. |
Step 4 | In the
Into destination
file field, use
Browse to
select the target folder.
|
Step 5 | Click
Finish.
The GNS3
.gns3 file converts to a Cisco Modeling Labs .virl file, using the original
filename of the file and it is automatically opened on the canvas.
|
Step 1 | Choose The Export dialog box appears. . |
Step 2 | Expand the
Topology
folder, choose
Export to GNS3
File and click
Next.
|
Step 3 | In the
To file
field, use
Browse to
select the target folder.
|
Step 4 | Enter a filename for the exported GNS3 file, or use the default filename. For example, sample_topology.virl is converted to sample_topology.gns3 and saved in the target directory. |
Step 5 | Click Finish. The Cisco Modeling Labs .virl file silently converts to a GNS3 .gns3 file. |
You can import a topology from an existing GraphML .graphml file.
Step 1 | Choose The Import dialog box appears. . |
Step 2 | Expand the
Topology
folder, choose
Import
GraphML and click
Next.
The Import GraphML File dialog box is displayed. |
Step 3 | In the From source file field, use Browse to select the directory and GraphML .graphml file to import. |
Step 4 | In the
Into destination
file field, use
Browse to
select the target folder.
|
Step 5 | Click
Finish.
The
GraphML .graphml file converts to a Cisco Modeling Labs .virl file, using the
original filename of the file and it is automatically opened on the canvas.
|
Step 1 | Choose The Export dialog box appears. . |
Step 2 | Expand the
Topology
folder, choose
Export to
GraphML File and click
Next.
|
Step 3 | In the
To file
field, use
Browse to
select the target folder.
|
Step 4 | Enter a filename for the exported GraphML file, or use the default filename. For example, sample_topology.virl is converted to sample_topology.graphml and saved in the target directory. |
Step 5 | Click Finish. The Cisco Modeling Labs .virl file silently converts to a GraphML .graphml file. |
You can import the per-node configurations previously exported as individual text files (.cfg suffix) into your .virl file. You can import the configuration files having made any necessary changes to them.
Step 1 | Choose
The
.
Import dialog box is displayed.
|
Step 2 | Choose
Import
Configurations into Existing Topology and click
Next.
The
Import
Configurations into Existing Topology dialog box is displayed.
|
Step 3 | Select the applicable location from the From Directory drop-down list or choose Browse. |
Step 4 | Click
Finish to
import the node configuration files.
The node
configuration files are imported into the existing topology and a message is
displayed to confirm this
|
You can export the per-node configurations from within your .virl file and export them to a directory location of your choice as individual text files (.cfg suffix). There you can make necessary changes to the configuration files before importing the configuration files back into the .virl file.
Step 1 | Choose
The
.
Export dialog box is displayed.
|
Step 2 | Choose
Export Nodes'
Configurations to Files and click
Next.
The
Export
Nodes' Configurations to Files dialog box is displayed.
|
Step 3 | Select a location from the To Directory drop-down list or choose Browse to select the applicable location. |
Step 4 | Click Finish to export the node configuration files. The node configuration files are exported to the chosen location. |
The topology design should be complete.
Step 1 | 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 2 | When you close
the comparison view, a notification is displayed, and you can choose whether or
not to open AutoNetkit Visualization.
|
AutoNetkit allows you to generate a stripped-back configuration that provides the basic infrastructure configuration required to support configuration extraction and Live Visualization.
With this feature enabled, no IP addressing or routing protocol configuration is created. This leaves the node in a state where it is ready for manual configuration. This is ideal when using a simulation for study practice or when wanting to go through the process of building an environment by hand.
You can specify the TCP port number that you want to use when connecting to the console, auxiliary, or monitor ports of a particular node running in a simulation. These port numbers are optional and can be set via the Cisco Modeling Labs client. The port number allocation is retained in the settings.ini file and is applied each time the simulation is started. Functionality is provided so that the TCP port numbers in use are easily adjusted.
VLANs can be assigned to the interfaces of the end nodes, using the
view.VLANs are set using the VLAN property under the General tab in the AutoNetkit field on the interface. The properties are set on the interfaces of the nodes connected to the IOSvL2 image, such as on the IOSv nodes, server node interfaces.
The Cisco IOSv Layer 2 switch introduces a managed switch to the Cisco Modeling Labs environment.
By default, all VLANs are placed in vlan2.
interface GigabitEthernet0/1 description to iosv-1 switchport access vlan 2 switchport mode access no shutdown ! interface GigabitEthernet0/2 description to iosv-3 switchport access vlan 2 switchport mode access no shutdown ! interface GigabitEthernet0/3 description to iosv-2 switchport access vlan 2 switchport mode access no shutdown ! interface GigabitEthernet1/0 description to iosv-4 switchport access vlan 2 switchport mode access no shutdown !
It is permissible to connect multiple managed switches together. Multiple managed switches connected together form a trunk link between the switches and their appropriate vtp domains.
The resultant interface configurations for iosvl2-1 and iosvl2-2 are as follows:
interface GigabitEthernet0/1 description to iosv-1 switchport access vlan 2 switchport mode access no shutdown ! interface GigabitEthernet0/2 description to iosv-3 switchport access vlan 2 switchport mode access no shutdown ! interface GigabitEthernet0/3 description to iosv-2 switchport access vlan 2 switchport mode access no shutdown ! interface GigabitEthernet1/0 description to iosv-4 switchport access vlan 2 switchport mode access no shutdown ! interface GigabitEthernet1/1 description to iosvl2-2 switchport trunk encapsulation dot1q switchport mode trunk no shutdown !
interface GigabitEthernet0/1 description to iosvl2-1 switchport trunk encapsulation dot1q switchport mode trunk no shutdown ! interface GigabitEthernet0/2 description to server-1 switchport access vlan 2 switchport mode access no shutdown ! interface GigabitEthernet0/3 description to iosv-5 switchport access vlan 2 switchport mode access no shutdown !
This release of Cisco Modeling Labs includes the demo version of the Cisco ASAv image (a fully-operational license is available by separate purchase). The Cisco ASAv image adds firewall capabilities to Cisco Modeling Labs.
The default AutoNetkit configuration puts each interface into security-level 0, adds a nameif, and allows http, SSH, and Telnet access to this nameif.
interface GigabitEthernet0/0 description to server-1 nameif outside security-level 0 no shutdown ip address 10.0.0.5 255.255.255.252 interface GigabitEthernet0/1 description to iosv-1 nameif outside-1 security-level 0 no shutdown ip address 10.0.0.9 255.255.255.252 interface GigabitEthernet0/2 description to iosv-2 nameif outside-2 security-level 0 no shutdown ip address 10.0.0.13 255.255.255.252 interface GigabitEthernet0/3 description to iosv-3 nameif outside-3 security-level 0 no shutdown ip address 10.0.0.17 255.255.255.252
http 0.0.0.0 0.0.0.0 mgmt ssh 0.0.0.0 0.0.0.0 mgmt telnet 0.0.0.0 0.0.0.0 mgmt http 0.0.0.0 0.0.0.0 outside ssh 0.0.0.0 0.0.0.0 outside telnet 0.0.0.0 0.0.0.0 outside http 0.0.0.0 0.0.0.0 outside-1 ssh 0.0.0.0 0.0.0.0 outside-1 telnet 0.0.0.0 0.0.0.0 outside-1 http 0.0.0.0 0.0.0.0 outside-2 ssh 0.0.0.0 0.0.0.0 outside-2 telnet 0.0.0.0 0.0.0.0 outside-2 http 0.0.0.0 0.0.0.0 outside-3 ssh 0.0.0.0 0.0.0.0 outside-3 telnet 0.0.0.0 0.0.0.0 outside-3
Security levels are set using the Security Level property under the Firewall tab in the AutoNetkit field on the interface. The properties are set on the Cisco ASAv node's interfaces, as shown.
interface GigabitEthernet0/0 description to server-1 nameif level-50 security-level 50 no shutdown ip address 10.0.0.5 255.255.255.252 interface GigabitEthernet0/1 description to iosv-1 nameif outside security-level 0 no shutdown ip address 10.0.0.9 255.255.255.252 interface GigabitEthernet0/2 description to iosv-2 nameif outside-1 security-level 0 no shutdown ip address 10.0.0.13 255.255.255.252 interface GigabitEthernet0/3 description to iosv-3 nameif outside-2 security-level 0 no shutdown ip address 10.0.0.17 255.255.255.252
http 0.0.0.0 0.0.0.0 level-50 ssh 0.0.0.0 0.0.0.0 level-50 telnet 0.0.0.0 0.0.0.0 level-50 http 0.0.0.0 0.0.0.0 mgmt ssh 0.0.0.0 0.0.0.0 mgmt telnet 0.0.0.0 0.0.0.0 mgmt http 0.0.0.0 0.0.0.0 outside ssh 0.0.0.0 0.0.0.0 outside telnet 0.0.0.0 0.0.0.0 outside http 0.0.0.0 0.0.0.0 outside-1 ssh 0.0.0.0 0.0.0.0 outside-1 telnet 0.0.0.0 0.0.0.0 outside-1 http 0.0.0.0 0.0.0.0 outside-2 ssh 0.0.0.0 0.0.0.0 outside-2 telnet 0.0.0.0 0.0.0.0 outside-2
Note | AutoNetkit automatically renames the nameif if there are multiple interfaces with the same security level. |
Generic routing encapsulation (GRE) is a simple IP packet encapsulation protocol that is used to transport packets over a network. Information is sent from one network to the other through a GRE tunnel.
In this example, you set the values on node iosv-1 and node iosv-2 to tell AutoNetkit to create the configuration for a GRE tunnel terminating on the external router node, ext_router_1.
! interface Tunnel1 ip address 172.16.100.2 255.255.255.252 tunnel source GigabitEthernet0/3 tunnel destination 0.0.0.0 !The tunnel destination is blank since it needs to be set to the IP address of the far-end device, which you may or may not know in advance. However, you can edit the configuration in the Cisco Modeling Labs client GUI before you start up the simulation. So if you do know the target address, you can add the target IP address in there (tunnel destination x.x.x.x.) Remember that it is not the IP address of the tunnel that goes in here but the IP address of the router/device terminating the GRE tunnel itself. If this is a devices that is on the FLAT network directly, then a 172.16.1.x address would go in here.
Note | You cannot do this using the standard guest account. The simulation will fail as you are using a system-level resource (the Static IP address), so an account with administrative permissions is required. |
You can now start your simulation.
Cisco IOS XRv virtual machines, version 5.3.0 and upwards can be automatically configured for communication and operation with an OpenDayLight (ODL) controller for path manipulation and control using MPLS TE tunnels. An option in available under the AutoNetkit properties tab in the Cisco Modeling Labs client called ODL Management Group. Cisco IOS XRv devices set with the ODL management group attribute must be paired with an external router entity, which is configured with the matching ODL Management Group attribute and an ODL external server IP address. The ODL server may be running on your Cisco Modeling Labs server or another location. It does not need to be part of the Cisco Modeling Labs simulation itself. However, connectivity between the simulation and the server must be provided.