beith12

@vgrebenschikov can you post the wireguard config (minus any keys of course) ?

Can we see the output of the following from the three PE devices (with addressing 172.16.19.1, 172.16.20.1, and 172.16.21.1)? `#show ip bgp vrf vrf-14` `#show bgp ipv4 vpn` `#show mpls...

@ton31337 Let me rebuild these and report back - the behavior seemed inconsistent.

Further results inconsistent - closing for now

This is a message from the log before we see the stuck in expiring state. `ISIS: [XXX] %ADJCHANGE: Adjacency to abc (eno4) for level-2 changed from Unknown to Initializing, unspecified`...

Do you know of a specific trace or debug that might help us pinpoint the issue? This seems to happen when the neighbor does not fully establish (intermittent up/down link)...

@odd22 Debugs with timestamps from expiring event > 2023/11/20 21:16:46 ISIS: [XXXX] ISIS-Adj (ABC): Sending L2 LAN IIH on eno4, length 65 . 2023/11/20 21:16:47 ISIS: [XXXX] ISIS-Adj (ABC): Rcvd...

I've managed to consistently reproduce this problem in a lab: !LAB Topology R1 R2 !Reproduction Steps On R2 restart FRR service multiple times in short period !Outcome #Up State >...

@odd22 Looking further into how I reproduced this error - It seems that when I stop the FRR service on one side of an ISIS peer (depending on how the...

What debug command did you have configured to see the log message? Just ran a test on 8.5.2 with the following configs and did not see the same log message:...