Jump to content United States-English
HP.com Home Products and Services Support and Drivers Solutions How to Buy
» Contact HP
More options
HP.com home
VSE Management Software Release Notes Version A.03.00.01 > Chapter 4 Known Problems and Workarounds

General Virtualization Manager Issues

» 

Technical documentation

Complete book in PDF
» Feedback
Content starts here

 » Table of Contents

 » Index

Incorrect Display After Changing System Type

If a system has been discovered by HP SIM as one type of system, such as an nPartition, and is later changed to be a different type of system, such as a virtual partition, then SIM and Virtualization Manager do not display the system's relationships correctly.

Workaround

For HP SIM 5.0.2.0

Reidentify the system from HP SIM; the subtype should change. You might see an “orphan” system created that you will need to remove after clearing its associated events. Otherwise, you can delete the system from HP SIM and then add it again.

For HP SIM 5.1.0.1 or Later

Reidentify the system from HP SIM. In the case of an nPartition becoming a virtual partition, the system remains a virtual partition type from then on (even when booted in nPars mode). This better defines what the system is configured to be and helps prevent the creation of “orphan” systems.

Cannot Create a Serviceguard Workload When HP SIM Has a Fully Qualified Domain Name for a System

You cannot create a Serviceguard workload in a cluster if HP SIM refers to any of the nodes of the cluster by their fully qualified name. Virtualization Manager reports that HP SIM is unaware of all the nodes in the cluster, because it does not recognize that HP SIM's fully qualified system name is the same as the unqualified name given by the Serviceguard command used to determine cluster membership.

Workaround

Ensure that all Serviceguard cluster members are known to HP SIM by their non-fully-qualified names. This can be accomplished by adding those systems by short name and, on most systems, by adding them by IP.

Unexpected Error with Exception Message When Defining a Workload by Cluster/Package

In order to define a workload by cluster/package, the following conditions must be met:

  • You must be authorized to manage all nodes in the Serviceguard cluster.

  • All nodes in the cluster must be properly licensed to manage.

In most cases, error messages will be displayed if any of these requirements are not satisfied. However, you may experience an unexpected error screen with an exception message if you attempt to select a package on a node that is managed by Application Discovery. You may also be prevented from creating cluster/package workloads on other clusters and nodes in this case.

Workaround

Choose one of the following actions:

  • Establish the required authorizations and install the required licenses.

  • Move the package to a node where you have the required authorizations and licenses.

  • Discontinue monitoring of the cluster nodes with Application Discovery.

  • Remove your authorizations for all nodes in clusters where you do not need to create cluster/package workloads.

Printable version
Privacy statement Using this site means you accept its terms Feedback to webmaster
© 2006-2007 Hewlett-Packard Development Company, L.P.