Announcements

SecurID® Discussions

Browse the SecurID discussion board to get product help and collaborate with other SecurID users.
vee_hernandez
New Contributor
New Contributor

Replication port 7002 communication error

Hi all, 

We are installing the replica server, however after attaching the replica package we encounter an error 
"The primary instance cannot communicate with the replica instance on the port(s) 7002"

vee_hernandez_0-1650441304470.jpeg

 

its on the Vmware environment, same ip segment, same vswitch and no firewall in between. 

anyone encounter the same issue?

thanks! 

Labels (2)
0 Likes
5 Replies
DanielRobinson
Occasional Contributor
Occasional Contributor

Can the Primary resolve the Replica's hostname, and can the Replica resolve the Primary's hostname?  2) Can they ping one another by hostname?

0 Likes
tom-arner
Contributor
Contributor

Yes - anyone encounter the same issue?

The current Primary and 2 replicas are syncing fine. But when I try adding a new hardware replica port 7002 is not open for the candidate - The servers are in the same broadcast network subnet?  ??

tom
tom-arner
Contributor
Contributor

Yes - same ip segment, same vlan and no firewall in between them - Thinking iptables is not set to open the port?

tom
0 Likes
tom-arner
Contributor
Contributor

Port 7002 for Transferring data from primary instance using afs3-prserver is working - tcp is setting up a handshake fine but the syncing data from the primary to the new server is failing. I have both rsaadmin users and passwords. They are not the same. Should they be? How does Authentication for creating a replica on a server work?

tom
0 Likes
tjoynt
Contributor
Contributor

Hi Vee, 

Try adding Host File entries for every RSA Authentication Manager. It is in the Operations Console, under Administration -> Network -> Hosts File. You may need to do this on the primary and each replica. This resolved a similar problem for me. 

Hope this helps,

-- Tom

0 Likes