Readme - HP Systems Insight Manager 6.0

3 Issues and suggested actions
Authentication
On a Linux or ESX system, you might receive the following error when running the
mxagentconfigmxagentconfig command or through Configure or Repair Agents:
Configuration failed to complete due to the following exception: Could not
access the file or directory sshd_config.orig on the target system esxhost1.
Remote system reported following error message: Permission denied. Check whether
the directory or file exists or whether the user has the operating system
permission to access it.
You must manually change the permissions in the file to 644.
Browser
If you are using a Firefox browser, you should avoid remaining on the Task Results page for an extended
period of time. If you notice the browser becoming sluggish while viewing the Task Results page, you
should sign out of Systems Insight Manager to allow the browser to release memory. You can then sign back
in.
Central Management Server
Resource-intensive applications such as HP Insight Control performance management have sometimes
encountered problems working with large numbers of systems. In an effort to improve the stability of the
CMS, Systems Insight Manager now imposes a limit of 2000 systems on the information that is provided to
these applications. This limit can be changed, if necessary, by adding a new property named
MaxNodesViaSOAP to globalsettings.props and setting it to the desired number of systems. Setting
MaxNodesViaSOAP to a negative number disables the limit checking. In some cases, setting this limit to a
number greater than 2,000, or disabling the limit, can results in errors, including the possibility of Systems
Insight Manager hanging or crashing.
Collections
Use English text for naming collections. If you do not use English text, you might see named collections
generated by Systems Insight Manager. For example, collection-<number>
Configure or Repair Agents
Configure or Repair Agents cannot be used to install the WBEM Providers to Integrity Windows systems.
You must manually install the WBEM provider by copying cp010621.exe (can be found in the
smartcomponents directory under the Systems Insight Manager install) to the target system and then running
it.
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.
Authentication 17