An expansion project added an E-Tap and Device Level Ring to interface FastEthernet1/1
of L2SW1. The administrator has looked at the logs of L2SW1 and found that
FastEthernet1/1 was in an error-disabled state.Using command line access on L2SW1,
the administrator issued the following commands in configuration mode:
L2SW1(config)# interface FastEthernet 1/1
L2SW1(config-if)# shutdown
L2SW1(config-if)# no shutdown
The administrator checked the logs of L2SW1 and found the following:
Mar 30 02:23:17.588: %PM-4-ERR_DISABLE: bpduguard error detected on Fa1/1, putting
Fa1/1 in err-disable state
The administrator checked the software configuration of the switch port and found the following:
interface FastEthernet1/1
switchport access vlan 310
switchport mode access
speed 100
duplex full
no mdix auto
spanning-tree portfast
spanning-tree bpduguard enable
Why has the port gone error-disabled?
A.
interface FastEthernet1/1 is configured as an access port on the wrong VLAN.
B.
There is a duplex mismatch between interface FastEthernet1/1 and the E-Tap.
C.
The E-Tap is not configured as a ring supervisor causing a loop on interface FastEthernet1/1.
D.
The E-Tap is configured at 10Mbps and the switch port is configured at 100Mbps.
E.
Automatic MDI Crossover detection is disabled.