HP Integrity Servers with Microsoft Windows Server 2003 Release Notes v6.1

IP Console Switch use causes screen to blank
Issue You might experience a variable delay where the monitor (or remote session)
connected to the IP Console Switch goes blank when using the reinstallation
media.
One step in the reinstallation process is plug-and-play device discovery. During
this time, drivers are not connected to devices. Without drivers, USB ports
disable their power output. The IP Console Switch relies on this power to transfer
video to the local and remote sessions. After the device discovery is complete,
a driver is connected, power is enabled, and video displays. The blanking time
depends on system configuration, but could take as long as 30 minutes. The
system will appear to hang, but is only going through device discovery.
Servers All Integrity
Workaround Use the command line interface for the most complete view of system status.
The command line is active and displays status at all times prior to video
initialization at power on, and at all times during the system operation. The
command line is accessible through the Management Processor interface.
NOTE: If you have a monitor connected directly to the system, the video does
not go blank.
Management Agents
Error event after firmware update
Issue When a system firmware bundle update is applied on an Integrity server rx6600
using the “HP Integrity Server rx3600/rx6600 System, BMC, iLO-2 MP, FPGA,
and PsoC Firmware Bundle” HP Package, an error event might be logged in
the Windows System Event Log. The The HP Insight Foundation Agent
service hung on starting event is logged because the underlying
baseboard management controller is taking longer to respond to data requests
from the agents service.
Servers rx6600
Workaround The event is logged only once during system reboot following the firmware
update. The Foundation Agent service operation is not affected.
Installation over the same version or older version is unsupported
Issue HP Insight Management Agents installation over the same version or an older
version (downgrading) is not supported. If you attempt to do this, an error code
is returned.
Servers All Integrity
Workaround There is no workaround..
Different port number reported by NIC Agents and NCU
Issue For a single-port network adapter, the port number reported by the NIC Agents
is different from the port number reported by the Network Configuration Utility
(NCU). For NIC Agents, the port number shown is 0 under System
Management Homepage→Network→Controller Information→Port and for
NCU it is 1. This discrepancy is caused by the NIC Agent using a 0-based
numbering scheme, while NCU uses a 1-based numbering scheme. It does not
interfere with the system operation.
Servers All Integrity
Workaround There is no workaround.
28 Release 6.1 Overview