[CCNAv6 S4] 8.2.4.15 Packet Tracer - Troubleshooting Challenge - Using Documentation to Solve Issues


Packet Tracer – Troubleshooting Challenge - Using Documentation to Solve Issues
Addressing Table


Objectives

Part 1: Gather Documentation

Part 2: Test Connectivity

Part 3: Gather Data and Implement Solutions

Part 4: Test Connectivity

Scenario

This is Part II of a two-part activity. Part I is Packet Tracer - Troubleshooting Challenge - Documenting the Network, which you should have completed earlier in the chapter. In Part II, you will use your troubleshooting skills and documentation from Part I to solve connectivity issues between PCs.

Part 1:     Gather Documentation
Step 1:     Retrieve network documentation.

To successfully complete this activity, you will need your documentation for the Packet Tracer - Troubleshooting Challenge - Documenting the Network activity you completed previously in this chapter. Locate that documentation now.

Step 2:     Documentation requirements.

The documentation you completed in the previous activity should have an accurate topology and addressing table. If necessary, update your documentation to reflect an accurate representation of a correct answer from the Packet Tracer - Troubleshooting Challenge - Documenting the Network activity. You may need to consult with your instructor.

Part 2:     Test Connectivity
Step 1:     Determine location of connectivity failure.

At the end of this activity, there should be full connectivity between PC to PC and PC to the www.cisco.pka server. However, right now you must determine where connectivity fails by pinging from:

• PCs to www.cisco.pka server

• PC to PC

• PC to default gateway

Step 2:     What pings were successful?

Document both the successful and failed pings.

Part 3:     Gather Data and Implement Solutions
Step 1:     Choose a PC to begin gathering data.

Choose any PC and begin gathering data by testing connectivity to the default gateway. You can also use traceroute to see where connectivity fails.

Step 2:     Telnet to the default gateway and continue gathering data.

a.     If the PC you chose does not have connectivity to its default gateway, choose another PC to approach the problem from a different direction.

b.     After you have established connectivity through a default gateway, the login password is cisco and the privileged EXEC mode password is class.

Step 3:     Use troubleshooting tools to verify the configuration.

At the default gateway router, use troubleshooting tools to verify the configuration with your own documentation. Remember to check switches in addition to the routers. Be sure to verify the following:

• Addressing information

• Interface activation

• Encapsulation

• Routing

• VLAN configuration

• Duplex or speed mismatches

Step 4:     Document network symptoms and possible solutions.

As you discover symptoms of the PC connectivity issue, add them to your documentation.

Step 5:     Make changes based on your solutions from the previous step.

Part 4:     Test Connectivity
Step 1:     Test PC connectivity.

a.     All PCs should now be able to ping each other and the www.cisco.pka server. If you changed any IP configurations, create new pings because the prior pings use the old IP address.

b.     If there are still connectivity issues between PCs or PC to server, return to Part 3 and continue troubleshooting.

Step 2:     Check results.

Your Packet Tracer score should be 70/70. If not, return to Part 2 and continue to troubleshoot and implement your suggested solutions. You will not be able to click Check Results and see which required components are not yet completed.




Configuration R3:

enable
configure terminal
router eigrp 1
 no auto-summary
 passive-interface GigabitEthernet0/0
 passive-interface GigabitEthernet0/0.5
 passive-interface GigabitEthernet0/0.15
 passive-interface GigabitEthernet0/0.25
 passive-interface GigabitEthernet0/0.35
 end
write memory
!

Configuration R2:

enable
configure terminal
interface Serial0/0/0
 ip address 10.1.0.3 255.255.255.248
 exit
router eigrp 1
 passive-interface GigabitEthernet0/0
 passive-interface GigabitEthernet0/0.100
 passive-interface GigabitEthernet0/0.105
 end
write memory
!

Configuration  R1:

enable
configure terminal
interface Serial0/0/0
 encapsulation frame-relay
 end
write memory
!

Configuration R4

enable
configure terminal
router eigrp 1
 network 10.0.0.0
 end
write memory
!

 Configuration  R5:

enable
configure terminal
ip nat inside source list 1 pool LAN overload
interface s0/0/1
 no shutdown
 end
write memory
!


END !~!







Nhận xét

Đăng nhận xét

Bài đăng phổ biến từ blog này

[CCNAv6 S4] 8.2.4.14 Packet Tracer - Troubleshooting Enterprise Networks 3

Hình ảnh
Packet Tracer – Troubleshooting Enterprise Networks 3 Addressing Table Background This activity uses a variety of technologies you have encountered during your CCNA studies, including routing, port security, EtherChannel, DHCP, NAT, PPP, and Frame Relay. Your task is to review the requirements, isolate and resolve any issues, and then document the steps you took to verify the requirements. Note: This activity begins with a partial score. Requirements DHCP ·         R1 is the DHCP server for the R1 LAN. Switching Technologies ·         Port security is configured to only allow PC1 to access S1's F0/3 interface. All violations should disable the interface. ·         Link aggregation using EtherChannel is configured on S2, S3, and S4. Routing ·         All routers are configured with OSPF process ID 1 and no routing updates should be sent across interfaces that do n...
Đọc thêm

[CCNAv6 S2] 2.2.2.4 Packet Tracer - Configuring IPv4 Static and Default Routes

Hình ảnh
Packet Tracer - Configuring IPv4 Static and Default Routes Addressing Table Objectives Part 1: Examine the Network and Evaluate the Need for Static Routing Part 2: Configure Static and Default Routes Part 3: Verify Connectivity Background In this activity, you will configure static and default routes. A static route is a route that is entered manually by the network administrator to create a reliable and safe route. There are four different static routes that are used in this activity: a recursive static route, a directly attached static route, a fully specified static route, and a default route. Part 1:     Examine the Network and Evaluate the Need for Static Routing a.     Looking at the topology diagram, how many networks are there in total? b.    How many networks are directly connected to R1, R2, and R3? c.     How many static routes are required by each router to reach networks that are not directly ...
Đọc thêm

[CCNAv6 S2] 7.3.2.4 Packet Tracer - Troubleshooting Standard IPv4 ACLs

Hình ảnh
Packet Tracer – Troubleshooting Standard IPv4 ACLs Addressing Table Objectives Part 1: Troubleshoot ACL Issue 1 Part 2: Troubleshoot ACL Issue 2 Part 3: Troubleshoot ACL Issue 3 Scenario This network is meant to have the following three policies implemented: ·         Hosts from the 192.168.0.0/24 network are unable to access network 10.0.0.0/8. ·         L3 can’t access any devices in network 192.168.0.0/24. ·         L3 can’t access Server1 or Server2. L3 should only access Server3. ·         Hosts from the 172.16.0.0/16 network have full access to Server1, Server2 and Server3. Note: All FTP usernames and passwords are “cisco”. No other restrictions should be in place. Unfortunately, the rules that have been implemented are not working correctly. Your task is to find and fix the errors related to the access lists on R1. Part 1:     Troublesh...
Đọc thêm