Have you tried manually installing database on the management server and tried to push policy towards the other gateways making sure everything is aware of the change of hostname and certificates? This is the point where I would simply enable IKE-debug on the affected gateways, grab the ike.elg and inspect it using IKEview from Check Point to get a better understanding of what is going on.
It's so quick and easy to enable ike debug on the firewalls, and the ike.elg is so small and easy to understand by using IKEview (sk30994) it will often save me a lot of time when I'm confused about why a VPN-tunnel is not working.
Connect to the gateway using SSH and enable IKE debugging:
vpn debug trunc
vpn debug ikeon
Make sure to force the tunnel establishment. I will normally utilise vpn tu on the gateway.
TYPE IN THE IP OF THE PEER GATEWAY
Make sure some traffic is trying to pass through the tunnel so we know it's trying to re-establish itself.
vpn debug truncoff
vpn debug ikeoff
Grab the ike.elg from $FWDIR/log/ike.elg and open it using IKEview and look through the details and figure out where it's failing. It should provide you with plenty of details. Is it because of the certificate exchange or is it failing because of something entirely different?
It might be a good idea to do this on both sides of the VPN tunnel if you have SSH access to both. So do the same on both the gateway that you re-named, and one of the other gateways that it's having difficulties establishing a VPN-tunnel towards.
Certifications: CCSA, CCSE, CCSM, CCSM ELITE, CCTA, CCTE, CCVS, CCME