HP Systems Insight Manager 5.3 Technical Reference Guide

I ran the following command to add systems through the CLI on a Korean system; mxnode -lf hpdcl3as3
> node.xml where node.xml is an .xml file listing all available systems. I then ran mxnode -a -f
node.xml to add the systems. However, I received an x-windows-949 error message.
Solution: Edit the .xmlfile that you created to add the systems and change the encoding name to UTF-8.
I used mxreport to dump the contents of an existing report and report category. For now, I only modified
some name fields and reviewed mxreport(4) and mxcategoryitem(4) to check format for new items
to make sure they were set appropriately to create a copy of the report/category I dumped under a new
name. I can successfully create my new report using:
# mxreport -a -f/home/bvilfer/work/PPUStorageLogicalUnitsReport.xml
Report successfully created.
When I try to create a category containing SQL for a new view that I want the report to use, it fails:
# mxreport -c -f/home/bvilfer/work/PPUStorageLogicalUnitsCategory.xml
Category failed to create in database.
PPU Storage Logical Units
null
Is there a log file somewhere that might give me more information as to what the "null" is referring to?
Solution: You need to create Category first, if you want to report new category items that are not in the
existing categories, then create the report. To be able to view log files of debug explanations, you need to
turn on debug by setting the following properties in the debugsettings file:
• MxCategoryManager, MxReportManager - set them to true, 30
• In the xml file, you should have created views for three different databases MSSQL, Postgresql and
Oracle. If they are the same, then set dbType=111.
From the command line, I entered mxmib -f SHIPPING CFGs not preloaded.txt , and I received
the error The following is an invalid argument value: CFGs.
Solution: The command mxmib cannot handle spaces. Place the file name in quotes. For example, enter
mxmib -f "SHIPPING CFGs not preloaded.txt".
The command mxagentconfig -a -n cms_name -u user_name- p password fails with
Unknown hostname: 'cms_name' .
Solution: For verification purposes, use nslookup cms_name to test the network name resolution on the
managed system. To correct the problem, set up a network name resolution properly on the managed system
by adding CMS information to the managed system /etc/hosts file.
The command mxnode -a system_name or mxnode -r system_name fails with: Unknown
host: ‘system_name’ System ignored.
Verification: Use nslookup system_name to test the network name resolution on the CMS.
Solution: Set up network name resolution properly on the CMS.
I am receiving a message, Another user is currently using mxmib, please try again.
How do I resolve this?
Solution: This behavior is expected. Run mxmib -r to clear the interlock.
MXMIB enables me to compile a MIB with a different file name, but the same internal module name already
exists and is a compiled MIB, which is causing inconsistency in the database.
Solution: The module name and file name must be consistent. If the file names do not match, the files might
become corrupt.
If attempting to compile a MIB that already exists in the database, the CLI message states that it is importing
even though it is actually updating.
I am a member of an existing HP SIM user group, but when I try to run commands from the CLI, I receive an
error message, stating There was a problem connecting to the HP SIM server. Be sure
that:
CLI 619