Cisco N5K-C5010P-BF Troubleshooting Guide - Page 29

Solution Summary, configuration terminal

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 29 highlights

Chapter 2 Troubleshooting FCoE Issues Data Center Bridging Send document comments to [email protected]. • Check for the same values for the FCoE Data Center Bridging and the Type-Length-Value on the host CNA software. • Ensure that the VSAN trunk protocol has been enabled. Use the configuration terminal command to enter into configuration mode and use the trunk protocol enable command to enable the trunking protocol. Solution Summary • Review every feature negotiation result. Use the show system internal dcbx info interface ethernet 1/4 command. (For releases earlier than 4.2(1)N1, use the sh platform software dcbx internal info interface ethernet x/y command.) Example: switch# show system internal dcbx info interface ethernet 1/4 feature type 3 sub_type 0 feature state variables: oper_version 0 error 0 oper_mode 1 feature_seq_no 0 remote_feature_tlv_present 1 remote_tlv_not_present_notification_sent 0 remote_tlv_aged_out 0 feature register params max_version 0, enable 1, willing 0 advertise 1, disruptive_error 0 mts_addr_node 0x101mts_addr_sap 0x1e5 Desired config cfg length: 1 data bytes:08 Operating config cfg length: 1 data bytes:08 • Errors - Indicates negotiation error. - Never expected to happen when connected to CNA. - When two Nexus 5000 switches are connected back-to-back, and if PFC is enabled on different CoS values, then a negotiation error can occur. • Operating configuration - Indicates negotiation result. - Absence of operating configuration indicates that the peer does not support the DCBX TLV or that there is a negotiation error. - The remote_feature_tlv_present message indicates whether the remote peer supports this feature TLV or not. • DCBX feature might not be working because: - Peer does not support the LLDP Protocol. - Peer does not support the DCBX Protocol. - Peer does not support some DCBX TLVs. - Unexpected DCBX negotiation result. • An option exists to force PFC mode on an interface. Use the inerfacet ethernet 1/21 command and the priority-flow-control mode command to force the PFC mode. Example: switch(config)# int eth1/21 switch(config-if)# priority-flow-control mode ? OL-25300-01 Cisco Nexus 5000 Series Troubleshooting Guide 2-5

  • 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-5
Cisco Nexus 5000 Series Troubleshooting Guide
OL-25300-01
Chapter 2
Troubleshooting FCoE Issues
Data Center Bridging
•
Check for the same values for the FCoE Data Center Bridging and the Type-Length-Value on the
host CNA software.
•
Ensure that the VSAN trunk protocol has been enabled.
Use the
configuration terminal
command to enter into configuration mode and use the
trunk
protocol enable
command to enable the trunking protocol.
Solution Summary
•
Review every feature negotiation result.
Use the
show system internal dcbx info interface ethernet 1/4
command.
(For releases earlier than 4.2(1)N1, use the
sh platform software dcbx internal info interface
ethernet x/y
command.)
Example:
switch# show system internal dcbx info interface ethernet 1/4
feature type 3 sub_type 0
feature state variables: oper_version 0 error 0 oper_mode 1 feature_seq_no 0
remote_feature_tlv_present 1
remote_tlv_not_present_notification_sent 0 remote_tlv_aged_out 0
feature register params max_version 0, enable 1, willing 0 advertise 1,
disruptive_error 0 mts_addr_node
0x101mts_addr_sap 0x1e5
Desired config cfg length: 1 data bytes:08
Operating config cfg length: 1 data bytes:08
•
Errors
–
Indicates negotiation error.
–
Never expected to happen when connected to CNA.
–
When two Nexus 5000 switches are connected back-to-back, and if PFC is enabled on different
CoS values, then a negotiation error can occur.
•
Operating configuration
–
Indicates negotiation result.
–
Absence of operating configuration indicates that the peer does not support the DCBX TLV or
that there is a negotiation error.
–
The remote_feature_tlv_present message indicates whether the remote peer supports this
feature TLV or not.
•
DCBX feature might not be working because:
–
Peer does not support the LLDP Protocol.
–
Peer does not support the DCBX Protocol.
–
Peer does not support some DCBX TLVs.
–
Unexpected DCBX negotiation result.
•
An option exists to force PFC mode on an interface.
Use the
inerfacet ethernet 1/21
command and the
priority-flow-control mode
command to force
the PFC mode.
Example:
switch(config)# int eth1/21
switch(config-if)# priority-flow-control mode ?