VMware Cloud Community
jaffanz
Enthusiast
Enthusiast
Jump to solution

registration failure vREP 6.5.1 with vCSA 6.5u3

Kia ora all, have run into this challenge to what was previously a 'never failed' easy task; registering vSphere Replication.

Anybody seen this before or can direct me in any way will be much appreciated.

Goal

To register vSphere Replication (vREP) 6.5.1 with a vCenter 6.5u3 appliance (vCSA).

The vREP & vCSA are running as VMs on a management vCenter.

Outcome

Registration fails. Error screen shot included below, top of RED text contains;

vCenter Server connection failed: Exception in thread "main" java.lang.RuntimeException

Configuration information

Deploy vSphere Replication to the Target Management vCenter which is:

A management vCenter & cluster that hosts the to-be-paired production vCenter and replication appliance.

                [vCSA-Mgmt] a vCenter for windows version 6.0. on LAN-Z.

     ESXi management cluster on LAN-Z.

vSphere Replication information:

[vRep-Prod] a vShere Replication appliance 6.5.1 -14002386 on LAN-A.

Production vCenter server to register vREP with:

[vCSA-Prod] a vCenter 6.5u3 appliance on LAN-A.

- Was upgraded in-place from vCenter 6.0u2. (3634788). the appliance is only a couple of weeks old with 1x cluster.

ESXi production cluster on LAN-B.

vSphere replication appliance is deployed to the management vCenter server. This also hosts the production vCenter for vREP to work with.

Note the Deploy OVF picks up the management vCenter server in the "Service Bindings" section. This is the server provided during installation as the installation target but is not the server replication will be registered with.

vSphere Replication will NOT be registered with the management vCenter server [vCenter-Mgmt].

vSphere Replication is to be registered with the vCenter server [vCSA-Prod].

The Appliance powers on fine. Can connect to it on port 5480 and go to configuration section.

Initially the incorrect management vcenter details for [vCSA-Mgmt] are loaded on the configuration screen, then they are changed and the correct production vcenter details are provided, including credentials.

Choose Save and Restart Service.

Get the red error page above.

Has anybody found this problem before?

Reply
0 Kudos
1 Solution

Accepted Solutions
jaffanz
Enthusiast
Enthusiast
Jump to solution

i ended up moving the source site vReplication Appliance and a second vReplication Server to the same subnet as the source ESXi Management vKernels were connected on and onto the source cluster hosts.

Registration was immediate.

View solution in original post

Reply
0 Kudos
5 Replies
KocPawel
Hot Shot
Hot Shot
Jump to solution

Hello,

What about PSC Controllers?

Is it embedded version? If it is external installation what version of PSC do you have?

Did you check connectivity between components?

VMware Knowledge Base

Reply
0 Kudos
jaffanz
Enthusiast
Enthusiast
Jump to solution

oh yes, forgot that.

the target production vCenter is a single vCSA appliance with embedded everything.

Around connectivity; according to the 'network & security guys' no firewalls between vCenter & ESXi hosts as in same 'security zone' and i've put the vREP appliance on the same subnet with no microsegmentation.

thanks for that link though.

Reply
0 Kudos
KocPawel
Hot Shot
Hot Shot
Jump to solution

What vSphere Replication version exactly do you have?

6.5.1 has few versions. Newest is 6.5.1.4.

For example vCenter 6.5 Update was supported starting from version 6.5.1.3.

Could you check that?

Reply
0 Kudos
jaffanz
Enthusiast
Enthusiast
Jump to solution

hi,

Using version

VMware vSphere Replication 6.5.1.4

https://my.vmware.com/group/vmware/details?downloadGroup=VR6514&productId=614&rPId=38663 ​​

VMWare-vSphere_Replication-6.5.1-14002386.ISO

went to the web link VMware Knowledge Base for vSphere Replication build numbers and noticed that 6.5.1.4 was missing.

Reply
0 Kudos
jaffanz
Enthusiast
Enthusiast
Jump to solution

i ended up moving the source site vReplication Appliance and a second vReplication Server to the same subnet as the source ESXi Management vKernels were connected on and onto the source cluster hosts.

Registration was immediate.

Reply
0 Kudos