# Fullsync takes a long time to complete

**Product**: ClusterXL, Maestro HyperScale Firewall, Scalable Chassis  
**Version**: R80.40 (EOS), R81 (EOS), R81.10 (EOS), R81.20  
**Last Modified**: 2023-07-19

## Symptoms
- Fullsync takes a long time to complete.
- The cluster node is down because of a FSYNC pnote. If you rebooted the appliance, the INIT pnote may be active.
- There are CCP packets on the sync interface of the two nodes (active and standby).
- Traffic captures show traffic on port 263 between the cluster members on the sync interfaces.

## Cause
During the Fullsync process, the standby node syncs the kernel table from the active node.

Some tables need to be synced for each FW instance, which increases the synchronization time depending on the number of instances configured on the node.

In addition, high CPU utilization on the active node can increase the synchronization time.

## Solution
We're here for you.

Please log in / sign in to view solution.

#### NOTE
This solution has been verified for the specific scenario, described by the combination of Product, Version and Symptoms. It may not work in other scenarios.

## Article Properties
**Access Level**: Advanced  
**Status**: Approved by TAC  
**Date Created**: 2023-04-13  
**Last Modified**: 2023-07-19