When a hostname change is performed locally on the FortiGate, FortiGate Cloud does not reflect the updated hostname immediately.
The FortiGate Cloud portal will still reflect the old hostname after the change on the FortiGate. The updated hostname is typically synced after the next FCP UpdateMgr request.
To force FortiGate Cloud to reflect the hostname change immediately, run below command:
diagnose fdsm contract-controller-update
Example:
FGT-HOSTNAME_UPDATED # diagnose fdsm contract-controller-update
Protocol=2.1|Response=202|Firmware=FAZ-4K-FW-2.50-100|SerialNumber=FAMS000000000000|Persistent=false|ResponseItem=HomeServer:g96.fortigate.forticloud.com*AlterServer:g96.fortigate.forticloud.com*AccountType:regular*Contract:XXXXXXXX*NextRequest:86400*UploadConfig:False*ManagementMode:Local*ManagementID:12XXXXXX78
Result=Success
If the result shows success, the updated hostname should reflect immediately on FortiGate Cloud.
Another option is to restart the 'forticldd' process. To check the current running forticldd process ID, run this command:
diagnose sys process pidof forticldd
To restart the process:
diagnose sys kill 11 <process_id>
Example:
FGT-HOSTNAME_UPDATED # diagnose sys process pidof forticldd
1934
FGT-HOSTNAME_UPDATED # diagnose sys kill 11 1934
If the issue persists after performing the process restart, run the following debug commands and provide the output to Fortinet TAC Support for checking:
diagnose debug console timestamp enable
diagnose debug application forticldd -1
diagnose debug enable
| 
