6.2.3.7 Packet Tracer Troubleshooting A VLAN Implementation Scenario 1 Instructions
6.2.3.7%20Packet%20Tracer%20-%20Troubleshooting%20a%20VLAN%20Implementation%20-%20Scenario%201%20Instructions
User Manual: Pdf
Open the PDF directly: View PDF 
.
Page Count: 3
| Download | |
| Open PDF In Browser | View PDF |
Packet Tracer - Troubleshooting a VLAN Implementation Scenario 1 Topology Addressing Table Device Interface IPv4 Address Subnet Mask Switch Port VLAN PC1 NIC 172.17.10.21 255.255.255.0 S1 F0/11 10 PC2 NIC 172.17.20.22 255.255.255.0 S1 F0/18 20 PC3 NIC 172.17.30.23 255.255.255.0 S1 F0/6 30 PC4 NIC 172.17.10.24 255.255.255.0 S2 F0/11 10 PC5 NIC 172.17.20.25 255.255.255.0 S2 F0/18 20 PC6 NIC 172.17.30.26 255.255.255.0 S2 F0/6 30 Objectives Part 1: Test Connectivity between PCs on the Same VLAN Part 2: Investigate Connectivity Problems by Gathering Data Part 3: Implement the Solution and Test Connectivity Scenario In this activity, you will troubleshoot connectivity problems between PCs on the same VLAN. The activity is complete when PCs on the same VLAN can ping each other. Any solution you implement must conform to the Addressing Table. © 2013 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public. Page 1 of 3 Packet Tracer - Troubleshooting a VLAN Implementation Scenario 1 Part 1: Test Connectivity between PCs on the Same VLAN From the command prompt on each PC, ping between PCs on the same VLAN. a. Can PC1 ping PC4? b. Can PC2 ping PC5? c. Can PC3 ping PC6? Part 2: Investigate Connectivity Problems by Gathering Data Step 1: Verify configuration on the PCs. Verify if the following configurations for each PC is correct. IP address Subnet mask Step 2: Verify the configuration on the switches. Verify if the following configurations on the switches are correct. Ports assigned to the correct VLANs. Ports configured for the correct mode. Ports connected to the correct devices. Step 3: Document the problem and the solutions. List the problems and the solutions that will allow these PCs to ping each other. Keep in mind that there could be more than one problem or more than one solution. PC1 to PC4 a. Explain the connectivity issues between PC1 and PC4. b. Record the necessary actions to correct the issues. PC2 to PC5 c. Explain the connectivity issues between PC2 and PC5. d. Record the necessary actions to correct the issues. PC3 to PC6 e. What are the reasons why connectivity failed between the PCs? © 2013 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public. Page 2 of 3 Packet Tracer - Troubleshooting a VLAN Implementation Scenario 1 f. Record the necessary actions to correct the issues. Part 3: Implement the Solution and Test Connectivity Verify PCs on the same VLAN can now ping each other. If not, continue to troubleshoot. Suggested Scoring Rubric Packet Tracer scores 70 points. Documentation in Part 2, Step 3 is worth 30 points. © 2013 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public. Page 3 of 3
Source Exif Data:
File Type : PDF File Type Extension : pdf MIME Type : application/pdf PDF Version : 1.5 Linearized : No Has XFA : No Language : en-US XMP Toolkit : Adobe XMP Core 5.4-c005 78.147326, 2012/08/23-13:03:03 Create Date : 2014:06:09 14:48:33-07:00 Creator Tool : Microsoft® Word 2010 Modify Date : 2014:06:09 14:58:30-07:00 Metadata Date : 2014:06:09 14:58:30-07:00 Producer : Microsoft® Word 2010 Format : application/pdf Creator : Betty Staerk State : 1 Version : 1.1 Document ID : uuid:14f0f676-f570-4f96-8081-4f5806015c61 Instance ID : uuid:b2e99f6d-e562-4bfb-8a67-26c3af60421c Page Count : 3 Author : Betty Staerk Warning : [Minor] Ignored duplicate Info dictionaryEXIF Metadata provided by EXIF.tools