Question

Difficulty: MediumInterswitch Connectivity and Trunking (802.1Q)

A Cisco switch receives an untagged Ethernet frame on an IEEE 802.1Q trunk link and forwards it out another 802.1Q trunk link. Arrange the operational steps in the correct order from initial frame arrival to final frame transmission.

  1. 1An untagged Ethernet frame arrives at an active switchport configured as an IEEE 802.1Q trunk.
  2. 2The switch assigns the untagged frame internally to the native VLAN configured on the ingress trunk port.
  3. 3The switch performs a Layer 2 MAC address table lookup within the context of the native VLAN to determine the egress port.
  4. 4The switch transmits the frame out the egress trunk interface untagged because the destination interface native VLAN matches the frame's VLAN.

Answer

The correct operational sequence begins with the arrival of an untagged Ethernet frame on an 802.1Q trunk port, followed by internal mapping to the ingress port's native VLAN, executing a MAC address table lookup within that native VLAN, and finally transmitting the frame untagged out an egress trunk configured with a matching native VLAN.
IEEE 802.1Q trunks handle untagged traffic by implicitly classifying ingress frames into the configured native VLAN. The switch uses that native VLAN's MAC address table for forwarding decisions and sends the frame out an egress trunk untagged if the egress interface shares the same native VLAN configuration.

Step-by-Step Solution

1
Identify ingress frame format
The switch identifies that the incoming frame lacks a 4-byte IEEE 802.1Q tag header.
Trunk ports process both tagged and untagged frames depending on whether traffic belongs to tagged VLANs or the native VLAN.
2
Classify frame to native VLAN
The frame is internally tagged/associated with the ingress port's native VLAN ID.
IEEE 802.1Q specification requires untagged frames traversing a trunk to be implicitly assigned to the native VLAN.
3
Execute Layer 2 forwarding lookup
The switch consults the MAC address table for the destination address within the native VLAN domain.
VLANs maintain isolated broadcast domains and separate MAC lookup tables to prevent cross-VLAN frame leakage.
4
Evaluate egress tagging behavior
The frame is forwarded across the egress trunk port without inserting an 802.1Q header tag.
To maintain compatibility, 802.1Q does not tag frames belonging to the native VLAN when sending them over trunk links.

Key Concept

IEEE 802.1Q Native VLAN Ingress and Egress Processing Mechanics
Rate this question