HP Servicecontrol Manager 3.0 Troubleshooting Guide

Servicecontrol Manager Issues
Problems With mxexec On A Managed Node (#1)
Chapter 3
29
Problems With mxexec On A Managed Node (#1)
Symptom The mxexec command fails on a managed node with the following message:
Authentication failed.
Verification On the managed node, list the CMS systems that the agent is configured for:
mxagentconfig -l
The hostname of the CMS should appear in the Servers list.
Fix If the CMS doesn’t appear in the Servers list, configure the agent to respond to the
CMS. On the managed node, execute:
/opt/mx/bin/mxagentconfig -a -n
cms_name -p password
where cms_name is the hostname or IP address of the CMS and password is the
MxConfigPassword.
Problems With mxexec On A Managed Node (#2)
The mxexec command may fail on a managed node when the CMS cannot connect with
the node. Several common causes of this situation are:
• the network cable is unplugged
• the node is powered off
• the node doesn’t have SCM agent software installed and running
Symptom The mxexec command fails on a managed node with the following message:
Unable to retrieve a connection from the RMIRegistry to system
node_name .
Exception creating connection to:
node_name ; nested exception is:
java.net.NoRouteToHostException: No route to host
where
node_name is the hostname of the managed node.
If the mxexec command failed, but this is the correct error message, see “Problems With
mxexec On A Managed Node (#1)” on page 29.
Verification 1. Log onto the CMS.
2. Attempt to establish communication with the managed node:
/usr/sbin/ping
node_name
where the node_name is the hostname of the managed node.
If these verification steps fail to establish communication with the managed node then
there is a LAN communication problem.