CCENT L A B GUIDE 1 -3

Interconnecting Cisco Network Devices

version 3.0

DAVID
DAVID
BOMBAL
BOMBAL
David Bombal CCNA Lab Lab 1.3

CCENT Lab 1-3 Troubleshooting Switch Media

Issues
In these tasks, you will apply a troubleshooting methodology to determine the source
of the connectivity issue. You will then correct the issues to complete the activity

Task 1: Initial Lab setup

Task 2: Troubleshoot Connectivity between PC1 and SW1

Task 3: Troubleshoot Connectivity between Switch SW1 and the Branch Router

Task 4: Can You Complete the Assessment Lab

om
Visual Objective: Troubleshooting Switch Media Issues

l.c
ba Troubleshooting Task 2
om

Troubleshooting Task 1
db
vi
da

Rev 1.0.1 L1.3-1

David Bombal CCNA Lab Lab 1.3

NOTE: The following table of commands is reference only. Do not try to type them all
in your lab now. Follow the steps after the table.

Command List Useful Shortcut Description

Command

>enable >en Activates privilege exec

mode

#show running- #sh run Displays the current

config configuration in RAM

om
#show interface #sh int status Displays the current
status Switch interface status

#show ip interface #sh ip int brief Displays the current IP

l.c
brief interface status
#show interface #sh int f0/2 Displays the current
ba
FastEthernet 0/2 interface statistics
#show running- #sh run Displays the current
om

config configuration in RAM

#configure terminal #conf t Activates configuration

Mode from the terminal
db

(config)#interface (config)#int f0/2 Enter interface figuration

f0/2 mode
vi

(config-if)#no shut (config-if)#no sh Enables the interface

da

(config-if)#speed Sets the speed for the

‘10/100/1000’ interface

(config-if)#duplex Sets the duplex for the

‘auto/full/half interface

(config-if)#end (config-if)#^Z Ends any configuration

(ctrl +Z) mode or sub-mode and
Returns the prompt to
privileged exec #
#ping ‘ip-address’ Uses icmp echo-request
and echo-replies to
determine connectivity
exists

Rev 1.0.1 L1.3-2

David Bombal CCNA Lab Lab 1.3

#copy running-config Copies the running (RAM)

startup-config config to Startup-config
SW1#copy run start (NVRAM)
#? Help may be requested at
any point in a command
by entering a question
mark '?'.

If nothing matches, the

help list will be empty and
you must backup until
entering a '?' shows the
available options.

om
l.c
Task 1: Initial Lab setup ba
In order to successfully complete this lab exercise, open the Packet Tracer file
‘CCENT Lab 1-3 Troubleshooting Switch Media Issues.pkt’
om

Task 2: Troubleshoot Connectivity between PC1 and SW1.

Problem Report: Jennifer has called you to say that her company user PC’s has no
db

network connectivity. She thinks someone has disconnected her from the network.
All the senior network engineers are out at lunch and you are the only one who can
possibly solve the problem right now. You only have access to SW1, but only via a
vi

local console connection.

da

Try to determine if you can ping from SW1 to Jennifer’s PC IP address (10.1.1.100)
to verify connectivity exists.

Step 1: Access SW1 console and test connectivity to PC1

SW1> enable

SW1# ping 10.1.1.100

Type escape sequence to abort.

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

Rev 1.0.1 L1.3-3

David Bombal CCNA Lab Lab 1.3

Therefore, you have confirmed that there is indeed a problem in the network for
Jennifer.

Step 2: Using the appropriate show commands discover what the status of
the interface, which connects to Jennifer's PC1

Remember to use the ? If you need help with commands and the TAB key to auto-
complete commands

SW1# sh int status

Port Name Status Vlan Duplex Speed Type

om
Fa0/1 disabled 1 auto auto 10/100BaseTX

Fa0/2 notconnected1 a-half a-100 10/100BaseTX

l.c
Fa0/3 connected 1 auto auto 10/100BaseTX

Fa0/4 notconnect 1 auto auto 10/100BaseTX

ba
Fa0/5 notconnect 1 auto auto 10/100BaseTX
om

Fa0/6 notconnect 1 auto auto 10/100BaseTX

~output ommitted~

Gi0/1 notconnect 1 auto auto Not Present

db

Gi0/2 notconnect 1 auto auto Not Present

SW1> enable
vi

SW1# ping 10.1.1.100

da

Type escape sequence to abort.

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

In this case, everything looks fine from the SW1 output. F0/1 is connected, but you
cannot ping Jennifer’s PC1 address of 10.1.1.100. The PC is directly connected on
F0/1.

Rev 1.0.1 L1.3-4

David Bombal CCNA Lab Lab 1.3

Step 3: Double-check with Jennifer that her PC address is correct. You ask Jennifer
to verify the PC IP Address by asking her to confirm the IP settings – She confirms
the settings as follows:

IP Address: 10.1.1.100
Subnet Mask: 255.255.255.0
Default-Gateway: 10.1.1.1

Once again, everything looks ok… What else could it be?

Step 4: You decide to test connectivity to other devices on the network to see if it is
just a local problem for Jennifer.

From the SW1 console, you test connectivity to SW2 and PC2:

om
SW1# ping 10.1.1.12

Type escape sequence to abort.

l.c
Sending 5, 100-byte ICMP Echos to 10.1.1.12, timeout is 2 seconds:
.....
Success rate is 0 percent (0/5)
ba
SW1# ping 10.1.1.101
om

Type escape sequence to abort.

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

Obviously, another problem is affecting your troubleshooting, as you cannot ping

vi

SW2, which is directly connected to SW1 or PC2 either.

da

Step 5: You decide to double-check that everything is ok on SW1, remembering that

you accessed SW1 from the console, you decide to check that SW1 IP Addressing is
fine. From SW1, using the appropriate verification command, you check the status of
the management interface.

SW1# sh int vlan 1

Vlan1 is administratively down, line protocol is down
Hardware is CPU Interface, address is 000b.be2b.27d6 (bia
000b.be2b.27d6)
Internet address is 10.1.1.11/24
MTU 1500 bytes, BW 100000 Kbit, DLY 1000000 usec,
--ommitted--

Rev 1.0.1 L1.3-5

David Bombal CCNA Lab Lab 1.3

What does the interface status mean on SW1?

Step 6: Now you have isolated an indirect problem, correct the issue with the
appropriate commands so you can continue to troubleshoot the issue with Jennifer’s
connection to the network.

SW1# conf t

SW1(config)# int vlan 1

SW1(config-if)# no shut

%LINK-5-CHANGED: Interface Vlan1, changed state to up

%LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan1,
changed state to up

SW1(config-if)# end

om
Step 7: Repeat the tests from SW1 to see what connectivity has been restored.

SW1# ping 10.1.1.12

l.c
ba
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.1.1.12, timeout is 2
om

seconds:
..!!!
Success rate is 60 percent (3/5), round-trip min/avg/max =
0/1/5 ms
db

SW1# ping 10.1.1.101

vi

Type escape sequence to abort.

Sending 5, 100-byte ICMP Echos to 10.1.1.101, timeout is 2
da

seconds:
.!!!!
Success rate is 80 percent (4/5), round-trip min/avg/max =
0/0/2 ms

SW1# ping 10.1.1.100

Type escape sequence to abort.

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

Rev 1.0.1 L1.3-6

David Bombal CCNA Lab Lab 1.3

Step 8: OK – you can now ping SW2 (10.1.1.12) and PC2 (10.1.1.101), but you still
cannot ping Jennifer’s PC (10.1.1.100). There has to be a local problem between
PC1 and the Port on SW1.

Investigate SW1 a little deeper to see if there could be anything preventing

connectivity. Using the ‘interface’ may provide more information than just the ‘show
int status’ has done so far

SW1# sh int f0/1

FastEthernet0/1 is administratively down, line protocol is
down (disabled)
Hardware is Lance, address is 00d0.bc68.1301 (bia
00d0.bc68.1301)
Description: to PC1
BW 100000 Kbit, DLY 1000 usec,

om
reliability 255/255, txload 1/255, rxload 1/255

Step 9: That is strange – the show interface output confirmed that the interface is

l.c
disabled, but the ‘show interface status’ command showed that the interface was
connected in Step 2 above. In this case, it appears to be a failure of Packet Tracer to
ba
report properly with the ‘show interface status’, but this could also be a result of a
‘bug’ in the operating system. Now you have isolated the problem with PC1, correct
the issue with the appropriate commands in order to get Jennifer’s PC connection to
om

the network working again.

SW1# conf t
db

SW1(config)# int f0/1

SW1(config-if)# no shut
vi

%LINK-5-CHANGED: Interface Vlan1, changed state to up

da

%LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan1,

changed state to up

SW1(config-if)#end

Rev 1.0.1 L1.3-7

David Bombal CCNA Lab Lab 1.3

Step 10: Verify connectivity with PC1 by pinging PC1 IP Address (don’t worry too
much if the first ping times out – This is normal operation for Spanning-Tree Protocol
operations. There are default timers that the switch waits for before allowing data to
go through the ports - just repeat the ping again if this happens and you should be
successful after 30 seconds.)

SW1# ping 10.1.1.100

Type escape sequence to abort.

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

om
Verify connectivity with PC1 by pinging PC1 IP address again – It should now be
successful:

l.c
SW1# ping 10.1.1.100
ba
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.1.1.100, timeout is 2
seconds:
!!!!!
om

Success rate is 100 percent (5/5), round-trip min/avg/max =

1/2/9 ms
db

Step 11: Now you have verified that the network is functioning properly again, save
vi

the working configuration.

da

SW1# copy run start

Destination filename [startup-config]?

Building configuration...
[OK]

Rev 1.0.1 L1.3-8

David Bombal CCNA Lab Lab 1.3

Task 3: Troubleshoot Connectivity between Switch SW1 and the

Branch Router
Problem Report: Your colleague calls to inform you that they noticed some duplex
mismatch errors coming from SW1 logging output on the monitoring server and they
were unable to prevent the messages. The senior network engineer has left you to
resolve the issue! Your colleague emails you with an example of the output being
received on the logging server that he wishes you to fix. He also informs you that the
messages have not been received in the last 10 minutes, but would still like you to
look it.
‘%CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on
FastEthernet0/2 (not full duplex), with Branch FastEthernet0/0 (full
duplex)’

Step 1: Using the appropriate show commands from the command list section,
identify the status of the FastEthernet 0/2 port, which connects from SW1 to the

om
Branch router

l.c
On SW1 verify the interface status:

SW1# sh int status

ba
Port Name Status Vlan Duplex Speed Type

Fa0/1 connected 1 a-full a-100 10/100BaseTX

om

Fa0/2 notconnected 1 a-half a-100 10/100BaseTX

db

Initially, all looks Ok. However, remember the show int status command may not
be completely trustworthy on Packet Tracer!
vi
da

Step 2: On the Branch router, verify the interface status

Branch> en

Branch# sh ip int brief

Interface IP-Address OK? Method Status Protocol

GigabitEthernet0/0 10.1.1.1 YES manual up down

GigabitEthernet0/1 unassigned YES TFTP administratively down down

Serial0/1/0 unassigned YES TFTP administratively down down

Serial0/1/1 unassigned YES NVRAMadministratively down down

--ommitted--

Rev 1.0.1 L1.3-9

David Bombal CCNA Lab Lab 1.3

You observe that the Line status is UP, but the Line protocol is DOWN – There is a
connection problem. That would explain why the log messages had stopped
reaching the logging server – the connection is down for some reason.

Step 3: From the Branch router console session, verify the interface and observe the
output.

Branch# sh int g0/0

GigabitEthernet0/0 is up, line protocol is down (disabled)
Hardware is CN Gigabit Ethernet, address is 00e0.f702.1e01 (bia
00e0.f702.1e01)
Internet address is 10.1.1.1/24

om
MTU 1500 bytes, BW 1000000 Kbit, DLY 100 usec,
reliability 255/255, txload 1/255, rxload 1/255

l.c
Encapsulation ARPA, loopback not set
Keepalive set (10 sec)
ba
Full-duplex, 100Mb/s, media type is RJ45
output flow-control is unsupported, input flow-control is
unsupported
om

---output omitted---
db

You confirm that the router’s interface is UP, but the line protocol is DOWN. You also
know that it is policy to have speed and duplex settings manually configured for
vi

networking devices. From the discovered output on the Branch router, you observe
that the setting are manually configured to match SW1 capability as a 10/100
da

FastEthernet interface. However, do these match on SW1?

Rev 1.0.1 L1.3-10

David Bombal CCNA Lab Lab 1.3

Step 4: Go back to the console session with SW1. Verify the interface settings using
the below appropriate commands.

SW1# sh int f0/2

FastEthernet0/2 is down, line protocol is down (disabled)
Hardware is Lance, address is 00d0.bc68.1302 (bia 00d0.bc68.1302)
Description: to Branch Router
BW 100000 Kbit, DLY 1000 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA, loopback not set
Keepalive set (10 sec)
Half-duplex, 100Mb/s

om
The connection on SW1 is seen as DOWN, DOWN.

l.c
SW1# sh run | begin 0/2
interface FastEthernet0/2
ba
description to Branch Router
duplex half
speed 100
!
om

interface FastEthernet0/3
description to SW2
!
--Output omitted--
db
vi

The interface settings are mismatched, and in this case bringing the interface down.
da

Rev 1.0.1 L1.3-11

David Bombal CCNA Lab Lab 1.3

Step 5: Correct the identified issue. Observe the log messages on both SW1 and the
Branch router as you change the duplex setting. Do not forget to save your
configuration at the end.

SW1# conf t

Enter configuration commands, one per line. End with CNTL/Z.

SW1(config)# int f0/2

SW1(config-if)# duplex full

%LINK-5-CHANGED: Interface FastEthernet0/2, changed state to up

%LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/2,
changed state to up

SW1(config-if)# end

om
SW1# copy run start

l.c
ba
Did you know?

It is considered a best practice to manually configure speed and duplex

om

settings between network ‘infrastructure’ devices, leaving the auto

negotiation protocol to achieve the best setting facing end user devices.
db
vi
da

Rev 1.0.1 L1.3-12

David Bombal CCNA Lab Lab 1.3

Task 4: Can You Complete the Assessment Lab?

Open the assessment file:

CCENT Lab 1-3 Troubleshooting Switch Media Issues PTSA.pka

Troubleshoot Switch Connectivity Issues

Problem Report No.1: Jennifer has called you to say that her company user PC’s
has no network connectivity. She thinks someone has disconnected her from the
network. All the senior network engineers are out at lunch and you are the only one
who can possibly solve the problem right now. You only have access to SW1, but
only via a local console connection.

om
Problem Report No.2: Your colleague calls to inform you that they noticed some
duplex mismatch errors coming from SW1 logging output on the monitoring server
and they were unable to prevent the messages. The senior network engineer has left
you to resolve the issue! Your colleague emails you with an example of the output

l.c
received on the logging server that he wishes you to fix. He also informs you that the
messages have not been received in the last 10 minutes, but would still like you to
look it.
ba
‘%CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on
FastEthernet0/2 (not full duplex), with Branch FastEthernet0/0 (full
om

duplex)’

Your objective is to restore connectivity so that SW1 can ping all network
devices.
db
vi

Activity Verification
da

You have completed this task when you obtain these results:

1. You identified and corrected the problem between PC1 and SW1

2. You identified and corrected the problem between SW1 and the Branch
Router

Rev 1.0.1 L1.3-13