When a GMS (Global Master Server) is broken, try to 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 then deploy a new DB server.
Ensure that GMS is turned off.
Open Advanced Authentication Administrative Portal on the DB server.
Browse the Cluster section. A message is displayed: Please wait. Configuration/loading in progress… Maximum loading time is 5 minutes. Usually it takes 40-60 seconds.
Wait until you see the Cluster section updated. GMS is displayed in red as a list of servers after more than 15 minutes of unavailability.
Click Failover.
Open database port 5432 (TCP/UDP) on your NAT/Firewall for a time of conversion.
Click Convert to Global Master.
Click OK.
Wait a few minutes while Advanced Authentication is performing the conversion.
When you again see the Cluster section, close the database port.
If you have been using RADIUS server, those settings need to be reconfigured. In the Advanced Authentication Administrative Portal, switch to Events and edit the Radius Server event. Check the configuration including the Clients section and click Save to reconfigure the RADIUS server.
Update DNS so that the DNS name of 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.
Login to the Administrative Portal on Web servers. If you are not able to do it, try to reboot the Web servers. If you are still unable to login to Administrative Portal on Web servers, redeploy the Web servers.