topic Re: VPM2.0.3 VPM Agent failed to install in Server Management - Systems Insight Manager

VPM2.0.3 VPM Agent failed to install

dc01 — Fri, 09 Mar 2007 06:34:12 GMT

Hi,

SIM5.1+VPM2.0.3 is used.
There are eight target systems,
and six of eight are on VMware ESX3.0.
VPM Agent cannot be installed in one target system on VMware.

Before,It was possible to install it in the all target systems on VMware .
When two of six was restructured, and the installation of VPM Agent was tried, one
alone was not able to be installed.
target system is Red Hat Linux ES 4.0 update4.

error massege:
Error: pvaclientinstall/21 : Failed to get DN for Client
Error: pvaclientinstall/21 : No Client DNs for the clients

What does this "DN" ?
If what correspondence is done, can this problem be solved?

The error message is appended.

Re: VPM2.0.3 VPM Agent failed to install

Lucas Medina — Mon, 12 Mar 2007 08:43:31 GMT

Hello,

There might be something wrong with the connection between the host and the target systems (RH4), please double check the following steps:

- Are you able to connect from the host to the target thru SSH?
- Could you ping the target machines from the host and vice versa?
- Global Protocol settings are properly set with the correct targets credentials in HPSIM/Options?
- SNMP package is installed in the target systems?
- Make sure hosts file is up to date in both sides with the ip and hostname of each other.

In addition, we don't use to bless VPM in these kind of targets because they are not in our support matrix.

Please let me know it if solves your issue.

Thanks,
Lucas

Re: VPM2.0.3 VPM Agent failed to install

dc01 — Mon, 12 Mar 2007 23:09:34 GMT

Hi,Lucas

Thank you for advice.

Though it confirmed,
There is no problem.

It is felt that there seems to be a problem in the VPM server as long as the
log is seen.
Though it is thought that SIM or VPM has information on the target system,
It thinks whether the information is correct.
Or, is 'DN' acquired from the target system?

After that, The matrix was confirmed.
The target systems on VMware are all outside the supports.

Regarads
dc01

Re: VPM2.0.3 VPM Agent failed to install

dc01 — Tue, 01 May 2007 00:43:08 GMT

Hi,Lucas

After all, the cause is uncertain.
It corresponded in the following way.

(1)The device.mk file is opened.
(2)Nothing is done and the superscription is preserved.

This makes DN information new.

Moreover, though there was an error message of "RMP:Alarm Container not present" on
the log, too
It was possible to restore it by reinstalling VPM.

Apparently, VPM seems to support VMware.

thanks

dc01

Re: VPM2.0.3 VPM Agent failed to install

Lucas Medina — Wed, 02 May 2007 11:54:20 GMT

So, in others words, VPM is properly working for you now, right?

Thanks,
lucas