Évaluations - 0, GPA: 0
(
)
)
|
Par ce dispositif a également d'autres instructions :
Ordinateurs - HP ProLiant BL280c Server Blade (691.53 kb)
Ordinateurs - HP ProLiant BL280c Server Blade (728.29 kb)
Ordinateurs - HP ProLiant BL280c Server Blade (686.99 kb)
Ordinateurs - HP ProLiant BL280c Server Blade (731.92 kb)
Facilité d'utilisation
Important notes and recommendations
VMware ESXi 3.5 Update 3 and the HP ProLiant
DL385 G5p Server
There is a defect in the SATA device driver that causes the ProLiant DL385 G5p to hang during boot up.
Removing the DVD Drive from this server enables it to properly boot up.
Do not re-install the DVD Drive until a repaired device driver is installed.
See the Read-This-First card (Part #: 517710-001), which has been added to the server packaging.
An EA/CA is available at the following website
(http://sawpro.atlanta.hp.com/km/saw/view.do?docId=emr_na-c01628011).
Incorrect processor ID might appear
On the Virtual Infrastructure Client configuration page, an incorrect processor ID might be reported for the
processor temperature. For example, Virtual Infrastructure Client might report Temp 7 for Processor 13,
even though the correct processor ID is Processor 2. Virtual Infrastructure Client cannot correctly handle
OEM-specific SDR on some ProLiant servers.
HP SIM might hang
After you select PCI Devices from the Configuration page, HP SIM might hang. To correct this issue,
download the HP SIM 5.3 Hotfix update kit, available at the following website
(http://www.hp.com/go/hpsim).
Collection of Memory Board and Memory Module
properties and health status from a DL785 G5 server
is very slow and could time out
When using HP WBEM providers (version 02.02.06) for ESXi 4.0 on a DL785 G5 server, querying
properties or health status for Memory Boards and Memory Modules properties might cause a time out.
The client software might hang while waiting for the remote ESXi host server to return the requested
information.
This issue might affect other server models when the DIMM slots are fully populated.
Resolution: There is no workaround for this issue.
Important notes and recommendations 4
...