ITC CCNP Temp Remote Network Pod
- You must be signed on to the ITC VPN or otherwise be on the ITC network before you can gain access to the remote pods.
- You must have PuTTY or another SSH client installed on your system for console port access to devices
- Your instructor must have set your ITC account up for access to the remote lab system
- You must open a console port connection (see below) to S1 and keep that console port connection open the entire time you are doing any work on a pod. Only one student at a time is able to connect to a console port so the way other students will know someone else is using the pod is that they are not able to connect to S1's console port
- You must use standard passwords of cisco for console or user access and class for enable access regardless of what your lab specifies. This will allow other students to get into your pod and reset the devices if you forget to do so.
- When you are done you must go into each device (regardless of whether you used it or not you are still responsible for doing this) and erase the startup-config file and then issue a reload command. On switches you should also delete flash:vlan.dat before reloading.
- If you are not able to access a device because it has a password on it (and it is not set to cisco or class) you must report the pod number and device to the ITC lab assistant so that it can be cleared.
- You should always use the lowest available pod number. Check to see if the pod is available by trying to connect to the S1 console port for the pod. If you receive an error message when connecting move on to the next pod. If none of the pods seem available (you are unable to connect to S1 on any pods) report the situation to your instructor and the ITC lab assistant.
Pod Wiring Topology
This diagram shows the physical wiring of each remote access pod. Using this combination of cables it is possible to complete all the CCNA and CCNA Security labs (though you may occasionally need to use different ports than specified in the lab or make other small modifications. Some examples of these modifications are explained below.
|R1||Cisco 4331 Router||T1 Serial card in slot 0/1|
|R2||Cisco 4331 Router||T1 Serial card in slot 0/1|
|R3||Cisco 1941 Router|
|S1||Cisco 3650 Switch|
|S2||Cisco 3650 Switch|
|S3||Cisco 2960 Switch|
NOTE: Serial ports are configured as T1 cards but are in different subslots than on 1900 series routers. See Cisco Back-to-Back T1 Interface Configuration for details on configuration.
NOTE: Newer Cisco devices (like the 4331 Routers and the 3650 Switches take a LONG time (5-10 minutes) to reboot. If you reload one of these devices please stay connected and be patient while the device boots. The console may appear frozen at various points during the boot process but unless you have waited 10 minutes without any progress on the screen the device is probably still booting.
Console Port Access
The console port of each network device in each pod is accessible by SSH connection through our serial port server. Simply enter the IP address and port number assigned (see table below) to the terminal server for the device you wish to access into your SSH client and log in with your ITC account credentials (it does take a minute to authenticate) to obtain access just as if you had plugged a console cable into the serial port of your PC. Remember you must be connected to the ITC network first. After you've entered your password and waited a minute press the return key a few times to get the console prompt just as if you had just plugged into the console port directly with a serial console cable.
NOTE: As of 9/12/20 Pods 1-3 do not have working console connections to R3!
NOTE: As of 9/13/20 Pod 1 S1 is frozen and needs a reboot, you will not be able to connect to or configure this device.
You will access PC-1 through PC-6 for each pod through the web console on the ITC NetLab VMware Server: https://netlab-ihcc.campus.ihitc.net Note that this is a different server than the ITC VSCA server you may use for other classes.
- Open your browser (Chrome or Firefox is suggested) to https://netlab-ihcc.campus.ihitc.net
- Click on the "Launch vSphere Client (HTML5)" link on the left side of the page
- You should be able to log in to the vSphere Web Client using your ITC network credentials (the same ones used to connect to the ITC VPN). Note that you will need to enter them as firstname.lastname@example.org (add the @campus.ihitc.net onto the end of your username.
- Once you are logged in to vSphere you can navigate on the left side of your screen to Datacenter -> Cluster where you will find a PC 1, through PC 6 for each pod.
- On the left side of your screen click on the PC attached to your Pod which you would like to access
- On the "Summary" tab for the PC click the "Launch Web Console" link in the upper left.
- A new tab will open in your browser (you may need to allow popups in your browser to see it). It's likely the PC has gone to sleep so the display will be all black. Move your mouse to the center of the window and click in the black space. The PC should wake up after a minute and you will be prompted to log on to the system. Use the password "Cisco123" to log in.
- You should be able to use the PC as normal, setting the IP, etc.
- These systems do not have Internet access, they are only connected to the network devices in your pod. If you need software or other files on the PC to complete your lab please contact the instructor and lab assistant for help.