I have a RIP router with two uplinks to R4 and R5. Both R4 and R5 have the same prefixes exported from ISIS to RIP.
I have the following on R5
root@R5# show | display set | match isis2RIP
set protocols rip group To-RIP export isis2RIP
set policy-options policy-statement isis2RIP term 1 from protocol isis
set policy-options policy-statement isis2RIP term 1 then metric 5
set policy-options policy-statement isis2RIP term 1 then tag 1234
set policy-options policy-statement isis2RIP term 1 then accept
I expect to see RIP router selects R4 as a preferred path, but RIP router still selects R5.
root@RIP-R# run show route protocol rip detail 192.168.15.0/24
inet.0: 38 destinations, 38 routes (38 active, 0 holddown, 0 hidden)
192.168.15.0/24 (1 entry, 1 announced)
*RIP Preference: 100
Next hop type: Router, Next hop index: 565
Next-hop reference count: 28
Next hop: 172.30.0.57 via ge-0/0/7.204, selected
Session Id: 0x1
State: <Active Int>
Age: 3:19 Metric: 6
Validation State: unverified
Announcement bits (2): 0-KRT 2-RIPv2
AS path: I
Route learned from 172.30.0.57 expires in 171 seconds
If I use metric-in or metric-out, it works as expected.
What did I miss ?
The above policy configuration is provided in Juniper Training materials.