Locale, Managed environment, Hp mibs – HP Systems Insight Manager User Manual

Page 176: Locale managed environment hp mibs

When a subscription license for a particular product has expired, license manager's opening table
will still show that product has no system limit. The true disposition of licenses for the corresponding
product can be determined by opening Manage Licenses. If an expected subscription license is
not listed, it has expired and is no longer available.

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.

Solution: 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.

Managed 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.
Solution: To bypass this problem, modify the Ignite tools from the CLI using the tools' original tdefs,
as follows:

Procedure 46 Issue with changing and saving the address of an Ignite server

From the CLI, go to the Tools directory under the HP SIM install directory on Windows and
under /var/opt/mx/tools on Linux and HP-UX.

Run mxtool -mf -x force' where 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

The LinkUp and LinkDown traps in IF-MIB.mib are redundant traps; these are also present in
rfc1215.mib

. As per the current framework, the redundant traps are not allowed in HP SIM

Traps with same name.
Change the loading of MIBs. The IF-MIB.mib is loaded first and then the RFC1215.mib. The
IF-MIB.mib

will be listed in mibcore.list and RFC1215 in preload.list. By doing this

the LinkUp and linkDown traps from IF-MIB.mib will only be registered with HP SIM. The RFC1215
file will only show four traps Cold Start, Warm Start, Authentication Failure, egp....
-------------------------------------------------------------
Do not rename, move, or delete MIB files from the MIBs directory after they are registered.
Solution: For a MIB file to be listed as registered, the MIB file must reside in the MIBs directory.

176

Troubleshooting