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

# sk170912 - Wrong Cluster interface is advertised as BGP next hop

| Property | Value |
|----------|-------|
| Solution ID | sk170912 |
| Date Created | 2020-12-10 |
| Last Modified | 2020-12-30 |
| Technical Level | Advanced |
| Products | Security Gateway |
| Versions | R82.10, R82, R81.20 |
| OS | Gaia |

## Symptoms

- * When a BGP border router goes down, Cluster member sends the source of wrong interface as the BGP next hop

* There is a second route to the BGP peer through a different interface.

## Cause

A race condition between BGP advertisement and interface coming up: When the first interface goes down, routed tries to use second interface to reach BGP peer, however when the first interface comes back up, the connection is now going through the first interface.

Since the connection got created and is in connection table it is NATed behind the Cluster VIP of the second interface.

Once the connection is shifted to the first interface, the entry in table remains the same and source NAT still hide behind cluster VIP of second interface. This is due to the design of clusterXL mechanism and VIPs.

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