Bmp Peer Up/Down Notification Message may be missed on OpenNMS/Sentinel

Description

When BMP listener is enabled on Minion and OpenNMS/Sentinel is running BmpAdapter, sometimes Adapter is missing PeerUp/PeerDown notification messages.

Ideally OpenNMS/Sentinel shouldn't miss any messages that are already present in the queue.

Acceptance / Success Criteria

None

Lucidchart Diagrams

Activity

Show:

Chandra Gorantla April 14, 2021 at 12:25 PM

Chandra Gorantla April 14, 2021 at 12:18 PM

Sometimes BmpParser sends PeerUp notification before Router Initiation message which result in Peer not getting persisted and any IP rib updates for that Peer doesn't get persisted. 

From Minion : 12:20:31.817 WARN [nioEventLoopGroup-3-1] Sending PeerUp packet for IpAddress /212.218.154.21 12:20:31.983 WARN [NettyDnsResolver-NIO-Event-Loop-6-0] Sending PeerUp message 12:20:31.990 WARN [NettyDnsResolver-NIO-Event-Loop-3-0] Sending Initiation message From Sentinel: 12:23:56.447 WARN [kafka-consumer-5] Peer entity with hashId 'cc60733c5e004dc69fd0bac9a6dd29d8', IpAddress = /212.218.154.21 doesn't exist yet 12:23:56.491 WARN [kafka-consumer-4] Got PEER_UP Message, v4: "\324\332\232\025" 12:23:56.595 WARN [kafka-consumer-4] Got INITIATION Message 12:24:56.446 WARN [RateLimitedLogRegistry-0] (suppressed 33776 logs similar to 'Peer entity with hashId '{}', IpAddress = {} doesn't exist yet' in PT59.999S) 12:24:56.447 WARN [kafka-consumer-5] Peer entity with hashId 'cc60733c5e004dc69fd0bac9a6dd29d8', IpAddress = /212.218.154.21 doesn't exist yet 12:25:56.447 WARN [RateLimitedLogRegistry-0] (suppressed 38801 logs similar to 'Peer entity with hashId '{}', IpAddress = {} doesn't exist yet' in PT1M) 12:25:56.449 WARN [kafka-consumer-5] Peer entity with hashId 'cc60733c5e004dc69fd0bac9a6dd29d8', IpAddress = /212.218.154.21 doesn't exist yet
Fixed

Details

Assignee

Reporter

Sprint

Fix versions

Priority

PagerDuty

Created March 30, 2021 at 3:39 PM
Updated April 21, 2021 at 1:23 PM
Resolved April 21, 2021 at 1:23 PM

Flag notifications