Files
infix/test/case/ietf_routing/route_pref_255
Ahmed Karic 3e0b816351 test: Match on edge attributes when mapping topologies
Implemented logic to check if the system supports required services.
Logical edges with 'requires' fields are mapped only if physical edges
provide corresponding services. If not, the test is skipped.
This ensures that tests only run when the required services are available
in the test system configuration.

Fixes #654
2025-01-24 11:51:55 +01:00
..

=== Route preference: Static Route Activation and Maximum Distance
==== Description
This test configures a device with a static route to a destination with 
a moderate routing preference (254), verifying that it becomes active. 
Then, the routing preference is increased to the maximum value (255), 
which should prevent the route from becoming active.

==== Topology
ifdef::topdoc[]
image::{topdoc}../../test/case/ietf_routing/route_pref_255/topology.svg[Route preference: Static Route Activation and Maximum Distance topology]
endif::topdoc[]
ifndef::topdoc[]
ifdef::testgroup[]
image::route_pref_255/topology.svg[Route preference: Static Route Activation and Maximum Distance topology]
endif::testgroup[]
ifndef::testgroup[]
image::topology.svg[Route preference: Static Route Activation and Maximum Distance topology]
endif::testgroup[]
endif::topdoc[]
==== Test sequence
. Set up topology and attach to target DUTs
. Configure targets with active static route
. Verify that static route with preference 254 is active
. Update static route preference to 255
. Verify that high-preference static route (255) does not become active


<<<