This is a OSPF visualization and analytics tool for network engineers which is aimed at working with OSPF network offline.
Docker version is available now! Repository
v2.25 The biggest release - Topolograph can be integrated with OSPF Watcher + ELK in order to listen, log and save all changes in an OSPF Topology: Up/Down neighbor adjacency, OSPF link cost changes, OSPF networks appeared/disappeared from the topology. The OSPF Watcher repo. All releases.
How to start to work with your OSPF network graph offline?
Two steps: firstly, find your device's vendor in the commands table and save the command's outputs from one of your routers as a single TXT file. Then, in the second step, upload it to the Topolograph (here or in docker's version). No logins and passwords are needed to provide!
Test topolograph's functionality right now! A test graph with 13 hosts has already pre-uploaded for everyone.
1. Save OSPF LSDB as txt file or use Napalm (for dockered version)
2. Get your OSPF topology visual
1. Simulate the link outage
2. Find network reaction on a failure
Reports can help to discover undirected links or asymmetric paths is your topology
In order to get familiar with the principles of calculating backup paths in the event of a link or node falling, you can play with Demo OSPF Graph!
Once you build SPT and check Backup paths, see network reaction on link or network shutdown etc!
Get your OSPF topology visual on the Upload LSDB page
If you have multiarea network - save outputs with different ABRs in the same file and then upload it on the Upload LSDB page. For not-registered users only one topology is saved. For registered users this limit is increased upto 5 topologies.
Check how the shortest path goes.
Traceroute or mtr is not helpful when a packet goes through a firewall. The firewall won't appear in a trace. In order to check the actual path through all network devices - build the shortest path using several ways:
In order to see a backup path - just press on a colored spt edge link. The algorithm will exclude this link and build a backup path.
What will be if we shutdown our Core switch or... one of our border router?)
You can find the network reaction in NetworkReactionOnFailure tab. Just choose your node (network device) and simulate shutdown from right-clicked menu. The algorithm will exclude this node from the topology and show you consequences of your test.
Change OSPF cost on a link on the fly.
Right-click on an edge and set a new OSPF cost. Topolograph shows the traffic change flow - links with a decreased and increased amount of traffic. If we set OSPF cost 9 between Node A and Node B - traffic will be redirected to a link via Node C and Node D.
This feature is going to be used when you want to adjust OSPF cost and would like to see the output of your changes.
Report. Asymmetric paths in OSPF domains.
When different costs are configured on different links - asymmetric paths could be in the network. The incoming path from W to F is going via C-D, but the outgoing path is via B-A. Paths can go via different ISPs and come with different delays and, probably, losses. The report is aimed at discovering such cases in order to eliminate it.
Report. Backup paths via 3d party locations.
Remote offices have the main link (OSPF cost 1) to their main offices and backup link (OSPF cost 10) to the foreign office.
Report. Network heatmap.
The topolograph knows what networks are advertised by nodes. When the network is terminated on both routers, using VRRP, both nodes advertise the network. The node is marked by red if it has a lot of unbackuped networks, and vise versa.
Privacy. Keep your network inside your organization.
Run your local copy of Topolograph inside your on-premises network using the docker image.
Save the output from min two commands (for getting LSA1 and LSA2) into a file with .txt or .log extenstion and upload it to Topolograph.