The scenario: VLAN Configuration . Objective: Slice this single broadcast domain into three separate pieces of virtual reality.
“Right,” Alex groaned. “The switch doesn’t know which PC belongs to which VLAN. It’s like a hotel front desk that doesn’t ask for your room key.” Back on S1: 3.3.12 packet tracer - vlan configuration.pka
Professor Lasky’s note floated at the top of the instructions: “VLANs don’t just happen. You build walls where there are none.” The scenario: VLAN Configuration
Professor Lasky walked by, glanced at the screen, and said only: “Three VLANs today. Three hundred in the real world. The logic doesn’t change.” “The switch doesn’t know which PC belongs to which VLAN
enable configure terminal vlan 10 name Accounting vlan 20 name Engineering vlan 30 name Staff end It felt like naming three new pets. But switches don’t wag tails. They just add lines to a file called vlan.dat .
“Check,” Alex whispered, moving to S2 and S3. Repeat. Repeat. VLAN 10, 20, 30. Accounting. Engineering. Staff.
“Perfect isolation,” Alex said, closing Packet Tracer. “Almost as good as my weekend plans.”