README - HP Systems Insight Manager 5.3

Locale
Certain parts of CLI output might contain system-generated text that always appears in the language indicated
by the default CMS locale, not the locale of the user's CLI terminal. This condition can occur following two
problems:
• This text might provide a localized property key of the TDef file, which is not allowed for TDef input.
• This text might be identified by one or more question mark (?) character strings appearing in the CLI
output.
The CMS locale is determined by the globalsettings.props file. To change the CMS locale and possibly allow
the CLI to generate proper locale text, edit the globalsettings.props file by running the following command:
To set CMS Locale to Japanese:
mxglobalsettings –s –f CMSLocale=ja_JP
To set CMS Locale to English:
mxglobalsettings –s –f CMSLocale=en_US
After you run this command, restart HP SIM.
Manage Environment
When you set the Ignite server on the Managed Environment page and then access the page again, you
cannot change and save the address again. To bypass this problem, modify the Ignite tools from the CLI
using the tools' original TDefs, as follows:
1. From the CLI, go to the Tools directory under the HP SIM install on Windows and under
/var/opt/mx/tools on Linux and HP-UX.
2. Run mxtool -mf <tool XML> -x force' where <tool XML> for each TDef is as follows:
iux_tools.xml
swm-msa-tools.xml
swm-ssa-tools-up.xml
swm-ssa-tools.xml
hpux\iux_tools.xml
hpux\swm-msa-tools.xml
HP MIBs
Do not rename, move, or delete MIB files from the MIBs directory after they are registered. For a MIB file to
be listed as registered, the MIB file must reside in the MIBs directory.
Mozilla
After creating a data collection task many systems and running the task, Mozilla stops responding. This error
happens if Mozilla is left on the Tasks Results page for an extended time.
OpenSSH
If the OpenSSH installation fails on a Windows XP SP3 system, verify that the Network access: Sharing
and security model for local accounts under Local Policies→Security Options is set to Classic -
local users are authenticate as themselves.
-------------------------------------------------------------
Because a local Administrator account was being used as the credentials to connect to the WinXP SP3 target
system, the Local Security Setting: "Sharing and Security Model for Local Account" being set to "Guest Only
- local users authorized as Guest" would force the HPSUM connection to fail, since HPSUM was attempting
to use the target systems local administrator account to make the connection. The credentials in this case
were being forced to be that of the "Guest" account and the password supplied did not match the "Guest"
Locale 33