Cisco N5K-M1600 - Expansion Module - 6 Ports Troubleshooting Manual page 31

Troubleshooting guide
Table of Contents

Advertisement

Chapter 2
Troubleshooting FCoE Issues
S e n d d o c u m e n t c o m m e n t s t o n e x u s 5 k - d o c f e e d b a c k @ c i s c o . c o m .
FIP
FIP Generation-1 CNAs are not supported on the Nexus 2232 FEX. Only FIP Generation-2 CNAs are
Note
supported on the Nexus 2232 FEX.
VFC down due to FIP failure
Host is not capable of supporting FIP-related TLVs.
Possible Cause
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:
In the output from the commands:
The state of the VFC never progresses further to solicitation.
Solution
Make sure you check for correct FIP supporting firmware and drivers on the CNA and FIP supporting
adapters.
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:
Use the show platform software fcoe_mgr info interface vfc<id> command to view the status of the
FIP solicitation.
OL-25300-01
show system internal dcbx info interface <bound-ethernet-interface-id>
show platform software fcoe_mgr info interface vfc<id>
Check for FIP capable is TRUE.
Check for triggered event: [FCOE_MGR_VFC_EV_FIP_VLAN_DISCOVERY].
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.)
Cisco Nexus 5000 Series Troubleshooting Guide
FIP
2-7

Hide quick links:

Advertisement

Table of Contents
loading

Table of Contents