12.6.1 Packet Tracer - Troubleshooting Challenge - Document the Network Answers
Topology
Table of Contents
- Addressing Table
- Instructions
- Reflection
- Network Topology Diagram (Annotated Topology, Device Interconnections)
Addressing Table
| Device | Interface | Device Type (router, switch, host) |
IP Address | Subnet Mask | Default Gateway |
|---|---|---|---|---|---|
| PC1 | NIC | Host | 192.168.1.153 | 255.255.255.0 | 192.168.1.1 |
| PC2 | NIC | Host | 192.168.3.50 | 255.255.255.0 | 192.168.3.1 |
| PC3 | NIC | Host | 192.168.4.115 | 255.255.255.0 | 192.168.4.1 |
| PC4 | NIC | Host | 192.168.5.83 | 255.255.255.128 | 192.168.5.1 |
| PC5 | NIC | Host | 192.168.5.227 | 255.255.255.128 | 192.168.5.129 |
| PC6 | NIC | Host | 192.168.2.48 | 255.255.255.224 | 192.168.2.33 |
| PC7 | NIC | Host | 192.168.2.67 | 255.255.255.224 | 192.168.2.65 |
| Hub | G0/0/0 | router | 192.0.2.1 | 255.255.255.252 | N/A |
| Hub | S0/1/0 | router | 192.168.0.1 | 255.255.255.252 | N/A |
| Hub | S0/1/1 | router | 192.168.0.5 | 255.255.255.252 | N/A |
| Hub | S0/2/0 | router | 192.168.0.9 | 255.255.255.252 | N/A |
| Hub | S0/2/1 | router | 192.168.0.13 | 255.255.255.252 | N/A |
| Branch-1 | G0/0/0 | router | 192.168.1.1 | 255.255.255.0 | N/A |
| Branch-1 | S0/1/0 | router | 192.168.0.2 | 255.255.255.252 | N/A |
| Branch-2 | G0/0/0.1 | router | 192.168.2.1 | 255.255.255.224 | N/A |
| Branch-2 | G0/0/0.32 | router | 192.168.2.33 | 255.255.255.224 | N/A |
| Branch-2 | G0/0/0.64 | router | 192.168.2.65 | 255.255.255.224 | N/A |
| Branch-2 | S0/1/0 | router | 192.168.0.6 | 255.255.255.252 | N/A |
| Factory | G0/0/0 | router | 192.168.3.1 | 255.255.255.0 | N/A |
| Factory | G0/0/1 | router | 192.168.4.1 | 255.255.255.0 | N/A |
| Factory | S0/1/0 | router | 192.168.0.14 | 255.255.255.252 | N/A |
| HQ | G0/0/0.1 | router | 192.168.6.1 | 255.255.255.0 | N/A |
| HQ | G0/0/0.5 | router | 192.168.5.1 | 255.255.255.128 | N/A |
| HQ | G0/0/0.10 | router | 192.168.5.129 | 255.255.255.128 | N/A |
| HQ | S0/1/0 | router | 192.168.0.10 | 255.255.255.252 | N/A |
| SW-B1 | VLAN 1 | switch | 192.168.1.252 | 255.255.255.0 | 192.168.1.1 |
| SW-B2 | VLAN 1 | switch | 192.168.2.17 | 255.255.255.224 | 192.168.2.1 |
| SW-F1 | VLAN 1 | switch | 192.168.3.252 | 255.255.255.0 | 192.168.3.1 |
| SW-F2 | VLAN 1 | switch | 192.168.4.252 | 255.255.255.0 | 192.168.4.1 |
| SW-HQ1 | VLAN 1 | switch | 192.168.6.252 | 255.255.255.0 | 192.168.6.1 |
| SW-HQ2 | VLAN 1 | switch | 192.168.6.253 | 255.255.255.0 | 192.168.6.1 |
| SW-HQ3 | VLAN 1 | switch | 192.168.6.254 | 255.255.255.0 | 192.168.6.1 |
| DNS Server | NIC | host (server) | 192.168.5.252 | 255.255.255.128 | 192.168.5.129 |
| ISP | G0/0/0 | router | 192.0.2.2 | 255.255.255.252 | N/A |
| Internet Server | NIC | host (server) | 203.0.113.27 | N/A | N/A |
Objectives
In this lab, you will document a network that is unknown to you.
- Test network connectivity.
- Compile host addressing information.
- Remotely access default gateway devices.
- Document default gateway device configurations.
- Discover devices on the network.
- Draw the network topology.
Background / Scenario
Your employer has been hired to take over the administration of a corporate network because the previous network administrator has left the company. The network documentation is missing and needs to be recreated. Your job is to document the hosts and network devices including all the device addressing and logical interconnections. You will remotely access network devices and use network discovery to complete a device table and draw the network topology.
This is Part I of a two-part series of activities. You will use the documentation that you create in this activity to guide you as you troubleshoot the network in Part II, Packet Tracer - Troubleshooting Challenge - Using Documentation to Solve Issues.
As you investigate and document the network topology, make note of issues that you discover that do not adhere to the practices taught in the CCNA curriculum.
Instructions
Part 1: Test Connectivity
Ping between the PCs and the internet server to test the network. All PCs should be able to ping one another and the internet server.
C:\> ping 203.0.113.27
Pinging 203.0.113.27 with 32 bytes of data:
Reply from 203.0.113.27: bytes=32 time=7ms TTL=125
Reply from 203.0.113.27: bytes=32 time=6ms TTL=125
Reply from 203.0.113.27: bytes=32 time=1ms TTL=125
Reply from 203.0.113.27: bytes=32 time=6ms TTL=125
Ping statistics for 203.0.113.27:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 7ms, Average = 5msPart 2: Discover PC Configuration Information
Go to the command prompt of each PC and display the IP settings. Record this information in the documentation table.
| PC | IPv4 Address | Subnet Mask | Default Gateway | Site / LAN |
|---|---|---|---|---|
| PC1 | 192.168.1.153 | 255.255.255.0 (/24) | 192.168.1.1 | Branch-1 LAN |
| PC2 | 192.168.3.50 | 255.255.255.0 (/24) | 192.168.3.1 | Factory LAN 1 |
| PC3 | 192.168.4.115 | 255.255.255.0 (/24) | 192.168.4.1 | Factory LAN 2 |
| PC4 | 192.168.5.83 | 255.255.255.128 (/25) | 192.168.5.1 | HQ VLAN 5 |
| PC5 | 192.168.5.227 | 255.255.255.128 (/25) | 192.168.5.129 | HQ VLAN 10 |
| PC6 | 192.168.2.48 | 255.255.255.224 (/27) | 192.168.2.33 | Branch-2 VLAN 32 |
| PC7 | 192.168.2.67 | 255.255.255.224 (/27) | 192.168.2.65 | Branch-2 VLAN 64 |
Part 3: Discover Information about the Default Gateway Devices
Connect to each default gateway device using the Telnet protocol and record information about the interfaces that are in use in the table. The VTY password is cisco and privileged EXEC password is class.
C:\> telnet IP_address
Access Map
Use this table to reach every router and switch. The switches and the Hub router are reached from a Telnet session on a nearby router.
| Device | Telnet from | IP Address | VTY Password | Enable Password |
|---|---|---|---|---|
| Branch-1 | PC1 | 192.168.1.1 | cisco | class |
| Branch-2 | PC6 (or any PC) | 192.168.2.33 (or 192.168.0.6) | cisco | class |
| Factory | PC2 | 192.168.3.1 | cisco | class |
| HQ | PC4 | 192.168.5.1 | cisco | class |
| Hub | Branch-1 (telnet session) | 192.168.0.1 | cisco | class |
| SW-B1 | PC1 | 192.168.1.252 | cisco | class |
| SW-B2 | Branch-2 (telnet session) | 192.168.2.17 | cisco | class |
| SW-F1 | Factory (telnet session) | 192.168.3.252 | cisco | class |
| SW-F2 | Factory (telnet session) | 192.168.4.252 | cisco | class |
| SW-HQ1 | HQ (telnet session) | 192.168.6.252 | cisco | class |
| SW-HQ2 | HQ (telnet session) | 192.168.6.253 | cisco | class |
| SW-HQ3 | HQ (telnet session) | 192.168.6.254 | cisco | class |
| Router | Interface | IP Address / Prefix | Connects to |
|---|---|---|---|
| Branch-1 | G0/0/0 | 192.168.1.1/24 | PC1 LAN |
| Branch-1 | S0/1/0 | 192.168.0.2/30 | WAN link |
| Branch-2 | G0/0/0.1 (native VLAN 1) | 192.168.2.1/27 | Switch management (SW-B2) |
| Branch-2 | G0/0/0.32 (VLAN 32) | 192.168.2.33/27 | PC6 LAN |
| Branch-2 | G0/0/0.64 (VLAN 64) | 192.168.2.65/27 | PC7 LAN |
| Branch-2 | S0/1/0 | 192.168.0.6/30 | WAN link |
| Factory | G0/0/0 | 192.168.3.1/24 | PC2 LAN |
| Factory | G0/0/1 | 192.168.4.1/24 | PC3 LAN |
| Factory | S0/1/0 | 192.168.0.14/30 | WAN link |
| HQ | G0/0/0.1 (native VLAN 1) | 192.168.6.1/24 | Switch management (SW-HQ1/2/3) |
| HQ | G0/0/0.5 (VLAN 5) | 192.168.5.1/25 | PC4 LAN |
| HQ | G0/0/0.10 (VLAN 10) | 192.168.5.129/25 | PC5 LAN and DNS server |
| HQ | S0/1/0 | 192.168.0.10/30 | WAN link |
Part 4: Reconstruct the Network Topology
In this part of the activity, you will continue recording information about the devices in the network in the Addressing Table. In addition, you will start to diagram the network topology based on what you can discover about the device interconnections.
Step 1: Access Routing Tables on Each Gateway Device.
Use the routing tables in each router to learn more about the network. Make notes of your findings.
Step 2: Discover Non-Gateway Devices.
Use a network discovery protocol to document neighboring devices. Record your findings in the addressing table. At this point you should also be able to begin documenting device interconnections.
| Device | Interface | Neighbor | Neighbor Interface | Network |
|---|---|---|---|---|
| Hub | S0/1/0 | Branch-1 | S0/1/0 | 192.168.0.0/30 |
| Hub | S0/1/1 | Branch-2 | S0/1/0 | 192.168.0.4/30 |
| Hub | S0/2/0 | HQ | S0/1/0 | 192.168.0.8/30 |
| Hub | S0/2/1 | Factory | S0/1/0 | 192.168.0.12/30 |
| Hub | G0/0/0 | ISP | G0/0/0 | 192.0.2.0/30 |
| Branch-1 | G0/0/0 | SW-B1 | G0/1 | 192.168.1.0/24 |
| Branch-2 | G0/0/0 (trunk) | SW-B2 | G0/1 | 192.168.2.0/27, .32/27, .64/27 |
| Factory | G0/0/0 | SW-F1 | G0/1 | 192.168.3.0/24 |
| Factory | G0/0/1 | SW-F2 | G0/1 | 192.168.4.0/24 |
| HQ | G0/0/0 (trunk) | SW-HQ1 | G0/1 | 192.168.5.0/25, .128/25, 192.168.6.0/24 |
Part 5: Further Explore Device Configurations and Interconnections
Step 1: Access Device Configurations.
Connect to the other devices in the network. Gather information about the device configurations.
| Switch | Management SVI | IP Address / Prefix | Default Gateway | Site |
|---|---|---|---|---|
| SW-B1 | VLAN 1 | 192.168.1.252/24 | 192.168.1.1 | Branch-1 |
| SW-B2 | VLAN 1 | 192.168.2.17/27 | 192.168.2.1 | Branch-2 |
| SW-F1 | VLAN 1 | 192.168.3.252/24 | 192.168.3.1 | Factory |
| SW-F2 | VLAN 1 | 192.168.4.252/24 | 192.168.4.1 | Factory |
| SW-HQ1 | VLAN 1 | 192.168.6.252/24 | 192.168.6.1 | HQ |
| SW-HQ2 | VLAN 1 | 192.168.6.253/24 | 192.168.6.1 | HQ |
| SW-HQ3 | VLAN 1 | 192.168.6.254/24 | 192.168.6.1 | HQ |
| Switch | VLAN | Access Ports | Connected Host / Subnet |
|---|---|---|---|
| SW-B2 | VLAN 32 (TEAM-1) | Fa0/1 - 9 | PC6 (192.168.2.32/27) |
| SW-B2 | VLAN 64 (TEAM-2) | Fa0/10 - 20 | PC7 (192.168.2.64/27) |
| SW-HQ1 | VLAN 10 (admin) | Fa0/1 | DNS Server (192.168.5.128/25) |
| SW-HQ2 | VLAN 5 (acct) | Fa0/1 | PC4 (192.168.5.0/25) |
| SW-HQ3 | VLAN 10 (admin) | Fa0/1 | PC5 (192.168.5.128/25) |
| SW-HQ2 | VLAN 99 (VLAN0099) | none | not used |
Step 2: View Neighbor Information.
Use discovery protocols to increase your knowledge of the network devices and topologies.
| Switch | Interface | Neighbor | Neighbor Interface | Link Type |
|---|---|---|---|---|
| SW-B1 | G0/1 | Branch-1 | G0/0/0 | access link |
| SW-B2 | G0/1 | Branch-2 | G0/0/0 | trunk, native VLAN 1 |
| SW-F1 | G0/1 | Factory | G0/0/0 | access link |
| SW-F2 | G0/1 | Factory | G0/0/1 | access link |
| SW-HQ1 | G0/1 | HQ | G0/0/0 | trunk, native VLAN 1 |
| SW-HQ1 | Po1 (Fa0/19 - 20) | SW-HQ2 | Po1 (Fa0/19 - 20) | LACP EtherChannel trunk |
| SW-HQ1 | Po3 (Fa0/23 - 24) | SW-HQ3 | Po3 (Fa0/23 - 24) | LACP EtherChannel trunk |
| SW-HQ2 | Po2 (Fa0/21 - 22) | SW-HQ3 | Po2 (Fa0/21 - 22) | LACP EtherChannel trunk, blocked by STP on SW-HQ2 |
Step 3: Connect to Other Devices.
Display configuration information for the other devices on the network. Record your findings in the device table.
By now you should know about all the devices and interface configurations in the network. All rows of the table should contain device information. Use your information to reconstruct as much of the network topology as you can.
Reflection
You may have noticed that some of the practices used to configure the network devices are out-of-date, inefficient, or not secure. Make a list of as many recommendations that you have regarding how the devices should be reconfigured to follow the practices that you have learned in the CCNA curriculum.
The list is a lengthy one. This question provides you with an opportunity to review many of the best practices that have been covered in the CCNA curriculum. Use student discussions to ensure that as many issues have been discussed as possible. Some issues are:
Security and Device Access
- All devices use the same simple and well-known passwords. These should be changed, should vary between devices, and should be stronger. (see Access Map)
- SSH is not in use in the network. (see Part 3)
- On SW-B1, SW-F1, and SW-F2, the line vty 5 15 lines are configured with login but without a password, so Telnet sessions that use these lines cannot log in. All vty lines should be configured consistently, preferably for SSH only. (see Part 5, Step 1 - SW-B1, SW-F1, SW-F2)
- Management access to all devices is not restricted using ACLs or AAA.
- Port security is not in use.
- 802.1x is not implemented.
- IP Source Guard is not implemented.
- CDP is on by default and should be turned off or restricted. (see Part 4, Step 2)
Switching and VLANs
- The switches all use the default SVI and management VLAN. This should be changed. (see Part 5, Step 1)
- Most switchports are in VLAN 1. They should be moved to different VLANs. (see Part 5, Step 1 - show vlan brief)
- All unused switchports are in VLAN 1 and are active. Unused switchports should be shut down and moved to an unused VLAN. (see Part 5, Step 1 - show vlan brief)
- DTP negotiation is active on trunk ports. This is a security risk. (see Part 5, Step 2 - SW-HQ3, Po2 in auto mode)
- DTP is active on all ports on SW-B1, SW-F1, SW-F2, SW-HQ1, SW-HQ2 and SW-HQ3 except those ports connected to PC-4 and PC-5.
- Native VLAN 1 is being used on trunk links and should be changed. (see Part 5, Step 2 - show interfaces trunk)
- Legacy STP is being used on all switches and should be changed to RSTP (802.1w). (see Part 5, Step 2 - SW-HQ2, protocol ieee)
- VLAN 99 is created only on SW-HQ2. It is not being used and does not have a name and should be removed. (see Part 5, Step 1 - SW-HQ2)
Routing
- OSPF is active on LAN interfaces. Passive interfaces will decrease unnecessary network traffic. (see Part 4, Step 1 - show ip protocols on Branch-1 and Factory)
Network Topology Diagram
Students’ drawings will differ in layout; however, the device interconnections should be consistent. The hidden topology is shown below.
Annotated Topology (built from the discovered information)
Device Interconnections
| Device | Interface | Neighbor | Neighbor Interface | Network / Notes |
|---|---|---|---|---|
| Hub | G0/0/0 | ISP | G0/0/0 | 192.0.2.0/30 |
| Hub | S0/1/0 (DCE) | Branch-1 | S0/1/0 | 192.168.0.0/30 |
| Hub | S0/1/1 (DCE) | Branch-2 | S0/1/0 | 192.168.0.4/30 |
| Hub | S0/2/0 (DCE) | HQ | S0/1/0 | 192.168.0.8/30 |
| Hub | S0/2/1 (DCE) | Factory | S0/1/0 | 192.168.0.12/30 |
| Branch-1 | G0/0/0 | SW-B1 | G0/1 | 192.168.1.0/24 |
| Branch-2 | G0/0/0 (trunk) | SW-B2 | G0/1 | VLAN 1, 32, 64 |
| Factory | G0/0/0 | SW-F1 | G0/1 | 192.168.3.0/24 |
| Factory | G0/0/1 | SW-F2 | G0/1 | 192.168.4.0/24 |
| HQ | G0/0/0 (trunk) | SW-HQ1 | G0/1 | VLAN 1, 5, 10 |
| SW-HQ1 | Po1 (Fa0/19 - 20) | SW-HQ2 | Po1 (Fa0/19 - 20) | LACP EtherChannel |
| SW-HQ1 | Po3 (Fa0/23 - 24) | SW-HQ3 | Po3 (Fa0/23 - 24) | LACP EtherChannel |
| SW-HQ2 | Po2 (Fa0/21 - 22) | SW-HQ3 | Po2 (Fa0/21 - 22) | LACP EtherChannel (STP blocked on SW-HQ2) |
| SW-HQ1 | Fa0/1 | DNS Server | NIC | VLAN 10, 192.168.5.252 |
| SW-HQ2 | Fa0/1 | PC4 | NIC | VLAN 5 |
| SW-HQ3 | Fa0/1 | PC5 | NIC | VLAN 10 |
Other items missing in the Topology documentation include the following:
- VLANs and port memberships
- DTE / DCE devices
- DNS Server addresses
- OSPFv2 Area
- Physical interfaces and associated IP addresses
- Physical switchports and associated VLAN / trunking
- Each Switch Management VLAN and IP address
- STP is being blocked on SW-HQ2 going to SW-HQ3
- EtherChannel is using LACP (802.3ad)
Next step: Use the documentation that you created in this activity to find and fix the network problems in Part II: 12.6.2 Packet Tracer - Troubleshooting Challenge - Use Documentation to Solve Issues.







