Troubleshooting Tip: Security Fabric automation stitches are not synchronized to downstream devices
| Description | This article describes how to troubleshoot the issue when the automation stitches are not synchronized from the Root FortiGate to the Downstream devices in the Security Fabric. |
| Scope | FortiGate v7.4.3, v7.4.8, in Security Fabric configuration. |
| Solution | In normal operations, all automation stitch objects (stitches, actions, triggers, destinations) should be synchronized. It is necessary to validate that both the parameters on the FortiGate Root and the downstream devices are correctly configured to allow object synchronization. More information can be found in the following document: Synchronizing objects across the Security Fabric.
In some configurations, after all the settings are validated, the automation stitch objects are not synchronized to downstream devices:
After performing a debug of the csfd daemon, the following output is displayed:
The information is sent by the Root FortiGate, but it is not received in the downstream device, because it has a buffer of 3,558 bytes to receive csfd objects (compressed using LZA4 algorithm), and the Root FortiGate is sending 4,818 bytes, so all the information is discarded.
As a workaround, it is possible to reduce the number of automation stitch objects until the synchronization is completed (command 'diagnose test application autod 2' shows automation stitches in the downstream device):
Note: Ensure configuration-sync is set to default on the root FortiGate to successfully run automation stitch to the downstream FortiGate. If this is set to local, the automation stitch will not sync from the root FortiGate to the downstream FortiGate, which leads to a failed automation stitch on the downstream FortiGate. |
