A customer is troubleshooting FCoE in its network. They have discovered that vFC is
currently down and there is no active STP port state on the bound Ethernet interface. What
should the STP port state be to correct this issue?
A.
The bound interface should be in an STP forwarding state for the native VLAN only.
B.
The bound interface should be in an STP learning state for both the native VLAN and
the member FCoE VLAN that is mapped to the active VSAN.
C.
The bound interface should be in an STP forwarding state for both the native VLAN and
the member FCoE VLAN that is mapped to the active VSAN.
D.
The bound interface should be in an STP blocking state for both the native VLAN and
the member FCoE VLAN that is mapped to the active VSAN.
VFC down because no active STP port-state on the bound Ethernet interface
No active STP port-state on the bound Ethernet interface causes the VFC to be down.
Possible Cause
The bound interface should be in a STP-forwarding state for both the native VLAN and the member
FCOE VLAN mapped to the active VSAN. If there are no STP active ports on the VLAN, then the switch
drops all FIP packets received on the VLAN over the bound interface. This means that the FIP is not
initiated to bring up the VFC.
Solution
Check the STP port state on the bound Ethernet trunk interface for both non-FCOE native VLAN and
FCOE member VLAN. Fix the STP port state and move it to forwarding, if in blocked inconsistent state
or error-disable state.