README - HP Systems Insight Manager 5.3

Discovery
When the number of objects to be collected on any given storage array exceeds the value of ~2500, it is
possible that data collection will fail for the array. 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 collectable 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 ldevs, 40n network ports, and ~150 disks.
For Windows 2008 MSCS clusters (inlcuding Hyper-V clusters), DHCP addresses are now allowed for the
cluster alias. In some circumstances the reverse lookup for the cluster alias IP resolves back to one of the
cluster nodes instead of the cluster alias name. If this occurs, HP SIM will not add the cluster and the cluster
nodes will not be associated in HP SIM with the cluster. To work around this, add an entry to the hosts file
on the HP SIM server for the cluster alias name and IP. On Windows, the host file is located in the
%windir%/system32/drivers/etc directory. The standard hosts file entry should be of the following
form: 15.2.9.1 hypcl1.vse.adapps.hp.com hypvcl1.
Discovery of an MSCS cluster service name or IP address (for example. a Fileserver service, and so on)
overwrites MSCS system information, making management of the cluster nodes through HP SIM, VMM, or
ID-VSE impossible. The resolution is to remove all systems associated with the MSCS cluster (this includes
the cluster alias, the cluster nodes, and any VMs that might be running on the cluster). Then, re-discover the
cluster (and any VMs) without discovering the service, for example add the IP address of the cluster service
to the ping exclusion range on the general discovery settings page.
-------------------------------------------------------------
If an iLO or Onboard Administrator (OA) was discovered prior to enabling/configuring SSO, re-identification
is required for SSO communication to work between HP SIM and the iLO/OA.
-------------------------------------------------------------
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
18 Known Issues and Workarounds