This post is more than 5 years old
43 Posts
1
10855
September 12th, 2011 07:00
Error when add Vcenter to RecoverPoint
Hi,
I tried to add a vcenter to RP through gui and cli but I receive always an invalid certificate or port. I used:
RP ver 3.3
ESX 4.1
I used port 443 with corp/user and password. I tried also with and without certificate but I cannot able to see any vm discovered.
Have you never encountered such problem?
Thanks,
Mario
No Events found!
JamesBEMC
257 Posts
0
September 21st, 2011 09:00
Sorry for the delay.
Please check EMC KB emc217806
Validate RPA can ping VC IP
Validate VC can ping RPA Cluster IP
Validate VC is listening on port 443 ( netstat -an | find "443")
Note : Use 'boxmgmt' user to run commands from following menu options :
** Main Menu **
[2] Setup
[8] Advanced options
[6] System internal operations
[2] Run internal command
This is the list of commands you are allowed to use: switch_utils netstat ethtool date telnet ping ssh top
Enter internal command:
Using this secure connection you must use the Virtual Center (VC) certificate which can be found in the following directory on the Virtual Center server:
C:\Documents and Settings\All Users\Application Data\VMware\VMware VirtualCenter\SSL\rui.crt
Copy this to a location on the PC that you are running the RecoverPoint GUI and vCenter Server install from.
NOTE: This location maybe different on Windows 2008 server and you will need to search accordingly for the certificate file.
Using the RecoverPoint Console, right-click vCenter Servers, select Add vCenter Server credentials.
Under Credentials :
Server IP : < Note : this is the Virtual Center IP address and not an ESX IP >
Port number : 443
Username :
Password :
Certificate files:
Reference RecoverPoint 3.2 Administrator Guide for more information.
Registered EMC Powerlink customers can download documentation from Powerlink. From the Powerlink home page menu bar, select Support > Technical Documentation and Advisories > Software ~ P-R ~ Documentation > RecoverPoint > Maintenance/Administration.
Because the view is restricted based on customer agreements, you may not have permission to view certain downloads. Should you not see a documentation download you believe you should have access to, follow the instructions in EMC Knowledgebase solution emc116045.
mcontestabile
43 Posts
0
September 23rd, 2011 04:00
Hi,
solved this issue following the solution indicated in this thread:
Using this secure connection you must use the Virtual Center (VC) certificate which can be found in the following directory on the Virtual Center server
I made a mistake because I continued to import the certificate from web site of vcenter.
I don't kwow if is the same problem
Mario
noqwertgb
5 Posts
0
September 23rd, 2011 04:00
Hi @ll,
this problem is really annoying. I´ve tried it with recoverpoint 3.4SP1 and vSphere 5 (VAPP vCenter) and it worked like a charm. A few mouseclicks and RPA was linked with vSphere5.
With vSphere 4.1 it won´t work at all. I always get this error. "Warning: Invalid port or certificate."
VC can ping the RPA Cluster-IP
VC is listening on Port 443
RPA can ping the VC
I´ve used the certificate from "C:\Users\All Users\VMware\VMware VirtualCenter\SSL\rui.crt".
Login Credentials tried from Domain Admin down to Local Admin of the vCenter Server.
rui.crt is valid till 2020.
The Firewall on the Win2k8R2-Server for vCenter is switched OFF.
It doesn´t matter if I do it via Java console or directly on the CLI.
What could be the problem?
Regards,
Wolfgang
brettesinclair
2 Intern
•
715 Posts
0
October 18th, 2011 16:00
I have the same problem as Wolfgangz.
A new RP 3.4sp2 install.
I have successfully added the remote site VC server to the RP gui.
When I try and add the local sitr VC server, it bounces up the "Invalid port or certificate" dialog.
Credentials and certificate have been checked and double checked.
Connectivity in both edirections is ok (ping telnet etc from VC server and from RPA)
Very frustrating !
mcontestabile
43 Posts
0
October 19th, 2011 04:00
Have you read the "EMC KB emc217806"? Please note that it means the certificate in Virtual Center. I've soved applying that solution to my 3.3 RP.
brettesinclair
2 Intern
•
715 Posts
0
October 19th, 2011 14:00
Yes, that's what I have done successfully for one of the virtual center servers, but not the other.
Think I'll have to log an SR....
sgtserge1
15 Posts
0
June 20th, 2012 06:00
Hi, same problem here. Solved by rebooting the RPAs..
Sergio