Skip to:

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

Spurious Trapd error logs: unknown SNMP protocol version 'v2'

Description

Trapd sometimes logs the following scary-looking message at ERROR severity:

Received a trap with an unknown SNMP protocol version 'v2'

The message is produced by accounting code in the TrapQueueProcessor class, which recognizes only v2c and not v2 when counting traps received using protocol version 2; it should treat the two values as equivalent. This message happens because some events derived from SNMPv2c traps end up having v2 rather than v2c recorded as their protocol version.

The impact should be limited to log noise (which could be quite significant in busy installs) and miscounted traps in the Trapd JMX statistics.

Environment

Unsure about exactly what triggers this, but it's been seen in the wild in a couple of different environments.

Acceptance / Success Criteria

None

Lucidchart Diagrams

Activity

Jeff Gehlbach November 22, 2016 at 11:09 AM

PR was against wrong branch. New PR:

https://github.com/OpenNMS/opennms/pull/1152

Jeff Gehlbach November 22, 2016 at 9:52 AM

Jeff Gehlbach November 22, 2016 at 9:51 AM

Update affected / target versions.

Jeff Gehlbach November 21, 2016 at 5:36 PM

Fix branch pushed with minimal change to TrapQueueProcessor and an update to TrapdIT to verify reception of v2 traps along with existing v1 trap verification. Waiting for bamboo.

Jeff Gehlbach November 21, 2016 at 5:26 PM

Blockerizing because this impacts at least one support customer with high trap volume.

Fixed

Details

Assignee

Reporter

Labels

Components

Fix versions

Affects versions

Priority

PagerDuty

Created November 21, 2016 at 5:20 PM
Updated November 30, 2016 at 11:11 AM
Resolved November 22, 2016 at 4:09 PM

Flag notifications