HP Systems Insight Manager 6.0 User Guide

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.
-------------------------------------------------------------
If you:
• Configure an HP Serviceguard package as an HP virtual machine which is hosted by two different HP
virtual machine hosts,
AND
• Complete a failover of the package from one HP virtual machine host to the other one,
AND
• Re-identify the package in Systems Insight Manager,
you might find that the package is not associated with the correct HP virtual machine host.
Solution After a Serviceguard package fails over from one host to a different host, you must re-identify the
HP virtual machine host system in Systems Insight Manager to see the correct association.
-------------------------------------------------------------
Orphan systems are appearing after I run discovery.
Solution: To prevent orphans from appearing in the future, review events and remove the system that you
have migrated to a new system type before rediscovering the new system after it is booted. This is true of
systems moving in or out of a virtual system environment.
-------------------------------------------------------------
If you see the preferred system name is different than the host name of the full DNS name for an HP virtual
machine guest, it is because the preferred system name is specified in the virtual machine package.
Solution: If you want Systems Insight Manager to display the same name as the host name of the full DNS
name, you must use the modify command to modify it.
Event
When you subscribe for WBEM events from either the command line (mxwbemsub) or the GUI
(Options→Events→Subscribe to WBEM Events), you might receive the error message String index
out of range.
Solution: Verify if the name of the local host resolves to a fully qualified name through DNS. The command
needs the FQDN name to work properly.
Host name
When installing Systems Insight Manager, CMS host names that exceed 15 characters are truncated, and
the truncated name must be used to complete the installation. After the install, two administrator accounts
are created. One account includes the original hostname\administrator and the other account
includes the truncated hostname\administrator.
Solution: To sign in, you must use the original host name in the Domain field on the Sign in page.
130 Troubleshooting