General Communication Issues

The vseassist Command Can Be Helpful

The vseassist command, with the -l and -r options (see vseassist(1M)) can be very helpful diagnosing communication problems in the VSE environment. Diagnostic functionality is also available from the upper, HP SIM menu bar by selecting DiagnoseTroubleshoot VSE ManagementCheck VSE CMS Configuration.

No Utilization Data from a Specific System

If you cannot display utilization data in Virtualization Manager or in VM Manager views, make sure that the Utilization Provider is running on the managed system.

No Utilization Data from All Systems in Specific Time Zones

The version of the Utilization Provider that was initially included with the VSE Management Software (A.01.02) and earlier versions contains a defect that makes utilization data unavailable for systems in time zones that observe daylight saving time on January 1. The defect does not depend on the current date and time. The following are symptoms of this defect:

Managed systems in the following time zones are affected:

In addition, any system is affected if the file /usr/lib/tztab has been modified so that the system honors daylight saving time as of January 1 (for example, systems in Brazil).

Utilization Meters Display “Timed Out”

Timeouts in the utilization meters might occur with slower systems or on networks that cannot consistently satisfy WBEM data requests within 10 seconds. In this case, the utilization meters display “ timed out ”.

No Perm. Message Although WBEM Credentials are Valid

You may intermittently encounter a “No Perm.” error message for a workload or system that has valid WBEM credentials entered in HP SIM.

No WBEM Credentials (Confusing Message)

The message “No WBEM credentials” may be confusing under certain circumstances. Depending on the source of the problem, the detailed error message for this situation may take the following form:

No WBEM credentials are available for system "system-name".
The system "system-name" has no hostname defined in HP-SIM.
To remedy this problem, enter "mxnode -r system-name; mxnode -a system-name"

The condition described by the second line of this message or may not exist. That is, the system may have its hostname correctly defined in HP SIM.