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

# sk184458 - Cannot add or remove BGP peers after upgrading to R81.20

| Property | Value |
|----------|-------|
| Solution ID | sk184458 |
| Date Created | 2026-02-26 |
| Last Modified | 2026-03-01 |
| Technical Level | Advanced |
| Products | Security Gateway |
| Versions | R81.20 |

## Symptoms

- After upgrading a clustered Security Gateway to R81.20, attempts to add or remove Border Gateway Protocol (BGP) configuration fail.

When attempting to add BGP peers, the following error appears:

`RTGRTG0019 BGP: No Global Router ID configured. Please configure the same Global Router ID on all cluster members.`

When attempting to configure the Global Router ID, the following error appears:

`RTGRTG0019 Router-id cannot be changed while BGP is configured and active.`

Additional Observations:

* Attempts to change the BGP configuration as described in [sk183315](https://support.checkpoint.com/results/sk/sk183315 )fail with the same error.
* Attempts to remove the BGP configuration as described in [sk115055](https://support.checkpoint.com/results/sk/sk115055) fail with the same error.
* No explicit Global Router ID was previously configured.
* The active Global Router ID was automatically derived from the Cluster Virtual IP (VIP).

## Cause

In R81.10 and lower versions, it is possible to configure BGP peers in a cluster without explicitly defining a Global Router ID. Although technically allowed, this configuration is not recommended.

Starting in R81.20, configuring an explicit BGP Global Router ID in a cluster is mandatory by design. This change enforces best practices and ensures consistent and stable BGP operation across all cluster members.
However, in this configuration the following conditions create a deadlock:  

* The system requires a Global Router ID to be configured on all cluster members before allowing BGP configuration changes.
* At the same time, an active BGP configuration prevents modifying the Global Router ID using standard commands.

This creates a configuration deadlock, where:

<!-- -->

* The Global Router ID cannot be set because BGP is active.
* BGP cannot be modified or removed because a Global Router ID is not configured.

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