.. _example_protocols_bgp_neighbor_soft-reconfiguration-inbound:

############################
Soft-Reconfiguration-Inbound
############################

This scenario demonstrates how to configure the soft-reconfiguration inbound option for a BGP neighbor.
When enabled, the router stores all received routes from the neighbor before applying inbound policies.
This allows viewing the original routes received (before filtering) using the received-routes command,
and enables soft resets to re-apply policies without tearing down the BGP session.

********************************************************************************
Test iBGP - Neighbor soft-reconfiguration inbound stores routes before filtering
********************************************************************************

Description
===========

Test to verify that soft-reconfiguration inbound stores received routes before policy filtering.
DUT1 advertises two routes (1.1.1.0/24 and 2.2.2.0/24) to DUT0.
DUT0 has a prefix-list configured to deny 1.1.1.0/24 and permit all other routes.
With soft-reconfiguration inbound enabled, DUT0 stores the original routes received from the neighbor
before applying the import policy. This allows verifying that 1.1.1.0/24 does not appear in the
BGP routing table because it was filtered, but it is still visible using the received-routes command
because soft-reconfiguration inbound preserved the original advertisement.

Scenario
========

.. include:: soft-reconfiguration-inbound/testibgp-neighborsoft-reconfigurationinboundstoresroutesbeforefiltering

.. raw:: html

  <hr>