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

System32\cpqmgmt\CqMgServ\hpmgtsvc.ini INI file. Then, restart the
HP Insight Management Service from the Services window.
During the Management Agents installation, if the WBEM Providers are detected
in the system, the Agents installer automatically disables the Windows System
Log logging by modifying the hpmgtsvc.ini file. To re-enable the Agent
logging, remove the semicolon before EVT=hpevtsvc.exe and restart the HP
Insight Management Service.
New events in the System Event Log (SEL)
Issue
When viewing the SEL events from the MP SL viewer, you might see some new
events of type DC or DD.
Servers All Integrity
Workaround
These are informational events. When the system is booted up, a type DC event
entry is generated in the SEL. When the system is gracefully shut down, one or
more type DD event entries are generated in the SEL.
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.
Network Interface Cards (NICs)
Warning message not a cause for concern
Issue At system power-up, you might see a warning message (with a source of b57nd
or e1000) indicating a disconnect. With the A7073A card, Event ID 4 is specified,
and with the A9899A card, Event ID 27.
Servers All Integrity
Workaround This is not an error, but rather a side-effect of the auto-negotiation process used
by the A7073A and A9899A cards. The cards do connect at the end of that
process. You can verify this by going into the Event Viewer, locating the Warning
message, and seeing the Informational message that follows it, indicating a
successful connection (Information Event ID 11 for the A7073A card; Information
Event ID 32 for the A9899A card).
Troubleshooting Common Issues 27