HP Insight Dynamics 6.0 Release notes

When prompted to specify whether you want to Cancel or Kill the task, select Kill and OK. This
action will abort auto-calibration of idle/max power and allow the Insight managed system setup
wizard to proceed. After the wizard completes, try running the wizard again, or see the Capacity
Advisor User Guide for alternative instructions about calibrating idle/max power. If time allows,
let the automatically scheduled nightly data collection gather power calibration information for
you.
Instant Capacity Manager
Limitations
Commands executed under privilege elevation may cause Instant Capacity Manager to monitor
but not control managed nodes
Some HP-UX security settings cause output to be generated every time a user is logged in. This
can occur, for example when sudo is used in Systems Insight Manager privilege elevation mode
to execute commands on HP-UX managed nodes, which can generate apparently extraneous
output to stderr. This output may be interpreted by some Instant Capacity (iCAP) Manager
functions executed under privilege elevation as error output from those commands.
When this apparent error output occurs, the affected iCAP Manager functions fail. In this
condition, iCAP Manager can be used only to monitor, and not control, managed nodes configured
in this way.
Suggested action Configure HP-UX managed nodes so that no extraneous output is generated
when the sudo command is executed.
For more information, see the following HP-UX documentation:
• HP-UX 11i Security Containment Administrator’s Guide
• HP-UX System Administrator's Guide: Configuration Management (HP-UX 11i v3)
• HP-UX Servers and Workstations – HP-UX Standard Mode Security Extensions (HP-UX 11i v2)
• the manpage man 4 security (particularly the discussion of DISPLAY_LAST_LOGIN)
Logical server management
Logical server management runs on an x86/x64 Windows CMS.
Limitations
Performing operations on a logical server running as a hypervisor
HP Insight Dynamics supports a logical server that is a physical server (including logical servers
on Virtual Connect whose storage is configured to use a local disk, and logical servers on non-HP
physical servers) running a hypervisor, and supports logical servers that are guest VMs on that
physical server. In order to protect the VM guests from inadvertent operations, a logical server
that is a physical server running a hypervisor has the following restrictions:
• Deactivate, move, power off, and delete operations on the hypervisor logical server are not
supported while there are guest VM logical servers residing on the hypervisor logical server.
You must move the guest VM logical servers off of the hypervisor logical server before
performing any of these operations on the hypervisor logical server.
• Deactivate, move, power off, and delete operations on the hypervisor logical server are not
supported while there are running jobs on a VM guest logical server or on the hypervisor
logical server that could result in creating or leaving a VM guest logical server on the
hypervisor logical server.
28 Issues and suggested actions