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

# sk107544 - BGP route appears with flags "H" (Hidden) and "i" (Inactive) in the output of "show route bgp all" command

| Property | Value |
|----------|-------|
| Solution ID | sk107544 |
| Date Created | 2015-09-07 |
| Last Modified | 2017-05-15 |
| Technical Level | Advanced |
| Products | Security Gateway |
| Versions | R82.10, R82, R81.20 |
| OS | Gaia |

## Symptoms

- * Output of "*show route bgp all*" command shows the learnt BGP route with flags "H" (Hidden) and "i" (Inactive).

* BGP traces (per [sk101399](https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&solutionid=sk101399)) show:  

  `BGP RECV flags 0x40 code Origin(1): Incomplete`

## Cause

This issue might occur when there are at least three BGP peers, two of which are adjacent and in the same Autonomous System, while the third BGP peer is in a ***different*** Autonomous system.

In such scenario:

1. When a route is propagated from one BGP peer to another BGP peer in a ***different AS*** - the nexthop address is the address of the BGP peer, from which the route was propagated - as expected.   

2. When a route is propagated from one BGP peer to another BGP peer in the ***same AS*** - the nexthop address is the address of the ***BGP peer from the different AS, from which the route originated***. This causes the route to become Hidden and Inactive, as the BGP peer, to which the route was propagated, does not know how to reach the original network, as the nexthop IP address is not directly connected to it.

To demonstrate, let us imagine the following scenario:

Topology:  
AS 10 ( X --- Y ) --- ( Z ) AS 20

* BGP peer X and BGP peer Y are in AS 10
* BGP peer Z is in AS 20
* BGP peer X and BGP peer Y are directly connected
* BGP peer Y and BGP peer Z are directly connected
* BGP peer Z has a directly connected route to 5.5.5.0/24, which we wish to propagate to BGP peer Y and ultimately to BGP peer X
* When the route is propagated from BGP peer Z to BGP peer Y, BGP peer Y knows that the nexthop for the route is BGP peer Z, as it arrived from a *different* Autonomous System
* When the route is propagated from BGP peer Y to BGP peer X, BGP peer X knows that BGP peer Z is the nexthop IP address, as the route came from the *same* Autonomous System

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