TShoot 1.0 Remote Labs
Price: $860 USD
Lab Time: 5 days (Monday to Friday)
Number of pods as part of the topology: 1
Recommended number of students per pod: 4
Total recommended number of students: 4
Lab Layout
The TShoot remote lab equipment for a single student pod consists of the following:
: 6 2811 ISR Routers,
: 2 3560 Layer3 Switches (CSW)
: 2 3550 Layer3 Switches (ASW/BSW)
: 1 File SVR
: 3 CLT PC’s
In addition, there are 3common routers and a Web Server that are connected to all pods as shown in Figure 1.

Figure 1: Workgroup lab topology
All routers are Cisco ISR 2811 with Advanced IP Services IOS software.

Figure 2: Instructor Backbone lab topology

Figure 3: Student Power Recycling Access

Figure 4: Instructor VMWare lab device Access. (To reset, shutdown and restart Pod devices ONLY)
Access to the Lab Devices
Access to the Remote Lab is gained through the following URL:
Lab / Classroom Organization
Each lab pod is independent of other pods. Each pod can accommodate up to 4 students.
Summary of Content Changes in Individual Exercises
Compared to the original lab exercises, the remote lab exercises are functionally equivalent. Instructors should note that there is no need for any VPN connection to a remote lab as all devices are accessed from www.livelabs.co.uk . All labs can be performed from within the remote lab environment.
Instructors should note the following:
Delegates should be informed that the alias commands are there to help load files from flash into the startup-config of the devices. Instructors should inform their delegates that they should reload their pod devices after issuing the appropriate lab alias command.
Sample Alias commands:
alias exec cleanup copy flash:/tshoot/cleanup.cfg running-config
alias exec restore configure replace flash:/tshoot/baseline.cfg list force
alias exec restore-capstone configure replace flash:/tshoot/capstone.cfg list force
alias exec init-2-1 copy flash:/tshoot/lab-2-1.cfg startup-config
alias exec init-3-1 copy flash:/tshoot/lab-3-1.cfg startup-config
alias exec init-4-1 copy flash:/tshoot/lab-4-1.cfg startup-config
alias exec init-4-2 copy flash:/tshoot/lab-4-2.cfg startup-config
alias exec init-5-1 copy flash:/tshoot/lab-5-1.cfg startup-config
alias exec init-5-2 copy flash:/tshoot/lab-5-2.cfg startup-config
alias exec init-5-3 copy flash:/tshoot/lab-5-3.cfg startup-config
alias exec init-5-4 copy flash:/tshoot/lab-5-4.cfg running-config
alias exec init-6-1 copy flash:/tshoot/lab-6-1.cfg startup-config
alias exec init-6-2 copy flash:/tshoot/lab-6-2.cfg startup-config
alias exec init-7-1 copy flash:/tshoot/lab-7-1.cfg startup-config
It was noted that the ‘configure replace’ command did not execute correctly consistently during testing. If students find this to be the case it is recommended that student copy from the tshoot directory the appropriate file.
Example:
CRO1#dir
Directory of flash:/
2 -rw- 43877520 Mar 26 2008 17:31:30 c2800nm-adventerprisek9_ivs-mz.124-11.T3.bin
3 drw- 0 Apr 11 2002 05:17:56 -07:00 route
18 drw- 0 Mar 1 2002 23:34:38 -08:00 tshoot
35 drw- 0 Jul 9 2010 08:48:22 -07:00 SWITCH
63881216 bytes total (19677184 bytes free)
CRO1#cd tshoot
CRO1#dir
Directory of flash:/tshoot/
19 -rw- 7033 Mar 10 2002 04:49:32 -07:00 baseline.cfg
20 -rw- 7834 Mar 10 2002 04:49:42 -07:00 capstone.cfg
21 -rw- 264 Mar 10 2002 04:49:48 -07:00 cleanup.cfg
22 -rw- 7004 Mar 10 2002 04:49:56 -07:00 lab-2-1.cfg
23 -rw- 7033 Mar 10 2002 04:50:02 -07:00 lab-3-1.cfg
24 -rw- 7033 Mar 10 2002 04:50:10 -07:00 lab-4-1.cfg
25 -rw- 7035 Mar 10 2002 04:50:24 -07:00 lab-5-1.cfg
26 -rw- 7279 Mar 10 2002 04:50:32 -07:00 lab-5-2.cfg
27 -rw- 7033 Mar 10 2002 04:50:38 -07:00 lab-5-3.cfg
28 -rw- 73593 Mar 10 2002 04:50:44 -07:00 lab-5-4.cfg
29 -rw- 8415 Mar 10 2002 04:50:52 -07:00 lab-6-1.cfg
30 -rw- 8395 Mar 10 2002 04:50:58 -07:00 lab-6-2.cfg
31 -rw- 7834 Mar 10 2002 04:51:08 -07:00 lab-7-1.cfg
32 -rw- 7033 Mar 10 2002 04:50:18 -07:00 lab-4-2.cfg
63881216 bytes total (19677184 bytes free)
######################################################
NOTE for LAB 5-4.
During testing it was noted that the injection of the large 10,000+ routes into IRO1 and IRO2 did not complete correctly with the configure replace or the alias command. Many errors were reported on the consoles and it appears the size of the startup-config being copied and executed from NVRAM causes the problem. To avoid such an issue, it is therefore recommended that the instructors inform their student to first erase start on both of the IRO devices and then issue the reload command. After reloading, student should then copy the following to load the IRO routers configs into RAM.
CRO1#copy flash:/tshoot/ lab-5-4.cfg running-config
After issuing this command student will appear to lose the console connection for a number of minutes while the config file is loaded into RAM. After 3 minutes or so the console will return to normal usage and the lab can proceed without the errors that copying into nvram witnessed.
######################################################
Navigating Flash(example):
Router#cd tshoot (takes you into tshoot directory)
Router#pwd (tells you which directory you are in)
Router#dir (lists what is in the directory)
Router#cd (takes you back one directory level)
Router#pwd (tells you which directory you are in)
Router#dir (lists what is in the directory)
The ISP and Frame-Relay routers have files located directly in the root of flash as these 3745 series routers do not support a directory structure in flash. Should instructors need to reload configurations the startup files will be found in flash and a copy flash:baseline-cfg start will reload the configuration.
Password Recovery:
Password recovery is supported via Livelabs.co.uk – the break sequence that was tested uses ‘Shift + break’. Students can use the break sequence as mentioned above at any stage on BRO1 and CRO2 as the config-register is set to 0x2002 on all stored flash files for these two devices. This config-register setting allows ‘break’ at any point in the CLI. Once the students realize that a password recovery is needed the instructor can inform the students of this feature and the student will be able to initiate the recovery procedure from the 'user' prompt.

