Server Management - Systems Insight Manager
1833476 Members
3123 Online
110052 Solutions
New Discussion

Re: Deploy SW via HP SIM

 
Aelus
Advisor

Deploy SW via HP SIM

I want deploy software (HP Version Control Agent) via HP SIM (same machine with VCRM).

Firstly I got the error "Agent trust error", so I created a certificate and distributed (manual!) it to the according server. Is therefor any automation possible?

Now, I get these messages on several servers:

- Agent failed command
- HTTP is disabled on the target system
- Unable to contact system
- Version Control agent is not available

I suppose, the last two error codes are not that difficult to guess, but a real problem for me are the first two ones.

I use HP SIM 5.1 and Proliant Servers.

Does anybody also got these errors and know any sollution or source for help?

Only one server was successfull (hope so, after an open restart).

Thanks a lot,
Florian
6 REPLIES 6
Rich Purvis
Honored Contributor

Re: Deploy SW via HP SIM

Well - don't know for sure what your issue is but:

1) In the future if you want to fix a trust issue the easiest way is to use the Configure Repair Agent Settings feature in HPSIM.

2) If you do not have the VCA on the target system the easiest way to get it there is to use the Initial PSP Deployment feature of HPSIM. If you do not want to deploy an entire PSP with this feature then just create a custom PSP in the VCRM with all the agents and the system management homepage and just deploy that. (You may also need the health driver - I don't recall it has been a while since I have done it.)

Once you have a trust setup and configured VCA's running on your target servers you should be able to use Version Control. The VCA's have to be configured to point to the VCRM and have credentials (not the Administrator ID)to login to the VCRM. This can be preconfigured in the VCA component before you deploy it.

Good Luck,

-Rich
Why does my tivo keep recording Nickelodeon?
Aelus
Advisor

Re: Deploy SW via HP SIM

Thank Rich for your answer.

In the time between I've had read the issue with configure agent settings in an another thread and it worked quite good.

I do have a VCA on the targets, but only an old version. My problem is not really the VCA itself, i've got the problem with other software (drivers), too.

Your solutions with creating an customized paket for distributing only single drivers or agents may work, but I prefer to solve these exciting error messages and I think it's the usual way for distributing software.

I'll try to create an customized paket and will post it here again.

See you later,
Florian
Aelus
Advisor

Re: Deploy SW via HP SIM

Back again.

I created a test paket (with one agent inside) and distributed it to my servers but only few worked (same which worked before, but rather less).

I think the function behind is the same - so the error messages I get are the same again.

My problematic errors are still:
Agent failed command
HTTP is disabled on the target system

An addition: the distribution of an entire Support Pack is successfull, I did it twice today.

Any suggestions? Thanks in advance.
dospavlos
Frequent Advisor

Re: Deploy SW via HP SIM

Also receiving the 4 error messages as the original poster when deploying multiple components to a large group of servers from a scheduled sim deployment job. Runing SIM 5.1 sp1. Anyone found a fix?
Aelus
Advisor

Re: Deploy SW via HP SIM

I still have this problem with software distribution. The trust relationship is installed and working, testet in/with MSH.

Any thoughts?
Nathan Gau
Occasional Advisor

Re: Deploy SW via HP SIM

First, I don't see why people are saying it is an agent trust issue. That is a different error. I think I managed to resolve this on my system (which is running SIM 5.1). To do that, I first tried to "configure and repair agents" from the Configure menu. This will take care of all trust agent issues, and notably it did not work. There was an error in that log saying open SSH was not installed. So, from the deploy menu, I chose to install Open SSH. For whatever reason, this took care of the "HTTP is disabled on the target system" error that I was getting. I do not deploy open ssh normally and have a number of systems where I have never installed it, so I cannot tell you why it is needed, but it allowed me to procede with the driver/firmware update.

Hope it helps

Nate