Home » Dell Manuals » Hubs & Switches » Dell Brocade 825 » Manual Viewer

Dell Brocade 825 Brocade Adapters Troubleshooting Guide - Page 50

Cannot boot over SAN from installed CNAs or Fabric Adapters - hp

Add to My Manuals
Save this manual to your list of manuals

Page 50 highlights

2 General adapter problems d. Download the dud from the "Driver Update Disks (DUDs)" area. 2. Possible Cause: Missing or improper storage array LUN mask setting. Action: Check LUN mapping and masking using the storage array configuration applications. 3. Possible Cause: Missing or improper storage array LUN mask setting. Action: Check LUN mapping and masking using storage array configuration tools. 4. Possible Cause: Adapter driver not loaded. Action: The adapter driver may not be loaded. Refer to "Adapter driver installation verification" on page 51 for methods to verify driver installation. Cannot boot over SAN from installed CNAs or Fabric Adapters You cannot boot over SAN from CNAs or Fabric Adapter ports configured in CNA mode. However, you can boot from HBAs or Fabric Adapter ports configured in HBA mode installed on the same system. Possible Cause: A maximum of four boot LUNs are exported to the system. Boot LUNs connected through HBAs and Fabric Adapter ports configured in HBA mode take precedence over boot LUNs connected through CNAs or Fabric Adapter ports configured in CNA mode. If all four boot LUNs are connected through HBAs or Fabric Adapter HBA ports, boot over SAN will not occur through installed CNAs or Fabric Adapter CNA ports. Action: If you want to boot over SAN through a CNA or Fabric Adapter port configured in CNA mode, disable BIOS on all installed HBAs. To disable BIOS, use BCU commands, the BIOS configuration utility, or HCM. Refer to the "Boot Code" chapter in the Brocade Adapters Installation and Reference Manual for instructions. Boot from SAN may stop on some Hewlett Packard hosts The boot process may stop on some Hewlett Packard systems, such as the HP DL180, and the following message displays. 02a2: BMC System Error Log (SEL) Full` /Press F1 to Continue, Press F2 to Setup/ Possible Cause: The System Event Log may become full of erroneous IPMI (intelligent platform management interface) events reported by the system BIOS. Action: Perform the following steps. 1. Boot the server and press F10 when prompted to run BIOS Setup. 2. Select the Advanced menu. 3. Scroll down to IPMI and press Enter. 4. Scroll down to the System Event Log selection and press Enter. 5. At the Clear System Event Log selection, press Enter to toggle between Enable and Disable. 6. Select Enable. 7. Press F10 to save the changes and exit the BIOS Setup. 26 Brocade Adapters Troubleshooting Guide 53-1002145-01

Section	Page
About this Document	11
In this chapter	11
How this document is organized	11
Host operating system support for adapter drivers	14
Host operating system support for HCM	16
What’s new in this document	17
Document conventions	18
Notice to the reader	19
Additional information	20
Providing details for support	21
Document feedback	23
Introduction to Troubleshooting	25
In this chapter	25
How to use this manual for troubleshooting	25
Gathering problem information	27
Isolating Problems	29
In this chapter	29
How to use this chapter	29
General adapter problems	33
Adapter not reported under server’s PCI subsystem	33
No adapters reported though BCU adapter --list command	34
Port link is not active	34
Device drivers not loading for all adapter instances	35
Installer program does not autorun	36
Host system freezes or crashes	36
Operating system errors (blue screen)	37
Driver event messages appearing in host system log files	37
BCU version mismatch warning	38
Errors or problems when entering BCU commands	38
bcu pcifn --list and vhba --query commands return errors	38
I/O data traffic issues	39
Support Save file is too large (Windows only)	39
Host system running Microsoft Windows fails to hibernate	40
Driver incompatible with CNA drivers	40
Brocade BCU desktop shortcut missing (Windows only)	40
Driver installation fails and system cannot be booted	41
Cannot remove Linux driver with uninstaller application or scripts	41
Removing Ethernet (network) drivers causes error	41
Files needed for bfad.sys message appears	42
Cannot roll back driver on all adapter instances using Device Manager	42
Device drivers not loading due to lack of MSI-X interrupt vectors	42
Driver installation fails on ESX systems	43
Errors when using GUI-based software installer	43
Errors when installing brocade_driver_linux_<versions>.tar.gz package	43
UEFI boot problems	44
BIOS boot problems	47
Fabric Adapter problems	51
VLANs and teams persist after changing port to HBA mode	51
HCM not discovering all Ethernet ports for vNICs	52
HBA problems	52
No adapters found on local host” message in HCM	52
Quality of Service performance issues	52
Quality of Service not functioning	53
Trunking problems	53
Unable to create more than 126 Virtual (NPIV) ports for adapter	54
CNA problems	55
Cannot manage CNAs after attempting upgrade to 3.0 drivers	55
VMQs not created for virtual network adapter instances	55
Network interface problems (CNA or NIC)	56
Ethernet loopback test problems	56
Ethernet link ports or LOM not coming up on reboot in Linux	57
Loss of adapter hardware address in Linux	57
Loss of adapter IP address in Linux	57
Network stack runs out of heap	58
NIC numbering unexpected on VMware systems	58
Ping to remote host is failing	58
Receive-side scaling disables unexpectedly	59
Applications using TDI driver stop responding	60
RSS network throughput decreases	60
SNMP MIB browser not displaying information on VLAN-related OIDs	60
Teaming errors	60
VLAN creation and operation problems	61
Teaming or VLAN operations through HCM fail	62
Poor network performance	63
Binding issues after Hyper-V enabled with teaming	63
FCoE and Fibre Channel problems	65
Loss of sync and loss of signal errors in port statistics	65
Fabric authentication failures	65
Adapter is not showing in the fabric	65
Virtual devices not listed in name server	66
Adapter not registering with the name server or cannot access storage	66
FCoE link is down	67
I/O problem on connected FCoE device	68
I/Os are not failing over immediately on path failure in MPIO setup	68
Disk I/O requests cause low throughput and high latency on Linux	69
Disk I/O requests cause low throughput and high latency on VMware	69
DCB network problems	69
DCB is not enabled	69
HCM and HCM Agent problems	70
Failed to connect to agent on host... error when using HCM	70
HCM Agent service cannot start	73
HCM Agent not auto starting if 3.0 driver updated with 2.3 HCM	73
Unable to completely uninstall HCM	73
Time on HCM screens does not match system time	74
Verifying Fibre Channel and DCB links (stand-up adapters)	74
Adapter driver installation verification	75
Confirming driver package installation with HCM	76
Confirming driver package installation in Windows systems	76
Confirming driver package installation in Linux systems	77
Confirming driver package installation in Solaris systems	78
Confirming driver package installation in VMware systems	78
Troubleshooting mezzanine card problems	79
Additional references for isolating problems	80
Tools for Collecting Data	81
In this chapter	81
For detailed information	82
Data to provide technical support	82
Data collection using host system commands	83
Data collection using BCU commands and HCM	85
Support Save	85
Using BCU commands	89
Data collection using Fabric OS commands (Brocade switches only)	90
Adapter event messages	91
Logs	93
Host system logs	93
HCM logs	94
Logging levels adjustment	95
Statistics	97
Authentication statistics	97
DCB statistics (CNA only)	98
DCB query (CNA only)	99
FCoE statistics (CNA)	99
Fabric statistics	100
Displaying FCP initiator mode statistics	101
FCP initiator mode statistics	101
Firmware statistics	102
I/O performance	103
Logical port statistics	104
Performance data	105
PHY module statistics	105
Port Performance	106
Port statistics	106
Real-time and historical performance statistics	107
Remote port statistics	108
Quality of Service statistics (HBA)	109
Trunking attributes	109
vHBA statistics	110
vNIC statistics (CNA or NIC)	110
Virtual port statistics	111
VLAN statistics for a team (CNA and NIC)	112
VLAN statistics for a port (CNA and NIC)	113
Diagnostics	113
Beaconing (stand-up adapters)	113
Internal and external loopback tests	114
Ethernet port loopback test (CNA)	115
PCI loopback test	116
Memory test	117
Pinging Fibre Channel end points	117
Adapter temperature	118
Queue test	118
SCSI test	119
Trace route	119
Echo test	120
Collecting BIOS data	121
Displaying BIOS data through BCU	121
Display BIOS data through HCM	121
Collecting LLDP data (CNA)	121
Collecting SFP data (stand-up adapters)	122
SFP properties	122
Predictive optical monitoring (POM)	122
Collecting port data	123
Displaying port properties	123
Displaying DCB port properties (CNA)	123
Displaying Ethernet port properties (CNA or NIC)	124
Displaying FCoE port properties (CNA)	124
Displaying FC port properties (HBA)	125
Displaying remote port properties	125
Displaying logical port properties	126
Displaying virtual port properties	126
Displaying the port log	126
Displaying the port list	127
Performing a port query	127
Displaying port speed	127
FCP-IM I/O profiling	128
Enabling FCP-IM profile through HCM	128
Collecting teaming information (CNA or NIC)	128
Displaying team data and statistics through HCM	128
Displaying configured team data through BCU	129
Authentication settings	129
Displaying authentication settings through HCM	129
Displaying authentication settings through BCU	130
PHY module data	130
QoS settings (HBA)	130
Determining QoS settings through HCM	131
Target rate limiting settings (HBA)	131
Determining target rate limiting settings through BCU	131
Determining settings through HCM	132
Persistent binding	132
Displaying Persistent Binding settings through BCU	133
Displaying Persistent Binding settings through HCM	133
Adapter properties	133
CNA Properties	133
HBA Properties	134
Adapter queries	135
Performance Optimization	137
In this chapter	137
Tuning storage drivers	137
Linux tuning	137
Solaris tuning	138
Windows tuning	138
VMware tuning	140
Tuning network drivers (CNA or NIC)	140
Windows tuning	140
Linux tuning	141
VMware tuning	141
Solaris tuning	143
Adapter BIOS and Event Message Reference	145
Adapter BIOS messages	145
Adapter driver event messages	146
HCM and Installer Message Reference	151

Match case Limit results 1 per page

Brocade Adapters Troubleshooting Guide

53-1002145-01

General adapter problems

Download the dud from the “Driver Update Disks (DUDs)” area.

Possible Cause:

Missing or improper storage array LUN mask setting.

Action:

Check LUN mapping and masking using the storage array configuration applications.

Possible Cause:

Missing or improper storage array LUN mask setting.

Action:

Check LUN mapping and masking using storage array configuration tools.

Possible Cause:

Adapter driver not loaded.

Action:

The adapter driver may not be loaded. Refer to

“Adapter driver installation verification”

on page 51 for methods to verify driver installation.

Cannot boot over SAN from installed CNAs or Fabric Adapters

You cannot boot over SAN from CNAs or Fabric Adapter ports configured in CNA mode. However,

you can boot from HBAs or Fabric Adapter ports configured in HBA mode installed on the same

system.

Possible Cause:

A maximum of four boot LUNs are exported to the system. Boot LUNs connected

through HBAs and Fabric Adapter ports configured in HBA mode take precedence over boot LUNs

connected through CNAs or Fabric Adapter ports configured in CNA mode. If all four boot LUNs are

connected through HBAs or Fabric Adapter HBA ports, boot over SAN will not occur through

installed CNAs or Fabric Adapter CNA ports.

Action:

If you want to boot over SAN through a CNA or Fabric Adapter port configured in CNA mode,

disable BIOS on all installed HBAs. To disable BIOS, use BCU commands, the BIOS configuration

utility, or HCM. Refer to the “Boot Code” chapter in the

Brocade Adapters Installation and

Reference Manual

for instructions.

Boot from SAN may stop on some Hewlett Packard hosts

The boot process may stop on some Hewlett Packard systems, such as the HP DL180, and the

following message displays.

02a2: BMC System Error Log (SEL) Full`

/Press F1 to Continue, Press F2 to Setup/

Possible Cause

: The System Event Log may become full of erroneous IPMI (intelligent platform

management interface) events reported by the system BIOS.

Action:

Perform the following steps.

Boot the server and press

F10

when prompted to run BIOS Setup.

Select the

Advanced

menu.

Scroll down to

IPMI

and press

Enter

Scroll down to the

System Event Log

selection and press

Enter

At the

Clear System Event Log

selection, press

Enter

to toggle between

Enable

and

Disable

Select

Enable

Press

F10

to save the changes and exit the BIOS Setup.