This lab runs on a virtualised environment for Cisco IOS called "Dynamips". The method of access to each virtual router is via Telnet to a specific port on the IP of the machine that runs the virtualization platform.
This lab uses a Cisco 3745 router with 16 Port 10BaseT/100BaseTX EtherSwitch (NM-16ESW) module.
Note: This Cisco model is actually a router, but the 16-port module provides basic Layer-2 capabilities, and we will use these as switches. Dynamips does not support the emulation of the Cisco Catalyst class of switches, unfortunately.
The instructors will divide the class into groups, where each group is responsible for the operation of a campus. Decide amongst yourselves which person will be responsible for configuring each switch.
Access to Dynamips is by telnet, where each virtual switch or router has a different port number in the table below.
Each participant should ensure that their device has a suitable telnet client. Linux and MacOS system have access to a shell command prompt (or Terminal) program, which allows telnet at the command line. Windows users should use Putty1 or another similar telnet program; make sure you select Telnet not SSH.
The instructor will provide the IP address of the host in this particular workshop. It will normally be vtp.ws.nsrc.org, but the instructor will confirm this at the start of this lab.
Campus 1
Device Name | Console Access |
---|---|
bdr1.campus1 | telnet vtp.ws.nsrc.org 2011 |
core1.campus1 | telnet vtp.ws.nsrc.org 2012 |
dist1-b1.campus1 | telnet vtp.ws.nsrc.org 2013 |
edge1-b1.campus1 | telnet vtp.ws.nsrc.org 2014 |
edge2-b1.campus1 | telnet vtp.ws.nsrc.org 2015 |
dist1-b2.campus1 | telnet vtp.ws.nsrc.org 2016 |
edge1-b2.campus1 | telnet vtp.ws.nsrc.org 2017 |
edge2-b2.campus1 | telnet vtp.ws.nsrc.org 2018 |
Campus 2
Device Name | Console Access |
---|---|
bdr1.campus2 | telnet vtp.ws.nsrc.org 2021 |
core1.campus2 | telnet vtp.ws.nsrc.org 2022 |
dist1-b1.campus2 | telnet vtp.ws.nsrc.org 2023 |
edge1-b1.campus2 | telnet vtp.ws.nsrc.org 2024 |
edge2-b1.campus2 | telnet vtp.ws.nsrc.org 2025 |
dist1-b2.campus2 | telnet vtp.ws.nsrc.org 2026 |
edge1-b2.campus2 | telnet vtp.ws.nsrc.org 2027 |
edge2-b2.campus2 | telnet vtp.ws.nsrc.org 2028 |
Campus 3
Device Name | Console Access |
---|---|
bdr1.campus3 | telnet vtp.ws.nsrc.org 2031 |
core1.campus3 | telnet vtp.ws.nsrc.org 2032 |
dist1-b1.campus3 | telnet vtp.ws.nsrc.org 2033 |
edge1-b1.campus3 | telnet vtp.ws.nsrc.org 2034 |
edge2-b1.campus3 | telnet vtp.ws.nsrc.org 2035 |
dist1-b2.campus3 | telnet vtp.ws.nsrc.org 2036 |
edge1-b2.campus3 | telnet vtp.ws.nsrc.org 2037 |
edge2-b2.campus3 | telnet vtp.ws.nsrc.org 2038 |
Campus 4
Device Name | Console Access |
---|---|
bdr1.campus4 | telnet vtp.ws.nsrc.org 2041 |
core1.campus4 | telnet vtp.ws.nsrc.org 2042 |
dist1-b1.campus4 | telnet vtp.ws.nsrc.org 2043 |
edge1-b1.campus4 | telnet vtp.ws.nsrc.org 2044 |
edge2-b1.campus4 | telnet vtp.ws.nsrc.org 2045 |
dist1-b2.campus4 | telnet vtp.ws.nsrc.org 2046 |
edge1-b2.campus4 | telnet vtp.ws.nsrc.org 2047 |
edge2-b2.campus4 | telnet vtp.ws.nsrc.org 2048 |
Campus 5
Device Name | Console Access |
---|---|
bdr1.campus5 | telnet vtp.ws.nsrc.org 2051 |
core1.campus5 | telnet vtp.ws.nsrc.org 2052 |
dist1-b1.campus5 | telnet vtp.ws.nsrc.org 2053 |
edge1-b1.campus5 | telnet vtp.ws.nsrc.org 2054 |
edge2-b1.campus5 | telnet vtp.ws.nsrc.org 2055 |
dist1-b2.campus5 | telnet vtp.ws.nsrc.org 2056 |
edge1-b2.campus5 | telnet vtp.ws.nsrc.org 2057 |
edge2-b2.campus5 | telnet vtp.ws.nsrc.org 2058 |
Campus 6
Device Name | Console Access |
---|---|
bdr1.campus6 | telnet vtp.ws.nsrc.org 2061 |
core1.campus6 | telnet vtp.ws.nsrc.org 2062 |
dist1-b1.campus6 | telnet vtp.ws.nsrc.org 2063 |
edge1-b1.campus6 | telnet vtp.ws.nsrc.org 2064 |
edge2-b1.campus6 | telnet vtp.ws.nsrc.org 2065 |
dist1-b2.campus6 | telnet vtp.ws.nsrc.org 2066 |
edge1-b2.campus6 | telnet vtp.ws.nsrc.org 2067 |
edge2-b2.campus6 | telnet vtp.ws.nsrc.org 2068 |
If there are more campuses, the port access scheme continues in the same style.
Using the telnet client on your PC or laptop, connect to the switches you have been assigned; for example, to connect to the console port of core1.campus1:
telnet vtp.ws.nsrc.org 2012
or to edge2-b1.campus6:
telnet vtp.ws.nsrc.org 2065
Once connected, you will see the Dynamips response, followed by the login or command prompt of the router:
bash-3.2$ telnet vtp.ws.nsrc.org 2012
Trying 10.10.0.241...
Connected to vtp.ws.nsrc.org.
Escape character is '^]'.
Connected to Dynamips VM "core1.campus1" (ID 4, type c3745) - Console port
Press ENTER to get the prompt.
....
If the “Connected to Dynamips VM” won’t appear, even after hitting the Return key several times, please request help from the workshop instructors.
Then, if you see this question:
Would you like to enter the initial configuration dialog? [yes/no]:
Answer "no".
The router will show some initialization routines, and finally, you will see the default prompt:
Router>
You can then go into privileged mode:
Router> enable
Router#
And then enter configuration mode:
Router# configure terminal
Router(config)#
And you are ready to start entering configuration statements. When you are done, exit configuration mode by typing end or pressing ctrl-Z and save your changes:
Router(config)# end
Router# write memory
The putty.exe programme is available on the workshop website, under the software heading in the references section. Windows users without a telnet client should download the software from the workshop website, and install it on their desktop (it doesn’t need administrator privileges). Once installed, simply click on it to run. Note that putty by default assumes connections will be by Secure Shell, so remember to select “telnet” and the correct port when making connections to the workshop lab equipment.↩