HP Systems Insight Manager - Manual (Page 184)

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 HP SIM,
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 HP SIM 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 HP SIM to display the same name as the host name of the full DNS name,
you must use the modify command to modify it.
-------------------------------------------------------------
If an iLO or Onboard Administrator was discovered prior to enabling/configuring Single Sign-on
(SSO), re-identification is required for SSO communication to work between HP SIM and the
iLO/OA.
-------------------------------------------------------------
If an Onboard Administrator is discovered with Discover systems in an enclosure when
Onboard Administrator is discovered
option enabled, then the percentage completion of the
discovery task in which the Onboard Administrator IP address is part of, fluctuates. Initially, the
percentage completion is higher, but as the discovery of iLOs are triggered, the overall percentage
completion comes down. As the iLO discovery completes, the percentage completion moves higher
and finally becomes 100% and task status becomes complete.
-------------------------------------------------------------
Some systems, such as Cisco Fibre Channel switches, that support both SNMP and SMI-S protocols
can appear as two separate systems within HP SIM.
-------------------------------------------------------------
HP SIM currently does not support an association of management processor to server if the system
is based on PA-RISC because a management processor is only supported on HP Integrity systems.
This will not be supported until a new release of firmware for the PA-RISC systems.
-------------------------------------------------------------
184 Troubleshooting