HP Integrity rx2800 HP Integrity Servers with Microsoft Windows Server 2008 R2 - Page 20

Event Log, Extensible Firmware Interface EFI and EFI-based Setup Utility EBSU, Fibre Channel - i2 firmware

Page 20 highlights

Event Log Corrected hardware errors Issue Integrity Servers running Windows Server 2008 R2 might receive Windows Event Log messages describing Corrected Hardware Errors for memory and processor components. These messages from the Microsoft WHEA-LOGGER service can occur several times daily on large memory configurations running under high load. Servers All Integrity Workaround These event log messages do not indicate a problem. The underlying hardware is operating correctly. 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. Windows does not start on Reboot after restoring system image Issue Occasionally, if you use EBSU before restoring the system image to a Fibre Channel boot controller or if only restoring the system image to a Fibre Channel boot controller, the system does not boot to Windows and might do either of the following: • Stop at the EFI prompt • Restart WinPe, if the reinstall DVD is still inserted This occurs because the Windows boot entry is missing from the boot menu. Servers HP Integrity BL8x0 i2 server blades Workaround To create the missing entry, enter the following command at the EFI prompt: EFI_drive_letter:\EFI\Microsoft\Boot\bootmgfw.efi Where EFI_drive_letter: is the mapping of the drive corresponding to the EFI System Partition (for example: fs:). The boot process then continues normally. The bootmgfw command automatically creates the Windows boot entry. 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 7.0 solution. Servers All Integrity Workaround Download the 9.1.8.19 or later version of the driver from http://www.hp.com. 20 Release 7.0 Overview

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30

Event Log
Corrected hardware errors
Issue
Integrity Servers running Windows Server 2008 R2 might receive Windows
Event Log messages describing Corrected Hardware Errors for memory and
processor components. These messages from the Microsoft WHEA-LOGGER
service can occur several times daily on large memory configurations running
under high load.
Servers
All Integrity
Workaround
These event log messages do not indicate a problem. The underlying hardware
is operating correctly.
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/itaniumserv
ers
for help.
Windows does not start on Reboot after restoring system image
Issue
Occasionally, if you use EBSU before restoring the system image to a Fibre
Channel boot controller or if only restoring the system image to a Fibre Channel
boot controller, the system does not boot to Windows and might do either of
the following:
Stop at the EFI prompt
Restart WinPe, if the reinstall DVD is still inserted
This occurs because the Windows boot entry is missing from the boot menu.
Servers
HP Integrity BL8x0 i2 server blades
Workaround
To create the missing entry, enter the following command at the EFI prompt:
EFI_drive_letter:
\EFI\Microsoft\Boot\bootmgfw.efi
Where
EFI_drive_letter:
is the mapping of the drive corresponding to the
EFI System Partition (for example:
fs:
). The boot process then continues
normally. The
bootmgfw
command automatically creates the Windows boot
entry.
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 7.0 solution.
Servers
All Integrity
Workaround
Download the 9.1.8.19 or later version of the driver from
http://www
.hp.com
.
20
Release 7.0 Overview