Manual topology mapping
After years of suffering with the horrific (and broken) topology mapping, how about just giving us the ability to create our own dependencies/maps, similar to The Dude or MangeEngine's OpManager?
Forum Discussion
Jordan-Eil
Neophyte
Neophyte
Were there other issues you were referring to that were introduced in 187?
Specifically, it seems when trying to export a saved Topology Map to a dashboard for reporting, the saved map is basically not reflective of what the dashboard appears under.
Add to the existing issues in 1.86 where moving items in the map is now basically impossible. Dynamic maps, even custom-made ones, just reset mere moments after the devices are moved, and reset whenever any property of any single device is changed.
For example, selecting “network” devices on an edge device, say a Floor Switch in HQ which is attached to the main switch to show its connected devices, will reset the entire map to a default, or randomized, dynamic map.
Essentially it either takes the way that LM displays the Topology in one of its default settings or nothing.
This wasn’t the case before, as we were once able to edit the placement of devices under Hierarchal modes and dynamic modes alike in order to better represent the network topology.
After 1.85 Hierarchal maps are no longer editable, and from that point forward we’ve been unable to build a legible topology map of our core network.
