I feel like I read something about this but I couldn’t find anything with google-fu Has anyone run into is-is routes showing up as rip routes in 7.20beta4?
[admin@edge-01.sa51.dev] > routing/route/print where rip
Flags: A - ACTIVE; r - RIP
Columns: DST-ADDRESS, GATEWAY, AFI, ROUTING-TABLE, DISTANCE, SCOPE
DST-ADDRESS GATEWAY AFI ROUT DIS SCO>
Ar 0.0.0.0/0 100.126.1.34%ether1 ip main 115 >
Ar 100.126.1.16/29 100.126.1.34%ether1 ip main 115 >
Ar 100.126.1.24/29 100.126.1.34%ether1 ip main 115 >
r 100.126.1.32/29 100.126.1.34%ether1 ip main 115 >
Ar 100.127.1.12/32 100.126.1.34%ether1 ip main 115 >
Ar ::/0 fe80::5200:ff:fe02:0%ether1 ipv6 main 115 >
Ar 271:994a:d1:d16::/64 fe80::5200:ff:fe02:0%ether1 ipv6 main 115 >
Ar 271:994a:d1:d24::/64 fe80::5200:ff:fe02:0%ether1 ipv6 main 115 >
r 271:994a:d1:d32::/64 fe80::5200:ff:fe02:0%ether1 ipv6 main 115 >
Ar 271:994a:d127:d1::12/128 fe80::5200:ff:fe02:0%ether1 ipv6 main 115 >
[admin@edge-01.sa51.dev] > routing/route/print where isis
rip isn’t configured and the AD shows up as 115 which is definitely is-is