Cisco N5K-C5010P-BF Troubleshooting Guide - Page 66

PFC, Link pause (flow control) not enabled on back to back Nexus 5000 switch links

Page 66 highlights

Chapter 4 Troubleshooting QoS Issues PFC Send document comments to [email protected]. switch# PFC Link pause (flow control) not enabled on back to back Nexus 5000 switch links When link pause (flow control) is not enabled on back-to-back Nexus 5000 switch links, packets are dropped while sending traffic on a no-drop class. Possible Cause If the peer Nexus 5000 switch supports PFC TLV with DCBX, then configuring flowcontrol send on and flowcontrol receive on will not enable the link pause. You have to disable the PFC TLV sent by DCBX on that interface. Use one of the following commands to verify: • Use the show interface ethx/y flowcontrol command and check to see if the operating state is off. • Use the show interface ethx/y priority-flow-control command and check to see if the operating state is on. Solution Configure the following commands under interface ethx/y to enable link pause instead of PFC on backto-back switch links. • no priority-flow-control mode on • flowcontrol receive on • flowcontrol send on Cannot enable "pause no-drop" on more than one ethernet class Cannot enable pause no-drop on more than one Ethernet class. CLI commands fail with the following error when trying to enable pause no-drop. ERROR: Module 1 returned status "Not enough buffer space available. Please change your configuration and re-apply" Possible Cause Nexus 5000 supports a maximum of three no drop classes (including FCoE). If five Ethernet classes are created, then there will be insufficient buffers to enable twoof the five Ethernet no-drop classes. You will get an error if not enough buffers exist to enable the no-drop. Example: class type network-qos s4 pause no-drop ERROR: Module 1 returned status "Not enough buffer space available. Please change your configuration and re-apply" Solution Cisco Nexus 5000 Series Troubleshooting Guide 4-8 OL-25300-01

  • 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].
4-8
Cisco Nexus 5000 Series Troubleshooting Guide
OL-25300-01
Chapter 4
Troubleshooting QoS Issues
PFC
switch#
PFC
Link pause (flow control) not enabled on back to back Nexus 5000 switch links
When link pause (flow control) is not enabled on back-to-back Nexus 5000 switch links, packets are
dropped while sending traffic on a no-drop class.
Possible Cause
If the peer Nexus 5000 switch supports PFC TLV with DCBX, then configuring
flowcontrol send on
and
flowcontrol receive on
will not enable the link pause. You have to disable the PFC TLV sent by
DCBX on that interface.
Use one of the following commands to verify:
Use the
show interface ethx/y flowcontrol
command and check to see if the operating state is off.
Use the
show interface ethx/y priority-flow-control
command and check to see if the operating
state is on.
Solution
Configure the following commands under
interface ethx/y
to enable link pause instead of PFC on back-
to-back switch links.
no priority-flow-control mode on
flowcontrol receive on
flowcontrol send on
Cannot enable “pause no-drop” on more than one ethernet class
Cannot enable pause no-drop on more than one Ethernet class.
CLI commands fail with the following error when trying to enable pause no-drop.
ERROR:
Module 1 returned status "Not enough buffer space available. Please change your
configuration and re-apply"
Possible Cause
Nexus 5000 supports a maximum of three no drop classes (including FCoE). If five Ethernet classes are
created, then there will be insufficient buffers to enable twoof the five Ethernet no-drop classes.
You will get an error if not enough buffers exist to enable the no-drop.
Example:
class type network-qos s4
pause no-drop
ERROR:
Module 1 returned status "Not enough buffer space available. Please change your
configuration and re-apply"
Solution