Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

snmp authentication error traps with Enhanced Linkd / bridge discovery

Description

we use Enhanced Linkd to detect links between network devices. Within the bridge discovery, OpenNMS use "<configured community>@1" as SNMP community on some Cisco routers to get the following OIDs:
.1.3.6.1.2.1.17.1.4.1.1
.1.3.6.1.2.1.17.1.4.1.2

By using this community, the router will send a snmp authentication failure trap. This happens for 101 devices (all Cisco routers) and will flood the alarm list.

Acceptance / Success Criteria

None

Lucidchart Diagrams

Activity

Patrick Schweizer September 28, 2019 at 4:01 PM

Jesse White September 25, 2019 at 1:26 PM

With the new flag enabled, we're not hitting the following exceptions:

It seems that this code path was never tested.

Patrick Schweizer September 17, 2019 at 4:37 PM

Jesse White September 17, 2019 at 2:22 PM
Edited

Maybe we can introduce a new flag in etc/enlinkd-configuration.xml (something like disable-bridge-vlan-discovery="true") that would allow us to skip the VLAN enumeration and proceed without these.

Sean Torres August 23, 2019 at 5:22 AM

A possible workaround is to edit enlinkd-configuration.xml and change use-bridge-discovery to false

Fixed

Details

Assignee

Reporter

Labels

Components

Sprint

Fix versions

Affects versions

Priority

PagerDuty

Created February 22, 2019 at 5:41 PM
Updated October 15, 2019 at 5:58 PM
Resolved October 15, 2019 at 5:58 PM