HP Systems Insight Manager 5.3 Technical Reference Guide

Cluster Monitor does not appear 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 discovery.
Solution: In 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
displays 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
Sign On support, Replicate Agents, Update Software, and so on) should trust all nodes of the cluster. See
“Setting up trust relationships” for more information about 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 http://www.hp.com, and then click Support & Drivers.
2. On the Support & Drivers page, under Or Select a product category, click Servers.
3. Click ProLiant and Pentium/Xeon servers.
4. Click Compaq ProLiant Servers.
5. Select the appropriate ProLiant series (for example, Compaq ProSignia 720 server series).
6. Select the appropriate server (for example, Compaq ProSignia 720 server 3/350-512).
7. In the tasks for your selected products box, click download drivers and software.
8. In the select operating system list, select the appropriate operating system (for example, Microsoft
Widows 2000).
9. In the select a category list, select Software - System Management.
10. Click HP Insight Management Agent for Windows 2000/Server 2003.
Collection
While trying to create a duplicate collection name in a Shared or Private section, an error message is generated.
Solution: Duplicate collection names are not allowed in Shared or Private sections. Collection names should
be unique even though the collections exist in Private and Shared.
After deleting a system, the product name or Web Agent criteria are not removed.
Solution: After a product name or Web Agent is discovered, that search criteria remains in the database
until the database is reinstalled, which enables you to search criteria that were present once and might be
present again in the future (for example, database tasks on a collection with these criteria, and set it to run
when new systems or events meet the search criteria).
Machine names that have spaces within their name are truncated at the space character in a collection.
622 Troubleshooting