HP Systems Insight Manager 5.2 Update 2 Technical Reference Guide

• Verify that the interop namespace for your WBEM provider exists in a port element in the
config/identification/wbemportlist.xml file. If it does not exist, add it to a port element
as an interopnamespace element, and restart HP SIM.
NOTE: Adding new ports or interop namespaces causes the discovery process to take longer because HP
SIM tries all possible combinations of ports, interop namespaces, and user name and password pairs on
each IP address in the discovery range.
NOTE: For information about storage system CIMOM problems, see the “SMI-S providers” and “Storage
system” sections.
Cluster
A cluster is not identified as a cluster.
Solution: If a cluster is not defined as a cluster or any of its nodes are not identified correctly, be sure all the
Cluster Management Agents are installed (if necessary, reinstall) on every cluster node of that cluster.
After manually adding a system as a cluster, the system type does not change, even if the system is not a
cluster.
Solution: If you manually add a system as a cluster, the system type might not change even if the system was
not a cluster originally. To reset the system type, delete the system and run discovery.
Clusters or cluster nodes are not identified correctly.
Solution: Clusters or cluster nodes might not be found for the following reasons:
• Starting with SmartStart version 6.30, one of the cluster agents is not installed correctly. The executable
is installed on the cluster node, but the Windows registry must be updated.
1. Access the Windows registry (select Start→Run and enter regedit.)
2. Create the following key:
HKEY_LOCAL_MACHINE,"SOFTWARE\Compaq\CompaqCommonClusterAgent\CurrentVersion"
Value: Pathname,%REG_EXPAND_SZ%,"%SystemRoot%\System32\svrclu.dll"
This update is available starting with SmartStart CD 7.4.
• Be sure the IP ranges in automatic discovery are set to include the cluster and cluster nodes (and not
exclude them).
• If the name of the cluster or its node has changed, be sure the DNS servers being used by the cluster
and HP SIM both have the new name.
• The cluster node might be down.
• The cluster node has Insight Agents older than version 4.22.
• The Insight Agents are not running on the cluster node.
• The SNMP Agents are not running on the cluster node.
• The network traffic is congesting the network for a significant time.
• SNMP community string might not be matching with that of the HP SIM settings.
Verify the following prerequisites are met:
• The Cluster Management Agents must be running on all the cluster nodes.
• The system must be identified as a server or cluster for cluster identification to run against that system
during discovery.
The cluster node is not identified properly by discovery.
Solution: The cluster node name for the DHCP server might be different than its Windows NT name. The
remedy is to explicitly place the Windows NT computer names into the LMHOSTS file on each cluster node
and then run discovery again. Also, be sure the registry key for the svrclu.dll has been created. See
the previous issue for information about the registry key.
A cluster or cluster node is not displayed in the Cluster Monitor cluster or node resource settings.
Cluster 621