.. _example_protocols_bgp_peer-group_nexthop-self:

############
Nexthop-Self
############


.. sidebar:: Contents

  .. contents::
    :depth: 2
    :local:

Scenario to verify BGP **peer-group nexthop-self** inheritance.
When ``nexthop-self`` is configured on a peer-group, routes reflected to
members have the next-hop changed to the reflector's address instead of
keeping the original next-hop.

.. image:: nexthop-self.svg
  :width: 400

*************************************************************************
Test iBGP - Without nexthop-self reflected route has unreachable next-hop
*************************************************************************

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

Test that without ``nexthop-self`` on the peer-group, routes reflected to DUT2
keep the original next-hop (DUT1: 10.10.0.200). Since DUT2 has no route
to 10.10.0.0/24, the next-hop is inaccessible and the route is not usable.

Scenario
========

.. include:: nexthop-self/testibgp-withoutnexthop-selfreflectedroutehasunreachablenext-hop

.. raw:: html

  <hr>

************************************************************************
Test iBGP - Peer-group nexthop-self changes next-hop on reflected routes
************************************************************************

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

Test that ``nexthop-self`` configured on a peer-group changes the next-hop of
reflected routes to DUT0's own address. DUT1 (eBGP) announces 10.10.0.0/24
to DUT0 (RR). DUT0 reflects it to DUT2 (iBGP client in peer-group CLIENTS).
With nexthop-self, DUT2 sees DUT0 (20.20.0.100) as next-hop instead
of DUT1 (10.10.0.200).

Scenario
========

.. include:: nexthop-self/testibgp-peer-groupnexthop-selfchangesnext-hoponreflectedroutes

.. raw:: html

  <hr>