Open laimaretto opened 1 year ago
Hi @laimaretto , many thanks for the commands output! I will check it shortly!
Hey @laimaretto , I fixed nokia is-is templates, but I didn't find RA-15, RA-16 and PE-14 in the lsdb output, so I got only three routers on a diagram. New templates are available on online version of Topolograph and then will be added into docker image soon.
Hi @Vadims06 ! thanks for the feedback. I believe I made a mistake with the previous output: somehow (don't know why) the output for PE-14 is missing but it's there, probably a copy+paste mistake; if you don't mind I've updated in the first message, the database output so it is now consistent. I believe that, if you execute again the template for the updated database, you'll see the missing PE-14 router, from the point of view of P-11.
However, let me share with you the following reasoning. It's interesting that (from the point of view of P-11) you can only see PE-13 (and hopefully PE-14 after my update), given that they both are L1L2 routers. RA-15 and RA-16 are both L1 routers, so I believe it kind of makes (a little) sense to me that you don't see them (please, bare in mind that I'm far from being an ISIS expert ;-) ).
However, let me show you first the following:
It looks to me that PE-14 is available from this output.
A:P-11# show router isis database
===============================================================================
Rtr Base ISIS Instance 0 Database
===============================================================================
LSP ID Sequence Checksum Lifetime Attributes
-------------------------------------------------------------------------------
Displaying Level 1 database
-------------------------------------------------------------------------------
Level (1) LSP Count : 0
Displaying Level 2 database
-------------------------------------------------------------------------------
P-11.00-00 0x7 0x6a03 685 L1L2
P-11.01-00 0x4 0x9527 690 L1L2
P-11.02-00 0x4 0x2b8c 791 L1L2
P-12.00-00 0x8 0x8ab0 1196 L1L2
PE-13.00-00 0x7 0x963 674 L1L2
PE-13.02-00 0x5 0xe2d1 1172 L1L2
PE-14.00-00 0x7 0x47bb 664 L1L2
Level (2) LSP Count : 7
===============================================================================
If we inspect the details for that LSP, we see that it actually has some knowledge about both neighoirs P-11 (172.16.0.11/32) and RA-16 (172.16.0.16/32)
A:P-11# show router isis database PE-14.00-00 detail
===============================================================================
Rtr Base ISIS Instance 0 Database (detail)
===============================================================================
Displaying Level 1 database
-------------------------------------------------------------------------------
Level (1) LSP Count : 0
Displaying Level 2 database
-------------------------------------------------------------------------------
LSP ID : PE-14.00-00 Level : L2
Sequence : 0x9 Checksum : 0x43bd Lifetime : 861
Version : 1 Pkt Type : 20 Pkt Ver : 1
Attributes: L1L2 Max Area : 3 Alloc Len : 283
SYS ID : 1720.1600.0014 SysID Len : 6 Used Len : 283
TLVs :
Area Addresses:
Area Address : (3) 49.0001
Supp Protocols:
Protocols : IPv4
IS-Hostname : PE-14
Router ID :
Router ID : 172.16.0.14
Router Cap : 172.16.0.14, D:0, S:0
TE Node Cap : B E M P
SR Cap: IPv4 MPLS-IPv6
SRGB Base:100000, Range:100001
SR Alg: metric based SPF
Node MSD Cap: BMI : 12 ERLD : 15
IS Neighbors :
Virtual Flag : 0
Default Metric: (I) 10
Delay Metric : (I) 0
Expense Metric: (I) 0
Error Metric : (I) 0
Neighbor : P-11.02
Internal Reach:
Default Metric: (I) 10
Delay Metric : (I) 0
Expense Metric: (I) 0
Error Metric : (I) 0
IP Address : 10.1.0.0
IP Mask : 255.255.255.252
Default Metric: (I) 10
Delay Metric : (I) 0
Expense Metric: (I) 0
Error Metric : (I) 0
IP Address : 10.14.0.0
IP Mask : 255.255.255.252
Default Metric: (I) 0
Delay Metric : (I) 0
Expense Metric: (I) 0
Error Metric : (I) 0
IP Address : 172.16.0.14
IP Mask : 255.255.255.255
Default Metric: (I) 10
Delay Metric : (I) 0
Expense Metric: (I) 0
Error Metric : (I) 0
IP Address : 172.16.0.16
IP Mask : 255.255.255.255
External Reach:
Default Metric: (I) 0
Delay Metric : (I) 0
Expense Metric: (I) 0
Error Metric : (I) 0
IP Address : 10.1.0.0
IP Mask : 255.255.255.252
Default Metric: (I) 0
Delay Metric : (I) 0
Expense Metric: (I) 0
Error Metric : (I) 0
IP Address : 10.14.0.0
IP Mask : 255.255.255.252
Default Metric: (I) 0
Delay Metric : (I) 0
Expense Metric: (I) 0
Error Metric : (I) 0
IP Address : 172.16.0.14
IP Mask : 255.255.255.255
I/F Addresses :
I/F Address : 10.1.0.2
I/F Address : 10.14.0.2
I/F Address : 172.16.0.14
TE IS Nbrs :
Nbr : P-11.02
Default Metric : 10
Sub TLV Len : 19
IF Addr : 10.14.0.2
LAN-Adj-SID: 17 20 16 00 00 11 Flags:v4VL Weight:0 Label:524287
TE IP Reach :
Default Metric : 10
Control Info: , prefLen 30
Prefix : 10.1.0.0
Default Metric : 10
Control Info: , prefLen 30
Prefix : 10.14.0.0
Default Metric : 0
Control Info: S, prefLen 32
Prefix : 172.16.0.14
Sub TLV :
Prefix-SID Index:4, Algo:0, Flags:NnP
Default Metric : 10
Control Info: S, prefLen 32
Prefix : 172.16.0.16
Sub TLV :
Prefix-SID Index:6, Algo:0, Flags:RNnP
Level (2) LSP Count : 1
-------------------------------------------------------------------------------
Control Info : D = Prefix Leaked Down
S = Sub-TLVs Present
Attribute Flags : N = Node Flag
R = Re-advertisement Flag
X = External Prefix Flag
E = Entropy Label Capability (ELC) Flag
Adj-SID Flags : v4/v6 = IPv4 or IPv6 Address-Family
B = Backup Flag
V = Adj-SID carries a value
L = value/index has local significance
S = Set of Adjacencies
P = Persistently allocated
Prefix-SID Flags : R = Re-advertisement Flag
N = Node-SID Flag
nP = no penultimate hop POP
E = Explicit-Null Flag
V = Prefix-SID carries a value
L = value/index has local significance
Lbl-Binding Flags: v4/v6 = IPv4 or IPv6 Address-Family
M = Mirror Context Flag
S = SID/Label Binding flooding
D = Prefix Leaked Down
A = Attached Flag
SABM-flags Flags: R = RSVP-TE
S = SR-TE
F = LFA
X = FLEX-ALGO
FAD-flags Flags: M = Prefix Metric
===============================================================================
So my guess is that it should be possible to reach RA-15 and RA-16 from P-11, which is an L2 router.
Other idea would be to only analyze the DB at an L1L2 router, such as PE-14. Let me share that DB with you. You'll see that it has information about all of the LSPs.
A:PE-14# show router isis database
===============================================================================
Rtr Base ISIS Instance 0 Database
===============================================================================
LSP ID Sequence Checksum Lifetime Attributes
-------------------------------------------------------------------------------
Displaying Level 1 database
-------------------------------------------------------------------------------
PE-14.00-00 0xe 0xc61 780 L1L2 ATT
PE-14.01-00 0x7 0x4a5e 666 L1L2
RA-16.00-00 0x9 0x9732 1149 L1
Level (1) LSP Count : 3
Displaying Level 2 database
-------------------------------------------------------------------------------
P-11.00-00 0xb 0x6207 1109 L1L2
P-11.01-00 0x8 0x8d2b 1171 L1L2
P-11.02-00 0x7 0x258f 658 L1L2
P-12.00-00 0xb 0x84b3 1119 L1L2
PE-13.00-00 0xc 0x20a4 665 L1L2
PE-13.02-00 0x8 0xdcd4 1056 L1L2
PE-14.00-00 0xa 0x41be 569 L1L2
Level (2) LSP Count : 7
===============================================================================
A:PE-14# show router isis database detail
===============================================================================
Rtr Base ISIS Instance 0 Database (detail)
===============================================================================
Displaying Level 1 database
-------------------------------------------------------------------------------
LSP ID : PE-14.00-00 Level : L1
Sequence : 0xe Checksum : 0xc61 Lifetime : 722
Version : 1 Pkt Type : 18 Pkt Ver : 1
Attributes: L1L2 ATT Max Area : 3 Alloc Len : 1492
SYS ID : 1720.1600.0014 SysID Len : 6 Used Len : 436
TLVs :
Area Addresses:
Area Address : (3) 49.0001
Supp Protocols:
Protocols : IPv4
IS-Hostname : PE-14
Router ID :
Router ID : 172.16.0.14
Router Cap : 172.16.0.14, D:0, S:0
TE Node Cap : B E M P
SR Cap: IPv4 MPLS-IPv6
SRGB Base:100000, Range:100001
SR Alg: metric based SPF
Node MSD Cap: BMI : 12 ERLD : 15
IS Neighbors :
Virtual Flag : 0
Default Metric: (I) 10
Delay Metric : (I) 0
Expense Metric: (I) 0
Error Metric : (I) 0
Neighbor : PE-14.01
Internal Reach:
Default Metric: (I) 10
Delay Metric : (I) 0
Expense Metric: (I) 0
Error Metric : (I) 0
IP Address : 10.1.0.0
IP Mask : 255.255.255.252
Default Metric: (I) 30
Delay Metric : (I) 0
Expense Metric: (I) 0
Error Metric : (I) 0
IP Address : 10.5.0.0
IP Mask : 255.255.255.252
Default Metric: (I) 20
Delay Metric : (I) 0
Expense Metric: (I) 0
Error Metric : (I) 0
IP Address : 10.12.0.0
IP Mask : 255.255.255.252
Default Metric: (I) 10
Delay Metric : (I) 0
Expense Metric: (I) 0
Error Metric : (I) 0
IP Address : 10.14.0.0
IP Mask : 255.255.255.252
Default Metric: (I) 30
Delay Metric : (I) 0
Expense Metric: (I) 0
Error Metric : (I) 0
IP Address : 10.23.0.0
IP Mask : 255.255.255.252
Default Metric: (I) 10
Delay Metric : (I) 0
Expense Metric: (I) 0
Error Metric : (I) 0
IP Address : 172.16.0.11
IP Mask : 255.255.255.255
Default Metric: (I) 20
Delay Metric : (I) 0
Expense Metric: (I) 0
Error Metric : (I) 0
IP Address : 172.16.0.12
IP Mask : 255.255.255.255
Default Metric: (I) 30
Delay Metric : (I) 0
Expense Metric: (I) 0
Error Metric : (I) 0
IP Address : 172.16.0.13
IP Mask : 255.255.255.255
Default Metric: (I) 0
Delay Metric : (I) 0
Expense Metric: (I) 0
Error Metric : (I) 0
IP Address : 172.16.0.14
IP Mask : 255.255.255.255
Default Metric: (I) 40
Delay Metric : (I) 0
Expense Metric: (I) 0
Error Metric : (I) 0
IP Address : 172.16.0.15
IP Mask : 255.255.255.255
External Reach:
Default Metric: (I) 0
Delay Metric : (I) 0
Expense Metric: (I) 0
Error Metric : (I) 0
IP Address : 10.1.0.0
IP Mask : 255.255.255.252
Default Metric: (I) 0
Delay Metric : (I) 0
Expense Metric: (I) 0
Error Metric : (I) 0
IP Address : 10.14.0.0
IP Mask : 255.255.255.252
Default Metric: (I) 0
Delay Metric : (I) 0
Expense Metric: (I) 0
Error Metric : (I) 0
IP Address : 172.16.0.14
IP Mask : 255.255.255.255
I/F Addresses :
I/F Address : 10.1.0.2
I/F Address : 10.14.0.2
I/F Address : 172.16.0.14
TE IS Nbrs :
Nbr : PE-14.01
Default Metric : 10
Sub TLV Len : 19
IF Addr : 10.1.0.2
LAN-Adj-SID: 17 20 16 00 00 16 Flags:v4VL Weight:0 Label:524286
TE IP Reach :
Default Metric : 10
Control Info: , prefLen 30
Prefix : 10.1.0.0
Default Metric : 30
Control Info: D , prefLen 30
Prefix : 10.5.0.0
Default Metric : 20
Control Info: D , prefLen 30
Prefix : 10.12.0.0
Default Metric : 10
Control Info: , prefLen 30
Prefix : 10.14.0.0
Default Metric : 30
Control Info: D , prefLen 30
Prefix : 10.23.0.0
Default Metric : 10
Control Info: D S, prefLen 32
Prefix : 172.16.0.11
Sub TLV :
Prefix-SID Index:1, Algo:0, Flags:RNnP
Default Metric : 20
Control Info: D S, prefLen 32
Prefix : 172.16.0.12
Sub TLV :
Prefix-SID Index:2, Algo:0, Flags:RNnP
Default Metric : 30
Control Info: D S, prefLen 32
Prefix : 172.16.0.13
Sub TLV :
Prefix-SID Index:3, Algo:0, Flags:RNnP
Default Metric : 0
Control Info: S, prefLen 32
Prefix : 172.16.0.14
Sub TLV :
Prefix-SID Index:4, Algo:0, Flags:NnP
Default Metric : 40
Control Info: D S, prefLen 32
Prefix : 172.16.0.15
Sub TLV :
Prefix-SID Index:5, Algo:0, Flags:RNnP
-------------------------------------------------------------------------------
LSP ID : PE-14.01-00 Level : L1
Sequence : 0x8 Checksum : 0x485f Lifetime : 1186
Version : 1 Pkt Type : 18 Pkt Ver : 1
Attributes: L1L2 Max Area : 3 Alloc Len : 1492
SYS ID : 1720.1600.0014 SysID Len : 6 Used Len : 81
TLVs :
IS Neighbors :
Virtual Flag : 0
Default Metric: (I) 0
Delay Metric : (I) 0
Expense Metric: (I) 0
Error Metric : (I) 0
Neighbor : PE-14.00
IS Neighbors :
Virtual Flag : 0
Default Metric: (I) 0
Delay Metric : (I) 0
Expense Metric: (I) 0
Error Metric : (I) 0
Neighbor : RA-16.00
TE IS Nbrs :
Nbr : PE-14.00
Default Metric : 0
Sub TLV Len : 0
TE IS Nbrs :
Nbr : RA-16.00
Default Metric : 0
Sub TLV Len : 0
-------------------------------------------------------------------------------
LSP ID : RA-16.00-00 Level : L1
Sequence : 0x9 Checksum : 0x9732 Lifetime : 1090
Version : 1 Pkt Type : 18 Pkt Ver : 1
Attributes: L1 Max Area : 3 Alloc Len : 190
SYS ID : 1720.1600.0016 SysID Len : 6 Used Len : 190
TLVs :
Area Addresses:
Area Address : (3) 49.0001
Supp Protocols:
Protocols : IPv4
IS-Hostname : RA-16
Router ID :
Router ID : 172.16.0.16
Router Cap : 172.16.0.16, D:0, S:0
TE Node Cap : B E M P
SR Cap: IPv4 MPLS-IPv6
SRGB Base:100000, Range:100001
SR Alg: metric based SPF
Node MSD Cap: BMI : 12 ERLD : 15
IS Neighbors :
Virtual Flag : 0
Default Metric: (I) 10
Delay Metric : (I) 0
Expense Metric: (I) 0
Error Metric : (I) 0
Neighbor : PE-14.01
Internal Reach:
Default Metric: (I) 10
Delay Metric : (I) 0
Expense Metric: (I) 0
Error Metric : (I) 0
IP Address : 10.1.0.0
IP Mask : 255.255.255.252
Default Metric: (I) 0
Delay Metric : (I) 0
Expense Metric: (I) 0
Error Metric : (I) 0
IP Address : 172.16.0.16
IP Mask : 255.255.255.255
I/F Addresses :
I/F Address : 10.1.0.1
I/F Address : 172.16.0.16
TE IS Nbrs :
Nbr : PE-14.01
Default Metric : 10
Sub TLV Len : 19
IF Addr : 10.1.0.1
LAN-Adj-SID: 17 20 16 00 00 14 Flags:v4VL Weight:0 Label:524287
TE IP Reach :
Default Metric : 10
Control Info: , prefLen 30
Prefix : 10.1.0.0
Default Metric : 0
Control Info: S, prefLen 32
Prefix : 172.16.0.16
Sub TLV :
Prefix-SID Index:6, Algo:0, Flags:NnP
Level (1) LSP Count : 3
Displaying Level 2 database
-------------------------------------------------------------------------------
LSP ID : P-11.00-00 Level : L2
Sequence : 0xb Checksum : 0x6207 Lifetime : 1049
Version : 1 Pkt Type : 20 Pkt Ver : 1
Attributes: L1L2 Max Area : 3 Alloc Len : 260
SYS ID : 1720.1600.0011 SysID Len : 6 Used Len : 260
TLVs :
Area Addresses:
Area Address : (3) 49.0002
Supp Protocols:
Protocols : IPv4
IS-Hostname : P-11
Router ID :
Router ID : 172.16.0.11
Router Cap : 172.16.0.11, D:0, S:0
TE Node Cap : B E M P
SR Cap: IPv4 MPLS-IPv6
SRGB Base:100000, Range:100001
SR Alg: metric based SPF
Node MSD Cap: BMI : 12 ERLD : 15
IS Neighbors :
Virtual Flag : 0
Default Metric: (I) 10
Delay Metric : (I) 0
Expense Metric: (I) 0
Error Metric : (I) 0
Neighbor : P-11.01
IS Neighbors :
Virtual Flag : 0
Default Metric: (I) 10
Delay Metric : (I) 0
Expense Metric: (I) 0
Error Metric : (I) 0
Neighbor : P-11.02
Internal Reach:
Default Metric: (I) 10
Delay Metric : (I) 0
Expense Metric: (I) 0
Error Metric : (I) 0
IP Address : 10.12.0.0
IP Mask : 255.255.255.252
Default Metric: (I) 10
Delay Metric : (I) 0
Expense Metric: (I) 0
Error Metric : (I) 0
IP Address : 10.14.0.0
IP Mask : 255.255.255.252
Default Metric: (I) 0
Delay Metric : (I) 0
Expense Metric: (I) 0
Error Metric : (I) 0
IP Address : 172.16.0.11
IP Mask : 255.255.255.255
I/F Addresses :
I/F Address : 10.12.0.1
I/F Address : 10.14.0.1
I/F Address : 172.16.0.11
TE IS Nbrs :
Nbr : P-11.01
Default Metric : 10
Sub TLV Len : 19
IF Addr : 10.12.0.1
LAN-Adj-SID: 17 20 16 00 00 12 Flags:v4VL Weight:0 Label:524287
TE IS Nbrs :
Nbr : P-11.02
Default Metric : 10
Sub TLV Len : 19
IF Addr : 10.14.0.1
LAN-Adj-SID: 17 20 16 00 00 14 Flags:v4VL Weight:0 Label:524285
TE IP Reach :
Default Metric : 10
Control Info: , prefLen 30
Prefix : 10.12.0.0
Default Metric : 10
Control Info: , prefLen 30
Prefix : 10.14.0.0
Default Metric : 0
Control Info: S, prefLen 32
Prefix : 172.16.0.11
Sub TLV :
Prefix-SID Index:1, Algo:0, Flags:NnP
-------------------------------------------------------------------------------
LSP ID : P-11.01-00 Level : L2
Sequence : 0x8 Checksum : 0x8d2b Lifetime : 1111
Version : 1 Pkt Type : 20 Pkt Ver : 1
Attributes: L1L2 Max Area : 3 Alloc Len : 81
SYS ID : 1720.1600.0011 SysID Len : 6 Used Len : 81
TLVs :
IS Neighbors :
Virtual Flag : 0
Default Metric: (I) 0
Delay Metric : (I) 0
Expense Metric: (I) 0
Error Metric : (I) 0
Neighbor : P-11.00
IS Neighbors :
Virtual Flag : 0
Default Metric: (I) 0
Delay Metric : (I) 0
Expense Metric: (I) 0
Error Metric : (I) 0
Neighbor : P-12.00
TE IS Nbrs :
Nbr : P-11.00
Default Metric : 0
Sub TLV Len : 0
TE IS Nbrs :
Nbr : P-12.00
Default Metric : 0
Sub TLV Len : 0
-------------------------------------------------------------------------------
LSP ID : P-11.02-00 Level : L2
Sequence : 0x7 Checksum : 0x258f Lifetime : 597
Version : 1 Pkt Type : 20 Pkt Ver : 1
Attributes: L1L2 Max Area : 3 Alloc Len : 81
SYS ID : 1720.1600.0011 SysID Len : 6 Used Len : 81
TLVs :
IS Neighbors :
Virtual Flag : 0
Default Metric: (I) 0
Delay Metric : (I) 0
Expense Metric: (I) 0
Error Metric : (I) 0
Neighbor : P-11.00
IS Neighbors :
Virtual Flag : 0
Default Metric: (I) 0
Delay Metric : (I) 0
Expense Metric: (I) 0
Error Metric : (I) 0
Neighbor : PE-14.00
TE IS Nbrs :
Nbr : P-11.00
Default Metric : 0
Sub TLV Len : 0
TE IS Nbrs :
Nbr : PE-14.00
Default Metric : 0
Sub TLV Len : 0
-------------------------------------------------------------------------------
LSP ID : P-12.00-00 Level : L2
Sequence : 0xb Checksum : 0x84b3 Lifetime : 1059
Version : 1 Pkt Type : 20 Pkt Ver : 1
Attributes: L1L2 Max Area : 3 Alloc Len : 260
SYS ID : 1720.1600.0012 SysID Len : 6 Used Len : 260
TLVs :
Area Addresses:
Area Address : (3) 49.0002
Supp Protocols:
Protocols : IPv4
IS-Hostname : P-12
Router ID :
Router ID : 172.16.0.12
Router Cap : 172.16.0.12, D:0, S:0
TE Node Cap : B E M P
SR Cap: IPv4 MPLS-IPv6
SRGB Base:100000, Range:100001
SR Alg: metric based SPF
Node MSD Cap: BMI : 12 ERLD : 15
IS Neighbors :
Virtual Flag : 0
Default Metric: (I) 10
Delay Metric : (I) 0
Expense Metric: (I) 0
Error Metric : (I) 0
Neighbor : PE-13.02
IS Neighbors :
Virtual Flag : 0
Default Metric: (I) 10
Delay Metric : (I) 0
Expense Metric: (I) 0
Error Metric : (I) 0
Neighbor : P-11.01
Internal Reach:
Default Metric: (I) 10
Delay Metric : (I) 0
Expense Metric: (I) 0
Error Metric : (I) 0
IP Address : 10.12.0.0
IP Mask : 255.255.255.252
Default Metric: (I) 10
Delay Metric : (I) 0
Expense Metric: (I) 0
Error Metric : (I) 0
IP Address : 10.23.0.0
IP Mask : 255.255.255.252
Default Metric: (I) 0
Delay Metric : (I) 0
Expense Metric: (I) 0
Error Metric : (I) 0
IP Address : 172.16.0.12
IP Mask : 255.255.255.255
I/F Addresses :
I/F Address : 10.23.0.1
I/F Address : 10.12.0.2
I/F Address : 172.16.0.12
TE IS Nbrs :
Nbr : PE-13.02
Default Metric : 10
Sub TLV Len : 19
IF Addr : 10.23.0.1
LAN-Adj-SID: 17 20 16 00 00 13 Flags:v4VL Weight:0 Label:524287
TE IS Nbrs :
Nbr : P-11.01
Default Metric : 10
Sub TLV Len : 19
IF Addr : 10.12.0.2
LAN-Adj-SID: 17 20 16 00 00 11 Flags:v4VL Weight:0 Label:524286
TE IP Reach :
Default Metric : 10
Control Info: , prefLen 30
Prefix : 10.12.0.0
Default Metric : 10
Control Info: , prefLen 30
Prefix : 10.23.0.0
Default Metric : 0
Control Info: S, prefLen 32
Prefix : 172.16.0.12
Sub TLV :
Prefix-SID Index:2, Algo:0, Flags:NnP
-------------------------------------------------------------------------------
LSP ID : PE-13.00-00 Level : L2
Sequence : 0xd Checksum : 0x1ea5 Lifetime : 1197
Version : 1 Pkt Type : 20 Pkt Ver : 1
Attributes: L1L2 Max Area : 3 Alloc Len : 283
SYS ID : 1720.1600.0013 SysID Len : 6 Used Len : 283
TLVs :
Area Addresses:
Area Address : (3) 49.0005
Supp Protocols:
Protocols : IPv4
IS-Hostname : PE-13
Router ID :
Router ID : 172.16.0.13
Router Cap : 172.16.0.13, D:0, S:0
TE Node Cap : B E M P
SR Cap: IPv4 MPLS-IPv6
SRGB Base:100000, Range:100001
SR Alg: metric based SPF
Node MSD Cap: BMI : 12 ERLD : 15
IS Neighbors :
Virtual Flag : 0
Default Metric: (I) 10
Delay Metric : (I) 0
Expense Metric: (I) 0
Error Metric : (I) 0
Neighbor : PE-13.02
Internal Reach:
Default Metric: (I) 10
Delay Metric : (I) 0
Expense Metric: (I) 0
Error Metric : (I) 0
IP Address : 10.5.0.0
IP Mask : 255.255.255.252
Default Metric: (I) 10
Delay Metric : (I) 0
Expense Metric: (I) 0
Error Metric : (I) 0
IP Address : 10.23.0.0
IP Mask : 255.255.255.252
Default Metric: (I) 0
Delay Metric : (I) 0
Expense Metric: (I) 0
Error Metric : (I) 0
IP Address : 172.16.0.13
IP Mask : 255.255.255.255
Default Metric: (I) 10
Delay Metric : (I) 0
Expense Metric: (I) 0
Error Metric : (I) 0
IP Address : 172.16.0.15
IP Mask : 255.255.255.255
External Reach:
Default Metric: (I) 0
Delay Metric : (I) 0
Expense Metric: (I) 0
Error Metric : (I) 0
IP Address : 10.5.0.0
IP Mask : 255.255.255.252
Default Metric: (I) 0
Delay Metric : (I) 0
Expense Metric: (I) 0
Error Metric : (I) 0
IP Address : 10.23.0.0
IP Mask : 255.255.255.252
Default Metric: (I) 0
Delay Metric : (I) 0
Expense Metric: (I) 0
Error Metric : (I) 0
IP Address : 172.16.0.13
IP Mask : 255.255.255.255
I/F Addresses :
I/F Address : 10.5.0.1
I/F Address : 10.23.0.2
I/F Address : 172.16.0.13
TE IS Nbrs :
Nbr : PE-13.02
Default Metric : 10
Sub TLV Len : 19
IF Addr : 10.23.0.2
LAN-Adj-SID: 17 20 16 00 00 12 Flags:v4VL Weight:0 Label:524287
TE IP Reach :
Default Metric : 10
Control Info: , prefLen 30
Prefix : 10.5.0.0
Default Metric : 10
Control Info: , prefLen 30
Prefix : 10.23.0.0
Default Metric : 0
Control Info: S, prefLen 32
Prefix : 172.16.0.13
Sub TLV :
Prefix-SID Index:3, Algo:0, Flags:NnP
Default Metric : 10
Control Info: S, prefLen 32
Prefix : 172.16.0.15
Sub TLV :
Prefix-SID Index:5, Algo:0, Flags:RNnP
-------------------------------------------------------------------------------
LSP ID : PE-13.02-00 Level : L2
Sequence : 0x8 Checksum : 0xdcd4 Lifetime : 994
Version : 1 Pkt Type : 20 Pkt Ver : 1
Attributes: L1L2 Max Area : 3 Alloc Len : 81
SYS ID : 1720.1600.0013 SysID Len : 6 Used Len : 81
TLVs :
IS Neighbors :
Virtual Flag : 0
Default Metric: (I) 0
Delay Metric : (I) 0
Expense Metric: (I) 0
Error Metric : (I) 0
Neighbor : PE-13.00
IS Neighbors :
Virtual Flag : 0
Default Metric: (I) 0
Delay Metric : (I) 0
Expense Metric: (I) 0
Error Metric : (I) 0
Neighbor : P-12.00
TE IS Nbrs :
Nbr : PE-13.00
Default Metric : 0
Sub TLV Len : 0
TE IS Nbrs :
Nbr : P-12.00
Default Metric : 0
Sub TLV Len : 0
-------------------------------------------------------------------------------
LSP ID : PE-14.00-00 Level : L2
Sequence : 0xb Checksum : 0x3fbf Lifetime : 1138
Version : 1 Pkt Type : 20 Pkt Ver : 1
Attributes: L1L2 Max Area : 3 Alloc Len : 1492
SYS ID : 1720.1600.0014 SysID Len : 6 Used Len : 283
TLVs :
Area Addresses:
Area Address : (3) 49.0001
Supp Protocols:
Protocols : IPv4
IS-Hostname : PE-14
Router ID :
Router ID : 172.16.0.14
Router Cap : 172.16.0.14, D:0, S:0
TE Node Cap : B E M P
SR Cap: IPv4 MPLS-IPv6
SRGB Base:100000, Range:100001
SR Alg: metric based SPF
Node MSD Cap: BMI : 12 ERLD : 15
IS Neighbors :
Virtual Flag : 0
Default Metric: (I) 10
Delay Metric : (I) 0
Expense Metric: (I) 0
Error Metric : (I) 0
Neighbor : P-11.02
Internal Reach:
Default Metric: (I) 10
Delay Metric : (I) 0
Expense Metric: (I) 0
Error Metric : (I) 0
IP Address : 10.1.0.0
IP Mask : 255.255.255.252
Default Metric: (I) 10
Delay Metric : (I) 0
Expense Metric: (I) 0
Error Metric : (I) 0
IP Address : 10.14.0.0
IP Mask : 255.255.255.252
Default Metric: (I) 0
Delay Metric : (I) 0
Expense Metric: (I) 0
Error Metric : (I) 0
IP Address : 172.16.0.14
IP Mask : 255.255.255.255
Default Metric: (I) 10
Delay Metric : (I) 0
Expense Metric: (I) 0
Error Metric : (I) 0
IP Address : 172.16.0.16
IP Mask : 255.255.255.255
External Reach:
Default Metric: (I) 0
Delay Metric : (I) 0
Expense Metric: (I) 0
Error Metric : (I) 0
IP Address : 10.1.0.0
IP Mask : 255.255.255.252
Default Metric: (I) 0
Delay Metric : (I) 0
Expense Metric: (I) 0
Error Metric : (I) 0
IP Address : 10.14.0.0
IP Mask : 255.255.255.252
Default Metric: (I) 0
Delay Metric : (I) 0
Expense Metric: (I) 0
Error Metric : (I) 0
IP Address : 172.16.0.14
IP Mask : 255.255.255.255
I/F Addresses :
I/F Address : 10.1.0.2
I/F Address : 10.14.0.2
I/F Address : 172.16.0.14
TE IS Nbrs :
Nbr : P-11.02
Default Metric : 10
Sub TLV Len : 19
IF Addr : 10.14.0.2
LAN-Adj-SID: 17 20 16 00 00 11 Flags:v4VL Weight:0 Label:524287
TE IP Reach :
Default Metric : 10
Control Info: , prefLen 30
Prefix : 10.1.0.0
Default Metric : 10
Control Info: , prefLen 30
Prefix : 10.14.0.0
Default Metric : 0
Control Info: S, prefLen 32
Prefix : 172.16.0.14
Sub TLV :
Prefix-SID Index:4, Algo:0, Flags:NnP
Default Metric : 10
Control Info: S, prefLen 32
Prefix : 172.16.0.16
Sub TLV :
Prefix-SID Index:6, Algo:0, Flags:RNnP
Level (2) LSP Count : 7
-------------------------------------------------------------------------------
Control Info : D = Prefix Leaked Down
S = Sub-TLVs Present
Attribute Flags : N = Node Flag
R = Re-advertisement Flag
X = External Prefix Flag
E = Entropy Label Capability (ELC) Flag
Adj-SID Flags : v4/v6 = IPv4 or IPv6 Address-Family
B = Backup Flag
V = Adj-SID carries a value
L = value/index has local significance
S = Set of Adjacencies
P = Persistently allocated
Prefix-SID Flags : R = Re-advertisement Flag
N = Node-SID Flag
nP = no penultimate hop POP
E = Explicit-Null Flag
V = Prefix-SID carries a value
L = value/index has local significance
Lbl-Binding Flags: v4/v6 = IPv4 or IPv6 Address-Family
M = Mirror Context Flag
S = SID/Label Binding flooding
D = Prefix Leaked Down
A = Attached Flag
SABM-flags Flags: R = RSVP-TE
S = SR-TE
F = LFA
X = FLEX-ALGO
FAD-flags Flags: M = Prefix Metric
===============================================================================
thanks! Lucas
Hi @laimaretto thank you for your feedback. A topology from PE-14 point of view
stable_lab_isis_database_v2.txt Hello,
I have a similar behaviour, I tried to upload on an offline instance of topolograph the following topology and I also get an empty graph message, can you check if the file as such should be parseable for you ?
Raw file with empty Level 1 Area part included if this could cause issues. stable_lab_isis_database_v3.txt
Hi @ailtchev ,
Many thanks for your templates. They helped me a lot.
I fixed my templates, like Neighbor
-> Nbr
and got such beautiful topology. I'm going to apply some other fixes and will release docker-based Topolograph under 2.35.3
or 2.36
tag next week. Fixes are available on online version of the Topolograph right now.
P.S.
I noticed that TE
is activated, I'm thinking to introduce some new features based on TE
data, like color link by Admin groups etc, could you please share what features could be valuable for you and other users of Topolograph to analyze MPLS?
Hello,
Thanks for the feedback, did you update only the Nokia textfsm template ?
The topology indeed looks like this in our validation network. I am planning to run it on our 800+ node network to visualise it.
For the features, admin group coloring is indeed a good way to see the current state of setup in the network.
At a previous job, I worked also on a similar app with flash displaying XML based topology. There, the aim was always to display the dynamic graph on predefined positions of the routers based on the visio base network design that I was maintaining. In a separate window, I was allowing the user to place new routers where he wanted and when the routers came back in topologies at the same place , like routers from south of the country being displayed in the bottom part of the diagram. positions were stored in db in absolute coordinates varying between (0,0) - bottom left and (1,1) - top right.
Extra features, that can be interesting to be displayed is physical interconnection between nodes using LLDP based network discovery where each node needs to be queried with napalm/netconf yang tree and where each logical link for OSPF/ISIS viewcan then displayed as a composition of N physical links aggregated in a PortChannel/ae/LAG interface. Data model can become complex and you can have a look on the proposed model from RFC8345 - A YANG Data Model for Network Topologies to see what can be used from there. Let me know if this makes sense.
Not going as far, you can parse and add as attributes Segment Routing infos available in LSDB like node IDs and interface segment labels assigned locally by each router.
More generally what vendor paying tools are proposing are visualisations of MPLS paths calculated by RSVP in decentralised mode available on the ingress nodes of these paths or centrally calculated paths based on topologies, admin group and bandwidth requirements delivered through PCE protocol. Your tool could verify if routers have correctly received calculated LSPs. You can use containerlab to play aroudn these concepts if you want to explore them further.
prod topology And ECMP path calculation on that topology
wow! looks cool! do you have any noticeable delay in building paths on such big topology?
Thank your feedback! I have a task to provide Drawio-based topology in my backlog, but first of all I would like to:
LLDP based network discovery
is also challenging task, but I think it's better to let the customer gather LLDP information via napalm/netconf by themselves (so many vendors with so many LLDP's command output) and push the LLDP data on the topology (drawio?) via uniform API.
parse and add as attributes Segment Routing infos available in LSDB like node IDs and interface segment labels assigned locally by each router.
yeah, it seems to be easy - I will put it into my backlog!
If you are not against - may I add you in "topolograph's friends" email group for the chance to ask the feedback from network professional community.
Hello, with pleasure for the topolograph's friends ! The graph takes some to build and to be parsed shortest path doesn't seem to be a problem. I provide you my email on another well known professional network.
Hi! I've built a lab to test the analysis on ISIS networks, but the tool complains with a "The graph is empty. Are you sure that you uploaded ISIS LSDB from Nokia".
The topology I'm using is this one:
And the DB is the one I obtained at the router P-11, which is an L2 router. EDIT: I've updated the DB output since PE-14 was missing in my original post.
Any ideas? Thanks!