When a GMS (Global Master server) breaks, restore it from backup or a snapshot. If this does not work, perform the following steps to convert an existing DB server from the same site as GMS to a new GMS and deploy a new DB server.
You can also use the following instructions to promote a DB server from a secondary site to a new DB Master of the same site when the current DB Master of the site is broken.
As a pre-requisite, ensure that the GMS is turned off.
Open the Advanced Authentication Administration portal on the DB server.
Click Cluster.
Wait until you see the Cluster section updated.
Click Failover.
Open database port 5432 (TCP/UDP) on your NAT/Firewall for a time of conversion.
Click Convert to Global Master.
Click OK.
When you see Cluster again, close the database port.
If you have been using the RADIUS server, you must reconfigure the settings.
In the Administration portal, click Events and edit the Radius Server event.
Check the configuration including the Clients section.
Click Save to reconfigure the RADIUS server.
Update the DNS so that the DNS name of the lost GMS resolves the IP address of the server being converted.
IMPORTANT:Do not change the IP addresses of working servers.
Update the load balancer configuration if required.
Install a new server with an ISO file of the same version as on the new GMS and configure a new DB server instead of the converted one.
NOTE:If you have two DB servers in the site, you must reinstall the second DB server to get the latest database.
Log in to the Administration portal on Web servers. If you are not able to log in, reboot the Web servers. If you are still unable to log in, redeploy the Web servers.