Experiment-1

Aim: Study of different types of Network cables and practically implement the cross-wired cable
and straight through cable using clamping tool.

Apparatus (Components): RJ-45 connector Crimping Tool, Twisted pair Cable

Procedure: To do these practical following steps should be done:

1. Start by stripping off about 2 inches of the plastic jacket off the end of the cable. Be very careful
at this point, as to not nick or cut into the wires, which are inside. Doing so could alter the
characteristics of your cable, or even worse render is useless. Check the wires, one more time for
nicks or cuts. If there are any, just whack the whole end off, and start over.

2. Spread the wires apart but be sure to hold onto the base of the jacket with your other hand. You
do not want the wires to become untwisted down inside the jacket. Category 5 cable must only
have 1/2 of an inch of 'untwisted' wire at the end; otherwise it will be 'out of spec'. At this point,
you obviously have ALOT more than 1/2 of an inch of un-twisted wire.

3. You have 2 end jacks, which must be installed on your cable. If you are using a pre-made cable,
with one of the ends whacked off, you only have one end to install - the crossed over end. Below
are two diagrams, which show how you need to arrange the cables for each type of cable end.
Decide at this point which end you are making and examine the associated picture below.

Diagram shows you how to prepare Cross wired connection

LUVKY PANCHAL2200321539008
1
 Diagram shows you how to prepare straight through wired connection

LUVKY PANCHAL2200321539008
2
 Experiment-2

Aim: Performing basic end device and switch configuration.

Topology Diagram

Objectives
Perform an initial configuration of a Cisco Catalyst 2960 switch.

Background / Preparation
In this activity, you will configure these settings on the customer Cisco Catalyst 2960 switch:
Host name
Console password
vty password
Privileged EXEC mode password
Privileged EXEC mode secret
IP address on VLAN1 interface
Default gateway
Note: Not all commands are graded by Packet Tracer.

Step 1: Configure the switch host name.

a. From the Customer PC, use a console cable and terminal emulation software to connect to the
console of the customer Cisco Catalyst 2960 switch.
b. Set the host name on the switch to CustomerSwitch using these commands.

Switch>enable
Switch#configure terminal

LUVKY PANCHAL2200321539008
3
 Switch(config)#hostname CustomerSwitch

Step 2: Configure the privileged mode password and secret.

a. From global configuration mode, configure the password as cisco.

CustomerSwitch(config)#enable password cisco

b. From global configuration mode, configure the secret as cisco123.

CustomerSwitch(config)#enable secret cisco123

Step 3: Configure the console password.

a. From global configuration mode, switch to configuration mode to configure the console
line. CustomerSwitch(config)#line console 0

b. From line configuration mode, set the password to cisco and require the password to be entered
at login.

CustomerSwitch(config-line)#password cisco
CustomerSwitch(config-line)#login
CustomerSwitch(config-line)#exit

Step 4: Configure the vty password.

a. From global configuration mode, switch to the configuration mode for the vty lines 0 through 15.

CustomerSwitch(config)#line vty 0 15

b. From line configuration mode, set the password to cisco and require the password to be entered
at login.

CustomerSwitch(config-line)#password cisco
CustomerSwitch(config-line)#login
CustomerSwitch(config-line)#exit

Step 5: Configure an IP address on interface VLAN1.

From global configuration mode, switch to interface configuration mode for VLAN1, and assign the IP
address 192.168.1.5 with the subnet mask of 255.255.255.0.

CustomerSwitch(config)#interface vlan
1CustomerSwitch(config-if)#ip address 192.168.1.5
255.255.255.0CustomerSwitch(config-if)#no
shutdownCustomerSwitch(config-if)#exit

Step 6: Configure the default gateway.

a. From global configuration mode, assign the default gateway to 192.168.1.1.

CustomerSwitch(config)#ip default-gateway 192.168.1.1

LUVKY PANCHAL2200321539008
4
 b. Click the Check Results button at the bottom of this instruction window to check your work.

Step 7: Verify the configuration.

The Customer Switch should now be able to ping the ISP Server at 209.165.201.10. The first one or two
pings may fail while ARP converges.

CustomerSwitch(config)#end
CustomerSwitch#ping 209.165.201.10

Type escape sequence to abort.

Sending 5, 100-byte ICMP Echos to 209.165.201.10, timeout is 2 seconds:
..!!!
Success rate is 60 percent (3/5), round-trip min/avg/max = 181/189/197 ms

CustomerSwitch#

Reflection
a. What is the significance of assigning the IP address to the VLAN1 interface instead of any of the
Fast Ethernet interfaces?

b. What command is necessary to enforce password authentication on the console and vty lines?

c. How many gigabit ports are available on the Cisco Catalyst 2960 switch that you used in the activity?

Output

LUVKY PANCHAL2200321539008
5
 Experiment-3

Aim: Configure Initial Router Settings

Topology Diagram

Use this syntax checker to practice configuring the initial settings on a router.

 Configure the device name.

 Secure the privileged EXEC mode.
 Secure and enable remote SSH and Telnet access.
 Secure all plaintext passwords.
 Provide legal notification.

The following tasks should be completed when configuring initial settings on a router.

1. Configure the device name.

Router(config)# hostnamehostname

2. Secure privileged EXEC mode.

Router(config)# enable secretpassword

3. Secure user EXEC mode.

Router(config)# line console 0

Router(config-line)#passwordpassword
Router(config-line)# login

4. Secure remote Telnet / SSH access.

Router(config-line)#line vty 0 4
Router(config-line)# password password
Router(config-line)# login
Router(config-line)# transport input {ssh | telnet}

LUVKY PANCHAL2200321539008
6
 5. Secure all passwords in the config file.

Router(config-line)#exit
Router(config)# service password-encryption

6. Provide legal notification.

Router(config)# banner motddelimiter message delimiter

7. Save the configuration.

Router(config)# end
Router# copy running-config startup-config

Part 1: Configure Router Interfaces

At this point, your routers have their basic configurations. The next step is to configure their interfaces.
This is because routers are not reachable by end devices until the interfaces are configured. There are many
different types of interfaces available on Cisco routers. For example, the Cisco ISR 4321 router is equipped
with two Gigabit Ethernet interfaces:

 GigabitEthernet 0/0/0 (G0/0/0)

 GigabitEthernet 0/0/1 (G0/0/1)

The task to configure a router interface is very similar to a management SVI on a switch. Specifically, it
includes issuing the following commands:

Router(config)# interfacetype-and-number
Router(config-if)#descriptiondescription-text
Router(config-if)# ip addressipv4-address subnet-mask
Router(config-if)# ipv6 addressipv6-address/prefix-length
Router(config-if)# no shutdown

the description command would be helpful to enter the third-party connection and contact information.
no shutdown command activates the interface and is similar to powering on the interface.

R1>enable

 R1# configure terminal

Enter configuration commands, one per line.

End with CNTL/Z.

LUVKY PANCHAL2200321539008
7
 R1(config)# interface gigabitEthernet 0/0/0

R1(config-if)#description Link to LAN

R1(config-if)#ip address 192.168.10.1 255.255.255.0

R1(config-if)#ipv6 address 2001:db8:acad:10::1/64

R1(config-if)#no shutdown

R1(config-if)#exit

R1(config)#

*Aug 1 01:43:53.435: %LINK-3-UPDOWN: Interface GigabitEthernet0/0/0, changed state to down

*Aug 1 01:43:56.447: %LINK-3-UPDOWN: Interface GigabitEthernet0/0/0, changed state to up

*Aug 1 01:43:57.447: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/0/0,

changed state to up

R1(config)#

R1(config)#

R1(config)# interface gigabitEthernet 0/0/1

R1(config-if)#description Link to R2

R1(config-if)#ip address 209.165.200.225 255.255.255.252

R1(config-if)#ipv6 address 2001:db8:feed:224::1/64

R1(config-if)#no shutdown

LUVKY PANCHAL2200321539008
8
 R1(config-if)#exit

R1(config)#

*Aug 1 01:46:29.170: %LINK-3-UPDOWN: Interface GigabitEthernet0/0/1, changed state to down

*Aug 1 01:46:32.171: %LINK-3-UPDOWN: Interface GigabitEthernet0/0/1, changed state to up

*Aug 1 01:46:33.171: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/0/1,

changed state to up

R1(config)#

Note: Notice the informational messages informing us that G0/0/0 and G0/0/1 are enabled.

Part 2: Verify Interface Configuration

There are several commands that can be used to verify interface configuration. The most useful of these is
the show ip interface brief and show ipv6 interface brief commands, as shown in the example.

R1# showip interface brief

Interface IP-Address OK? Method Status Protocol

GigabitEthernet0/0/0 192.168.10.1 YES manual up up

GigabitEthernet0/0/1 209.165.200.225 YES manual up up

Vlan1 unassigned YES unset administratively down down

R1# show ipv6 interface brief

GigabitEthernet0/0/0 [up/up]

FE80::201:C9FF:FE89:4501

LUVKY PANCHAL2200321539008
9
 2001:DB8:ACAD:10::1

GigabitEthernet0/0/1 [up/up]

FE80::201:C9FF:FE89:4502

2001:DB8:FEED:224::1

Vlan1 [administratively down/down]

unassigned

R1#

Part 3: Configuration Verification Commands

The table summarizes the more popular show commands used to verify interface configuration.

Table caption

Commands Description

show ip interface The output displays all interfaces, their IP addresses, and their current status.
brief The configured and connected interfaces should display a Status of “up” and
show ipv6 interface Protocol of “up”. Anything else would indicate a problem with either the
brief configuration or the cabling.

show ip route
Displays the contents of the IP routing tables stored in RAM.
show ipv6 route
Displays statistics for all interfaces on the device. However, this command
show interfaces
will only display the IPv4 addressing information.

show ip interfaces Displays the IPv4 statistics for all interfaces on a router.

show ipv6 interface Displays the IPv6 statistics for all interfaces on a router.

R1# show ip interface brief Interface IP-Address OK? Method Status Protocol GigabitEthernet0/0/0
192.168.10.1 YES manual up up GigabitEthernet0/0/1 209.165.200.225 YES manual up up Vlan1
unassigned YES unset administratively down down R1#

LUVKY PANCHAL2200321539008
10
 output

LUVKY PANCHAL2200321539008
11
 Experiment-4
Aim: Interpreting Ping and Traceroute Output

Topology Diagram

Objectives
 Distinguish the difference between successful and unsuccessful ping attempts.
 Distinguish the difference between successful and unsuccessful traceroute attempts.

Background / Preparation
In this activity, you will test end-to-end connectivity using ping and traceroute. At the end of this activity, you will
be able to distinguish the difference between successful and unsuccessful ping and traceroute attempts.
Note: Before beginning this activity, make sure that the network is converged. To converge the
networkquickly, switch between Simulation mode and Realtime mode until all the link lights turn green.

Step 1: Test connectivity using ping from a host computer and a router.
Click N-Host, click the Desktop tab, and then click Command Prompt. From the Command Prompt window, ping
the Cisco server at www.cisco.com.
Packet Tracer PC Command Line 1.0
PC>ping www.cisco.com

Pinging 64.100.1.185 with 32 bytes of data:

Request timed out.

LUVKY PANCHAL2200321539008
12
 Reply from 64.100.1.185: bytes=32 time=185ms TTL=123
Reply from 64.100.1.185: bytes=32 time=281ms TTL=123
Reply from 64.100.1.185: bytes=32 time=287ms TTL=123

Ping statistics for 64.100.1.185:

Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
Minimum = 185ms, Maximum = 287ms, Average = 251ms

PC>

From the output, you can see that N-Host was able to obtain an IP address for the Cisco server. The IP address was
obtained using (DNS). Also notice that the first ping failed. This failure is most likely due to lack of ARP
convergence between the source and destination. If you repeat the ping, you will notice that all pings succeed.
From the Command Prompt window on N-Host, ping E-Host at 192.168.4.10. The pings fail. If you do not want to
wait for all four unsuccessful ping attempts, press Ctrl+C to abort the command, as shown below.
PC>ping 192.168.4.10

Pinging 192.168.4.10 with 32 bytes of data:

Request timed out.

Request timed out.

Ping statistics for 192.168.4.10:

Packets: Sent = 3, Received = 0, Lost = 3 (100% loss),

Control-C
^C
PC>

Click the N-Branch router, and then click the CLI tab. Press Enter to get the router prompt. From the router prompt,
ping the Cisco server at www.cisco.com.
N-Branch>ping www.cisco.com
Translating "www.cisco.com"...domain server (64.100.1.242)
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 64.100.1.185, timeout is 2 seconds:
.!!!!
Success rate is 80 percent (4/5), round-trip min/avg/max = 210/211/213 ms

N-Branch>

As you can see, the ping output on a router is different from a PC host. Notice that the N-Branch router resolved the
domain name to the same IP address that N-Host used to send its pings. Also notice that the first ping fails, which is
indicated by a period (.), and that the next four pings succeed, as shown with an exclamation point (!).
From the CLI tab on N-Branch, ping E-Host at 192.168.4.10. Again, the pings fail. To not wait for all the
failures, press Ctrl+C.
N-Branch>ping 192.168.4.10

Type escape sequence to abort.

Sending 5, 100-byte ICMP Echos to 192.168.4.10, timeout is 2 seconds:
...
Success rate is 0 percent (0/4)

N-Branch>

LUVKY PANCHAL2200321539008
13
 Step 2: Test connectivity using traceroute from a host computer and a router.
a. Click N-Host, click the Desktop tab, and then click Command Prompt. From the Command
Prompt window, trace the route to the Cisco server at www.cisco.com.

PC>tracert www.cisco.com

Tracing route to 64.100.1.185 over a maximum of 30 hops:

1 92 ms 77 ms 86 ms 192.168.1.1
2 91 ms 164 ms 84 ms 64.100.1.101
3 135 ms 168 ms 151 ms 64.100.1.6
4 185 ms 261 ms 161 ms 64.100.1.34
5 257 ms 280 ms 224 ms 64.100.1.62
6 310 ms 375 ms 298 ms 64.100.1.185

Trace complete.

PC>

The above output shows that you can successfully trace a route all the way to the Cisco server at 64.100.1.185.
Each hop in the path is a router responding three times to trace messages from N-Host. The trace continues until the
destination for the trace (64.100.1.185) responds three times.
From the Command Prompt window on N-Host, trace a route to E-Host at 192.168.4.10. The trace fails, but notice
that the tracert command traces up to 30 hops. If you do not want to wait for all 30 attempts to time out, press
Ctrl+C.

PC>tracert 192.168.4.10

Tracing route to 192.168.4.10 over a maximum of 30 hops:

1103 ms 45 ms 91 ms 192.168.1.1
256 ms 110 ms 125 ms 64.100.1.101
3174 ms 195 ms 134 ms 64.100.1.6
4246 ms 183 ms 179 ms 64.100.1.34
5217 ms 285 ms 226 ms 64.100.1.62
6246 ms 276 ms 245 ms 64.100.1.154
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10
Control-C
^C
PC>

The tracert command can be helpful in finding the potential source of a problem. The last device to
respond was 64.100.1.154, so you would start troubleshooting by determining which device is
configured with the IP address 64.100.1.154. The source of the problem might not be that device,
but the trace has given you a starting point, whereas a ping simply tells you that the destination is
either reachable or unreachable.
Click the N-Branch router, and then click the CLI tab. Press Enter to get the router prompt. From the router prompt,
trace the route to the Cisco server at www.cisco.com.

LUVKY PANCHAL2200321539008
14
 N-Branch>traceroute www.cisco.com
Translating "www.cisco.com"...domain server (64.100.1.242)
Type escape sequence to abort.
Tracing the route to 64.100.1.185

1 64.100.1.101 60 msec 32 msec 59 msec

2 64.100.1.6 98 msec 65 msec 65 msec
3 64.100.1.34 138 msec 147 msec 147 msec
4 64.100.1.62 189 msec 148 msec 145 msec
5 64.100.1.185 219 msec 229 msec 293 msec
N-Branch>

As you can see, traceroute output on a router is very similar to the output on a PC host. The
only difference is that on a PC host, the IP address is listed after the three millisecond outputs.
From the CLI tab on N-Branch, trace the route to E-Host at 192.168.4.10. The trace fails at the same IP address as
it failed when tracing from N-Host. Again, you can use Ctrl+C to abort the command.

N-Branch>traceroute 192.168.4.10
Type escape sequence to abort.
Tracing the route to 192.168.4.10

1 64.100.1.101 41 msec 19 msec 32 msec

2 64.100.1.6 33 msec 92 msec 117 msec
3 64.100.1.34 98 msec 102 msec 102 msec
4 64.100.1.62 166 msec 172 msec 156 msec
5 64.100.1.154 157 msec 223 msec 240 msec
6 * * *
7 * * *
8 * * *
9
N-Branch>

Step 3: Practice the ping and trace route commands.

Throughout this course, you will often use ping and traceroute to test connectivity and troubleshoot problems.
To practice these commands, ping and trace from W-Host and S-Host to any other destination in the network.
You can also ping and trace from N-Branch to other locations.

LUVKY PANCHAL2200321539008
15
LUVKY PANCHAL2200321539008
16
LUVKY PANCHAL2200321539008
17
LUVKY PANCHAL2200321539008
18
LUVKY PANCHAL2200321539008
19
LUVKY PANCHAL2200321539008
20
 Output

LUVKY PANCHAL2200321539008
21
 Output

LUVKY PANCHAL2200321539008
22