.. _example_protocols_rip_redistribute_redistributeconnectedmetric:

#############################
Redistribute Connected Metric
#############################

Test to verify RIP **metric** configuration for redistributed connected routes.
The ``redistribute connected metric`` command sets the metric value for connected routes
redistributed into RIP. Valid values are 1-16, where ``metric 1`` is the default when not
specified. This test validates the default behavior (metric 1), custom valid metric values,
and the special case of ``metric 16`` where routes are not announced (infinity).

******************************************
Test RIP Default Metric With Default Value
******************************************

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

Test RIP **redistribute connected metric** with the **default value** (``metric 1``).
When metric is not explicitly configured, RIP uses ``metric 1`` by default.
**DUT0** redistributes the connected route ``10.10.10.0/24`` with the default metric.
**DUT1** learns this route with ``metric 2`` (incremented by 1 hop). The route is
installed in the routing table and connectivity is verified with ping.

Scenario
========

.. include:: redistributeconnectedmetric/testripdefaultmetricwithdefaultvalue

.. raw:: html

  <hr>

****************************************
Test RIP Default Metric With Valid Value
****************************************

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

Test RIP **redistribute connected metric** with a valid value (``metric 5``).
**DUT0** redistributes the connected route ``10.10.10.0/24`` with ``metric 5``.
**DUT1** learns this route with ``metric 6`` (incremented by 1 hop). The route is
installed in the routing table and connectivity is verified with ping.

Scenario
========

.. include:: redistributeconnectedmetric/testripdefaultmetricwithvalidvalue

.. raw:: html

  <hr>

**************************************
Test RIP Metric 16 Route Not Announced
**************************************

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

Test RIP **redistribute connected metric 16** - route is **not announced**.
When **DUT0** redistributes ``10.10.10.0/24`` with ``metric 16`` (infinity), the route
is **not announced** to neighbors because it is already unreachable at the source.
**DUT1** does not see the route in RIP database, does not install it in routing table,
and **ping fails**.

Scenario
========

.. include:: redistributeconnectedmetric/testripmetric16routenotannounced

.. raw:: html

  <hr>