Once this action is taken, check that Application Discovery is receiving messages from the
host. (See
#8
in this section.)
5.
Check that SSH is configured correctly on the managed node .
In this case, you may need to repair the HP Systems Insight Manager agent on the managed
system. Click the following menu selections:
Configure
, then
Configure or Repair Agents
.
Make sure to check the box for 'configure SSH access' before running the repair agent.
To verify that the repair action has resolved any SSH configuration problem, you can issue
a remote
ls
command toward the managed system by doing the following:
a.
Select
Tools
→
Command Line Tools
→
UNIX/Linux
→
ls...
b.
In the text field, type
/tmp
If the contents in
/tmp
are visible, then SSH is working correctly.
If the configuration is still not working, you may see an error message:
Ssh Operation failed for node:managed_node.
The connection could not be established.
Reason:Failed to read remote identification
In conjunction with this, you may also notice that running
mxagentconfig
and selecting
Configure
→
Configure or Repair Agents
fail on the target managed node.
To reconfigure SSH on the managed node, do the following steps:
1.
Log on the managed node as user
root
.
2.
# cd /.ssh /* <root_user_home_directory>/.ssh */
3.
# rm * /* Erase all possible corrupted contents */
4.
# ssh-keygen -b 2048 -t rsa /* Generate root ssh key */
5.
# ps -elf|fgrep sshd /* Find the sshd PID */
6.
# kill -1 <pid> /* Re-start sshd */
7.
# mxagentconfig -a -n managed_node
8.
# amgr_remote_config -a -n managed_node -mx
Once this action is taken, check that Application Discovery is receiving messages from the
host. (See
#8
in this section.)
6.
Check that Application Discovery agent is authorized to exchange data with the CMS
and that exchange is complete.
Click through the following HP Systems Insight Manager menus:
Configure
→
Configure
VSE Agents
→
Check AD Agent States
. Any status other than
Connected
indicates that
a certificate exchange may be necessary.
See
“Introduction” (page 63)
for completing the certificate exchange. The Application
Discovery agent starts running (and begins sending data to the Application Discovery server)
on completion of the certificate exchange.
Once this action is taken, check that Application Discovery is receiving messages from the
host. (See
#8
in this section.)
7.
Check that the WBEM connection is working correctly on the managed node.
To check the status of the WBEM connection, do the following in Application Discovery
user interface:
a.
Click the
AD Agents
tab.
b.
Look for the
WBEM Stat
column in the 'Hosts/Agents' table.
If the status message for WBEM is 'WBEM down', do the following:
Check that HP Systems Insight Manager CMS has an authorized logon with the
managed system.
Introduction
47
