HP Systems Insight Manager - Manual (Page 550)

I cannot find custom tools that I have created.
Solution: New custom tools are added to the All Tools toolbox. You might not have authorization to use
that toolbox. To view the tool under Tools
→custom tools, add the tool to your authorized toolbox, which
is present under Command Line Tools. See “Editing toolboxes” for more information.
Database
When trying to reinstall HP SIM on a Windows system from which I previously uninstalled HP SIM, I receive
Unable to Create Database
. I receive this error during the database creation process.
Solution: This problem is a result of not deleting or renaming the HP SIM database files from MSDE or
Microsoft SQL Server after uninstalling HP SIM. Manually delete or rename the database files, and then run
the HP SIM installation again.
Discovery
A system that has had a new IP address assigned to it is discovered as a new system in HP SIM instead of
having the existing system in HP SIM updated with the new IP address. The original system shows a Critical
status.
Solution: This issue results when DNS is not configured on the network. HP SIM tries to use system names
from DNS to match previously discovered systems with new systems of the same name. Be sure that DNS is
configured on the HP SIM server, and ensure that the DNS server itself is properly configured for the systems
in question. Both forward DNS lookups and reverse lookups must resolve to the same system. On Windows,
nslookup <address or name>
can be used to help diagnose the problem.
There is a mismatch between the system table view and the picture view.
Solution: Delete all the systems that are in the affected rack, which includes all the servers, iLOs, enclosures,
and switches in that rack, and run discovery on those deleted systems.
NOTE: Before deleting the servers, iLOs, and switches, note the IP addresses of these systems, then delete
the systems, and run discovery.
After upgrading from HP SIM 4.1 to HP SIM 4.2, my ProLiant BL40p server blade to enclosure associations
are displayed as "server in iLO" instead of "server in Enclosure."
Solution: Delete the affected server blades from the database and run discovery again. The server blade to
enclosure association will now be displayed correctly.
After running discovery, I noticed that a system was discovered but not identified as a WMI/WBEM device.
Why was this system not discovered properly?
Solution: A system might not be discovered properly for several possible reasons, including:
•
The user credentials were incorrect.
•
The provider encounters a problem responding to the WBEM requests.
•
The system names can only contain alphabet (A-Z), digits (0-9), minus sign (-), and period (.). However,
the system name cannot start with a digit, and the last character must not be a minus sign (-) or period
(.).
•
On HP-UX or Linux CMS's, no WMIMapper was specified. Therefore, no Windows systems can be
identified as WBEM enabled systems.
•
There is no provider installed on the target HP-UX or Linux system.
I am trying to see the association of management processor and the HP-UX server, but I do not see the
association between the server the management processor.
Solution: Currently, HP SIM cannot make an association of management processor to server if the system is
based on PA-RISC.
Event/SNMP trap
Why am I not receiving notification when there is a SNMP Authentication trap received?
550 Troubleshooting