HP Integrity Superdome SX2000 HP StorageWorks Emulex Fiber Channel HBA Release - Page 9

Boot from SAN issues

Get HP Integrity Superdome SX2000 PDF manuals and user guides View all HP Integrity Superdome SX2000 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 9 highlights

The application failed to initialize because the windows station is shutting down. • Downgrading a version 2.0 or greater STORport driver does not work when initiated via the Smart Component. To downgrade an HP-branded Emulex HBA, 1. Run the Smart Component, containing the desired driver, to extract the contents to a folder. 2. Run the STORport driver installer from the extracted folder using the default values. For example: storportminiportcorekit_2-01a4 This will uninstall the current driver before downgrading to the desired driver version. • When using the Smart Component to install drivers, the following message may appear during reboot. There was a problem installing this hardware. This device is not working properly because Windows cannot load the drivers required for this device. (Code 31) Uninstall and then reinstall your device. Should the above message appear, click Finish. Do not reply to Microsoft and continue with the reboot procedure. No known issue has been observed in connection with the display of this message. Secure Path 4.0c SP1 issues With Secure Path 4.0c SP1, during a rolling driver upgrade, a blue-screen error may occur under any of the following conditions: • Secure Path is not supported on WS2008 or 8Gb HBAs and 8Gb mezzanine cards. • The server boots from a SAN. • All HBAs are accessing their LUNs in a single-path configuration. • The HBA is directly attached in a single path to its own MSA controller. If the blue-screen error occurs, reboot the server and check the driver revisions to verify that the upgrade is complete on all HBAs. Upgrading to Secure Path 4.0c SP2 corrects this problem. SCSIport miniport driver issues On Windows Server 2003 systems, clients may be disconnected, generating Event ID 11 and Event ID 15 in the application log. This problem can occur under high-stress conditions due to a SCSIport miniport driver error. It can also cause network timeouts if remote computers are accessing data on drives that use the SCSIport driver on the Windows Server 2003 system. To correct this problem, install the latest Microsoft QFE from the website: http://support.microsoft.com/default.aspx?scid=kb;en-us;895573 Boot from SAN issues • In a direct connect environment, Boot From SAN fails to boot after adding a second path to an EVA4000/6000/8000 running firmware 6.110. • Boot from SAN on c-Class blade servers fail to boot on an Active/Passive MSA1000/1500 running firmware 5.20. • In Boot from SAN configurations where there are more than two Emulex HBAs in the same zone as the boot HBA, a crash-dump may not be generated due to a time-out condition when the boot HP StorageWorks Emulex fibre channel host bus adapters for ProLiant and Integrity servers using Microsoft Windows and VMware operating systems release notes 9

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
The application failed to initialize because the windows station is
shutting down.
•
Downgrading a version 2.0 or greater STORport driver does not work when initiated via the Smart
Component. To downgrade an HP-branded Emulex HBA,
1.
Run the Smart Component, containing the desired driver, to extract the contents to a folder.
2.
Run the STORport driver installer from the extracted folder using the default values. For ex-
ample:
storportminiportcorekit_2-01a4
This will uninstall the current driver before downgrading to the desired driver version.
•
When using the Smart Component to install drivers, the following message may appear during
reboot.
There was a problem installing this hardware. This device is not working
properly because Windows cannot load the drivers required for this
device. (Code 31)
Uninstall and then reinstall your device.
Should the above message appear, click
Finish
. Do not reply to Microsoft and continue with the
reboot procedure. No known issue has been observed in connection with the display of this mes-
sage.
Secure Path 4.0c SP1 issues
With Secure Path 4.0c SP1, during a rolling driver upgrade, a blue-screen error may occur under
any of the following conditions:
•
Secure Path is not supported on WS2008 or 8Gb HBAs and 8Gb mezzanine cards.
•
The server boots from a SAN.
•
All HBAs are accessing their LUNs in a single-path configuration.
•
The HBA is directly attached in a single path to its own MSA controller. If the blue-screen error
occurs, reboot the server and check the driver revisions to verify that the upgrade is complete on
all HBAs. Upgrading to Secure Path 4.0c SP2 corrects this problem.
SCSIport miniport driver issues
On Windows Server 2003 systems, clients may be disconnected, generating Event ID 11 and Event
ID 15 in the application log. This problem can occur under high-stress conditions due to a SCSIport
miniport driver error. It can also cause network timeouts if remote computers are accessing data on
drives that use the SCSIport driver on the Windows Server 2003 system.
To correct this problem, install the latest Microsoft QFE from the website:
h
t
tp://su
ppo
r
t
.mi
c
r
o
s
o
f
t
.co
m/de
f
a
ult
.a
s
p
x?s
c
i
d=kb;e
n
-u
s;8
9
5
5
7
3
Boot from SAN issues
•
In a direct connect environment, Boot From SAN fails to boot after adding a second path to an
EVA4000/6000/8000 running firmware 6.110.
•
Boot from SAN on c-Class blade servers fail to boot on an Active/Passive MSA1000/1500 running
firmware 5.20.
•
In Boot from SAN configurations where there are more than two Emulex HBAs in the same zone
as the boot HBA, a crash-dump may not be generated due to a time-out condition when the boot
HP StorageWorks Emulex fibre channel host bus adapters for ProLiant and Integrity servers using
Microsoft Windows and VMware operating systems release notes
9