README - HP Systems Insight Manager 5.3 with Update 1
Credentials
When a discovery credential is used to successfully communicate with a system, a credential reference is
created for that system. If the credential is later changed on that same discovery task, the credential that is
used on all systems referencing it changes. This enables credentials to be changed in one place (usually
passwords for an account) and immediately be available for use in HP SIM. The same is true for global
credentials.
Because of this, if a global or discovery credential is deleted, you are asked if all references to that credential
should be removed or if copies should be made as system credentials for each system that is referencing the
current credential.
However, when a credential is overwritten, instead of deleted and then re-added, the credential is changed
and each system referencing it uses the new username/password values.
If the intent is not to change what is currently in use, you must add a new credential. For discovery tasks, a
new discovery task must be created with its own credentials, instead of editing an existing discovery task,
if the systems require different credentials than contained in the existing discovery task.
Custom Tool
DOS environment variables are supported in the custom command parameters and work as parameters on
the New Custom Tool page or the Manage Custom Tools page. However, they must be surrounded by
double % signs. For example, to pass the NOTICELABEL environment variable as a parameter, it should
be entered as %%NOTICELABLE%% on the parameter line. The environment variables can also be accessed
from a batch file or script file. To use them in a batch file or a script file, only a single % sign should precede
and succeed the environment variable name. See the
HP Systems Insight Manager Technical Reference
Guide
under Tools that extend Management - Custom Tools - Custom Tools Reference -
Parameterized Strings Substitution Table for a list of other substitutable variables.
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.
-------------------------------------------------------------
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
16 Known Issues and Workarounds