Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

largest map-able ospf datasbase? #43

Closed
spacklePatch opened this issue Oct 3, 2023 · 11 comments
Closed

largest map-able ospf datasbase? #43

spacklePatch opened this issue Oct 3, 2023 · 11 comments

Comments

@spacklePatch
Copy link

Is there a size limit for the numbers of nodes in area 0? I currenty tried a large network (1700+ nodes) and nothing would load.

@Vadims06
Copy link
Owner

Vadims06 commented Oct 3, 2023

Hi @spacklePatch,
wow, 1700+ nodes! Actually I tested on 0.5k nodes and it worked. I can admit, that there is no any limits for the number of nodes. May I ask you to send this LSDB to admin @ topolograph.com?.. If it's not possible, I will try to generate a graph with similar size.

@Vadims06
Copy link
Owner

Vadims06 commented Oct 3, 2023

tested on 1600 nodes.
Could you please provide some more context: do you upload LSDB via text file or create a network via "Create Topology" and yaml file? Do you see a loading bar, when you press "Load dynamic graph"?
image

@spacklePatch
Copy link
Author

I uploaded a Mikritok LSB file from router os 7.3.1. I have other versions and a few other router models I can try. I'm still waiting to see if I can send the actual file I used. I don't see anything happening when I press the "Load dynamic graph" button. I'll keep you informed

@spacklePatch
Copy link
Author

I got his to work, I'm thinking router OS7 changed the format what exporting the LSA file. routerOS 6.48.6 loaded just fine. And it turns out we're closer to 2000 routers in area 0:

image

@Vadims06
Copy link
Owner

Vadims06 commented Oct 4, 2023

It's beautiful! I will be glad if reports about asymmetric links and paths help you, as well as building paths and find backups, etc!
I suppose that Mikrotik changed LSDB output in 7.3.1, I could try to fix templates for new version if you can share a small peace of it, but if it's not crucial and it works with 6.48.6, it's okay. All in all I will try to evaluate how much memory and other resources are required to work with such big graphs!

@spacklePatch
Copy link
Author

I'm still waiting to see if the company will let me release the LSADB (nothing secret in there, but i have to verify). In the mean time, I upgraded one of my small routers at my house (yes, I have OSPF running in my home network), with a before/after DB export. I do believe it's mostly a formatting change between versions:

lsa-ROS-6.48.6.txt
lsa-ROS-7.10.txt

@Vadims06
Copy link
Owner

Vadims06 commented Oct 7, 2023

thank you for the provided output. I compared it and they differ, i.e

6.48 7.10
type=router type="router"
Stub 192.168.43.0 type=stub id=192.168.43.0

but good news is that current templates match both options. I fixed only pattern for external subnet. Let me clarify the problem once again - if you upload either 6.48 or 7.10 LSDB output and graph name with date and number of hosts appears in your list - it means that parsing was successful. If you press the "Load dynamic graph" button and can see the topology for 6.48, but not for 7.10 it means that something happened during topology generation. If so - could please check any errors in browser console ( available via F12 ).

@spacklePatch
Copy link
Author

spacklePatch commented Oct 9, 2023 via email

@Vadims06
Copy link
Owner

Vadims06 commented Oct 9, 2023

@spacklePatch, I afraid that attached error was not attached to your comment if you replied via your email.

@Vadims06
Copy link
Owner

Hi @spacklePatch ,
thanks to @moghue42, I applied fix for ROS 7.10, please check if your LSDB works properly

@Vadims06
Copy link
Owner

Confirmed by @moghue42

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants