Topology Map shows cloud icons (shared segment) where none exist

Description

Using a simple star topology. Couple of switches connected to a core router.

For this purposes of this example, all routers and switches are cisco.

All switches are directly connected to the switches, YET, openNMS network topology map shows "shared segment" cloud icons all over the place.

  • Clicking on the cloud icons says "Shared segment [$hostname] Port [$port]"

($hostname and $port are respective ports of the links)

  • Clicking on the links themselves says ""Bridge Layer 2

The "Link detail info" of the core router shows lot of information under

"Bridge Forwarding Table Links found by Enhanced Linkd"

And also from "CDP Cache Table Links found by Enhanced Linkd"

 

Tried all sorts of things:
increase / decrease semantic zoom
actual zoom,
changing focus

Environment

Ubuntu 16.04

Acceptance / Success Criteria

None

Attachments

1

Lucidchart Diagrams

Activity

Show:

Sandy Skipper November 19, 2021 at 4:16 PM

Please reopen if this occurs in the current release.

Jonathan Vaughn December 15, 2018 at 1:15 AM

I am seeing this same issue, though in my case it's all Netgear "smart" "semi-managed" switches (supporting SNMP and LLDP, but no CDP/OSPF/IS-IS I believe - ). I have just set up OpenNMS in a VM for testing purposes to give it a try.

Ports which have a single MAC on them still show up as "Multiple Mac Addresses" with a cloud icon. Sometimes both "Shared Segments found by Enhanced Linkd" and "LLDP Remote Table Links found by Enhanced Linkd" will list a MAC, sometimes just "Shared Segments" (not all devices appear to respond to LLDP?), but it doesn't matter, the ports will still show connected to a cloud rather than the single device.

Axel Fenn September 25, 2018 at 8:14 AM

I have exact the same issue:

Core Switch is a Linksys (by Cisco) SRW2024P 24Port-Gbit switch. All end-devices are directly connected + one managed HP switch + Internet Router and 2 Access Points.

The topology map only shows resiliant the shared segments and the LLD-links to the HP switch. On next level (2+) in most cases no connections are shown.

I digged into the bridge-to-bridge information collected by enlinkd. All mac adresses and links discovered are correct and there .

The funny thing is: when I reload the topology map, sometimes 1 or 2 devices directly connected to the bridge are shown, but more with a hazard principle.

Example: I have two exactly the same access-points connected with the same version and configuration; one is shown sometimes, the other never)

As i tried this on 2 different installations (docker, Horizon Core Web V22.0.3, V23.0.0.) with exactly the same behaviour: I assume that there must pe an issue with the instance who renderes the topology map (vertex and edges).

 

I tried nearly everything to relsolve: deleted the core switch and waited until discovery of other devices is reloaded/calculated; then re-provisioned the switch, tried different endlinkd /snmp-config configurations and time-out sesstings etc.

Nothing helps!

pls help!

 

Won't Fix

Details

Assignee

Reporter

Labels

Components

Affects versions

Priority

PagerDuty

Created April 9, 2018 at 8:42 PM
Updated November 22, 2021 at 10:16 PM
Resolved November 19, 2021 at 4:16 PM