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

# sk109401 - BGP routes are not synchronized to Standby cluster member / Standby Virtual System

| Property | Value |
|----------|-------|
| Solution ID | sk109401 |
| Date Created | 2015-12-31 |
| Last Modified | 2020-09-21 |
| Technical Level | Advanced |
| Products | Security Gateway |
| Versions | R82.10, R82, R81.20 |
| OS | Gaia |

## Symptoms

- * Routes learned from BGP are not synchronized to the Standby cluster member (or Standby virtual System).

* Upon fail-over, a traffic outage will occur for all the networks, which have been added/removed on the Active cluster member (or Active virtual System).

## Cause

**Definition:**   
The RouteD daemon connection (over TCP port 2010) between Standby and Active cluster members idles after standard TCP session timeout (3600 seconds) if no routing update has been pushed for that duration.  
A bug in the implied rule that should accept traffic from/to TCP port 2010 causes the traffic to drop on the cleanup rule instead of being accepted on rule 0.  

Enabling RouteD daemon traces / rebooting the Standby cluster member will make the issue disappear for additional 3600 seconds.  
The reason - when we enable/disable traces, we cause the RouteD daemon to reconfigure itself. As a result, a new connection will be established, and the routes will be synchronized after a few moments.  

*Example* :  
If a BGP environment, which receives routing changes (to the Active cluster member) from its BGP peer, does not have a any change for 3600 seconds, then no route updates will be synchronized between the Active and Standby cluster members over TCP port 2010.  
At that point, the connection, which is originated by the slave RouteD daemon (usually on the Standby cluster member) will be expired and removed from the Connections table.  
After this, any new routing update that will be pushed by the BGP peer, will be updated on the Active cluster member, but when RouteD daemon will attempt to synchronize it to the Standby cluster member, the update will be dropped on the Standby cluster member.

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