Soru

Zorluk: Çok zorSwitching Concepts and VLANs

A network engineer is auditing advanced Layer 2 switching configurations and traffic handling mechanisms across an enterprise network infrastructure. Match each switching concept or frame processing scenario on the left with its corresponding Layer 2 operational behavior on the right.

  • Voice VLAN configuration on a single physical switch interface connected to an IP phone and workstationSeparates voice and data traffic on a single interface by expecting 802.1Q tagged frames for voice while placing untagged traffic from the attached PC into the access VLAN.
  • Private VLAN (PVLAN) Isolated Port operational behaviorRestricts Layer 2 frame forwarding so the interface can communicate only with promiscuous ports, blocking direct communication with all other ports in the same secondary VLAN.
  • IEEE 802.1Q Trunk Port handling of incoming untagged Ethernet framesProcesses ingress untagged frames by mapping them to the configured native VLAN and forwarding them without an internal 4-byte 802.1Q header across the trunk.
  • Switch CAM table MAC address aging expiration and unknown unicast frame handlingFloods arriving frames out all active interfaces belonging to the ingress VLAN except the receiving port because the destination hardware address is no longer cached.

Cevap

Voice VLAN pairs with separating voice 802.1Q tagged traffic from untagged PC data on a single port. PVLAN Isolated Port pairs with restricting frame forwarding exclusively to promiscuous ports while blocking other isolated/community ports. IEEE 802.1Q Trunk handling of untagged frames pairs with mapping them to the native VLAN without inserting an 802.1Q header. CAM table aging expiration pairs with unknown unicast flooding out all active ports in the VLAN except the receiving interface.
Each concept correctly maps to its foundational Layer 2 behavior: Voice VLAN separates tagged VoIP traffic from untagged PC traffic on one physical interface; PVLAN Isolated Ports restrict Layer 2 forwarding exclusively to promiscuous ports; 802.1Q Trunk Native VLAN handling processes untagged ingress frames without appending internal 802.1Q headers; and CAM table aging triggers unknown unicast flooding strictly within the source VLAN.

Adım Adım Çözüm

1
Analyze Voice VLAN operation on an interface connected to an IP phone daisy-chained to a PC.
Identify that voice traffic utilizes 802.1Q tagging (often with 802.1p Class of Service bits) while data traffic from the PC remains untagged on the port's access VLAN.
Voice VLAN segregation relies on Layer 2 tagging to differentiate real-time voice packets from standard data packets over a single physical link.
2
Analyze Private VLAN (PVLAN) Isolated Port mechanics.
Determine that an isolated port completely blocks Layer 2 communication to all other ports within the primary/secondary VLAN except promiscuous ports.
PVLANs enforce micro-segmentation by ensuring isolated host ports cannot talk to each other directly at Layer 2.
3
Analyze IEEE 802.1Q trunking behavior for native VLAN ingress frames.
Confirm that untagged ingress frames on a trunk interface are associated with the native VLAN and sent without adding an 802.1Q tag header.
IEEE 802.1Q maintains backward compatibility for untagged traffic by assigning untagged frames to a single native VLAN per trunk link.
4
Analyze CAM table MAC aging and frame forwarding behavior.
Recognize that when a MAC address is flushed or aged out of the CAM table, frames directed to that MAC address are treated as unknown unicast traffic and flooded out all ports in the broadcast domain except the ingress port.
Switches use unknown unicast flooding to ensure delivery when a destination MAC-to-port mapping is absent from the forwarding database.

Anahtar Kavram

Advanced Layer 2 Switching Mechanics, Frame Tagging, VLAN Isolation, and Forwarding Logic
Bu soruyu puanla