How Does Next Hop in Route Redistribution Profile Work?
Resolution
This document describes a next hop field in the route redistribution profile works in conjunction with interface and destination addresses.
Details
In a route redistribution profile, select the source type (for example, static, connect) desired to redistribute. There are three more optional filters that can be configured (interface, destination and next hop). If one or more interfaces/destination/next-hop is configured, then static routes(in this example) which have those interfaces "AND" those destination addresses "AND" those next hops will only be used for redistribution.
For example, static routes are being redistributed. Interfaces, destination and next hop are configured, as shown below:
Logic to filter the routes will be like this:
(Static routes) AND (eth1/3 or eth1/4) AND (172.16.10.0/24 or 172.16.18.0/25 or 10.10.10.0/24 or 172.100.10.0/24 ) AND (next-hop 192.168.88.2 or next-hop 10.66.24.1).
See the following static routes configured in the VR:
Output of OSPF LSDB where this redistribution profile was used in export rules:
> show routing protocol ospf lsdb
VIRTUAL ROUTER: default (id 1)
==========
VR Area ID Orig RTR ID LS ID LSA Type Seq Number CheckSum
1 0.0.0.0 10.66.18.80 10.66.18.80 type-1 (Router) 0x80000325 0x00004C0E
1 0.0.0.0 10.66.18.88 10.66.18.88 type-1 (Router) 0x80000003 0x0000E0AA
1 0.0.0.0 10.66.18.93 10.66.18.93 type-1 (Router) 0x80000332 0x00008ABD
1 0.0.0.0 10.66.18.80 10.66.24.80/23 type-2 (Network) 0x8000031F 0x00003A77
1 10.66.18.88 10.10.10.0/24 type-5 (External) 0x80000003 0x0000FE7C <<<<< redistributed route
1 10.66.18.88 172.16.10.0/24 type-5 (External) 0x80000003 0x0000745E <<<<< redistributed route
1 10.66.18.88 172.100.10.0/24 type-5 (External) 0x80000003 0x000080FD <<<<< redistributed route
Notice that 172.16.18.0/25 is not being redistributed as its next hop address doesn't match the filter.
owner: dreputi