.. _example_protocols_bgp_peer-group_disable-connected-check:

#######################
Disable-Connected-Check
#######################

Scenario to verify BGP **peer-group disable-connected-check** inheritance.
When ``disable-connected-check`` is configured on a peer-group, members can
establish eBGP sessions with non-directly connected peers (loopback peering).

**********************************************************************
Test eBGP - Peer-group disable-connected-check allows loopback peering
**********************************************************************

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

Test that ``disable-connected-check`` configured on a peer-group allows eBGP
sessions with non-directly connected peers. DUT0 and DUT1 peer using loopback
addresses instead of directly connected interface addresses.

Scenario
========

.. include:: disable-connected-check/testebgp-peer-groupdisable-connected-checkallowsloopbackpeering

.. raw:: html

  <hr>

*******************************************************************************
Test eBGP - Session fails without disable-connected-check on non-connected peer
*******************************************************************************

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

Test that without ``disable-connected-check`` on the peer-group, the eBGP session
fails to establish when the neighbor address is not on a directly connected network.
Both DUT0 and DUT1 try to peer using loopback addresses but without
disable-connected-check and without static routes, the session does not establish.

Scenario
========

.. include:: disable-connected-check/testebgp-sessionfailswithoutdisable-connected-checkonnon-connectedpeer

.. raw:: html

  <hr>