SSH uses Administrator account

[gldiii]

Can someone please explain to me why it appears that when I run the "Install OpenSSH" Task against a remote server from SIM, that according to the event logs on the CMS, it still tries to use the Administrator account to open the SSH session to itself, no matter what account you are logged in as or what account you specify as the account to run the task under??? It is especially annoying in that the "Administrator" account hasn't been named that since the server was built several years ago, and has since been renamed for obvious security purposes. SIM and SSH we're just recently installed so I do not know where it is getting the Administrator account from in the first place. It would seem this Task has the Administrator id hardcoded into it or something between SIM and SSH is not communicating the correct user account to run this task under. Can anyone make any sense of this? I've seen all the documentation and NOTHING addresses the use of the Administrator account sufficiently.

[gldiii]

I've found where the openssh-install.xml file contains the Administrator reference, I was able to change that and run U:\>mxtool -m -f "c:\program files\HP\Systems Insight Manager\tools\openssh-install.xml" to update the tool in the DB. This got rid of the event log messages referring to "Administrator" but it still fails with EXCEPTION CLASS: com.hp.mx.exceptions.MxFailedAuthenticationException
EXCEPTION: Authentication failed.
No events this time to speak of. I can connect fine to the CMS via SSH just fine from a client using the specified accounts in passwd. I give up, this implementation of SSH for SIM sucks!

[Jim_301]

I'm having the same problem. Can connect via putty/mxagentconfig. But any task run from HP SIM fails..

[Troy Powers]

I finally figured this out, you need to modify the proliant-msa-tools.xml files to put in the account you are using with the mkpasswd. By default it only uses Administrator in the XML file. After putting in the account you want to use, type in mxtool -m -f and it will modify the appropriate database items.

[gldiii]

From my second post you can see I found that but it still fails...anybody else have any luck?

[Chad Taggart]

Hi,

I'm experiencing this same problem with SSH. In that i can connect via "ssh @ and also via mxagentconfig. Although when i try and launch a custom command i get the error EXCEPTION CLASS: com.hp.mx.exceptions.MxFailedAuthenticationException
EXCEPTION: Authentication failed.

I have run both mxgroup and mxpasswd but still it fails....

Any ideas?

[Chad Taggart]

I should've waited the extra 1hr that it took me to resolve before writing asking for help.

Anyway the fix for me in addition to the previous steps was to complete the section on configuring for Windows 2003 (Appendix A - SSH White Paper). As soon as i did this i can now run "Custom Commands"

Chad

[Scott_278]

Troy, you are the MAN! I've been working for days on this problem and finally found your resolution. Modifying the XML file fixed this really frustrating problem for me.

THANK YOU THANK YOU THANK YOU THANK YOU!!!!

[COOPERCAV]

I have been pulling my hair out with the same problems. I get the MxFailedAuthenticationException errors in the scheduled task log. I am running W2K with SIM, OpenSSH, Version Repository Manager etc all on this same server. I have tried the WS2K3 services workaround anyway but can seem to create a connection. If I try to connect via the GUI MXAGENTCONFIG I get 'could not connect to server'. I have also tried the netstat tool suggested, however, I get the same MxFailedAuthenticationException error. I can deploy the Proliant Support pack remotely manually without a problem and the updates are downloading fine so I really want to complete the circle. I do have an administrator account so named, but I have also looked at the proliant-msa-tools.xml file but can't see where to make the change(s). Thanks.

[Scott_278]

Cooper - can you confirm whether or not you are using the "Administrator" account, or have you renamed it?

Can you log in using ssh from a command line to your target system?

[COOPERCAV]

The administrator account is NOT renamed and I am unable to connect via SSH using either the GUI or command line. GUI says it cannot connect to server and command line refers to an exception connecting to server.
B.T.W. I have just removed SIM4.0 and done a clean install on SIM4.1 to see if that helps

[Mike Angley]

I too have the same problem. One of the fixes referenced using any account but a local system to run openssh sever, but now the only account i can get to run it is .\administrator. Local system cannot run it anymore, a domain account with admin priv just for this cannot run it either. It refuses to start, telling me no error message is availible. Right now nothing as far as commands is working. I also have done all the documented fixes in the forum as well as the whitepaper and the readme. I have reconfigured the mx-tools, etc, tried the netstat, all to no avail. This is a fresh install of 4.1 on a different server from the old 4.0. I have attempted to run the netstat against the 4.1 cim server, i cannot choose it as a target since it tells me openssh is not supported on the target system (the CMS itself).

[COOPERCAV]

I have had some good fortune. Having removed SIM4.0, SSH and VCRM etc etc, I did a clean install of SIM4.1 and all of the above apps on the same server as before. Strange thing was this time the repository was not populated despite selecting 2 PSP's. This was not a problems before and also the VCRM did not show up in the servers managment page. I therefore installed VCRM and SSH on 2 seperate servers. The first failed to populate the repository folder but did show the VCRM in the servers managment page. The second did populate this directory as well so I selected this from SIM and sucessfully deployed my first PSP (at last). I cannot say conclusively why it is now working but it seems very hit and miss but maybe down to having VCRM and SSH on a seperate server (same server should be simpler you would think). Anyway, its working now and to be honest I've spend to much time already to try to pin the problem/cause down any further. Fingers crossed. Ta all.