ISIS DB from Nokia emtpy #34
Comments
|
Hi @laimaretto , many thanks for the commands output! I will check it shortly! |
|
Hey @laimaretto , |
|
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. However, let me show you first the following: Brief database of P-11It looks to me that PE-14 is available from this output. Details for PE-14.00-00 at P-11If 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) So my guess is that it should be possible to reach RA-15 and RA-16 from P-11, which is an L2 router. Final thoughts...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. PE-14 brief DBPE-14 detailed DBthanks! |
|
Hi @laimaretto |
|
stable_lab_isis_database_v2.txt 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. |
|
Hi @ailtchev , |
|
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 |
|
wow! looks cool! |
|
Thank your feedback!
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. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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!
The text was updated successfully, but these errors were encountered: