Refer to the exhibit.
L3SW1 has a spanning-tree priority of 8192 set on VLANs 1, 300, and 301, and these
VLANs are configured on and trunked between all switches.
Executing the command show spanning-tree blockedports on L2SW5 results in:
L2SW5# show spanning-tree blockedports
Name Blocked Interfaces List
——————– ————————————
VLAN0001 Gi1/1
VLAN0300 Gi1/1
VLAN0301 Gi1/1
An additional VLAN, VLAN302, is defined on all switches and trunked between them.
VLAN302 access ports are set up on each of the switches and PLC#1, I/O#1, and the
PanelView are attached. You expect the new VLAN to be listed as blocked on interface
GigabitEthernet1/1 of L2SW5 but it is not. The three new devices are able to communicate
with each other.
After executing the same command on all switches you see this output on L2SW4:
L2SW4# show spanning-tree blockedports
Name Blocked Interfaces List
——————– ————————————
VLAN0001 Gi1/2
VLAN0300 Gi1/2
VLAN0301 Gi1/2
Why is VLAN302 forwarding on L2SW5 interface GigabitEthernet 1/1 and L2SW4 interface GigabitEthernet 1/1 and 1/2?
A.
VLAN302 is not configured in the VLAN database on L2SW5
B.
VLAN302 is not in the allowed list on the L2SW5 interface GigabitEthernet1/1 trunk
C.
L2SW4 is the spanning tree root for VLAN 302
D.
The FO3 fiber-optic cable between L2SW4 and L2SW5 is damaged