Releases: Vadims06/topolograph
Releases · Vadims06/topolograph
v2.26.3 (26.11.2022)
Fix
IS-IS template for Cisco XR LSDB fix.
Enhancements
- How-to doc minor changes.
v2.26.2 (21.07.2022)
NetworkReactionOnFailure enhancements
- Topolograph builds a topology based on OSPF adjacency and physical connectivity is hidden. But in some cases, we can assume that neighbors share the same media, in some cases - not. For example, if neighbors have a common DR - we assume that they are connected via shared physical media and then we emulate one of the edge failures between such neighbors - we emulate all edges down.
Mark all shared media links (which have common DR) is enabled 
- Network reaction if a link/s goes down on dedicated media.
If neighbors do not have DR or they have, but they are only two neighbors on the link, and when we emulate edge failure - we remove the only a single link between two particular neighbors.
Mark all shared media links (which have common DR) is disabled 
v2.26.1 (14.06.2022)
Enhancements
- Asymmetric links counter is added in
Unidirectional and Asymmetric linksreport
v2.26 (20.02.2022)
ISIS support is added for Cisco, Juniper, Nokia, Huawei
v2.25 (09.12.2021)
OSPF Watcher is added
Architecture
The Quagga container has network_mode=host so it sees the GRE tunnel, which is configured by Admin on the Linux Host.
Functional Role
Demo
Click on the image in order zoom it.
Discovering OSPF logs in Kibana. Examples
OSPF cost changes on links
Logs if OSPF adjacency was Up/Down or any networks appeared/disappeared.
Enhancements
v2.24 (17.10.2021)
Enhancements
- save layout
- NetworkReactionOnFailure. unsimulate brokenness for clicked links
- Migrate hostnames automatically for new graph
- the shortest path between two nodes with the names
- give custom prefix to graphs/network state, i.e. 'before R123 upgrade', 'after upgrade'
v2.23 (07.09.2021)
Enhancements
- Ubiquiti support is added.
v2.22 (21.08.2021)
v2.22 (21.08.2021)
Enhancements
- HP (limited) support is added. Why limited - read on realize notes.
v2.21.1 (08.08.2021)
v2.21 (27.07.2021)
v2.21 (27.07.2021)
Enhancements
- Backup paths via 3d party locations.
This report checks that if two locations are directly connected, backup paths should be only between two locations and do not go via third location as transit. Before running this report - it's needed to create groups (~site names/locations) and assign devices to groups. For example, there are two locations in France: the main site (EU_FRA) and the remote site (EU_FRA1). The same schema with offices in Italy. The main offices in France and Italy are connected to each other and have main (OSPF cost 10) and backup (OSPF cost 20) link.
network scheme
Remote offices have the main link (OSPF cost 1) to their main offices and backup link (OSPF cost 10) to the foreign office.
If the main link between main offices goes down - the backup path goes via remote offices in different locations!
- fixes in ECMP backup paths report in v2.20
v2.20 (6.07.2021)
- ECMP backup paths report
- passed report
- failed report
