> Source: [sk180742](https://support.checkpoint.com/results/sk/sk180742)

# sk180742 - Fullsync takes a long time to complete

| Property | Value |
|----------|-------|
| Solution ID | sk180742 |
| Date Created | 2023-04-13 |
| Last Modified | 2023-07-19 |
| Technical Level | Advanced |
| Products | Security Gateway, Scalable Platforms |
| Versions | R81.20, R81.10 (EOS), R81 (EOS), R81.20, R81.10 (EOS), R81 (EOS) |

## 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.

<br />

## Solution

This solution requires authentication. Please log in to view the full solution.

---

# Agent Instructions

This content is from the Check Point Support Center (https://support.checkpoint.com), the official knowledge base for Check Point cybersecurity products.

## Navigating This Knowledge Base

- **Complete index**: [llms.txt](https://support.checkpoint.com/llms.txt)
- **All SK articles**: [SecureKnowledge Sitemap](https://support.checkpoint.com/sitemaps/secureknowledge-sitemap-index.xml)
- **SK article URL pattern**: `https://support.checkpoint.com/results/sk/{skId}`
- **Markdown responses**: AI bot User-Agents automatically receive `text/markdown` content