- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
After promotion of replica to primary, new replica is unreachable
Hi all,
situation: a couple of auth manager 8.2 SP1, one primary one replica.
After promotion on the replica to primary the new replica is in Replication Status unreachable.
Pre-check before promotion was ok, checked all (network, dns resolution, clock, port...), user are autenthicating on both instances. The old primary seems to be correctly demoted and it is shown as replica now.
What can I do to solve this unreachable status?
Thanks a lot
BR
Elena
- Tags:
- AM
- am 8.2 sp1
- Auth Manager
- Authentication Manager
- Community Thread
- Discussion
- Forum Thread
- replica unreachable
- rsa authenticaion manager
- RSA Authentication Manager
- RSA SecurID
- RSA SecurID Access
- SecurID
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I would recommend you contact Customer Support for this type of issue.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I would recommend you contact Customer Support for this type of issue.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
When you promoted the original replica, did you promote for Maintenance? that type of promotion would attempt to attach the original primary as a replica, after copying over all log files. If you promoted for Disaster Recovery DR, then the original primary will never attach. If the Promotion was for Maintenance but the original primary failed to attach, there would be logs associated with that, and that is why Piers recommended opening a case. Some error messages could indicate port 7072 was not open between the Primary and the Replica. But there are other reasons it could have failed
