Device dependencies and loops

Hi,

I know loops in device dependencies have been discussed previously but some of the posts are quite old so I am not sure if they are still accurate.

The network I am monitoring contains many “ring” topologies for fail-over reasons. This is implemented through Cisco’s Resilient Ethernet Protocol (REP). This is a reasonable large network with almost 400 network devices. Therefore the performance of LibreNMS is important.

I would like to model the following device dependencies to match the actual topologies:

router <- switch <-> switch <-> switch <-> switch -> router

Every switch depends on both of its two neighbour switches and a neighbour router if applicable.

Does anyone have experience with such a configuration and what would be the impact on LibreNMS?

Thanks for your feedback.

I managed to set-up a copy of the live environment, applied all parent/child relationships (that’s a total of 708 entries in the device_relationships table, and includes loops) and running php daily.php -f recalculate_device_dependencies completed without a problem.

So far so good. Next step: try the same on the live set-up.

The Device Dependency Map is now very slow but I can live with that. With so many parent/child relationships it is not useful anyway.

Next: Alert rules with device dependencies.