- Collapse
-
Right-click the icon for S1, choose Delete, and confirm Yes.
-
Open the All Devices view.
-
Choose the VPCS option and drag a new VPC to the former location of S1.
It will probably have the name PC3. -
Link PC3 to SW1, in the same Ethernet slot (on SW1) that S1 was previously connected. If needed, see similar steps in Lab #7 to refresh your memory.
NOTE: In subsequent pictures below, you may still see S1, so just know that it is now PC3!
- Collapse
-
Press Ctrl-A (or choose "Select All" from the Edit menu, and drag your topology to the center of your screen
-
Open the All Devices view.
-
Choose the Cloud option and drag a new cloud to the left of R1.
It will probably have the name Cloud 1. -
Open up the Windows command line utility, enter the command ipconfig, and look for an entry that looks like this, with an IP address of 10.0.0.240 :
Ethernet adapter ____________: Connection-specific DNS Suffix . : Link-local IPv6 Address . . . . . : fd99:9a7c:ee50::/48 IPv4 Address. . . . . . . . . . . : 10.0.0.240 Subnet Mask . . . . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . . . . :
(NOTE: 10.0.0.240 will be the IP address to look for on it21. For it22, it23, etc. -- look for 241, 242, etc.)
Make a note of the adapter name you see in the blank. - Right click on Cloud 1 and select Configure.
-
Click Add, followed by OK:
- Link Cloud 1 to R1, in the slot FastEthernet0/0. If needed, see similar steps in Lab #7 to refresh your memory.
- Collapse
- Right click on R1 and select Configure.
- On the Advanced tab, change the Base MAC value to c403.1d2x.0y00 -- replacing "2x" with the number for your physical machine and "y" with your section number (1 or 3). Example below is for workstation it28 and Section 3
- Click OK.
- Collapse
Go to the toolbar at the top of your application (just under the menu bar) and click the right-pointing green arrow, which will "Start/resume all devices":
Now that they are "on", we can work with them.
- Collapse
- You need not worry about Cloud 1, as it is primarily a logical entity representing a bridge to your physical machine's Ethernet adapter.
- Start with PC1. Right click on its icon and choose Console...
...which will give you a user interface like this:
- Do the following (and write about it in your admin log):
Type ip 192.168.2x.101/24 192.168.2x.1 at the command prompt and press Enter. (Replace "2x" with the number for your physical machine.) Next, type ip dns 10.0.0.1 and press Enter. Then, type show ip and press Enter.What happens when you do this?
- Leave the console for PC1 open, and start up separate consoles for PC2 and PC3:
- At PC2: Type ip 192.168.2x.102/24 192.168.2x.1 at the command prompt and press Enter.
- At PC3: Type ip 192.168.2x.103/24 192.168.2x.1 at the command prompt and press Enter.
- Use the commands ip dns 10.0.0.1 and show ip for both PC2 and PC3.
- Try some pings back and forth to confirm that PCs 1-3 can interact with each other.
- Start a console for R1 . Because the command-line interface to the router is different, we will need more specialized steps...
- CollapseEnter these commands provided below, paying some attention to changes in the command prompt and the output given.
configure terminal
int fa0/1
ip address 192.168.2x.1 255.255.255.0
no shut
exit (Back to previous prompt)
int fa0/0
ip address dhcp
no shut
exit (Back to previous prompt)
ip name-server 10.0.0.1
exit (Back to previous prompt)What happens when you go through these commands?Try the command show ip interface brief again and see what happens this time.- CollapseWhat (if anything) changed, and why?
What IP address are you getting for each Ethernet interface?
Try some pings back and forth to confirm that R1 can interact with other devices with addresses starting with 192.168.2x.
At this point, you have four networking devices connected by a switch -- your three virtual PCs and a virtual router. Each device (R1, only FastEthernet0/1) should have an IP address starting with 192.168.2x -- which tells you that they are on a (virtual) LAN of their very own. Using the connected devices' associated network addresses (i.e., IP addresses), see if you can make them ping one another back and forth.
- Collapse- Collapse
NOTE: To do this part, you will need to have read Chapter 7, Sections 4 and 5, closely enough to be somewhat familiar with their contents.
- If you are not already working in Privileged Mode, change to that mode.
- How do you know if you are in User Mode or Privileged Mode?
- How did you (or would you) change from the former mode to the latter?
- Type show flash at the command prompt and press Enter.
- What information does this give you? (Not the specific output, but rather, what is the output telling you about the router?)
- Find out how long the router has been up.
- What command do you use to find this out?
- How long has the router been up?
- What version of the Cisco operating system is the router using?
- Look at the previous entries on the router. Also, try out the up and down arrow keys at the command line.
- What command do you use to do this?
- How long has the router been up?
- What happens on pressing the up and down arrows?
- Your router's current hostname is R1. Change the hostname to r2x-0y -- replacing "2x" with the number for your physical machine and "y" with your section number (1 or 3).
- What command (or command sequence) do you use to do this?
- Set the following for your router:
enable secret r2x-0y console password r2x-0y vty password r2x-0y - What command (or command sequence) do you use to do each of these?
