I have two Juniper routers connected like this:
r1[ge-0/0/2] <-> [ge-0/0/3]r2
Both ge-0/0/2
in r1
and ge-0/0/3
in r2
do not have a family inet
configured:
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 192.168.1.1/32
and 172.18.1.0/24
to r2
:
Those are not installed to RIB in r2
:
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, 172.26.1.1/30
to ge-0/0/2.0
in r1
and 172.26.1.2/30
to ge-0/0/3.0
in r2
. Is there a separate TLV for next-hop IP address?