Windows Integrity Enterprise Edition Release Notes

Release Notes

Troubleshooting common issues

HP Integrity Servers with Microsoft® Windows® Server 2003, Enterprise Edition

from a U320 controller (embedded or HBA) with the external port connected to

an MSA30 after a fresh OS installation. The problem does not occur if you install

the OS using Reinstall media, or if the U320 is not used as a boot controller.

Workaround Install the driver using the individual smart component only, found on the

Software tab on your Smart Setup Media. Click on the link titled: “HP

StorageWorks Event Notification Driver for Ultra320 SCSI devices for Windows

Server 2003 on Itanium-based Systems”.

all Integrity

servers

The system hangs when flashing smart array controller firmware using the EBSU

Express Setup option

Issue The system may hang while flashing the smart array controller firmware using the

EBSU Express Setup Option.

Workaround Reboot the system if a hang occurs. Verify the firmware updated successfully by

going to the EFI shell and running the saupdate utility available at

\efi\io_cards\smartarray. If the firmware update failed use saupdate to update

the firmware, or use the online smart component to perform the update. Follow

this procedure to update and verify the firmware version:

1. Run saupdate list. This lists all the Smart Array controllers with their

latest firmware version and the segment/bus/device/function for each

controller.

2. Write down the seg/bus/dev/fun information for each controller.

3. Run the command

saupdate update <seg/bus/dev/fun> cyborg.bin.

Run saupdate for more help.

Extensible Firmware Interface (EFI) and EFI-based Setup Utility (EBSU)

rx8620, rx7620 EFI > LANBOOT command does not appear to find the default LAN card

Issue During system boot, entering a LANBOOT command at the EFI prompt produces

an error message stating that a default LAN card cannot be found. This error is

incorrectly displayed because there is no default LAN in a cell-based system.

Because each cell has its own core I/O LAN, the default path can change,

depending on which cells boot and interact. It can also change in order for the

system to boot successfully around failed hardware.

Workaround Use the LANBOOT SELECT command and choose the desired LAN card from the

displayed list.