In this tutorial, we shall look at Virtual LANs (VLANs). VLANs are logical grouping of devices in the same broadcast domain. VLANs are usually configured on switches by placing some interfaces into one broadcast domain and some interfaces into another. A VLAN acts like a physical LAN, but it allows hosts to be grouped together in the same broadcast domain even if they are not connected to the same switch. They can be spread across multiple switches, with each VLAN being treated as its own broadcast domain. By default, all ports on a switch belong to the default VLAN, VLAN 1.
In this tutorial, we will create a simple Lab in the Pocket CLI App to configure VLAN on a switch. Devices we’ll use in this Lab are 1 Switch, and 4 Hosts. To setup this Lab:
In this tutorial, we shall look at the initial step-by-step configuration of a cisco switch in the Pocket CLI App. To get the nodes and your working area in the App, you first need to design a lab. In this case we are going to add a switch to the lab. To achieve this:
In the previous tutorial, we looked at getting used to the various prompts in the Pocket CLI App. In this tutorial, we will explore some keyboard shortcuts, and how to auto-complete commands.
There are several IOS keyboard shortcuts but we shall explore just a few, relevant to navigating around the Pocket CLI App.
At launch of the App, the only keyboard visible is your own smartphone’s keyboard. There is a ‘hidden’ keyboard (also known at the custom keyboard) that has the Tab, Ctrl, Alt, Break, and the Navigation/Arrow keys. To view this keyboard, tap on the dotted box at the top right corner of the screen as shown in the screenshot below. Tap on that same box to hide the keyboard again.
Primarily, the Cisco IOS offers these modes of operation: the user EXEC mode, the privileged EXEC mode, the Global Configuration mode, and other specific configuration modes such as; the Interface Configuration mode, Line Configuration Mode, and Router Configuration Mode.
The initial prompt you interface with when you first connect to a Cisco network Router or Switch is the user EXEC mode. This is denoted by a text and the greater-than (>) sign to the right of the text. See below an example of user EXEC mode prompt:
The text represents the hostname of the device, which by default is the device type; Router or Switch. In this mode, you cannot edit or view device configurations; you can only view the device’s status and other miscellaneous information. See below a list commands you can execute in this mode:
disable Turn off privileged commands
disconnect Disconnect an existing network connection
enable Turn on privileged commands
exit Exit from the EXEC
logout Exit from the EXEC
ping Send echo messages
show Show running system information
ssh Open a secure shell client connection
telnet Open a telnet connection
terminal Set terminal line parameters
traceroute Trace route to destination
Available on update version 1.55
Organize the lab list with tags.
Notice the new ALL folder when viewing the labs table.
To add a tag to a network layout, select the Edit Info option from the labs menu after right swiping a user designed lab.
Type a tag information. Separate multiple tags with a comma. Save.
A new folder will be created from the tag(s) entered: TEST in this example.
Once a folder is created, the option to drag and drop becomes available. Hold down on a cell to activating the movement option. To remove a tag, edit the tag field, or drag the lab back to the ALL section.
The image below is after dragging New Lab Design 140 to the TEST section.
Labs can have multiple tags or belong to multiple folders. Tap the folder name to hide or show its contents.
Available on update version 1.54
First, let's answer the question, what is a scenario? A scenario is the network lab that the IOS Network Simulator team currently provides for download. Scenarios should not be confused with the user created labs that can be freely designed and configured. It has the following characteristics:
Now that we know what a scenario is ... here's how to create one yourself.
New privileged EXEC commands for managed devices (routers and switches):
Just to be clear, these new commands are specific to the simulator. You will not find these commands on the real devices.
Use configure scenario instead of configure terminal to start the scenario creation mode. All configuration commands entered while in scenario configuration mode will be flagged as a scenario expected answer. The flagged configurations will show on the answer page as soon as the write memory or copy running-config startup-config command is entered.
Remove the answers from running-config by typing no scenario-config for the current device, or no scenario-config all devices to have it take effect for the whole lab.
The example below configures hostname test as the expected answer.
***** Still in testing *****
IOS NETWORK SIM
SCENARIO CREATION MODE
***** Still in testing *****
Enter scenario expected commands, one per line. End with CNTL/Z
%SYS-5-CONFIG_I: Configured from console by console
* Scenario configuration are not saved to startup-config. If you need a configuration copied to startup-config, please use the configure terminal command.
Copy the expected answers back to running-config with the command:
# copy scenario-config running-config
New commands for Host devices:
Disable the scenario port lights from any of the host devices with the command:
c:\> disable scenario port lights
Negate with the enable command.
Other global scenario mode commands for managed devices:
(config)# scenario disable command configure terminal
- makes the device configuration read only
(config)# scenario disable command startswith interface
- interface configuration is not allowed
(config)# scenario disable command startswith router
- dynamic routing configuration is blocked
(config)# scenario disable command endswith fastethernet 0/1
- configuration involving this interface (fastethernet 0/1) is blocked
The command is per device, and the full command needs to be entered, for the block to work.
(config)# scenario disable command conf t
result: configure terminal will not be block because the wrong command (a command shortcut) was used.
Negate the block commands with the prefix no.
(config)# no scenario disable command configure terminal
Sharing of your created scenarios will be available soon. Thank you!