Problem deploying Initial ProLiant Support Pack Install

[James Allen]

I have set up HP System Management on a server and have OpenSSH installed on my other servers. Trust has been established between the Repository and hpSIM.

However, when I try to deploy the Initial ProLiant Support Pack to a server, I get the following fail message:

EXCEPTION CLASS: java.rmi.ConnectException
EXCEPTION: Connection refused to host: 192.168.1.5; nested exception is:
java.net.ConnectException: Connection refused: connect


192.168.1.5 is the address of the hpSIM/repository server.

What am I missing?

TIA

[Edward Latzko]

To resolve this issue Schedule the task to run 1 minute in the future instead of "Run Now". There is a know bug. Hope this helps....

[David Claypool]

The scheduling issue, while known, yields a different error. Your problem is with SSH.

The Initial PSP Install task requires SSH on the hpSIM server itself--it is not needed for any of the target servers (this is why the tasks prompts for username/password/domain because it is going to use OS security to connect remotely and install the PSP). The error message you are getting means that the hpSIM application is not able to talk to SSH on itself.

Have you followed the instructions in the README for post-install procedures regarding SSH?

http://www.hp.com/wwsolutions/misc/hpsim-helpfiles/readme.txt

[James Allen]

Thanks for the replies.

Edward: Yes, I found about the bug in my research on this forum and was scheduling my deployment jobs accordingly.

David: Yes, I did find that file and had read it. I tried the procedures mentioned about a problem I had with mxagentconfig being refused a connection to two of my servers. Since I am running Win2K, I did not perform any procedures described for Win2K3.

I was under the impression that I needed to manually install OpenSSH on the managed servers prior to doing anything else. Was that my problem you think: that because I had already installed OpenSSH on my managed servers that it was causing problems with the PSP deployment? If so, that is a key element to consider.

So assuming that, I should just prepare the hpSIM server only, then run the InitPSP to the others without pre-installing anything on them?

As of yesterday, I removed all hpSIM components from the servers in preparation for a clean re-install, because I know it should not be complicated.

Let me know, and I'll make another go of it.

TIA

[David Claypool]

Functionality that allows a task to be distributed and executed on a remote system requires SSH at each station. The "Initial PSP Install" does NOT use that functionality.

Under the covers what happens is that the hpSIM application uses SSH to execute ON ITS OWN SYSTEM the command line version of the PSP install,

setupc /t:TARGETSERVER /user:USERNAME /passwd:PASSWORD bpXXXXXX.xml

This will iterate for each server that was in the target list, replacing the servername for TARGETSERVER above, using the USERNAME and PASSWORD received from the prompts during the task and finally the XML reference comes from the lookup into the VCRM.

Nothing needs to be on the target servers to receive the PSP installation.

Once you have hpSIM operational, confirm that OpenSSH is functional by creating new custom commands that will run on the central management server like a simple 'dir' command. Once that is confirmed as working, try the Initial PSP install again, remembering to schedule it rather than using the [Run Now] button.

[James Allen]

OK..nothing should be so frustrating to set up. I cleaned up the other servers in preparation for the PSP deployment.

Next, I installed hpSIM on the management server.

Now, when the scheduled PSP job runs, I get the following error...

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

It would be nice if it actually told you WHAT authentication failed.

Right now, everything is set to run with the domain administrator account....and it's failing????

One difference I have is that I've renamed the SNMP Public community to another name (for security). SNMP is already configured on all the servers.

[Rob Buxton]

I'm seeing this whenever I try and run any task in an account other than the one I installed HPSIM / OpenSSH in.

I've set up OpenSSH, added Users, used mxagentconfig to create the keys for additional users. No Go. I can login to the account using SSH / Putty.

What does work if I change any tasks to run under the account HPSIM was installed under, then things work.

I'm still hacking / playing with OpenSSH. I actually pulled a version down and reinstalled which did fix some initial problems but I'm still floundering around.
I agree it's a tad difficult finding out what has failed where!

[James Allen]

Well, that's the rub...I installed it under the domain admin account. I suppose what I'll try is the recommended fix for Win2K3, even though I'm using Win2KSP4.

[Rob Buxton]

James,
A couple of things to try.
Can you use the SSH Utility or Putty to login to various SSH Accounts?
Try:
Local Administrator, Account you installed HPSIM/OpenSSH under, your account.

I found these worked.
Run the mxagentconfig for each of the above accounts to ensure the OpenSSH keys have been correctly loaded. With the reinstall of OpenSSH I wiped the local Administrator keys.

If there's a Run As option in the Task set up, change that to the account that you installed things under and test and / or try the local Administrator.

I've fixed some issues but cannot get an Event Notification task that calls a Custom command to work under my account, but it will work under the Domain Admin Account.

[Anton_27]

I uninstalled and reinstalled the Open SSH from the managmnet CD 7.2 and I can now connect...