Zurück
-
Titel
How to transfer the Primary role to another console appliance -
Beschreibung
How to transfer the Primary role to another console appliance. -
Ursache
The 'Transfer Authoritative Primary' function is used when you want to switch the primary role from one cluster member to another. This should only be used when the original primary member is up and running. -
Lösung
Transferring the primary role is typically a quick operation taking from 5 to 30 minutes.
As the console appliances will need to be changed into maintenance mode there will be an outage.
At the end of the process end users will need to access /tpam using the IP address/DNS name of the new primary.
To transfer the primary role to another console appliance in the cluster1. Log on to the /admin interface of the primary.2. Make sure the primary is selected in the cluster member list.3. Select the Run Level check box.4. Select Maintenance from the list.5. Click the Change Run Level button.6. Click the Continue with Change button.7. Select the replica from the cluster member list that you want to transfer the primary role to.8. Select the Run Level check box.9. Select Maintenance from the list.10. Click the Change Run Level button.11. Click the Continue with Change button.12. Click the Transfer Author. Primary button.13. Click the Continue with Change button. The role of the replica will automatically change to “Primary”and the original primary will automatically have it’s role changed to “Replica”. Any other replicas in the cluster will automatically recognize the new primary.
14. Select the former primary from the cluster member list.15. Select the Run Level check box.16. Select Operational from the list.17. Click the Change Run Level button.18. Log on to the /admin interface of the new primary.19. Select the Run Level check box.20. Select Operational from the list.21. Click the Change Run Level button. -
Weitere Informationen
After transfer of the Primary role, some users may complain that they are unable to login using their browsers. Closing any previously open browser connections to the TPAM appliances, deleting the browser cache and then reattempting to login will resolve this issue in most cases.