Hi Champions,
I am working on a POC for Pathfinder Automation installation for a customer and the suite installation is successfully complete. I am in the process of configuring the MX routers(RR) to export the topology information from the TED database to Pathfinder via BGP-LS. BGP is up and running but here is the problem.
MX exports the information from the lsdist.0 table via BGP-LS using which the topology is built on the Pathfinder. I have done this in my lab and everything works fine but in the customer lab it did not and the difference noticed is that I used the interfaces(ge-0/0/0.0) without any tagging in my topology whereas customer has vlan-tagging and hence non-zero units(ge-0/0/0.1) in his topology. Because of this I see the link information is missing in the lsdist.0 table but is present in the lsdist.1 table. I need the link information in the lsdist.0 table so that it is exported to Pathfinder.
root@LAB-DC-01_RR-BNG> show route table lsdist.0lsdist.0: 4 destinations, 4 routes (4 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = BothNODE { ISO:0020.0200.2001.00 ISIS-L2:0 }/1216
*[IS-IS/18] 00:07:50
Fictitious
NODE { ISO:0020.0200.2002.00 ISIS-L2:0 }/1216
*[IS-IS/18] 00:07:50
Fictitious
PREFIX { Node { ISO:0020.0200.2001.00 } { IPv4:2.2.2.1/32 } ISIS-L2:0 }/1216
*[IS-IS/18] 00:07:50
Fictitious
PREFIX { Node { ISO:0020.0200.2002.00 } { IPv4:2.2.2.2/32 } ISIS-L2:0 }/1216
*[IS-IS/18] 00:07:50
Fictitious
root@LAB-DC-01_RR-BNG> show route table lsdist.1lsdist.1: 6 destinations, 6 routes (6 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = BothNODE { ISO:0020.0200.2001.00 ISIS-L2:0 }/1216
*[IS-IS/18] 00:07:53
Fictitious
NODE { ISO:0020.0200.2002.00 ISIS-L2:0 }/1216
*[IS-IS/18] 00:07:53
Fictitious
LINK { Local { ISO:0020.0200.2001.00 }.{ IPv4:10.100.100.0 } Remote { ISO:0020.0200.2002.00 }.{ IPv4:10.100.100.1 } ISIS-L2:0 }/1216
*[IS-IS/18] 00:00:24
Fictitious
LINK { Local { ISO:0020.0200.2002.00 }.{ IPv4:10.100.100.1 } Remote { ISO:0020.0200.2001.00 }.{ IPv4:10.100.100.0 } ISIS-L2:0 }/1216
*[IS-IS/18] 00:07:53
Fictitious
PREFIX { Node { ISO:0020.0200.2001.00 } { IPv4:2.2.2.1/32 } ISIS-L2:0 }/1216
*[IS-IS/18] 00:07:53
Fictitious
PREFIX { Node { ISO:0020.0200.2002.00 } { IPv4:2.2.2.2/32 } ISIS-L2:0 }/1216
*[IS-IS/18] 00:07:53
Fictitious
What I noticed is that the link information is present in the ted database with topology l3-unicast but not present for the traffic-engineering. Whereas it is present when interfaces without tagging are used.
root@LAB-DC-01_RR-BNG> show ted database topology-type l3-unicast
TED database: 2 ISIS nodes 2 INET nodes 0 INET6 nodes
ID Type Age(s) LnkIn LnkOut Protocol
LAB-DC-01_RR-BNG.00(2.2.2.1) Rtr 683 1 1 IS-IS(2)
To: LAB-DC-01_JUNIPER-01.00(2.2.2.2), Local: 10.100.100.0, Remote: 10.100.100.1
Local interface index: 342, Remote interface index: 342
ID Type Age(s) LnkIn LnkOut Protocol
LAB-DC-01_JUNIPER-01.00(2.2.2.2) Rtr 611 1 1 IS-IS(2)
To: LAB-DC-01_RR-BNG.00(2.2.2.1), Local: 10.100.100.1, Remote: 10.100.100.0
Local interface index: 342, Remote interface index: 342
root@LAB-DC-01_RR-BNG> show ted database topology-type traffic-engineering
TED database: 2 ISIS nodes 2 INET nodes 0 INET6 nodes
ID Type Age(s) LnkIn LnkOut Protocol
LAB-DC-01_RR-BNG.00(2.2.2.1) Rtr 687 0 0 IS-IS(2)
LAB-DC-01_JUNIPER-01.00(2.2.2.2) Rtr 615 0 0 IS-IS(2)
While debugging, noticed that disabling the point-to-point on the ISIS gets the link information into the database but then it also adds pseudo nodes in the topology which is not desired.
This could be a simple config as I am sure in most of the case of real world design, we use vlan-tagging on the interfaces and hence there should be a way around. Appreciate your help on this to move forward.
Thanks and Regards
Pradeep Kumar M
------------------------------
Pradeep Kumar Maddinani
Pradeep Kumar
------------------------------