Limitations of This Release

HP Systems Insight Manager requires each managed system to have a unique name. System information will be reported incorrectly if two systems have the same name, even if they represent the same physical machine. For example, you cannot have an nPartition named the same as a vPars host, even if the vPars host is running on that nPartition. If this situation occurs, you can correct it by renaming one of the partitions using the appropriate command, such as cplxmodify(1M), parmodify(1M), vparmodify(1M), or hpvmmodify(1M). These commands do not require a reboot to change the name.

There is no support for IPv6 in this release of the Virtual Server Environment.

This release of the Virtual Server Environment does not allow the CMS to be made fully HA (High Availability) compliant. To protect against failure of the CMS, HP recommends that the HP SIM database and the VSE Management Database be regularly backed up. For information about backing up the VSE Management Database, see vseinitconfig(1M). Refer to the HP SIM manuals or online help for information about backing up the HP SIM database.

Monitored workloads are not able to track CPU utilization for processes that are in existence for less than five minutes. This behavior is documented in the online help. If you need to track utilization of short-lived processes, use a managed workload. See the Create Monitored Workload help topic for more details.

A system may contain monitored workloads or managed workloads, but may not contain both types of workloads.

Any user that is able to authenticate on the CMS will have the ability to view parked workloads, regardless of whether they have authorizations for any VSE related tools or toolboxes. A workload is “parked” if its container assignment is set to None -- Park the workload in the Monitored Workload Definition Properties screen.