Problem with a replica site
I have a replica site that stopped reporting to the primary. In the Replication Status Report, it shows that the Instance is Offline. I have rebooted it and still no avail. There is an option to delete the instance which I did. How do I add it back as a replica site so that my primary recognizes it?
- Auth Manager
- Authentication Manager
- Community Thread
- Forum Thread
- RSA Authentication Manager
- RSA SecurID
- RSA SecurID Access
often it is worth troubleshooting a offline replica, there are replication logs in /opt/rsa/am/server/logs and there is a procedure to force the replica [Synch] button, which transfers the whole primary database to the replica. Sometimes a firewall rule is changed to prevent replicas and primaries from communicating on TCP 7002 and other ports.
But if you have deleted the replica from the primary, now the primary is no longer trying to connect. You have to deploy a new replica. This means creating a replica package on the Primary, very easy, but the existing replica would have to be made into a brand new, about to be deployed replica. If it were a VM, you need to follow the getting started guide and deploy a new VM, run quick setup and import the little replica package from the primary.
RSA Authentication Manager to find version 8.5 getting started guides.
If replica were a hardware server, you need to "factory reset" it by running installation software from CD, DVD or USB stick. See this KB