I have two Juniper routers connected like this:
r1[ge-0/0/2] <-> [ge-0/0/3]r2
r2 do not have a family
root@r1> show interfaces ge-0/0/2 terse Interface Admin Link Proto Local Remote ge-0/0/2 up up ge-0/0/2.0 up up iso multiservice root@r1> root@r2> show interfaces ge-0/0/3 terse Interface Admin Link Proto Local Remote ge-0/0/3 up up ge-0/0/3.0 up up iso multiservice root@r2>
However, the ISIS adjacency between the two routers is still established. This is expected.
r1 advertises routes
Those are not installed to RIB in
root@r2> show route protocol isis inet.0: 11 destinations, 11 routes (11 active, 0 holddown, 0 hidden) iso.0: 1 destinations, 1 routes (1 active, 0 holddown, 0 hidden) inet6.0: 1 destinations, 1 routes (1 active, 0 holddown, 0 hidden) root@r2>
I guess this is because there is no next-hop IP address for those two routes? If yes, then how does ISIS find a next hop address for a prefix learned by ISIS when the IP addresses are configured? For example,
r2. Is there a separate TLV for next-hop IP address?