HP Systems Insight Manager User Manual
Page 180
To discover an XP P9500 array, you can either discover it with a CVAE server or discover it with
embedded SMI-S. Do not use both methods of discovery together because there are chances for
Data collection and WBEM subscriptions to fail. However, if you use both methods of discovery
and observe that Data Collection or WBEM subscription is failing please delete the system and
run discovery again.
-------------------------------------------------------------
Discovery of a Microsoft Windows 2008 MSCS cluster in HP SIM fails to illustrate the second IP
address on the Cluster Monitor page even though HP SIM discovers the cluster correctly.
Solution: If the first IP address of the MSCS cluster is not in the same subnet as the HP SIM 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, HP SIM will not add the cluster and the cluster nodes will not be associated
in HP SIM with the cluster. To work around this, add an entry to the hosts file on the HP SIM 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:
IP Hostname alias
(for example: 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 HP
SIM, 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.
Solution: This is due to a default timeout value of three hours for this operation. There are two ways
to resolve the issue:
•
Configure the array to have a maximum of 2500 collectible objects (volumes, disks, ports,
and so on).
•
Increase the timeout value, depending on the configuration, to an optimal value by modifying
the configurable parameter Storage_DC_Timeout which is set to a default value of 10800
(equals 3 hours), with the mxglobalsettings command.
◦
Example to retrieve the current value:
mxglobalsettings -ld Storage_DC_Timeout
◦
Example to modify the value to 4 hours (14,400 seconds):
mxglobalsettings -s Storage_DC_Timeout=14400
It has been observed that data collection can take 3 hours and 37 minutes on an XP24000 array
that has ~3200 lives, 40n network ports, and ~150 disks.
-------------------------------------------------------------
If an HP Logical Server that is created in Insight Dynamics is given the same name as the operating
system host name of the blade on which it is applied, then the logical server is deleted when the
blade is rediscovered.
Solution: To avoid this, be sure the logical server name is different from the host name of the blade.
180 Troubleshooting