Users Guide

B EX 172.16.1.1/32 via 10.10.0.1
20/0 00:22:58
via 10.10.0.2
B EX 172.16.1.2/32 via 10.10.0.1
20/0 00:22:58
via 10.10.0.2
B EX 172.16.1.3/32 via 10.10.0.1
20/0 00:22:58
via 10.10.0.2
B EX 172.16.1.4/32 via 10.10.0.1
20/0 00:22:58
via 10.10.0.2
B EX 172.16.1.201/32 via 10.10.0.1
20/0 00:22:58
via 10.10.0.2
B EX 172.16.1.202/32 via 10.10.0.1
20/0 00:22:58
via 10.10.0.2
B EX 192.168.0.1/32 via 10.10.0.1
20/0 00:22:58
via 10.10.0.2
B EX 192.168.0.2/32 via 10.10.0.1
20/0 00:22:58
via 10.10.0.2
B EX 192.168.2.0/31 via 10.10.0.1
20/0 00:14:11
via 10.10.0.2
B EX 192.168.2.2/31 via 10.10.0.1
20/0 00:14:11
via 10.10.0.2
B EX 192.168.2.4/31 via 10.10.0.1
20/0 00:13:49
via 10.10.0.2
B EX 192.168.2.6/31 via 10.10.0.1
20/0 00:13:49
via 10.10.0.2
B EX 192.168.2.240/31 via 10.10.0.1
20/0 00:14:11
via 10.10.0.2
Administrative distance for leaked routes
Routers use administrative distance (AD) to determine the best path between two or more routes to reach the same
destination. AD indicates the reliability of the route; the lower the administrative distance, the more reliable the route.
If a local route exists in the destination VRF where route is being leaked, the local route is chosen as the best route. You can use
the set distance command to configure AD for routes when they are exported from one VRF to another using a route-map.
This command allows you to set AD of leaked routes to be of lower value so that the leaked routes are chosen over the local
routes.
Restrictions and limitations
● The set distance command is effective in setting the administrative distance only when used with route-map while
exporting routes.
● The set distance command does not take effect in the following scenarios:
○ When used with route-map while importing routes.
○ When redistributing routes using the redistribute or network command.
○ When used as part of BGP neighbor-level route-map.
● If static route and dynamic protocol route are configured to have the same AD, both the routes will be active.
754
Layer 3