Dell Brocade 825 Brocade Adapters Troubleshooting Guide - Page 69

Disk I/O requests cause low throughput and high latency on Linux, DCB network problems

Get Dell Brocade 825 PDF manuals and user guides View all Dell Brocade 825 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 69 highlights

DCB network problems 2 Disk I/O requests cause low throughput and high latency on Linux If a high number of I/O requests is causing low throughput and high latency on Linux systems, refer to the following descriptions of possible causes and recommended actions to help resolve the problem. Possible Cause: The maximum input/output operations per second are too low on Linux hosts. Action: Refer to "Linux tuning" on page 113 for suggestions to optimize adapter performance in Linux systems. Disk I/O requests cause low throughput and high latency on VMware If a high number of I/O requests is causing low throughput and high latency on VMware systems, refer to the following descriptions of possible causes and recommended actions to help resolve the problem. Possible Cause: The maximum input/output operations per second are too low on VMware hosts. Action: Refer to "VMware tuning" on page 116 for suggestions to optimize adapter performance in VMware systems. DCB network problems NOTE This issue applies to CNAs and Fabric Adapter ports configured in CNA mode only. This section provides information to resolve problems of adapter operation on the Data Center Bridging (DCB) network. For additional information on troubleshooting problems on mezzanine card or expansion card adapters, refer to "Troubleshooting mezzanine card problems" on page 55. DCB is not enabled The DCB state does not show "DCB Linkup" when you run the BCU port --query command. 1. Possible Cause: The link between the adapter port and switch is down. Action: Run the dcb --query command for the port to gain a better understanding of LLDP attributes, DCB maps, and priority tables configured for the port. Also check the error reason code for the DCB link failure. The error reason code will tell you why the DCB is not enabled or active. If the error reason is "Physical Link down," refer to "Port link is not active" on page 10 and "Verifying Fibre Channel and DCB links (stand-up adapters)" on page 50. 2. Possible Cause: Adapter did not receive DCB configuration or received invalid DCB configuration from the FCoE switch. Action: Run the BCU dcb --query command for the port to gain a better understanding of LLDP attributes and DCB configuration (such as DCB maps and priority tables) configured for the port. Also check for the error reason code for the DCB link failure. The reason code will tell you why the DCB is not enabled or active. Change or fix the DCB configuration at the switch appropriately based on the displayed error reason code. Brocade Adapters Troubleshooting Guide 45 53-1002145-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
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
Brocade Adapters Troubleshooting Guide
45
53-1002145-01
DCB network problems
2
Disk I/O requests cause low throughput and high latency on Linux
If a high number of I/O requests is causing low throughput and high latency on Linux systems, refer
to the following descriptions of possible causes and recommended actions to help resolve the
problem.
Possible Cause:
The maximum input/output operations per second are too low on Linux hosts.
Action:
Refer to
“Linux tuning”
on page 113 for suggestions to optimize adapter performance in
Linux systems.
Disk I/O requests cause low throughput and high latency on VMware
If a high number of I/O requests is causing low throughput and high latency on VMware systems,
refer to the following descriptions of possible causes and recommended actions to help resolve the
problem.
Possible Cause:
The maximum input/output operations per second are too low on VMware hosts.
Action:
Refer to
“VMware tuning”
on page 116 for suggestions to optimize adapter performance in
VMware systems.
DCB network problems
NOTE
This issue applies to CNAs and Fabric Adapter ports configured in CNA mode only.
This section provides information to resolve problems of adapter operation on the Data Center
Bridging (DCB) network. For additional information on troubleshooting problems on mezzanine card
or expansion card adapters, refer to
“Troubleshooting mezzanine card problems”
on page 55.
DCB is not enabled
The DCB state does not show “DCB Linkup” when you run the BCU
port --query
command.
1.
Possible Cause:
The link between the adapter port and switch is down.
Action:
Run the
dcb --query
command for the port to gain a better understanding of LLDP
attributes, DCB maps, and priority tables configured for the port. Also check the error reason
code for the DCB link failure. The error reason code will tell you why the DCB is not enabled or
active. If the error reason is “Physical Link down,” refer to
“Port link is not active”
on page 10
and
“Verifying Fibre Channel and DCB links (stand-up adapters)”
on page 50.
2.
Possible Cause:
Adapter did not receive DCB configuration or received invalid DCB
configuration from the FCoE switch.
Action:
Run the BCU
dcb --query
command for the port to gain a better understanding of LLDP
attributes and DCB configuration (such as DCB maps and priority tables) configured for the
port. Also check for the error reason code for the DCB link failure. The reason code will tell you
why the DCB is not enabled or active. Change or fix the DCB configuration at the switch
appropriately based on the displayed error reason code.