Troubleshooting
Debugging cloud-init
Retrieving the cloud-init log can be useful when issues are occurring at bootup. To retrieve the log, log in to the FortiGate-VM and type the following into the CLI:
diag debug cloudinit show
Output will look similar to the following:
>> Checking metadata source gcp
>> GCP processing json format user-data
>> GCP trying to get config script from: https://us-central1-*********.cloudfunctions.net/fortigateautoscale-rnmlo
>> GCP download config script successfully
>> Run config script
>> Finish running script
>> FortiGate-VM64-GCPON~AND $ config system dns
>> FortiGate-VM64-GCPON~AND (dns) $ unset primary
>> FortiGate-VM64-GCPON~AND (dns) $ unset secondary
>> FortiGate-VM64-GCPON~AND (dns) $ end
>> FortiGate-VM64-GCPON~AND $ config system auto-scale
>> FortiGate-VM64-GCPON~AND (auto-scale) $ set status enable
>> FortiGate-VM64-GCPON~AND (auto-scale) $ set sync-interface "port1"
>> FortiGate-VM64-GCPON~AND (auto-scale) $ set hb-interval 25
>> FortiGate-VM64-GCPON~AND (auto-scale) $ set role slave
>> FortiGate-VM64-GCPON~AND (auto-scale) $ set master-ip xxx.xxx.xxx.xxx
>> FortiGate-VM64-GCPON~AND (auto-scale) $ set callback-url https://us-central1-************.cloudfunctions.net/fortigateautoscale-rnmlo
>> FortiGate-VM64-GCPON~AND (auto-scale) $ set psksecret ****************
>> FortiGate-VM64-GCPON~AND (auto-scale) $ end
How to reset the elected primary FortiGate
To reset the elected primary FortiGate, navigate to FireStore > FortiGateMasterElection and delete the only item. A new primary FortiGate is elected and a new record is created as a result.
For details on locating FireStore > FortiGateMasterElection , see Verifying the deployment.