Dell Brocade 825 Brocade Adapters Troubleshooting Guide - Page 39

I/O data traffic issues, Support Save file is too large (Windows only)

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

General adapter problems 2 I/O data traffic issues I/O data traffic issues are occurring, such as an application is not receiving data, FTP problems on an Ethernet network, data is not reaching a target on a Fibre Channel network, or ping failures. 1. Possible Cause: Ethernet traffic problem NOTE This applies to CNAs or Fabric Adapter ports configured in CNA mode. Action: Run the Ethernet loopback serdes test on the suspected Ethernet port using the BCU diag --ethloopback command. This tests internal adapter hardware components. If the test passes, suspect the following external problems: • Faulty fiber • Faulty software • Destination host problem Action: Run the BCU Ethernet external loopback test using the BCU command diag --ethloopback command (stand-up adapters only). Be sure that a loopback connector is installed in the port. If the serdes or internal loopback test passes, but the external test fails, suspect the following problems: • Loopback connector not inserted in transceiver • Faulty SFP or loopback connector. 2. Possible Cause: Fibre Channel or FCoE I/O problems. NOTE This applies to CNAs, HBAs, and Fabric Adapter ports configured in CNA or HBA mode. Action: Run the loopback serdes test on the suspected Fibre Channel port (HBA port) or FCoE port (CNA port) using the BCU diag --loopback -t serdes command. If the test passes, suspect the following external problems: • Faulty fiber • Faulty software • Target problem Action: Run the BCU external loopback test (stand-up adapters only) using the BCU command diag --loopback . Be sure that a loopback connector is installed in the port. If the serdes or internal loopback test passes, but the external test fails, suspect the following problems: • Loopback connector not inserted in transceiver • Faulty SFP or loopback connector. Support Save file is too large (Windows only) The Support Save file is getting too large (it may be larger than 1 Gb). Possible Cause: The hbaagent.log file may be exceeding its maximum size. Action: Delete the larger files, especially hbaAgent.log if it exceeds 10 Mb, in the following location, and then run Support Save again Brocade Adapters Troubleshooting Guide 15 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
15
53-1002145-01
General adapter problems
2
I/O data traffic issues
I/O data traffic issues are occurring, such as an application is not receiving data, FTP problems on
an Ethernet network, data is not reaching a target on a Fibre Channel network, or ping failures.
1.
Possible Cause:
Ethernet traffic problem
NOTE
This applies to CNAs or Fabric Adapter ports configured in CNA mode.
Action:
Run the Ethernet loopback serdes test on the suspected Ethernet port using the BCU
diag --ethloopback
command. This tests internal adapter hardware components. If the test
passes, suspect the following external problems:
•
Faulty fiber
•
Faulty software
•
Destination host problem
Action:
Run the BCU Ethernet external loopback test using the BCU command
diag
--ethloopback
command (stand-up adapters only). Be sure that a loopback connector is
installed in the port. If the serdes or internal loopback test passes, but the external test fails,
suspect the following problems:
•
Loopback connector not inserted in transceiver
•
Faulty SFP or loopback connector.
2.
Possible Cause:
Fibre Channel or FCoE I/O problems.
NOTE
This applies to CNAs, HBAs, and Fabric Adapter ports configured in CNA or HBA mode.
Action:
Run the loopback serdes test on the suspected Fibre Channel port (HBA port) or FCoE
port (CNA port) using the BCU
diag --loopback <port_id> -t serdes
command. If the test passes,
suspect the following external problems:
•
Faulty fiber
•
Faulty software
•
Target problem
Action:
Run the BCU external loopback test (stand-up adapters only) using the BCU command
diag --loopback <port_id> <pattern>
. Be sure that a loopback connector is installed in the port.
If the serdes or internal loopback test passes, but the external test fails, suspect the following
problems:
•
Loopback connector not inserted in transceiver
•
Faulty SFP or loopback connector.
Support Save file is too large (Windows only)
The Support Save file is getting too large (it may be larger than 1 Gb).
Possible Cause:
The hbaagent.log file may be exceeding its maximum size.
Action:
Delete the larger files, especially hbaAgent.log if it exceeds 10 Mb, in the following location,
and then run Support Save again