HP BL860c Cli Manual page 8

• Using HP ACU-CLI on HP Integrity cellular servers is slow.
THIS ISSUE WAS FIXED IN THE 8.28 RELEASE.
Using HP ACU-CLI on HP Integrity cellular servers (for example, an rx8640 server is
cell-based) is extremely slow. Operations within hpacucli, such as "ctrl all show"
status can take several minutes to finish. This issue does not occur on non-cellular HP
Integrity servers.
Workaround: Ensure that you allow an adequate amount of time, commensurate with the
storage size of your server, for the operation to complete. Do not attempt to execute additional
commands until the hpacucli operation has finished.
• Rebuild issue when Smart Array 6402 controller is installed in an rx4640 connected to
internal volumes.
THIS ISSUE WAS FIXED IN THE 7.65 RELEASE.
ACU-CLI should perform a rescan of the SCSI bus as a result of running "rescan" or "pd
show all" commands. This in turn should initiate a rebuild of an array after replacement
of a failed drive. The rebuild does not take place as a result of running these commands with
the released version.
Workaround: You can initiate a rescan by exiting and then rerunning HP ACU-CLI, or by
rebooting the system.
• CCISS interface/driver reports inaccurate information on logical volumes.
THIS ISSUE WAS FIXED IN THE 7.65 RELEASE.
Under some circumstances, the CCISS driver can show devices that have not actually been
created. When this happens, a number of different devices are reported to the OS, but there
is actually only one logical volume.
Workaround: You should reboot the system after creating a new logical volume.
• Using HP ACU-CLI from two clients at the same time results in warning messages upon
exiting from one of the clients.
THIS ISSUE WAS FIXED IN THE 7.65 RELEASE.
Workaround: Use only one instance of HP ACU-CLI at a time.
• Unexpected LED behavior under some circumstances.
THIS ISSUE WAS FIXED IN THE 7.65 RELEASE.
All LEDs will go "off" if the customer performs the following steps:
ACUCLI> modify led=on
ACUCLI> pd xxx modify led=off
Workaround: There is no workaround.
• Logical volume status abnormal after powering down OS on some cell-based systems.
THIS ISSUE WAS FIXED IN THE 7.65 RELEASE.
After a cell-based system is powered off using the Linux command "poweroff" or "halt",
the status of logical volumes that have been previously created may show as FAILED. Also
you may be unable to delete the logical volume in question.
Workaround:You must use the management processor to power off the HW partition, then
power on again.
• Logical volume created on rx2620 does not appear on rx7620.
THIS ISSUE WAS FIXED IN THE 7.65 RELEASE.
In some circumstances, logical volumes created on one system do not appear on another
system, even after a system reset.
8