Cisco N5K-C5010P-BF Troubleshooting Guide - Page 31

FIP, VFC down due to FIP failure, VFC down due to FIP solicitation failure

Get Cisco N5K-C5010P-BF - Nexus 5010 Switch PDF manuals and user guides
UPC - 882658212208
View all Cisco N5K-C5010P-BF manuals
Add to My Manuals
Save this manual to your list of manuals

Page 31 highlights

Chapter 2 Troubleshooting FCoE Issues FIP Send document comments to [email protected]. FIP Note FIP Generation-1 CNAs are not supported on the Nexus 2232 FEX. Only FIP Generation-2 CNAs are 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: • show system internal dcbx info interface • show platform software fcoe_mgr info interface vfc In the output from the commands: • Check for FIP capable is TRUE. • Check for triggered event: [FCOE_MGR_VFC_EV_FIP_VLAN_DISCOVERY]. 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: • 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. OL-25300-01 Cisco Nexus 5000 Series Troubleshooting Guide 2-7

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
Send document comments to [email protected].
2-7
Cisco Nexus 5000 Series Troubleshooting Guide
OL-25300-01
Chapter 2
Troubleshooting FCoE Issues
FIP
FIP
Note
FIP Generation-1 CNAs are not supported on the Nexus 2232 FEX. Only FIP Generation-2 CNAs are
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:
•
show system internal dcbx info interface
<bound-ethernet-interface-id>
•
show platform software fcoe_mgr info interface vfc
<id>
In the output from the commands:
•
Check for FIP capable is TRUE.
•
Check for triggered event: [FCOE_MGR_VFC_EV_FIP_VLAN_DISCOVERY].
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:
•
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
<
id
>
command to view the status of the
FIP solicitation.