Systems Insight Manager 6.1 User Guide

Procedure B-7 Issue with data collection failing because of WBEM connection
1. Physically verify all of the configured Pegasus WMI Mapper proxies. From the Administrative
tools→Services menu on the server hosting the Pegasus WMI Mapper proxy, be sure the Pegasus
WMI Mapper is running.
2. If not, restart the Pegasus WMI Mapper if possible.
3. If you are unable to restart the proxy or if the Pegasus WMI Mapper was uninstalled, delete it from the
CMS WMI Mapper Proxy settings found in the Options→Protocol Settings→WMI Mapper Proxy
page.
4. Be sure you have at least one running Pegasus WMI Mapper Proxy configured in Systems Insight
Manager.
5. Verify credentials for the systems.
6. Run identification on all systems.
-------------------------------------------------------------
If data collection of a system fails with the STDOUT error, stating An error occurred connecting
to this system with the WBEM protocol. Check the system configuration
Solution: This might be caused by any of the following conditions:
• You failed to make appropriate port number entries in the wbemportlist.xml file:
/etc/opt/mx/config/identificationOn Linux and HP-UX:
On Windows: C:\program files\hp\systems insight
manager\config\identification
The folders listed above are the default folders and should be used unless you have changed the
installation folder location.
• You might have failed to set up and specify appropriate WMI Mapper proxy servers.
• You might have failed to specify appropriate WBEM credentials.
-------------------------------------------------------------
If you run a data collection task on a storage host and select the Append new data set (for historical
trend analysis) option instead of the default option, Overwrite existing data set (for detailed analysis),
the data collection task will fail and the data for that storage host is erased.
Solution: To restore the missing data, do one of the following:
Procedure B-8 Issue with data collection failing and data for the storage host being erased
1. Delete the storage host from the Systems Insight Manager database, and then discover it again.
2. Wait fifteen minutes, and run the data collection task again with Overwrite existing data set (for
detailed analysis) selected.
Database
Database creation under SuSE 10 PostgreSQL reports warning messages at various stages as the database
is created.
Solution: A warning message states that the view which provides license reporting has caused an exception
and has not been inserted. Subsequently, there are warnings indicating that the license view cannot be
dropped as it does not exist (creation failed earlier). However, the final step for updating the database in
Systems Insight Manager 5.1 correctly inserts the license view for SuSE 10. Therefore, the view is present
when database creation is complete and license reporting should function correctly.
Discovery
Discovery of a Microsoft Windows 2008 MSCS cluster in Systems Insight Manager fails to illustrate the
second IP address on the Cluster Monitor page even though Systems Insight Manager discovers the cluster
correctly.
Solution: If the first IP address of the MSCS cluster is not in the same subnet as the Systems Insight Manager
server, a pop-up window appears when browsing to the Cluster Monitor page. See the Microsoft link for
setting up MSCS cluster with two-subnet Failover Cluster at http://technet.microsoft.com/en-us/library/
bb676403.aspx.
-------------------------------------------------------------
For Windows 2008 MSCS clusters (including Hyper-V clusters), DHCP addresses are now allowed for the
cluster alias. In some circumstances the reverse lookup for the cluster alias IP resolves back to one of the
cluster nodes instead of the cluster alias name.
Database 131