A customer is deploying FCoE in its networ and has found that the connected host does
not support FIP. Which command will be useful in troubleshooting this issue?
A.
show platform fcoe_mgr info interface vfc id
B.
show platform fcoe_mgr info software interface vfc id
C.
show platform software fcoe_mgr info interface vfc id
D.
show platform software interface fcoe_mgr info vfc id
VFC down due to FIP solicitation failure
When the FIP solicitation fails, the VFC goes down.
Possible Cause
Once the first step of FIP VLAN-discovery has succeeded, the host sends FIP solicitations. The switch should respond with FIP advertisements in detail. If the response is not sent or the advertisement is not sent back to the solicitation received, the VFC does not come up. The host continues trying to solicit, but never succeeds.
The following are possible reasons for no response or advertisement:
•No active fabric-provided MAC address exists. (Possible wrong fc-map, etc.)
•Fabric is not available for FLOGI.
•MAC address descriptor may be incorrect. (This is the address the CNA uses as the DMAC when it sends responses.)
Use the show platform software fcoe_mgr info interface vfc command to view the status of the FIP solicitation.
In the output from the command, check for triggered event: [FCOE_MGR_VFC_EV_FIP_VLAN_DISCOVERY];
followed by triggered event: [FCOE_MGR_VFC_EV_FIP_SOLICITATION].
If the solicitation is successful, then triggered event: [FCOE_MGR_VFC_EV_FIP_FLOGI] is displayed.
If the solicitation has failed, then triggered event: [FCOE_MGR_VFC_EV_FIP_FLOGI] is not displayed and no further progress occurs.
Solution
Need to check and ensure that the VSAN is active, the memberships are correct, and that the fabric is available. Also while in NPV mode, check that an active border/NP port is available.
0
0
http://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus5000/sw/troubleshooting/guide/N5K_Troubleshooting_Guide/n5K_ts_fcoe.html
When the connected host does not support FIP, the first step of VLAN-discovery fails based on which VFC is brought up. Use show commands to verify that the three basic TLVs required for FIP are exchanged by DCBX over the bound interface, and that FCOE-MGR is enabled for FIP. The three TLVs are FCoE TLV, PriGrp TLV, and PFC TLV. These three TLVs should be checked for both local and peer values.
Verify the TLVs with the following commands:
•show system internal dcbx info interface
•show platform software fcoe_mgr info interface vfc
0
0