HP Systems Insight Manager - Manual (Page 546)

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:
1. Your user name has been added to HP SIM. Do this by signing in to the HP
SIM GUI at least one time.
2. Your user name and password, if specified, are correctly spelled.
3. HP SIM is running.
4. You used '--' for any long options and double quotes if your username
includes a domain. For example, <commandname> --user "mydomain\myusername"
--pass mypassword.
Solution: Be sure that the HP SIM service is running by using the ps -ef | grep mx command. If the
managed system is not discovered on the CMS, this message will appear for mxagentconfig -a -n
managed system -u username -p password
. Be sure that the managed system is discovered.
I ran the command mxnodesecurity -r -p protocol –n <non-full-DNS-name> and received
a message that the system was removed.
However, the system still exists in the mxnodesecurity
list.
Solution: To delete a system from the mxnodesecurity list using the command mxnodesecurity -r –p
protocol –n <hostname>
, use the fully qualified domain name in place of <hostname>.
I am a full configuration rights user. However, I receive an exception when trying to run the CLI commands.
Solution for mxnodesecurity: On a Linux system, the command must be executed by the root user.
Solution for all CLI commands:
•
If you are a member of an HP SIM user group, sign in to the HP SIM GUI at least one time. After that,
you will be in the list of authorized users and will be able to run commands from the CLI.
•
On a Windows system, you must be a member of the Windows Administrators group to execute CLI
commands.
When using CLI commands in script files, the commands consume any input data available and when the
script is ran, the intended recipient has no data to read.
Solution: When specifying a CLI command in a script, specify echo "" | command -ln as the source
of standard input data for the CLI command for Windows .bat files and UNIX systems. Specify command
-ln < /dev/null
for HP-UX and Linux systems.
546 Troubleshooting