Scribd
Upload
18 views40 pages

Activity 3

Uploaded by

ericabelarmino3
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
18 views40 pages

Activity 3

Uploaded by

ericabelarmino3
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 40

CPE529C

COMPUTER NETWORK AND SECURITY

Act # 3: Configuring a Cisco Router


Objectives
1. Perform the lab activity.

2. Answer the inline questions.

3. Perform the supplementary activities.

4. Export the GNS3 project for the lab and supplementary activities
into a .gns3project files (follow naming convention) and upload it
together with the lab document into the Server.
Considerations in using VMWare with GNS3 VM
1. GNS3 VM requires nested virtualization (Intel VT-x or equivalent)
enabled in the BIOS settings.

2. Microsoft Hyper-V and other similar services must be disabled


when using VMWare. Check your computer’s settings.

3. In Windows 10 / 11, you need to disable Memory Isolation in your


computer’s settings.
Let’s all work quietly. Raise your
hand to get my attention.
The Terminal Console
Configure your VMWare’s preference.ini
settings appropriately.

Configure your GNS3 settings to connect


to your designated GNS3 VM.

Create a new GNS3 project.


Add 2 routers
Set the device hostname appropriately and
connect them onto their G0/0 interfaces.
Start the devices
Start the devices
Establish console connection
Wait until the terminal
console log entries stop.

Press the Enter key to engage on the device to show the Router# prompt.
Type the word “exit” then press the Enter key. This
will execute the exit command. What happened to
the terminal console? (Q#1)
Execute the following commands:

configure terminal
line console 0
privilege level 0
end
exit

What is the terminal prompt? (Q#2)


The Console Exec Modes
When the prompt ends in a greater than sign (>), the console
mode is what we call “User Exec Mode”. At this mode, the
privilege level is commonly at zero (0) which limits the
commands that can be executed. This protects the device
from unwanted changes.
Execute the command “enable”.
The prompt changed and ends with a number sign (#).
Therefore, the console mode has changed and is what we call
“Privilege Exec Mode”.

At this mode, this is where we can execute different show


commands to validate the device status, features and
configurations.
Execute the command “show ip interface brief”. Take note the
command output. (Q#3)

Execute the command “show ip route”. Take note the


command output. (Q#4)

Execute the command “configure terminal”. What is the


prompt? (Q#5)
This console mode is what we call “Global Configuration Mode”.

At this mode, you can execute commands that will modify device
settings and configuration. Notice how the prompt is formatted.

Execute the command “hostname R1”. What happened to the


prompt? (Q#6) This command changes the device hostname.
Execute the command “interface GigabitEthernet 0/0”. What
happened to the prompt? (Q#7)

At this mode, you are on a sub-configuration mode. Specifically,


on the interface configuration mode. There are many sub-
configuration modes. It is dependent on the executed
commands within the Global Configuration mode.

Continue with the commands “ip address 192.168.0.1


255.255.255.0” & “no shutdown”. What do you think these
command do? (Q#8)
Execute the “end” command. What happened to the prompt and
at what console mode you are currently at? (Q#9)

Go back again to the interface configuration mode for


GigabitEthernet 0/0. This time, execute the “exit” command.
What happened to the prompt? Differentiate the “exit”
command with the “end” command. (Q#10)
The Device Configurations
Go back to the privilege exec mode and execute the command
“show running-config”.
This command displays the current
running configuration. In Cisco
devices, the active configuration is
called “running config”. The saved
configuration is called “startup config”.

When the output is longer than the window, the output


is paged and the --More-- prompt shown. Press the
Enter key to display the next line. What happens when
you press the Space bar key? (Q#11)
Continue until you reach the end of the running
configuration. Highlight the configuration output to
copy the text into the clipboard. Note the configuration
on your lab report. (Q#12)
Execute the above command. Save the configuration
on the destination file as “startup-config”.

The command “reload” restarts the device. Any


unsaved configurations are erased. The device reboots
and undergoes the startup process and then loads the
startup-config.

Execute the command “show version”. Take note the


command output. (Q#12) What does this show us?
(Q#13)
Execute the command “show ip interface brief” and
take note the output. (Q#14).

Go back to the interface configuration mode for


GigabitEthernet 0/0. Execute the command “no ip
address”. Go back to the privilege exec mode and
execute again “show ip interface brief”. What does the
“no” command do? (Q#15)

Reapply the same ip address back on its GigabitEthernet


0/0 interface.
Configuring Router 2
Configure Router 2 having the following
settings:
1. Hostname as R2.
2. Set the ip address to 192.168.0.2 with subnet mask
of 255.255.255.0 on its GigabitEthernet 0/0
interface.
3. Enable its GigabitEthernet 0/0.
4. Set the console privilege level to 0.
5. Save and note the configuration. (Q#16)
On R2’s console, ping R1’s ip address. Take note the
command output. You should have the same output.
(Q#17)

The exclamation (!) of the ping command indicates


positive result. This means the packet is echoed
properly to the target device.
Supplementary Activity
The Network Design

GigabitEthernet 0/0 GigabitEthernet 0/1


IP: 192.168.12.2 IP: 192.168.23.2
Subnet Mask: Subnet Mask:
255.255.255.0 255.255.255.0

GigabitEthernet 0/0 GigabitEthernet 0/1


IP: 192.168.12.1 IP: 192.168.23.3
Subnet Mask: Subnet Mask:
255.255.255.0 255.255.255.0
Activities
1. Implement the network as shown on the diagram.
2. Set the hostname and IP address of each of its interface(s)
appropriately.
3. From R1, ping R2 on its GigabitEthernet 0/0 interface. Does the
ping command result success? Capture the command output on
your document.
4. From R2, ping R3 on its GigabitEthernet 0/1 interface. Does the
ping command result success? Capture the command output.
5. From R3, ping R1 on its GigabitEthernet 0/0 interface. Does the
ping command result success? Capture the command output.
Activities
6. Apply the following configurations:
a. On R1: ip route 0.0.0.0 0.0.0.0 192.168.12.2
b. On R3: ip route 0.0.0.0 0.0.0.0 192.168.23.2
7. From R1, ping R3 on its GigabitEthernet 0/1 interface. Does the
ping command result success? Capture the command output.
8. From R3, ping R1 on its GigabitEthernet 0/0 interface. Does the
ping command result success? Capture the command output.
Raise your hand so I can check your work,
once you are finish.

Upload your activity files on the Server.

Close GNS3. This will also close VMWare.


Ensure before leaving:

Open %AppData%\VMware and open


preferences.ini file again on a text editor.

Clear the value of prefvmx.defaultVMPath to


empty string value.
END

You might also like