[CCNAv6 S2] 6.1.2.7 Packet Tracer - Investigating a VLAN Implementation



Packet Tracer – Investigating a VLAN Implementation
Addressing Table

Objectives

Part 1: Observe Broadcast Traffic in a VLAN Implementation

Part 2: Observe Broadcast Traffic without VLANs

Part 3: Complete Reflection Questions

Background

In this activity, you will observe how broadcast traffic is forwarded by the switches when VLANs are configured and when VLANs are not configured.
Part 1:     Observe Broadcast Traffic in a VLAN Implementation
Step 1:     Ping from PC1 to PC6.

a.     Wait for all the link lights to turn to green. To accelerate this process, click Fast Forward Time located in the bottom yellow tool bar.

b.    Click the Simulation tab and use the Add Simple PDU tool. Click on PC1, and then click on PC6.

c.     Click the Capture/Forward button to step through the process. Observe the ARP requests as they traverse the network. When the Buffer Full window appears, click the View Previous Events button.

d.    Were the pings successful? Why?

e.     Look at the Simulation Panel, where did S3 send the packet after receiving it?

In normal operation, when a switch receives a broadcast frame on one of its ports, it forwards the frame out all other ports. Notice that S2 only sends the ARP request out Fa0/1 to S1. Also notice that S3 only sends the ARP request out F0/11 to PC4. PC1 and PC4 both belong to VLAN 10. PC6 belongs to VLAN 30. Because broadcast traffic is contained within the VLAN, PC6 never receives the ARP request from PC1. Because PC4 is not the destination, it discards the ARP request. The ping from PC1 fails because PC1 never receives an ARP reply.

Step 2:     Ping from PC1 to PC4.

a.     Click the New button under the Scenario 0 dropdown tab. Now click on the Add Simple PDU icon on the right side of Packet Tracer and ping from PC1 to PC4.

b.    Click the Capture/Forward button to step through the process. Observe the ARP requests as they traverse the network. When the Buffer Full window appears, click the View Previous Events button.

c.     Were the pings successful? Why?

d.    Examine the Simulation Panel. When the packet reached S1, why does it also forward the packet to PC7?

Part 2:     Observe Broadcast Traffic without VLANs
Step 1:     Clear the configurations on all three switches and delete the VLAN database.

a.     Return to Realtime mode.

b.    Delete the startup configuration on all 3 switches. What command is used to delete the startup configuration of the switches?

c.     Where is the VLAN file stored in the switches?

d.    Delete the VLAN file on all 3 switches. What command deletes the VLAN file stored in the switches?

Step 2:     Reload the switches.

Use the reload command in privileged EXEC mode to reset all the switches. Wait for the entire link to turn green. To accelerate this process, click Fast Forward Time located in the bottom yellow tool bar.

Step 3:     Click Capture/Forward to send ARP requests and pings.

a.     After the switches reload and the link lights return to green, the network is ready to forward your ARP and ping traffic.

b.    Select Scenario 0 from the drop down tab to return to Scenario 0.

c.     From Simulation mode, click the Capture/Forward button to step through the process. Notice that the switches now forward the ARP requests out all ports, except the port on which the ARP request was received. This default action of switches is why VLANs can improve network performance. Broadcast traffic is contained within each VLAN. When the Buffer Full window appears, click the View Previous Events button.

Part 3:     Complete Reflection Questions
1.     If a PC in VLAN 10 sends a broadcast message, which devices receive it?

2.     If a PC in VLAN 20 sends a broadcast message, which devices receive it?

3.     If a PC in VLAN 30 sends a broadcast message, which devices receive it?

4.     What happens to a frame sent from a PC in VLAN 10 to a PC in VLAN 30?

5.     In terms of ports, what are the collision domains on the switch?

6.     In terms of ports, what are the broadcast domains on the switch?





Show vlan brief
show flash:
delete vlan.dat
reload



Link Download: Here



Nhận xét

Đăng nhận xét

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

[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] 8.3.1.2 Packet Tracer - Skills Integration Challenge

Hình ảnh
Packet Tracer – Skills Integration Challenge Addressing Table VLAN Port Assignments and DHCP Information Scenario In this culminating activity, you will configure VLANs, trunks, DHCP Server, DHCP relay agents, and configure a router as a DHCP client. Requirements Using the information in the tables above, implement the following requirements: ·         Create VLANs on S2 and assign VLANs to appropriate ports. Names are case-sensitive ·         Configure S2 ports for trunking. ·         Configure all non-trunk ports on S2 as access ports. ·         Configure R1 to route between VLANs. Subinterface names should match the VLAN number. ·         Configure R1 to act as a DHCP server for the VLANs attached to S2. -       Create a DHCP pool for each VLAN. Names are case-sensitive. -       Assign the ap...
Đọc thêm

[CCNAv6 S3] 7.2.3.5 Packet Tracer - Troubleshooting EIGRP for IPv4

Hình ảnh
Packet Tracer – Troubleshooting EIGRP for IPv4 Addressing Table Scenario In this activity, you will troubleshoot EIGRP neighbor issues. Use show commands to identify errors in the network configuration. Then, you will document the errors you discover and implement an appropriate solution. Finally, you will verify full end-to-end connectivity is restored. Troubleshooting Process 1.     Use testing commands to discover connectivity problems in the network and document the problem in the Documentation Table. 2.     Use verification commands to discover the source of the problem and devise an appropriate solution to implement. Document the proposed solution in the Documentation Table. 3.     Implement each solution one at a time and verify if the problem is resolved. Indicate the resolution status in the Documentation Table. 4.     If the problem is not resolved, it may be necessary to first remove the implemented solution befor...
Đọc thêm