Secure Shell (SSH) in HP Systems Insight Manager 5.1 and 5.2

30
v.
Copy the
authorized_keys2
file from the CMS into the .
ssh
directory
b.
On Linux and HP
-
UX
–
similar process as above, except as noted:
i.
Login as root on the CMS platform
ii.
Create an
au
thorized_keys2
file for copying to other systems by entering the
command:
cp /etc/opt/mx/config/sshtools/.dtfSshkey.pub /<user’s
home directory>/.ssh/authorized_keys2
iii.
The above file is now manually copied to other systems into the
$HOME/.ssh
directory.
Verify that the permissions on the
$HOME, $HOME/.ssh
directory, and the
authorized_keys2
file are owner write only and there are no write permissions
for group or everyone.
As a work
-
around to public key authentication you can try password authentication
.
Configure the CMS with the password for this user:
CMS> mxnodesecurity
-
a
-
p ssh
-
n blade08
-
c myadmin:mypwd
Credential added for node: "blade08"
7.
Run an SSH task on the target system to verify correct operation:
CMS> mxexec
-
t ls
-
A .
-
n blade08
Running
tool ls with job id 2353.
Task Name :defRunNowTaskId_1121379737441_4
Job ID :2353
Tool Name :ls
Job State :Complete
User Name :mydomain
\
myuser
Execute As User :root
Start Time :Thursday, July 14, 2005 3:22:18 PM PDT
E
nd Time :Thursday, July 14, 2005 3:22:19 PM PDT
Elapsed Time :1 second 266 milliseconds
Node :blade06
Status :Complete
Exit Code :0
STDOUT :
bin
core
dev
etc
mxagentconfig errors
Problem: mxagentconfig
–
c faile
d
CMS> mxagentconfig
-
c
-
n blade08
-
u administrator
[e-mail]: failed
Completed with errors.
This
return indicates that the SSH server cannot be contacted on the target system, or the specified
user has not been configured for SSH a
ccess from this system.

Verify OpenSSH is running on the target system

Run
mxagentconfig
–
a
to add the user.
CMS> mxagentconfig
-
a
-
n blade08
-
u administrator
Problem: “There was a problem connecting to the HP SIM server”