Database, Discovery, Database discovery – HP Systems Insight Manager User Manual
Page 129
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 A-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
-------------------------------------------------------------
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.
Solution: If this occurs, Systems Insight Manager will not add the cluster and the cluster nodes will not be
associated in Systems Insight Manager with the cluster. To work around this, add an entry to the hosts file
on the Systems Insight Manager server for the cluster alias name and IP. On Windows, the host file is located
in the %windir%/system32/drivers/etc directory. The standard hosts file entry should be of the
following form: 15.2.9.1 hypcl1.vse.adapps.hp.com hypvcl1.
-------------------------------------------------------------
Discovery of an MSCS cluster service name or IP address (for example. a Fileserver service, and so on)
overwrites MSCS system information, making management of the cluster nodes through Systems Insight
Manager, HP Insight Control virtual machine management, or HP Insight Dynamics impossible.
Solution: Remove all systems associated with the MSCS cluster (this includes the cluster alias, the cluster
nodes, and any VMs that might be running on the cluster), and then re-discover the cluster (and any VMs)
without discovering the service. For example, add the IP address of the cluster service to the ping exclusion
range on the general discovery settings page.
-------------------------------------------------------------
When the number of objects to be collected on any given storage array exceeds the value of ~2500, it is
possible that data collection will fail for the array.
Database
129