# BGP Sessions Fail to Re-Establish After SMO Failover Due to Physical Link Failure

**Product**: Maestro HyperScale Firewall  
**Version**: R81.10 (EOS), R81.20, R82  
**OS**: Gaia  
**Last Modified**: 2026-07-23

## Symptoms

- The original Single Management Object (SMO) went down due to a physical link failure (for example, a cable was accidentally disconnected).
- After restoring the link, when the original SMO recovers and becomes active again, Border Gateway Protocol (BGP) sessions fail to establish.
- BGP sessions alternate between active and connect states for 10-15 minutes before stabilizing.

## Cause

The original SMO did not synchronize BGP session state with the new SMO during failover. As a result, stale entries remained in the connection table, causing session establishment delays after recovery.

## Solution

This problem was fixed. The fix is included in:

- [Jumbo Hotfix Accumulator for R82](https://sc1.checkpoint.com/documents/Jumbo_HFA/R82/Default.htm) starting from Take 103
- [Jumbo Hotfix Accumulator for R81.20](https://sc1.checkpoint.com/documents/Jumbo_HFA/R81.20/Default.htm) starting from Take 158

If you choose not to upgrade, [Contact Check Point Support](https://www.checkpoint.com/support-services/contact-support/) to get a Hotfix for this issue.

A Support Engineer will make sure the Hotfix is compatible with your environment before providing it.

For faster resolution and verification, collect these files:

1. [CPinfo](https://support.checkpoint.com/results/sk/sk92739) file from the Management Server involved in the case.
2. [CPinfo](https://support.checkpoint.com/results/sk/sk92739) file from the Security Gateway / each Cluster Member / Security Group involved in the case.

**Hotfix installation instructions:**  
Refer to [sk168597 - How to install a Hotfix](https://support.checkpoint.com/results/sk/sk168597).

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