Installation guide

190
EMC Host Connectivity with QLogic Fibre Channel HBAs and CNAs in the Windows Environment
Troubleshooting
Known issues
Be aware of these issues:
◆ QLogic BIOS 1.26 and later for QLA23xx and BIOS 1.79 and later
for QLA22xx adapters allow for multiple Boot Port Name entries
to be configured for high-availability booting after path failures.
Previous BIOS versions do not support this functionality, will
boot only from a single storage array port, and cannot provide
boot capability with path failures.
◆ NTOSKNL BSOD (blue screen) during a link-down event can
cause file system corruption to mounted file systems.
◆ adapter boot BIOS does not support high availability while the
OS is booting. It can handle path failures at boot initialization
time, and after the OS has loaded. Path failures while the OS is
loading will require the host to reboot before successfully
completing the boot process.
◆ Degraded response time as the I/O load approaches storage
system capacity can make the OS appear hung or result in a
NTOSKNL BSOD.
◆ Boot files, Windows system files, and swap space should all be on
the boot LUN. With certain server models, you can use an internal
disk for the page file for stability; however, this might not
increase fault tolerance and might reduce system recovery
options.
◆ Swap space must be available on %SYSTEMROOT% or core dump
will fail.
◆ For Windows 2003 on 64-bit IA64-2 servers, the system no longer
uses an x86-compatible BIOS; therefore, enabling boot-from-array
support with the adapter requires a separate firmware EFI
download.
◆ For servers booting from the array, a Symmetrix out-of-family
microcode load, VNX OE for block, or a CLARiiON FLARE
®
NDU between versions will cause the server to require a reboot.
This occurs because Windows requires a reboot when
characteristics of the boot LUN change. During the NDU process
on EMC storage arrays, the serial number and inquiry VPD data
will change to reflect the new code version. When Windows
performs a rescan and recognizes this change, it assumes a
change has occurred on the boot LUN and will require a reboot.