ISIS adjacency issue

[kenji-osr]

Hi all nice to meet you, i am using frr v4 on ubuntu 18.04 LTS i have issue in isis neignbour state. i am running with two router.R1 and R2. show isis neighbors R1 R1# show isis neighbor Area 1: System Id Interface L State Holdtime SNPA R1 eth2 2 Up 29 2020.2020.2020 R2# show isis neighbor Area 1: System Id Interface L State Holdtime SNPA R2 eth2 2 Up 29 2020.2020.2020

R1# show isis neighbor detail Area 100: 1720.2615.0175
Interface: eth2, Level: 2, State: Up, Expires in 29s Adjacency flaps: 1, Last: 2m13s ago Circuit type: L2, Speaks: IPv4 SNPA: 2020.2020.2020 Area Address(es): 49.0100 IPv4 Address(es): 172.26.134.202

R2# show isis neighbor detail Area 100: 1720.2615.0176
Interface: eth2, Level: 2, State: Up, Expires in 29s Adjacency flaps: 1, Last: 2m14s ago Circuit type: L2, Speaks: IPv4 SNPA: 2020.2020.2020 Area Address(es): 49.0100 IPv4 Address(es): 172.26.134.201

R1# show isis interface eth2 Area 100: Interface: eth2, State: Up, Active, Circuit Id: 0x4 Type: p2p, Level: L2 Level-2 Information: Metric: 10, Active neighbors: 1 Hello interval: 3, Holddown count: 10 (pad) CNSP interval: 10, PSNP interval: 2 IP Prefix(es): 172.26.134.201/30

R2# show isis interface eth2 Area 100: Interface: eth2, State: Up, Active, Circuit Id: 0x4 Type: p2p, Level: L2 Level-2 Information: Metric: 10, Active neighbors: 0 <---------------------------------------------------------- i found strange Hello interval: 3, Holddown count: 10 (pad) CNSP interval: 10, PSNP interval: 2 IP Prefix(es): 172.26.134.202/30

R1# show interface eth2 Interface eth2 is up, line protocol is up PTM status: disabled vrf: Default-IP-Routing-Table index 4 metric 0 mtu 1700 speed 1000 flags: <UP,BROADCAST,RUNNING,MULTICAST> Type: Ethernet HWaddr: 00:f0:c9:ee:f0:66 inet 172.26.134.201/30 broadcast 172.26.134.203 Interface Type Other

R2# show interface eth2 Interface eth2 is up, line protocol is up PTM status: disabled vrf: Default-IP-Routing-Table index 4 metric 0 mtu 1700 speed 1000 flags: <UP,BROADCAST,RUNNING,MULTICAST> Type: Ethernet HWaddr: 00:0e:c4:cf:4e:fd inet 172.26.134.202/30 broadcast 172.26.134.203 Interface Type Other

R2 recieved all route from R1 but R1 cannot get all route from R2 via ISIS.

i fount this log from R1 2022/02/03 21:50:58 ISIS: ISIS-Spf: No LSP found for 1720.2615.0175.00-00 <---------- this ID is R2 net ID

Here is debug log for isis adjency packet and isis events R1 2022/02/03 19:27:24 ISIS: ISIS-Adj (100): Sending P2P IIH on eth2, length 1697 2022/02/03 19:27:25 ISIS: ISIS-Adj (100): Rcvd P2P IIH on eth2, cirType L2, cirID 4 2022/02/03 19:27:25 ISIS: ISIS-Adj (100): Rcvd P2P IIH from (eth2), cir type L2, cir id 04, length 1697 2022/02/03 19:27:26 ISIS: ISIS-Adj (100): Sending P2P IIH on eth2, length 1697 2022/02/03 19:27:27 ISIS: ISIS-Adj (100): Rcvd P2P IIH on eth2, cirType L2, cirID 4 2022/02/03 19:27:27 ISIS: ISIS-Adj (100): Rcvd P2P IIH from (eth2), cir type L2, cir id 04, length 1697 2022/02/03 19:27:28 ISIS: ISIS-Adj (100): Sending P2P IIH on eth2, length 1697 2022/02/03 19:27:29 ISIS: ISIS-Adj (100): Rcvd P2P IIH on eth2, cirType L2, cirID 4 2022/02/03 19:27:29 ISIS: ISIS-Adj (100): Rcvd P2P IIH from (eth2), cir type L2, cir id 04, length 1697 R2 2022/02/03 19:27:18 ISIS: ISIS-Adj (sbs54): Rcvd P2P IIH on eth2, cirType L2, cirID 4 2022/02/03 19:27:18 ISIS: ISIS-Adj (sbs54): Rcvd P2P IIH from (eth2), cir type L2, cir id 04, length 1697 2022/02/03 19:27:19 ISIS: ISIS-Adj (sbs54): Sending P2P IIH on eth2, length 1697 2022/02/03 19:27:20 ISIS: ISIS-Adj (sbs54): Rcvd P2P IIH on eth2, cirType L2, cirID 4 2022/02/03 19:27:20 ISIS: ISIS-Adj (sbs54): Rcvd P2P IIH from (eth2), cir type L2, cir id 04, length 1697 2022/02/03 19:27:21 ISIS: ISIS-Adj (sbs54): Sending P2P IIH on eth2, length 1697

[qlyoung]

Can you describe the issue? Preferably following the issue template?

What is frrv4?

[kenji-osr]

Frrouting version 4

[odd22]

Hum, this let us think that it is an old bug. FRR is currently version 8.x. Can you check that you could reproduce the same problem with the latest version of FRR ?

In addition, can you provide the configuration of R1 & R2 ? I'm suspecting a wrong configuration on one side letting to only half of the adjacency fire up. Typically, check that MTU, network type (point-to-point or broadcast) of the interface ... are the same on both side.

[kenji-osr]

I can't upgrade to frr 8. This error occured in our production network. Network type is point to point. I already check configuration there is no missmatch config.

[github-actions[bot]]

This issue is stale because it has been open 180 days with no activity. Comment or remove the autoclose label in order to avoid having this issue closed.

[frrbot[bot]]

This issue will be automatically closed in the specified period unless there is further activity.