.. _example_protocols_bgp_neighbor_strict-capability-match:

#######################
Strict-Capability-Match
#######################

This scenario demonstrates how to configure the strict-capability-match option for a BGP neighbor.
When enabled, BGP session will only establish if capabilities match exactly between peers.
If capabilities do not match (e.g., one has IPv6 enabled, the other does not), the session fails.

***********************************************************************
Test iBGP - Neighbor strict-capability-match with matching capabilities
***********************************************************************

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

Test to verify that BGP session establishes when strict-capability-match is enabled
and both peers have matching capabilities (both IPv4 only in this case).
DUT1 advertises route 1.1.1.0/24 and DUT0 should receive it.

Scenario
========

.. include:: strict-capability-match/testibgp-neighborstrict-capability-matchwithmatchingcapabilities

.. raw:: html

  <hr>

****************************************************************************
Test iBGP - Neighbor strict-capability-match rejects mismatched capabilities
****************************************************************************

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

Test to verify that BGP session fails to establish when strict-capability-match is enabled
and there is a capability mismatch. DUT0 has IPv6 address-family enabled while DUT1 does not.
With strict-capability-match, DUT0 rejects the session due to capability mismatch.
DUT0 should NOT receive route 1.1.1.0/24 because session cannot establish.

Scenario
========

.. include:: strict-capability-match/testibgp-neighborstrict-capability-matchrejectsmismatchedcapabilities

.. raw:: html

  <hr>