HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- HPE ProLiant
- >
- Server Management - Systems Insight Manager
- >
- Re: Configuring VCA to connect to newer VCRM
Server Management - Systems Insight Manager
1833845
Members
2321
Online
110063
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
back
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
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- 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
10-09-2008 12:41 PM
10-09-2008 12:41 PM
Configuring VCA to connect to newer VCRM
I'm running SIM 5.2 with VCRM 2.1 on the same server, and I've got another server running VCA 2.1.1.720. We discovered this morning that the VCA on this server had settings that pointed to an repository that is now decommissioned. From the credentials that were previously used, I can tell that the VCRM on the decommissioned server was older than what I'm running now.
I'm trying to get the VCA configured to where it points to the current repositry, but when I use the credentials that I use everywhere else, I get an error "The specified repository, [SIM server], is invalid or not reachable." I can ping and traceroute from the server with the old agent to my current repository, so I'm feeling sure that there's not some funky network topology lurking around.
I tried to use Replicate Agent Settings and copy the VCA settings from a known good configuration, but got "There was an error processing the request to the agent, possibly due to a version conflict."
I've also tried making sure that there's a valid trust relationship between this server and the SIM server, and that the SNMP strings are set properly. Where should I go from here?
I'm trying to get the VCA configured to where it points to the current repositry, but when I use the credentials that I use everywhere else, I get an error "The specified repository, [SIM server], is invalid or not reachable." I can ping and traceroute from the server with the old agent to my current repository, so I'm feeling sure that there's not some funky network topology lurking around.
I tried to use Replicate Agent Settings and copy the VCA settings from a known good configuration, but got "There was an error processing the request to the agent, possibly due to a version conflict."
I've also tried making sure that there's a valid trust relationship between this server and the SIM server, and that the SNMP strings are set properly. Where should I go from here?
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-10-2008 12:34 PM
10-10-2008 12:34 PM
Re: Configuring VCA to connect to newer VCRM
I'd recommend to make sure that's the latest VCA, since one of the newest versions was very problematic, it could very easily be the cause. PSP 8.11 has just come out, you may want to try it out.
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP