This would be best done as a page which showed cdp/lldp/etc "links" as opposed to the core page, which his based on port descriptions. We already use this logic when drawing the map, so as not to draw links twice.
We don't have such a page yet, but it probably wouldn't be terribly difficult to create.
adam.
Adam Armstrong Managing Director & Lead Architect Observium Limited http://www.observium.org http://docs.observium.org http://jira.observium.org On 2017-11-27 23:53:30, Nick Schmalenberger nick@schmalenberger.us wrote: On Mon, Nov 27, 2017 at 01:43:31PM +0000, Andrew Lemin wrote:
Hi,
We are evaluating Observium at the moment, and we have many point-to-point links in our WAN as everyone should ;)
Each end of the same p2p link is labeled to be identical; interface Te1/1/1 description CORE:DeviceA=DeviceB
This results in two graphs in Observium. One for DeviceA (labelled "CORE:DeviceA=DeviceB") and one for DeviceB (labelled "CORE:DeviceA=DeviceB").
However as they are connected back-to-back to each other they show the exact same information (just "in" and "out" reversed obviously).
Is it possible to merge these two ports/graphs into a single logical Core link?
This would significantly save on screen real estate (halving the Core page at the least) and make tracing paths through the network much more logical.
Similar to how the Customer graphs aggregate multiple ports with the same description together. But I guess throwing away one side of the link maybe?
Details for each end could still be seen on the specific device's page to view locally significant things like port errors etc Thanks, Andy.
Maybe you could also include something about an A and Z side of each link. This won't work directly with the port description parsing, but you could easily make a group of A side links and use the group for aggregation. -Nick _______________________________________________ observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium