Dell Brocade 825 Brocade Adapters Troubleshooting Guide - Page 35

Device drivers not loading for all adapter instances, Brocade Adapters Installation

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

General adapter problems 2 3. Possible Cause: Adapter port is disabled. Action: Verify port state using the HCM Port Properties dialog box or BCU port --list command. Use BCU port --enable command to enable the port. 4. Possible Cause: Adapter's port speed or topology mismatch with the switch port (HBAs or Fabric Adapter ports configured in HBA mode only). Action: Check the port topology setting on the switch using the Fabric OS portCfgShow command to ensure that Locked L_Port is OFF. Use the portCfgLport command to change the setting to OFF if required. Action: Check the switch port speed using the Fabric OS portCfgShow command to verify that speed is either AUTO or matches the speed of the attached adapter port (for example, the speed setting for both ports is 4 Gbps). Action: Check port speed on the adapter with the BCU port --list or port --query commands to display the current and configured speed. Refer to "Displaying port speed" on page 103 and "Performing a port query" on page 103 for details on using these commands. 5. Possible Cause: Non-Brocade-branded SFP installed (stand-up adapters). If non-Brocade branded SFPs are inserted on the adapter or switch, the port link will not come up. Action: On the switch, execute the Fabric OS switchShow command to verify that "Mod_Inv" (invalid module) does not display for the port state. Action: On the adapter, execute the port --list or port --query BCU commands to verify display in the Sfp field. Refer to "Displaying the port list" on page 103 and "Performing a port query" on page 103. If an unsupported SFP is detected, the Sfp field displays "us" (unsupported SFP) for port --list, and the Media field displays "Unsupported SFP" for port --query. For additional actions and fixes for the port link not coming up, refer to "Verifying Fibre Channel and DCB links (stand-up adapters)" on page 50. 6. Possible Cause: Firmware failure. In most cases this causes a heartbeat failure, and if auto-recovery is enabled, the driver recovers. No corrective action is needed. Action: If link does not recover and BCU port --list command shows fcoe and eth state is link down, download the latest driver package, and then remove and reinstall the package using instructions in the "Software Installation" chapter of the Brocade Adapters Installation and Reference Manual. To download the driver package, perform the following steps: a. Go to the adapters website at www.brocade.com/adapters. b. Navigate to the adapters Downloads page. c. Select your operating system from the Downloads list to display appropriate downloads or download the ISO image. Device drivers not loading for all adapter instances On Windows systems, not all adapter instances have device drivers loaded after a driver update. As a result, some of the adapter instances show up in Device Manager with a yellow bang (yellow circle with explanation point). This is more often seen when there are a large number of adapter instances on the server. Possible Cause: The available memory resources on the server are insufficient to support all adapter instances for the current boot. Brocade Adapters Troubleshooting Guide 11 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
11
53-1002145-01
General adapter problems
2
3.
Possible Cause:
Adapter port is disabled.
Action:
Verify port state using the HCM
Port Properties
dialog box or BCU port --list command.
Use BCU
port --enable
command to enable the port.
4.
Possible Cause:
Adapter’s port speed or topology mismatch with the switch port (HBAs or
Fabric Adapter ports configured in HBA mode only).
Action:
Check the port topology setting on the switch using the Fabric OS
portCfgShow
command to ensure that Locked L_Port is OFF. Use the
portCfgLport
command to change the
setting to OFF if required.
Action:
Check the switch port speed using the Fabric OS
portCfgShow
command to verify that
speed is either AUTO or matches the speed of the attached adapter port (for example, the
speed setting for both ports is 4 Gbps).
Action:
Check port speed on the adapter with the BCU
port --list
or
port --query
commands to
display the current and configured speed. Refer to
“Displaying port speed”
on page 103 and
“Performing a port query”
on page 103 for details on using these commands.
5.
Possible Cause:
Non-Brocade-branded SFP installed (stand-up adapters). If non-Brocade
branded SFPs are inserted on the adapter or switch, the port link will not come up.
Action:
On the switch, execute the Fabric OS
switchShow
command to verify that “Mod_Inv”
(invalid module) does not display for the port state.
Action:
On the adapter, execute the
port --list
or
port --query
BCU commands to verify display in
the
Sfp
field. Refer to
“Displaying the port list”
on page 103 and
“Performing a port query”
on
page 103. If an unsupported SFP is detected, the
Sfp
field displays “us” (unsupported SFP) for
port --list
, and the
Media
field displays “Unsupported SFP” for
port --query
.
For additional actions and fixes for the port link not coming up, refer to
“Verifying Fibre Channel
and DCB links (stand-up adapters)”
on page 50.
6.
Possible Cause:
Firmware failure. In most cases this causes a heartbeat failure, and if
auto-recovery is enabled, the driver recovers. No corrective action is needed.
Action:
If link does not recover and BCU
port --list
command shows fcoe and eth state is
link
down
, download the latest driver package, and then remove and reinstall the package using
instructions in the “Software Installation” chapter of the
Brocade Adapters Installation and
Reference Manual
. To download the driver package, perform the following steps:
a.
Go to the adapters website at
www.brocade.com/adapters
.
b.
Navigate to the adapters
Downloads
page.
c.
Select your operating system from the
Downloads
list to display appropriate downloads or
download the ISO image.
Device drivers not loading for all adapter instances
On Windows systems, not all adapter instances have device drivers loaded after a driver update. As
a result, some of the adapter instances show up in Device Manager with a yellow bang (yellow
circle with explanation point). This is more often seen when there are a large number of adapter
instances on the server.
Possible Cause:
The available memory resources on the server are insufficient to support all
adapter instances for the current boot.