.. _example_protocols_bgp_parameters_no-client-to-client-reflection:

##############################
No-Client-To-Client-Reflection
##############################

Scenario to verify BGP **no-client-to-client-reflection** parameter configuration.

In standard iBGP, the split-horizon rule prevents a router from re-announcing routes
learned from one iBGP peer to another iBGP peer. Route Reflectors override this rule
for their clients, reflecting routes between them to avoid full-mesh requirements.

The ``no-client-to-client-reflection`` parameter re-enables a form of split-horizon
specifically between Route Reflector clients. When configured, the RR will not reflect
routes from one client to another client. This is useful when RR clients have direct
iBGP sessions between themselves or when you want finer control over route propagation.

In this test, **DUT0** acts as a Route Reflector with two clients: **DUT1** and
**DUT2**. First, with default RR behavior, routes from DUT1 are reflected to DUT2.
Then, after enabling ``no-client-to-client-reflection``, the route is no longer
reflected between clients.

***************************************
Test BGP No Client To Client Reflection
***************************************

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

This test demonstrates the effect of ``no-client-to-client-reflection`` on a
Route Reflector. First, with default behavior, **DUT0** (RR) reflects routes
from **DUT1** to **DUT2** (both are RR clients). Then, after enabling
``no-client-to-client-reflection``, the route from DUT1 is no longer reflected
to DUT2.

Scenario
========

.. include:: no-client-to-client-reflection/testbgpnoclienttoclientreflection

.. raw:: html

  <hr>