HP Matrix Operating Environment Software User Manual
Page 43
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.
# /opt/amgr/bin/agent_config -start
Once this action is taken, check that Application Discovery is receiving messages from the
host. (See
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 not 'OK', do the following:
Check that HP SIM CMS has an authorized logon with the managed system.
See
to complete this authorization.
Alternatively, you can configure the managed system's WBEM authorization to trust
the CMS to perform a remote "root" WBEM user logon. Do this by clicking Configure
→Configure or Repair Agents. Make sure to mark the box for 'Configure WBEM client
certificate authentication' before you run the tool.
Once this action is taken, check that Application Discovery is receiving messages from
the host. (See
in this section.)
8.
Check that Application Discovery is receiving messages from the host.
a.
Click the following tabs in Application Discovery: Admin/Config, then AD Agents.
b.
Find the column headings providing message data on the far right of the data table on
this screen. Check that the cells have data and that the time stamp is within the period
set by the Global Host/Process Interval selector on that screen.
See also:
Errors due to incompatibilities between different versions of Application Discovery
Data missing in Application Discovery screens
43