HP Integrity rx8640 HP Integrity Servers with Microsoft Windows Server 2008 R2 - Page 18

Extensible Firmware Interface (EFI) and EFI-based Setup Utility (EBSU) I/O card firmware values display as unknown Issue The EBSU Maintain Firmware feature displays some I/O card firmware values as unknown in the Local version column. This occurs when the card firmware does not return a data structure that EBSU recognizes because the card firmware is configured for 32-bit systems, it lacks an EFI driver, or has corrupted firmware. Servers All Integrity Workaround Flash the card firmware to correct the problem. If the card still has unknown values after flashing it and resetting the system, contact your local support specialist or visit http://www.hp.com/support/itaniumservers for help. Express Setup fails when launched from EBSU Issue The OS installer fails when launched by EBSU if the DVD drive is attached to a U320 controller. Servers All Integrity Workaround 1. Exit EBSU. 2. Put the OS media in the DVD drive. 3. From the EFI Shell, issue the reconnect -r command followed by the map -r command. 4. Run the OS installer. Fibre Channel Event ID 129 messages with QLogic 8 GB HBAs Issue On HP Integrity systems with QLogic 8 GB HBAs (451871-B21, AH400A, and AH401A) using version 9.1.8.17 of the driver, excessive Event ID 129 messages could result in slow system performance or a system crash. The supported driver is not on the Smart Setup 6.5 solution. Servers All Integrity Workaround Download the 9.1.8.19 or later version of the driver from http://www.hp.com. Error message during system boot Issue On a system with an Emulex LPe1205-HP 8 Gb Mezzanine card, during system boot, a VOLTAGE_DEGRADES_TO_NON_RECOVERABLE message is posted in the System Event Log (SEL). You can view this message with the SL command under the MP menu. Servers HP Integrity BL860c Server Blade and BL870c Server Blade Workaround This is only an alert message. The function and performance on the Mezzanine card are not adversely affected. No actions are needed. Mixing Fibre Channel HBA models within same system might cause a blue screen Issue Mixing HBA cards from different vendors with different I/O maximum transfer packet sizes in a Multipath I/O (MPIO) configuration on the same server can cause a blue screen with Stopcode 0x000000D1 and a reference to elxstor.sys. Servers All Integrity Workaround Do not mix HBAs from different vendors in the same server configuration in an MPIO environment. 18 Release 6.5 Overview