You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
Can you send us the complete IS-IS and interface configuration you used as well as the output of "show isis database detail" and finally the output of "show isis mpls-te database detail"?
In particular, do you check that "link-params" are setup on each interfaces advertises by ISIS?
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
How to reproduce
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
The text was updated successfully, but these errors were encountered: