3.3.12 Packet Tracer - Vlan Configuration.pka [ Mobile ]

The problem slapped Alex in the face: .

He walked off. The switches hummed.

Alex cracked knuckles. Time to build walls. On Switch S1 , Alex typed:

Alex smiled at the virtual topology—three separate networks living on the same wires, never arguing, never colliding. 3.3.12 packet tracer - vlan configuration.pka

Alex learned the hard lesson: deleting a VLAN from one switch doesn’t delete it from others. But it does break connectivity for any access port still assigned to that missing VLAN on that switch.

The Switch that Forgot How to Listen

Professor Lasky’s note floated at the top of the instructions: “VLANs don’t just happen. You build walls where there are none.” The problem slapped Alex in the face:

Packet Tracer’s simulation mode revealed the truth: red packets dropping at the trunk port, rejected like a bouncer checking an expired ID.

The basement lab of Meridian Community College. Racks of aging but reliable Cisco switches hum in the corner. On a monitor, the Packet Tracer interface glows green.

Alex did this for all three switches, matching the color-coded diagram in Packet Tracer. Red for Accounting. Blue for Engineering. Green for Staff. Alex cracked knuckles

“Walls built,” Alex said, leaning back. But Professor Lasky’s note glowed again: “VLANs are islands. How do islands talk?” Alex realized: S1 knows VLAN 10 exists on its own ports. S2 knows VLAN 10 exists on its own ports. But between switches? Silence.

“I need a trunk,” Alex whispered.

But when Alex tried to ping from PC1 (Accounting) to PC5 (Engineering)…

Alex saved the configuration: write memory .