Server Management - Systems Insight Manager
1833764 Members
2831 Online
110063 Solutions
New Discussion

HP SIM 4.x OPENSSH MxAgentConfig Connection Problem.

 
Murat ACINCI
Occasional Contributor

HP SIM 4.x OPENSSH MxAgentConfig Connection Problem.

I installed HP Systems Insight Manager on my 2003 Enterprise Server. and installed openssh on my crm server which also runs 2003 enterprise. I've added my hpsim user to passwd file with mkpasswd -d -u hpsim consept >>....
And on CMS, I tried to connect to my crm server with MxAgentConfig tool.. I used the same account.. hpsim. but i recieve "failed to establish connection to ctsc"...

what may be the problem ?
does anyone have any idea ? or have the same problem and also the solution !
thanks
3 REPLIES 3
Alan Wells_1
Occasional Advisor

Re: HP SIM 4.x OPENSSH MxAgentConfig Connection Problem.

Hello,

I am also having this same "failed to establish connection" message. I tried logging in as and using both my local admin account and the domain account I used when installing the app. I had this same problem with HPSIM 4.0 and rebuilt the entire server and installed 4.01. I have the same problem with both builds. I have gone through all the troublshooting in the HPSIM SSH guides. I checked this stuff http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=384587.

I have done every troubleshooting step I could find. I have searched this forum for over a week and still have not foud a resolution. And yes I have reinstalled OpenSSH about 20 times before rebuilding the server. I did all the steps to check the keys and deleting them and all that. I am stuck here.

Anyhelp would be appreciated. Apparently th HP support line folks start drooling on themselves as soon as I say OpenSSH. Open What?
Ivan KOVAC
Respected Contributor

Re: HP SIM 4.x OPENSSH MxAgentConfig Connection Problem.

hello

For Windows2003 is a procedure in Readme.txt file how to configure SSH to work corectly. Are you done this.

Ivan.
Alan Wells_1
Occasional Advisor

Re: HP SIM 4.x OPENSSH MxAgentConfig Connection Problem.

Actually I am running Windows 2000 but I did perform the changes recomended for 2k3 in the read me. I did finaly get this to work by following these steps also.

I logged in as my domain account. The domain account that HPSIM is starting with.

I removed OpenSSh.

I reinstalled but the setup would freeze. I ended the task and performed another uninstall because it did put some stuff on the system. I did not delete the folders after uninstall because every time I did that, the re-install would freeze. Without deleting the folder I was able to finish the install. Don't ask why.

Once the install was done I ran the mkpasswd -d -u >>c:\progra~1\openssh\etc\passwd. This completed with no errors. In fact it only goes back to the command prompt with no messages just so you know.

I ran mkgroup -d >>c:\progra~1\openssh\etc\group. This took a while because it copies all domain group info to the file on the HD. Again no messages except a few about some groups that it couldn't find or something.

I logged off and back on as the local admin and ran mkpasswd -l -u >>c:\progra~1\openssh\etc\passwd. This is just to add the local admin to the password file for good measure.

I logged off and back on as my domain account. I ran ssh domainusername@servername from c:\progra~1\openssh\bin and it prompted me for yes or no to login. I said yes. I typed my password and login was successful. I typed quit. I typed MxAgentConfig -g and entered my info into the GUI. The logon was successful. Be careful here. You must use the domain login that your are currently logged in as since the app looks for the home share and will fail if you use some other login like local admin.

Once I knew OpenSSH was working again I then checked my Event task which was calling to my custom command in HPSIM. I made sure that the task owner was my domain account. In my case I was using a task to identify invalid logins as a test. When I logged in with an invalid login I received the page from Attention software that I expected. All the task logs now show completed with no errors.