Home » HP Manuals » Servers » HP Integrity Superdome SX2000 » Manual Viewer

HP Integrity Superdome SX2000 HP Integrity Servers with Microsoft Windows Serv - Page 18

Troubleshooting Common Issues

View all HP Integrity Superdome SX2000 manuals

Add to My Manuals
Save this manual to your list of manuals

Page 18 highlights

BL860c and BL870c Server Blade Table 1-7 Components supported with BL860c and BL870c Operating System • Windows Server 2003, Enterprise Edition with SP2 for Itanium-based Systems • Windows Server 2003, Datacenter Edition with SP2 for Itanium-based Systems I/O Mezzanine Support • Dual Port 4 Gb/s FC Mezzanine Card (Q-Logic) (403619-B21) • 8 Gigabit Mezzanine FC HBA (Emulex) (456972-B21) • 8 Gigabit Mezzanine FC HBA (QLogic) (451871-B21) • Emulex LPe1105-HP 4 Gb FC HBA (403621-B21) • Direct Adaptor Mezzanine Card for connecting to the Direct Attached Storage Blade (431643-B21) • PCI Express Quad Port Gigabit Mezzanine NIC (NC364M) (447883-B21) • PCI Express Dual Port Gigabit Mezzanine NIC (NC360m) (445978-B21) • P700m Smart Array Mezzanine Card (451017-B21) Graphic Console • TFT7600 Rack Mount Keyboard Monitor (all versions) Troubleshooting Common Issues Read this section completely before installing or running Windows Server 2003 on HP Integrity servers. This section includes workarounds that may save you valuable time and effort. Array Configuration Utility (ACU) Verifer.exe causes ACU inaccuracies Issue ACU reports incorrect results when the Windows Driver Verifier (Verifier.exe) is enabled and running in the background. Servers All Integrity Workaround There is no workaround at this time. To run the ACU, you must first end the Verifier.exe process using the Windows Task Manager, then launch ACU. Do not run both simultaneously. Array Diagnostic Utility (ADU) Uninstall feature not functional Issue The ADU uninstall feature is not working. Servers All Integrity Workaround There is no workaround at this time. Clustering Cluster nodes unable to see messages Issue Typically, events reported to the Windows Event Log are visible to all nodes connected to the cluster. However, because of a Microsoft limitation, when an event with more than 896 bytes in the data field is reported, only the cluster node that reported the event can see it. Other nodes in the cluster are unable to see this event. Servers All Integrity servers Workaround There is no workaround at this time. 18 Release 6.2 Overview

Section	Page
Release Notes	1
Table of Contents	3
About This Document	7
Typographic Conventions	7
HP Encourages Your Comments	7
1 Release 6.2 Overview	9
What’s New in Windows Solution 6.2?	9
System Configurations	10
Software Requirements	12
Web Browser	12
TCP/IP and SNMP	12
Utility Meter	12
Supported Components	12
Superdome (with sx2000 chipset)	12
rx8640	13
rx7640	14
rx6600	15
rx3600	16
rx2660	17
BL860c and BL870c Server Blade	18
Troubleshooting Common Issues	18
Array Configuration Utility (ACU)	18
Verifer.exe causes ACU inaccuracies	18
Array Diagnostic Utility (ADU)	18
Uninstall feature not functional	18
Clustering	18
Cluster nodes unable to see messages	18
Device Drivers	19
Missing driver affects Virtual Machines	19
Drivers missing from Microsoft media	19
Driver roll back causes crash	19
prlntss.sys installation issue	19
Extensible Firmware Interface (EFI) and EFI-based Setup Utility (EBSU)	20
I/O card firmware values display as unknown	20
QLogic HBA firmware and EFI driver revisions display incorrectly	20
EBSU displays incorrect firmware version	20
EBSU fails when flashing an Emulex 4 Gb HBA	21
ESBU can lose mapping of drives connected to QLogic controllers	21
Express Setup fails when launched from EBSU	21
Fibre Channel	21
Error message during system boot	21
Target LUN and boot controller WWN not visible in a VC environment	21
Inapplicable errors seen in kit update	22
Redundant entries seen in the Add/Remove Program	22
Emulex HBAs use different driver	22
MSA fails with Storport driver installed	22
LUNs undetected by ACU	23
HBA removal fails	23
HPSUM hangs on MSA 1500 boot	23
Hard Disk Configuration	23
Disk configuration lost after reboot	23
HP c-Class Blade System Infrastructure	23
Onboard Administrator displays wrong CPU	23
HP Smart Update Manager	24
hpsum_swdiscovery.exe Application Error	24
Baseboard Management Controller IPMI device driver not displayed in HP-SUM	24
HPVM	24
Patches required on virtual machine guests	24
Installation	24
Attempting installation from a second DVD drive results in system message	24
Installation from graphics console might require additional steps	25
Component time outs cause installation failure	25
Screen is blank at system startup	25
Maximum Payload Size parameter must be off	25
Use Esc+8 instead of F8 key on headless server	25
Custom Install option disables Remote Desktop	26
Management Agents	26
Error event after firmware update	26
Management Agents and WBEM Providers log the same event	26
New events in the System Event Log (SEL)	27
Installation over the same version or older version is unsupported	27
Different port number reported by NIC Agents and NCU	27
Network Interface Cards (NICs)	27
Warning message not a cause for concern	27
Power Management	28
PAL_HALT_LIGHT disables idle power state	28
PAL_HALT_LIGHT status not displayed in HP-SUM, VCRM, and SMS	28
PXE boot on Intel Dual Core Itanium systems	28
Patch required to enable PXE boot	28
SCSI	28
Ultra 320 firmware update fails	28
Event log entry caused by timeout condition	29
Smart Array	29
640x/530x generates errors in system event log	29
6402 as internal disk drive controller generates errors	29
StorageWorks 43xx enclosures might cause errors	29
Configuration utility might be inaccessible	29
Tools menu radio buttons inactive	30
640x/530x might not load during system boot	30
640x/530x do not rebuild the internal HDD	30
640x hot add not supported	31
6400 cannot be hot-replaced during error message display	31
Command causes machine check abort	31
System Management Homepage (SMH)	31
Software Information page in SMH is blank	31
Components flagged with red exclamation mark	32
SMH fails to open	32
Program terminates after error message	32
Version Control	32
Some HP Integrity servers marked as non-compliant by Microsoft System Management Server	32
Baseboard Management Controller IPMI device driver not displayed in VCA	33
VCRM unsupported components	33
VCRM fails to start	33
VCRM updates wrong support pack	33
Inaccurate VGA information displayed	34
Video	34
Video not displayed	34
vKVM and vMedia	34
Tool bar fails to redraw as expected	34
vMedia drive not immediately accessible	34
vKVM session stops updating	34
2 Installing Windows Server 2003	37
Preinstallation Tasks	37
Installation Tasks	37
Post-Installation Tasks	38
Tips and Tricks	38
3 Product Support	41
Technical Documentation	41
Technical Support	42
Get Windows-specific firmware, drivers, and utilities	42

Match case Limit results 1 per page

BL860c and BL870c Server Blade

Table 1-7 Components supported with BL860c and BL870c

•

Windows Server 2003, Enterprise Edition with SP2 for Itanium-based Systems

•

Windows Server 2003, Datacenter Edition with SP2 for Itanium-based Systems

Operating System

•

Dual Port 4 Gb/s FC Mezzanine Card (Q-Logic) (403619-B21)

•

8 Gigabit Mezzanine FC HBA (Emulex) (456972-B21)

•

8 Gigabit Mezzanine FC HBA (QLogic) (451871-B21)

•

Emulex LPe1105-HP 4 Gb FC HBA (403621-B21)

•

Direct Adaptor Mezzanine Card for connecting to the Direct Attached Storage Blade

(431643-B21)

•

PCI Express Quad Port Gigabit Mezzanine NIC (NC364M) (447883-B21)

•

PCI Express Dual Port Gigabit Mezzanine NIC (NC360m) (445978-B21)

•

P700m Smart Array Mezzanine Card (451017-B21)

I/O Mezzanine

Support

•

TFT7600 Rack Mount Keyboard Monitor (all versions)

Graphic Console

Troubleshooting Common Issues

Read this section completely before installing or running Windows Server 2003 on HP Integrity

servers. This section includes workarounds that may save you valuable time and effort.

Array Configuration Utility (ACU)

Verifer.exe causes ACU inaccuracies

Issue

ACU reports incorrect results when the Windows Driver Verifier

(

Verifier.exe

) is enabled and running in the background.

Servers

All Integrity

Workaround

There is no workaround at this time. To run the ACU, you must first end the

Verifier.exe

process using the Windows Task Manager, then launch ACU.

Do not run both simultaneously.

Array Diagnostic Utility (ADU)

Uninstall feature not functional

Issue

The ADU uninstall feature is not working.

Servers

All Integrity

Workaround

There is no workaround at this time.

Clustering

Cluster nodes unable to see messages

Issue

Typically, events reported to the Windows Event Log are visible to all nodes

connected to the cluster. However, because of a Microsoft limitation, when an

event with more than 896 bytes in the

data

field is reported, only the cluster

node that reported the event can see it. Other nodes in the cluster are unable to

see this event.

Servers

All Integrity servers

Workaround

There is no workaround at this time.

Release 6.2 Overview