README - HP Systems Insight Manager 5.3 with Update 1
-------------------------------------------------------------
If an HP Logical Server that is created in Insight Dynamics - VSE 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. To avoid this, be sure the logical server name is different from the host name of the blade.
-------------------------------------------------------------
If you have configured the rack name or enclosure name which can be resolved to an IP address, after
running discovery or identification, you may get incorrect result. To check if a name is resolvable to an IP
address, you can run nslookup <name|IP> or mxgethostname -n <name|IP>. To correct, change
the name of the rack or enclosure to be a non-IP addressable name.
-------------------------------------------------------------
Discovery of P-class servers and enclosures requires SNMP agents to be installed.
-------------------------------------------------------------
If an OA 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 OA 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.
When an HP BladeSystem enclosure contains redundant OAs, HP SIM merges the two systems together to
display one enclosure, and the primary OA shows both the IP address for the primary and secondary OA.
Should the Primary OA fail, the user interface shows a critical failure, and for HP SIM to resolve the links to
the OA IP address correctly, a new Identification or Discovery must be run on the IP address for the secondary
OA.
-------------------------------------------------------------
To access the Automatic Discovery page and perform discovery functions, you must have the System
Automatic Discovery tool selected when creating a custom tool box. This tool is found on the Users and
Authorizations Toolbox tab under the System Administration category. In addition, you must have an
authorization configured for the toolbox that has both of these tools listed.
Naming restrictions
• Complex name and
creatorSerialNumber
must be specified
• Within one complex, you cannot have more than one virtual partition monitor with no nPar name
-------------------------------------------------------------
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.
-------------------------------------------------------------
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. If you
Discovery 19