Severe ISIS TED Inconsistency
Hawkins-Sherpherd opened this issue · comments
Description
I run ISIS on tunnels. ISIS run well on those tunnels, able to exchange ISIS packets normally. But when I try to implement MPLS-TE, ISIS TED go wrong.
I can see MPLS-TE enabled interfaces have complete information in "show isis database detail" and "show isis mpls-te interface", but in "show isis mpls-te database edge", I can only see partial MPLS-TE enabled interface has been learned. Even worse, every node learn different TED edges, totally inconsistent.
Outputs can be seen here:
They are all running in a private experimental network. Nothing open.
Version
FRRouting 9.1
FRRouting 10.0
How to reproduce
- Enable ISIS process
- Enable MPLS-TE and Segment Routing for ISIS process
- Configure loopback interface IPv6 address as MPLS-TE IPv6 router address
- Add Segment Routing SID for IPv6 address on loopback interface
- Assign unnumbered IPv4 address for interfaces
- Assign ULA IPv6 address for interfaces
- Add interfaces to ISIS process
- Set "isis network point-to-point"
- Add link-params for interfaces
- See link-params added interfaces shown up in "show isis mpls-te interface" and "show isis database detail" with complete information
Expected behavior
TED have full synchronization with ISIS database.
Actual behavior
TED don't have full synchronization on any node. Only several random edge have learned from ISIS database.
Additional context
No response
Checklist
- I have searched the open issues for this bug.
- I have not included sensitive information in this report.
Switching tunnel protocol to GRETAP, the inconsistency has decreased.
Switching tunnel protocol to GRETAP, the inconsistency has decreased.
@Hawkins-Sherpherd , have you checked you are configured in point to point ? isis network point-to-point
Switching tunnel protocol to GRETAP, the inconsistency has decreased.
@Hawkins-Sherpherd , have you checked you are configured in point to point ? isis network point-to-point
I'm sure they are configured point to point.