README - HP Systems Insight Manager 5.3 with Update 1

-------------------------------------------------------------
When using MSDE (or Microsoft SQL Server 2005 Express Edition), Microsoft SQL, or Oracle database
server located on a remote Windows XP SP2 server, the firewall settings on the remote server must be turned
off. To do this:
1. Select StartControl PanelWindows Firewall.
2. Select Off.
-------------------------------------------------------------
Database creation under SuSE 10 PostgreSQL reports warning messages at various stages as the database
is created. A warning message states that the view which provides license reporting has caused an exception
and has not been inserted. Subsequently, there are warnings indicating that the license view cannot be
dropped as it does not exist (creation failed earlier). However, the final step for updating the database in
HP SIM 5.1 correctly inserts the license view for SuSE 10. Therefore, the view is present when database
creation is complete and license reporting should function correctly.
Discovery
Discovery of a Microsoft Windows 2008 MSCS cluster in HP SIM fails to illustrate the second IP address on
the Cluster Monitor page even though HP SIM discovers the cluster correctly. If the first IP address of the
MSCS cluster is not in the same subnet as the HP SIM server, a pop-up window appears when browsing to
the Cluster Monitor page. See the Microsoft link for setting up MSCS cluster with two-subnet Failover Cluster
at http://technet.microsoft.com/en-us/library/bb676403.aspx.
-------------------------------------------------------------
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 (including 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 fix this issue, see the Microsoft Knowledge Base
article at: http://support.microsoft.com/kb/969049.
-------------------------------------------------------------
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.
18 Known Issues and Workarounds