HP Systems Insight Manager User Manual
Page 548
•
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 on the registry key.
A cluster or cluster node is not displayed in the Cluster Monitor cluster or node resource settings.
Solution: This issue can result from specific HP Insight Management Agent for those Cluster Monitor Resources
that were not running at the time discovery was run. Ensure that the correct agents are running on the clusters
and cluster nodes, and then run discovery again.
Cluster Monitor is not displaying properly.
Solution: Ensure that your browser is configured to use Small Fonts as the Font Size.
The list boxes under Cluster Monitor within Settings are not working properly.
Solution: It takes a few seconds for the down arrows to appear on the list boxes. If there is more than one
list box, select an option from the first box, and wait a few seconds to select an option from the second box
and each subsequent box. If you make a selection too soon, the list boxes might not work properly.
The cluster nodes are not discovered when the cluster alias is used as the system in manual discovery.
Solution: In manual discovery, add the cluster alias and each node separately to ensure they are entered
into the database. Alternatively, include the cluster alias and the node IP addresses in the IP range.
What should I expect when running HP SIM on a cluster?
Solution: HP SIM is not a cluster-aware application. If each node of the cluster has an instance of HP SIM
installed, each node has a different certificate with the name of the node, not the name of the cluster, unless
you have created your own certificates using a certificate server or other certification authority. When
browsing to the cluster, if your browser is configured to Warn about invalid site certificates, the browser
should display a security alert, warning you the name you have browsed to does not match the name in the
certificate. If you have not imported the certificate into the browser or the certificate has not been issued by
a trusted certification authority, the security alert also informs you of the untrusted origin of the certificate.
Verify the certificate is correct and continue.
During a failover, one node fails and the other node becomes active. Because HP SIM is not cluster-aware,
any browsers open to HP SIM must be closed, and you must browse to the cluster again. You might again
be presented with another security alert, using the certificate of the other node as previously described. If
so, verify the certificate and continue.
Any managed system that establishes a trust relationship with the HP SIM server (for example, for Single
Login support, Replicate Agents, Update Software, and so on) should trust all nodes of the cluster because
any node could be active and issue the desired command to the system. See
“Setting up trust relationships”
for more information on setting up trust relationships.
I am having problems identifying clusters.
Solution: If you notice that the cluster name or cluster member name is the IP address of the system and not
the host name, download the new HP Insight Management Agent for Windows 2000/Server 2003 for each
cluster member of the cluster.
1.
See
and click Support & Drivers.
2.
On the Support & Drivers page, under Or Select a product category, click Servers.
548 Troubleshooting