HP Systems Insight Manager - Manual (Page 130)

1. Select Options
→Discovery→Identify Systems.
2. Select the ProLiant BL e-Class Integrated Administrator.
3. Click Run Now.
Credentials
If you delete a credential (system credential, global credential, or one configured with a discovery task)
while discovery or identification is running, and that credential is found to work with a system, the attempt
to write the working credential to the database fails because the original credential has been removed. If
you try to view System Credentials for such a system, the system will not be listed in the Credentials that
are in use
table, or the table includes No data available. Normally, a system is listed in this table;
even one with no working credentials is listed with an Access Type of None.
To resolve this issue, restart Systems Insight Manager to remove any extraneous database records, and re-run
the discovery or identification task.
Data Collection
After a Systems Insight Manager upgrade, the Data Collection task might fail when executed.
Solution: 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.
Solution: This affects the individual task only and does not affect other tasks in the batch.
-------------------------------------------------------------
Systems Insight Manager 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.
Solution: 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.
-------------------------------------------------------------
You see a problem with more than two mxinventory processes starting on the CMS.
Solution: Complete the following:
Procedure B-6 Issue with two mxinventory processes starting
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 superseding 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
superseding 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.
Solution: 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.
Solution: Complete the following steps:
130 Troubleshooting