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

FIP
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 .
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.
VFC down because VLAN response not received by CNA
Though the switch sends out a VLAN response, the response is not received by the CNA. This indicates
that the VFC is down.
Possible Cause
A bound interface native VLAN ID should be a non-FCoE VLAN. If not, and the native VLAN matches
the FCoE VLAN, the VLAN response sent out will be untagged. However, the FIP adapters expect
tagged frames. This means that the native VLAN on the trunk interface should be a non-FCoE VLAN.
Solution
Check the configuration on the bound Ethernet trunk interface and ensure that it is a non-FCoE native
VLAN.
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.
VFC down due to FIP keepalive misses
The VFC goes down due to FIP keepalive misses.
Possible Cause
When FIP keepalives (FKA) are missed for a period of approximately 22 seconds, this means that
approximately three FKAs are not continuously received from the host. Missed FKAs can occur for
many reasons, including congestion or link issues.
Cisco Nexus 5000 Series Troubleshooting Guide
2-8
Chapter 2 Troubleshooting FCoE Issues
OL-25300-01