A network engineer configures SPAN on a Cisco Catalyst switch to monitor traffic between two hosts. The engineer configures the source interface as GigabitEthernet0/1 and the destination interface as GigabitEthernet0/2. After the configuration, the engineer notices that the monitored traffic is not being forwarded to the destination port. What is the most likely cause?
Trap 1: The destination port is not in the same VLAN as the source port.
Incorrect because SPAN can monitor traffic across different VLANs; the destination port does not need to be in the same VLAN.
Trap 2: The destination port is configured as a trunk port.
Incorrect because a trunk port can be a SPAN destination; this would not prevent traffic forwarding.
Trap 3: The source interface is not in the same VLAN as the destination…
Incorrect because SPAN does not require the source and destination to be in the same VLAN; the destination port simply receives a copy of the traffic.
- A
The destination port is not in the same VLAN as the source port.
Why wrong: Incorrect because SPAN can monitor traffic across different VLANs; the destination port does not need to be in the same VLAN.
- B
The destination port is configured as a trunk port.
Why wrong: Incorrect because a trunk port can be a SPAN destination; this would not prevent traffic forwarding.
- C
The destination port is in a blocking state due to Spanning Tree Protocol.
Correct because SPAN destination ports are not expected to participate in STP; they should be configured with 'spanning-tree portfast' to avoid blocking.
- D
The source interface is not in the same VLAN as the destination interface.
Why wrong: Incorrect because SPAN does not require the source and destination to be in the same VLAN; the destination port simply receives a copy of the traffic.