IS-IS route not installing in the RIB

[Rogman]

I have 3 routers(R1, R2, R3) running in a frame relay network. 172.12.123.0/24 is the common subnet over the frame cloud.
I also have 2 additional routers R4 and R5 which are attached to R3 and R2 respectively

R2 and R5 are connected by ethernet on subnet 46.0.0.0/24. R3 and R4 are connected by ethernet on network 51.1.1.0/24.

R1 is in IS-IS area 49.0001.
R2 is in IS-IS area 49.0002.
R3 is in IS-IS area 49.0003.

R4 is in area 49.0003
R5 is in area 49.0002


R1, R2 and R3 are all at the default L1/L2 router setting.

R4 and R5 were set to Level-1 routers

However when I have IS-Is routing setup only the L1 route 51.1.1.0/24 route is placed in R1's table and not the 46.0.0.0/24 route. this despite R1 having adjacencies with both R2 and R3.

I am not sure why one route and not the other would install.


I have listed the relevant output below.

R1#sh ip route
Gateway of last resort is not set

51.0.0.0/24 is subnetted, 1 subnets
i L2 51.1.1.0 [115/20] via 172.12.123.3, Serial1/0
172.12.0.0/24 is subnetted, 1 subnets
C 172.12.123.0 is directly connected, Serial1/0



R1#sh clns nei

System Id Interface SNPA State Holdtime Type Protocol
R2 Se1/0 DLCI 122 Up 9 L2 IS-IS
R3 Se1/0 DLCI 123 Up 8 L2 IS-IS


R1#sh clns nei det

System Id Interface SNPA State Holdtime Type Protocol
R2 Se1/0 DLCI 122 Up 8 L2 IS-IS
Area Address(es): 49.0002
IP Address(es): 172.12.123.2*
Uptime: 00:45:30
NSF capable
R3 Se1/0 DLCI 123 Up 9 L2 IS-IS
Area Address(es): 49.0003
IP Address(es): 172.12.123.3*
Uptime: 01:16:40
NSF capable


interface Serial1/0
ip address 172.12.123.1 255.255.255.0
ip router isis
encapsulation frame-relay
ip split-horizon
serial restart-delay 0
frame-relay map ip 172.12.123.2 122 broadcast
frame-relay map ip 172.12.123.3 123 broadcast
frame-relay map clns 122 broadcast
frame-relay map clns 123 broadcast
no frame-relay inverse-arp
end

[Rogman]

on R2


R2#sh ip route


172.12.0.0/24 is subnetted, 1 subnets
C 172.12.123.0 is directly connected, Serial1/0
46.0.0.0/24 is subnetted, 1 subnets
C 46.0.0.0 is directly connected, Ethernet0/0

R2#sh clns nei det

System Id Interface SNPA State Holdtime Type Protocol
R1 Se1/0 DLCI 221 Up 28 L2 IS-IS
Area Address(es): 49.0001
IP Address(es): 172.12.123.1*
Uptime: 00:51:30
NSF capable

R2#sh run int s1/0
interface Serial1/0
ip address 172.12.123.2 255.255.255.0
ip router isis
encapsulation frame-relay
serial restart-delay 0
frame-relay map clns 221 broadcast
frame-relay map ip 172.12.123.1 221 broadcast
frame-relay map ip 172.12.123.3 221 broadcast
no frame-relay inverse-arp

R2#sh run int e0/0
interface Ethernet0/0
ip address 46.0.0.2 255.255.255.0
ip router isis

R2#sh clns int e0/0
Ethernet0/0 is up, line protocol is up
Checksums enabled, MTU 1497, Encapsulation SAP
ERPDUs enabled, min. interval 10 msec.
CLNS fast switching disabled
CLNS SSE switching disabled
DEC compatibility mode OFF for this interface
Next ESH/ISH in 51 seconds
Routing Protocol: IS-IS
Circuit Type: level-1-2
Interface number 0x1, local circuit ID 0x2
Level-1 Metric: 10, Priority: 64, Circuit ID: R2.02
DR ID: 0000.0000.0000.00
Level-1 IPv6 Metric: 10
Number of active level-1 adjacencies: 0
Level-2 Metric: 10, Priority: 64, Circuit ID: R2.02
DR ID: 0000.0000.0000.00
Level-2 IPv6 Metric: 10
Number of active level-2 adjacencies: 0
Next IS-IS LAN Level-1 Hello in 5 seconds
Next IS-IS LAN Level-2 Hello in 4 seconds

[Rogman]

R3#sh ip route


51.0.0.0/24 is subnetted, 1 subnets
C 51.1.1.0 is directly connected, Ethernet0/0
172.12.0.0/24 is subnetted, 1 subnets
C 172.12.123.0 is directly connected, Serial1/0


R3#sh clns nei det

System Id Interface SNPA State Holdtime Type Protocol
R1 Se1/0 DLCI 321 Up 22 L2 IS-IS
Area Address(es): 49.0001
IP Address(es): 172.12.123.1*
Uptime: 01:39:15
NSF capable


R3#sh run int s1/0
!
interface Serial1/0
ip address 172.12.123.3 255.255.255.0
ip router isis
encapsulation frame-relay
serial restart-delay 0
frame-relay map clns 321 broadcast
frame-relay map ip 172.12.123.1 321 broadcast
frame-relay map ip 172.12.123.2 321 broadcast


R3#sh run int e0/0
interface Ethernet0/0
ip address 51.1.1.3 255.255.255.0
ip router isis
half-duplex
end

[Rogman]

# Simple lab
autostart = false
ghostios = True
sparsemem = True
model = 3640

[localhost]

workingdir = C:\Users\Roger\Downloads\bryantisislabs

[[3640]]
image = C:\Users\Roger\Downloads\c3640-is-mz.124-16.bin
# On Linux / Unix use forward slashes:
# image = /opt/7200-images/c7200-jk9o3s-mz.124-7a.image
ram = 96
slot0 = NM-4E


[[ROUTER R1]]
s1/0 = F1 1


[[ROUTER R2]]
s1/0 = F1 2
e0/0 = R5 e0/0




[[ROUTER R3]]
s1/0 = F1 3
e0/0 = R4 e0/0




[[ROUTER R4]]


[[ROUTER R5]]


[[FRSW F1]]
1:122 = 2:221
1:123 = 3:321


This is the dynamips config used

[Ivan Pepelnjak]

IS-IS does not behave well over partially-meshed Frame Relay subnets. You should establish a fully-meshed topology (insert the missing DLCI) or use point-to-point subinterfaces.

See also our Wiki for more details