- Community Home
- >
- Servers and Operating Systems
- >
- HPE ProLiant
- >
- Server Management - Systems Insight Manager
- >
- VPM2.0.3 VPM Agent failed to install
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-08-2007 10:34 PM
тАО03-08-2007 10:34 PM
VPM2.0.3 VPM Agent failed to install
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-12-2007 01:43 AM
тАО03-12-2007 01:43 AM
Re: VPM2.0.3 VPM Agent failed to install
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-12-2007 04:09 PM
тАО03-12-2007 04:09 PM
Re: VPM2.0.3 VPM Agent failed to install
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-30-2007 05:43 PM
тАО04-30-2007 05:43 PM
Re: VPM2.0.3 VPM Agent failed to install
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-02-2007 04:54 AM
тАО05-02-2007 04:54 AM
Re: VPM2.0.3 VPM Agent failed to install
Thanks,
lucas