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.
The simulation phase is when you run the simulation of your topology design. The Simulation perspective provides a set of views that support the simulation phase. By comparison, the design and build activities occur in the Design perspective, which provides a set of views that support the design activity. Some views in the Simulation perspective can also be viewed in the Design perspective.
Note | To reset your current perspective to its original configuration when the workbench was first opened, right-click the perspective button and select Reset. |
In Cisco Modeling Labs Corporate Edition, the number of nodes you can run is limited by the resources available on the server and the number of licenses available. In Cisco Modeling Labs Corporate Edition, the design limit is 1,000 nodes.
During the simulation phase, you can perform the tasks described in the following sections.
Complete the topology design.
Complete the task of building the nodes and interfaces.
Caution | When you manually make changes to a node configuration and bypass AutoNetkit auto-generation, those changes do not appear in the topology view of the Design perspective or Simulation perspective. For example, if you use the hostname command to change the host name from iosv-1 to Router-1 in the configuration, the node name in the topology view and in other related views remains as iosv-1. |
Open the desired topology.
Note | The topology should be open and visible in the Topology Editor. If you have multiple topologies open in the Topology Editor, simulation will launch for the currently active view. |
Step 1 | To connect to a
console for a specific node, right-click the node in the
Simulations view and choose
.
A new Terminal view opens.
| ||||
Step 2 | To disconnect a
terminal from the simulation, click
Disconnect in the
Terminal view toolbar or click the
Close icon in the
Terminal view.
|
There are several methods for stopping an entire simulation. These are discussed in the following sections.
Step 1 | In the toolbar, click the Stop Simulations button. A Stop Simulation(s) dialog box appears. | ||
Step 2 | In the Simulation column, click once to highlight the simulation to stop. | ||
Step 3 | (Optional) To
save the configurations, click the adjacent setting in the
Extract
Configurations? column until the prompt changes to
Yes.
| ||
Step 4 | (Optional) To
close the internal terminals associated with the simulation, click the adjacent
setting in the
Close
Terminals? column until the prompt changes to
Yes.
| ||
Step 5 | To stop the simulation, click the adjacent setting in the Stop Simulation? column until the prompt changes to Yes. | ||
Step 6 | Click
OK to confirm
stopping the simulation, or click
Cancel to leave
the simulation running.
On Mac OS X, you update the values for Extract Configurations?, Stop Simulation? and Close Terminals? in the columns directly. You do not need to select the name of the simulation.
|
Step 1 | In the Simulations view, right-click the Simulation name and select Stop Simulation. The Stop simulation confirmation dialog box appears. | ||
Step 2 | Click
OK to stop the
simulation.
Once
selected, all nodes in the simulation start shutting down. It may take a few
minutes for the simulation to shut down completely and to disappear from the
Simulations view.
|
Step 1 | In the
Simulations view, right-click the node to stop and
select
Stop this node.
The Are you sure dialog box appears. | ||
Step 2 | Click
OK to stop the
simulation. Alternatively, click
Cancel to abandon
the operation and return to the simulation.
|
Step 1 | Right-click a stopped node. When a node is stopped, its status changes to [DELETED]. | ||
Step 2 | Click
Start this node.
The Requesting start dialog box appears.
| ||
Step 3 | Choose one or more
of the following actions:
|
Step 1 | Connect to a
console on a router node. Right-click the node in the
Simulations view and choose
Telnet > to
its Console port.
A new Terminal view opens.
| ||
Step 2 | If no banner or router prompt is visible, press Enter. You are now working with the operating system running on the node, for example, Cisco IOS software. | ||
Step 3 | Use the
operating system commands to view or modify the node configuration.
|
Step 1 | In the
Simulations view, right-click the topology name,
making sure not to click the node name, and select
Extract
Configurations.
| ||
Step 2 | Ensure that all
external Telnet connections to the simulation are closed before proceeding.
| ||
Step 3 | Click
OK.
A dialog box appears. | ||
Step 4 | Click
Run in Backgroud.
When the
extraction is complete, a message is displayed.
| ||
Step 5 | Click OK. |