Difference between revisions of "ITC Remote Network Pod Instructions"

From ITCwiki
Jump to navigation Jump to search
(→‎Console Port Access: decrease table length by dividing into three tables)
 
Line 160: Line 160:
  
 
Notice that the network card on each PC is connected to two different places on the topology diagram, directly to one port on a router and also to a port on the switch. Normally you would only actually have the PC connected to one of these two ports so you should disable whichever port you are not using on the router or the switch.
 
Notice that the network card on each PC is connected to two different places on the topology diagram, directly to one port on a router and also to a port on the switch. Normally you would only actually have the PC connected to one of these two ports so you should disable whichever port you are not using on the router or the switch.
 +
 +
# Open your browser (Firefox is suggested) to https://vcsa.campus.ihitc.net/
 +
# Click on the "vSphere Client (HTML5) - partial functionality" 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).
 +
# Once you are logged in to vSphere you can navigate on the left side of your screen to ITC -> Cluster -> Remote Pods where you will find a PC A, PC B, and PC C 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. 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 "cisco" 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. Any additional files you need to complete your lab on the PC should already be loaded onto the PC in the "C:\CCNA Security VM Files" directory.

Latest revision as of 15:28, 1 April 2020

Pre-Requisites

  • 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

Rules

  • You must open a console port connection (see below) to R1 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 R1'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 R1 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 R1 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.

MAP ASA IHCC.svg

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 assigned to the terminal server for the device you wish to access into your SSH client and log in with your ITC account credentials 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.

Pod Device Console Port IP
Pod 1 R1 172.18.1.1
R2 172.18.1.2
R3 172.18.1.3
S1 172.18.1.4
S2 172.18.1.5
S3 172.18.1.6
ASA 172.18.1.7
Pod 2 R1 172.18.1.8
R2 172.18.1.9
R3 172.18.1.10
S1 172.18.1.11
S2 172.18.1.12
S3 172.18.1.13
ASA 172.18.1.14
Pod 3 R1 172.18.1.15
R2 172.18.1.16
R3 172.18.1.17
S1 172.18.1.18
S2 172.18.1.19
S3 172.18.1.20
ASA 172.18.1.21
Pod Device Console Port IP
Pod 4 R1 172.18.1.22
R2 172.18.1.23
R3 172.18.1.24
S1 172.18.1.25
S2 172.18.1.26
S3 172.18.1.27
ASA 172.18.1.28
Pod 5 R1 172.18.1.29
R2 172.18.1.30
R3 172.18.1.31
S1 172.18.1.32
S2 172.18.1.33
S3 172.18.1.34
ASA 172.18.1.35
Pod 6 R1 172.18.1.36
R2 172.18.1.37
R3 172.18.1.38
S1 172.18.1.39
S2 172.18.1.40
S3 172.18.1.41
ASA 172.18.1.42
Pod Device Console Port IP
Pod 7 R1 172.18.1.43
R2 172.18.1.44
R3 172.18.1.45
S1 172.18.1.46
S2 172.18.1.47
S3 172.18.1.48
ASA 172.18.1.49
Pod 8 R1 172.18.1.50
R2 172.18.1.51
R3 172.18.1.52
S1 172.18.1.53
S2 172.18.1.54
S3 172.18.1.55
ASA 172.18.1.56
Pod 9 R1 172.18.1.57
R2 172.18.1.58
R3 172.18.1.59
S1 172.18.1.60
S2 172.18.1.61
S3 172.18.1.62
ASA 172.18.1.63

PC Access

You will access PC-A, PC-B, and PC-C for each pod through the web console on the ITC VMware Server: https://vcsa.campus.ihitc.net

Notice that the network card on each PC is connected to two different places on the topology diagram, directly to one port on a router and also to a port on the switch. Normally you would only actually have the PC connected to one of these two ports so you should disable whichever port you are not using on the router or the switch.

  1. Open your browser (Firefox is suggested) to https://vcsa.campus.ihitc.net/
  2. Click on the "vSphere Client (HTML5) - partial functionality" link on the left side of the page
  3. 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).
  4. Once you are logged in to vSphere you can navigate on the left side of your screen to ITC -> Cluster -> Remote Pods where you will find a PC A, PC B, and PC C for each pod.
  5. On the left side of your screen click on the PC attached to your Pod which you would like to access
  6. On the "Summary" tab for the PC click the "Launch Web Console" link in the upper left.
  7. A new tab will open in your browser. 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 "cisco" to log in.
  8. You should be able to use the PC as normal, setting the IP, etc.
  9. These systems do not have Internet access, they are only connected to the network devices in your pod. Any additional files you need to complete your lab on the PC should already be loaded onto the PC in the "C:\CCNA Security VM Files" directory.