3808ICT Routing and Internetworking
Practice Network Troubleshooting Assessment – Answer
Tips on Network Troubleshooting
Here are some tips and a suggestion on how to systematically troubleshoot a network.
1. When solving a ticket, students will first make some changes to the network configuration before
checking if the ticket has been solved via some ping test for example.
However the network may take some time to re-converge, in particular after a change to its VLAN
settings. So a ping test may not necessarily work if it’s done immediately after a change to the
VLAN settings.
In Packet Tracer, there is a Fast Forward button on the bottom left of the workspace that can be
pressed to speed up the network convergence process. It is recommended that students press this
button first before attempting any ping tests.
2. If an attempt to solve a ticket does not work (e.g. the ping test still fails), it is recommended to
remove the changes that were made to the network configuration (in the attempt to solve the ticket).
To remove any changes made, use the “no” command.
If the changes were not removed, this may potentially add more errors into the network
configuration.
3. Here is a suggestion on how to systematically troubleshoot a ticket. Using Ticket #2 in the
Practice Troubleshooting as an example, PC2 cannot SSH to S2:
– We need to first identify the path that the SSH packet will take to travel from PC2 to S2, and
from S2 back to PC2. Network communication is normally a request-response type of
communication, so we need to consider the path that the request packet takes from PC2 to S2,
and the path that the response packet takes from S2 back to PC2.
– Since PC2 and S2 are on different VLANs, this means Inter-VLAN routing is involved.
– The path that the request packet takes from PC2 to S2 is
PC2 S1 HQ S1 S2
– The path that the response packet takes from S2 to PC2 is
S2 S1 HQ S1 PC2
– For the path that the request packet takes from PC2 to S2, we then check each device on that
path to determine if their configuration is correct. For example,
o PC2 – check that its IP address, subnet mask, gateway information is correct
o S1
Check that F0/15 is correctly configured as an access port for VLAN 20, the
F0/15 port is “up up”.
Check that F0/5 port is correctly configured as a trunk, native VLAN correctly
configured for VLAN 1000, allowed VLANs correctly configured as
10,20,99,1000.
o HQ
Check that the subinterface G0/1.20 is correctly configured with its VLAN ID, IP
address, subnet mask.
Check that the subinterface G0/1.99 is correctly configured with its VLAN ID, IP
address, subnet mask.
Check that the parent interface G0/1 is “up up”.
o S1
Check that VLAN 99 is configured
Check that the EtherChannel is correctly configured, is configured as a trunk,
native VLAN correctly configured for VLAN 1000, allowed VLANs correctly
configured as 10,20,99,1000.
o S2
Check that the EtherChannel is correctly configured, is configured as a trunk,
native VLAN correctly configured for VLAN 1000, allowed VLANs correctly
configured as 10,20,99,1000.
Check that VLAN 99 is configured
Check that S2’s VLAN 99 SVI interface is correctly configured with its IP
address, subnet mask, gateway information.
– Do the same for each device on the path that the response packet takes from S2 to PC2.
– If a potential error is identified on a device, try to correct that error and test to verify that the
ticket is now solved.
– If the ticket is not solved (i.e. in this example PC2 still cannot SSH to S2), then this means the
potential error was wrongly identified. Any changes made to the network configuration (for this
ticket) must be removed in order to avoid adding new errors into the network configuration.
Continue checking on the next item on this device, or move on to the next device.
– If the ticket is solved, write down the answers, and then move on to the next ticket.
| Tickets | Root cause of error and on which Device(s) |
List Command(s) used to Troubleshoot the error and on which Device(s) [An answer of show run will not be accepted] |
List Command(s) to correct the error and on which Device(s) |
| Ticket 1 | |||
| PC1 cannot ping PC3. |
S2: Trunk port Po1 doesn’t allow traffic from VLAN 10. It’s allowing traffic from VLANs 1,20,99,1000 instead of VLANs 10,20,99,1000. |
S2: show int trunk |
S2: int po1 switchport trunk allowed vlan 10,20,99,1000 |
| Ticket 2 | |||
| PC2 cannot SSH to S2. |
HQ: Interface g0/1.99 has the wrong subnet mask 255.255.255.252 instead of 255.255.255.0. |
HQ: show ip int g0/1.99 or show int g0/1.99 |
HQ: int g0/1.99 ip address 192.168.99.1 255.255.255.0 |
| Ticket 3 | |||
| PC4 cannot ping ISP’s Lo1 interface on IPv4. |
BRANCH: There is no IPv4 default route on BRANCH. Instead it has a wrong summarized static route to 192.168.0.0/16. |
BRANCH: show ip route |
BRANCH: no ip route 192.168.0.0 255.255.0.0 ip route 0.0.0.0 0.0.0.0 192.168.1.1 |
| Ticket 4 | |||
| PC4 cannot ping PC1 on IPv6. |
HQ: There is no IPv6 static route to the 2001:DAB:ACAD:2::/64 network |
HQ: show ipv6 route |
HQ: ipv6 route 2001:DAB:ACAD:2::/64 2001:DAB:ACAD:1::2 |
| Ticket 5 | |||
| PC1 cannot ping ISP’s Lo1 interface on IPv6. |
ISP: A wrong summary static route to 2001:DAB:ACAD::/62 is configured, instead of 2001:DAB:ACAD::/58. |
ISP: show ipv6 route |
ISP: no ipv6 route 2001:DAB:ACAD::/62 ipv6 route 2001:DAB:ACAD::/58 s0/0/0 ipv6 route 2001:DAB:ACAD::/58 s0/0/1 80 |
The post 3808ICT Routing and Internetworking appeared first on My Assignment Online.