HP Matrix Operating Environment 7.3 Update 1 Installation and Configuration Guide for Provisioning with Virtual Resources

2. Ensure that the WBEM provider is not missing from the managed node. Run vseassist —l
—n nodename (or select the managed systems from the HP SIM user interface, and then from
the Diagnose menu, select Troubleshoot Matrix Operating Environment→Check CMS to Managed
Node Communication).
• If vseassist reports a WBEM authentication failure for the CMS, ensure that the FQDN by
which HP SIM knows the CMS corresponds to the IP address of the WMI Mapper:
◦ Determine the FQDN by which HP SIM knows the CMS: In HP SIM, use the Search
tool to find the CMS and mouse over the System Name to see the FQDN known to
HP SIM.
◦ Determine the WMI Mapper settings: In HP SIM, navigate to Options→Protocol
Settings→WMI Mapper Proxy.
◦ If a mismatch is determined, either reconfigure the WMI Mapper or re-discover the
CMS using the FQDN or IP address of the WMI Mapper. For example, in HP SIM,
navigate to Options→Discovery. If necessary, create a new discovery task for the
CMS using the FQDN or IP address of the WMI Mapper and run that task.
3. If the target system has been identified as WBEM enabled, but the credentials are failing for
the target system, perform the following steps:
• Verify the credentials and identify the target system again.
• The password might be incorrect on the System Credentials page. To access, select
Options→Security→Credentials→System Credentials.
Communication with HP SIM server has been lost
Issues
The HP SIM portal relies on the CMS to respond quickly to all requests.
• Browser performance degrades when CMS responses are delayed.
• The browser appears to lock up completely when CMS responses are delayed.
• The browser displays the message, Communication with the HP SIM server has
been lost, even though the CMS might be responsive to other browser sessions.
Possible causes
This could be a temporary condition due to CMS or network congestion, or CMS restart. Retrying
after a short period might resolve the issue.
On a LAN, the browser receives a CMS response to most requests within 10 to 100 milliseconds.
Requests that involve database queries or secondary network communication might take a few
seconds to respond.
There are situations that might result in particularly slow response times. For example:
• Viewing large collections of systems or events
• Specific and custom database queries taking an unexpectedly long time
• Many users simultaneously accessing a shared resource, such as the database
• Network delays
Pages that retrieve data using WBEM or SNMP Webagent and display the results (for example,
System Properties) can take a long time, especially when the requests are destined to time out.
Troubleshooting procedures 141