README - HP Systems Insight Manager 5.3
Data Collection
Data Collection reports might report the network interface for HP-UX systems incorrectly. This is due to an
issue with SNMP agents on HP-UX. In the future, the HP-UX WBEM provider will include a Link Aggregate
Provider to report the network interface on HP-UX systems, and HP SIM can then provide the correct data
from the WBEM provider.
After an HP SIM upgrade, the Data Collection task might fail when executed. Following upgrade procedures,
you must run either the Identification Task or System Discovery Task against the systems for them to be
reconciled following the completed upgrade procedure. The Daily Identification task is available by default
and can be ran be any time by selecting Run Now. In a future release, the upgrade process will incorporate
the automatic launching of the Identification task against discovered systems.
-------------------------------------------------------------
The Data Collection task for an Onboard Administrator times out on non-Windows CMS . It affects the
individual task only and does not affect other tasks in the batch.
-------------------------------------------------------------
HP SIM might report duplicate entries for array controllers if the data is collected using both WBEM and
SNMP protocols on a HP Insight Management WBEM Providers for Windows Server 2003/2008 target.
To see the correct data in report, you can perform data collection by disabling one of the protocols. You
can also access SMH to see the correct number of Array Controllers.
-------------------------------------------------------------
If you see a problem with more than two mxinventory processes starting on the CMS you should:
1. Verify that your HP-UX CMS has the latest HP-UX kernel patches required for Java 1.5 execution. If the
CMS is HP-UX 11.23 IA/PA, then verify that the PHKL_35029 Kernel patch (or its superceding patch)
is installed. See http://www.hp.com/go/java.
2. Verify that all your HP-UX managed systems have HP WBEM Services for HP-UX A.02.00.11 or newer
and for managed systems running HP-UX 11.23 IA/PA, verify the PHSS_33349 Kernel path (or its
superceding patch) is installed.
-------------------------------------------------------------
If you cancel a running task, by clicking Stop or Delete, and immediately try to start another task of the
same type, the second task does not run until the previously canceled task fully completes the cancellation.
Systems in the cancelled task that are currently being processed are allowed to run to completion. For some
long-running tasks like data collection or software deployment, it can take some time to allow the systems
in progress to reach completion and finally cancel the task. If data collection runs for an unusually long time
you might want to stop or delete the task, and wait 5 to 10 minutes after the cancellation has completed
before running another data collection task.
If the data collection task is allowed to run to full completion without canceling, another data collection task
cannot be run for at least 15 minutes or the task will fail because it is skipped (this would be shown in the
STDOUT of the task instance).
-------------------------------------------------------------
If you see that data collection failed because of a WBEM connection, it might be caused by a failed WMI
Mapper proxy. Complete the following steps:
1. Physically verify all of the configured Pegasus WMI Mapper proxies. From the Administrative
tools→Services menu on the server hosting the Pegasus WMI Mapper proxy, be sure the Pegasus
WMI Mapper is running.
2. If not, restart the Pegasus WMI Mapper if possible.
3. If you are unable to restart the proxy or if the Pegasus WMI Mapper was uninstalled, delete it from the
CMS WMI Mapper Proxy settings found in the Options→Protocol Settings→WMI Mapper Proxy
page.
4. Be sure you have at least one running Pegasus WMI Mapper Proxy configured in HP SIM.
5. Verify credentials for the systems.
6. Run identification on all systems.
-------------------------------------------------------------
16 Known Issues and Workarounds