Authentication Failed error on SIM 4.1

[Troy Powers]

I am trying to push the initial proliant software to several servers w2k/w2k3, but everytime I try I get the following error messages. I saw someone else ask about them, but I did not see any response to the questions. Thanks in advance for the help...

Error Message:

EXCEPTION CLASS: com.hp.mx.exceptions.MxFailedAuthenticationException
EXCEPTION: Authentication failed.

[Joel Rubenstein]

Before you can successfully perform an Initial PSP install Open SSH must be properly configured on your SIM CMS. This is because the CMS logs on to itself using Open SSH in order to run the batch jobs that perform the Initial PSP install. An easy test to verify if Open SSH is properly configured on the CMS is to display all systems, select the CMS and then execute Tools-->Command Line Tools-->Windows--netstat.

Also if the CMS is running Windows 2003 then you must make the required configuration changes as documented in the SIM readme file for Open SSH to function properly.

[Troy Powers]

This doesn't seem to be the case because I have tried the install with both OpenSSH running (with the win2k3 workaround) and without it running.

There were several other posts here saying you didn't need OpenSSH, in fact in the manual it says OpenSSH is optional unless you want to use command line batch files, etc.

Anyone else have any insight into this error? Thanks again

[David Claypool]

SSH needs to be on the central management server running the hpSIM application in order for hpSIM to call command lines to execute locally.

SSH does NOT need to be installed anywhere else unless the distributed task function is used.

With the Initial ProLiant Support Pack Install, HP SIM runs a task that prompts the user to specify the machines they desire to do this on, select the PSP out of the VCRM, and supply Windows logon credentials. HP SIM then "shells out" to a command line prompt locally to address the remote systems using the setupc.exe utility from the PSP and passes the parameters for the machine name and authorization.

OpenSSH needs to be on the central management server running HP SIM. Nowhere else. The target must be running Windows and you have to know valid login credentials. Nothing else needs to be on the target machines.

[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.

[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.

[Joel Rubenstein]

Mark,

More information on the setup and troubleshooting of OpenSSH can be found in the whitepaper located at

http://www.hp.com/go/hpsim --> Information Library --> White papers --> Secure Shell (SSH) in HP Systems Insight Manager

[COOPERCAV]

Cheers. I will work my way through this.

[COOPERCAV]

I worked through this to no avail. However, 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.