| Description | This article discusses issues with ZTNA tag syncing. |
| Scope | FortiGate v7.x. |
| Solution |
ZTNA tags are synced when FortiClient EMS is added to Security Fabric To add FortiClient EMS to Security Fabric, follow this related document: Add EMS to Fabric Connector
To check the fcnacd status and the web socket connection, use the following command. This command works under 'config system global' in the VDOM environment: diagnose test application fcnacd 2
Verify if the tag is being synced:
diagnose firewall dynamic list | grep <tag_name>
If ZTNA tags are not being synchronized properly, enable the following debugs and make some changes to tags on some endpoints:
diagnose debug application fcnacd -1 diagnose debug console timestamp enable diagnose endpoint filter show-large-data yes diagnose debug en
Restart the fcnacd process or make changes to endpoints to check the logs.
To restart the fcnacd process use the following command:
diagnose test application fcnacd 99
Stop the debugs after reproducing the issue using the following commands:
diagnose debug disable diagnose debug reset
To force the tag sync without restarting the fcnacd, terminate the WebSocket connections:
diagnose test application fcnacd 11
General syntax:
diagnose test application fcnacd
In scenarios where the issue manifests randomly yet persists over time, an automation script can be used to mitigate the behavior. However, upgrading the FortiEMS server to the latest available patch is recommended.
config system auto-script edit "refresh_ztna_tags" set interval 600 set repeat 0 set start auto set script " diagnose test app fcnacd 4 diagnose test app fcnacd 5" next end
Related article: |
The Fortinet Security Fabric brings together the concepts of convergence and consolidation to provide comprehensive cybersecurity protection for all users, devices, and applications and across all network edges.
Copyright 2026 Fortinet, Inc. All Rights Reserved.