README - HP Systems Insight Manager 5.3

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
want HP SIM to display the same name as the host name of the full DNS name, you must use the vmmodify
command to modify it.
-------------------------------------------------------------
If the partition has a vPar already created and been discovered by HP SIM but the IP address used by the
vPar has been moved to a stand-alone server, HP SIM will not delete the vParMon association to the complex
or the management processor; the reason is the partition still has vPar defined within the partition.
Virtual identifiers from Virtual Connect Manager
Introduction A new feature of virtual connect is to enable server profiles to have virtual identifiers, such
as serial numbers and unique identifiers. These identifiers then move with the profile across server hardware.
There are a number of management tools that currently rely on these identifiers to remain stable for any
given hardware platform, if not some serious issues, such as loss of software licenses will occur.
Required updates to support Virtual Identifiers in HP SIM and other management tools.
When setting up an environment for virtual identifier support the following steps must be taken for proper
operations of the management tools.
1. Upgrade HP SIM to version 5.2 Update 2 or later.
2. For any server that will have a profile with a virtual identifier, upgrade the ROM BIOS to the latest
version to ensure it contains virtual identifier support.
Note The server hardware must be listed in the virtual ID support matrix.
3. Upgrade the agents and WMI providers on the servers that will be used for virtual identifiers. (See the
version table below for proper versions).
Discovery 19