Skip to:

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

Snmp collect reversing to unticked after a few hours

Description

See

Issue is that interfaces are being selected, and then a few hours or a day later, they are set to not collect (unticked). This is a new issue since upgrading from 29 → 30.x

e.g. from the forum post

We have a Cisco device that has 210 interfaces, so only selected interfaces are selected for Collection. I need to monitor two specific interfaces, and when I select the Collect option next to them in the "Choose SNMP Interfaces for Data Collection (inside Manage SNMP Data Collection per Interface), it collects data for a couple of hours and then it stops monitoring it and the Collect check box is unticked. The collection goes back to some kind of default and only those interfaces selected before are now collected. This worked until version 29. This started since upgrading to our current version 30.0.4. It is running on CentOS Stream release 8.

Environment

30.0.4-1 redhat 8.5

Acceptance / Success Criteria

None

Lucidchart Diagrams

Activity

Show:

Alex May January 5, 2023 at 3:16 PM

Merged into foundation-2023

Alex May January 4, 2023 at 9:09 PM

This issue was introduced in 30.0.3 via the fix for this issue:

PR:

JianYet December 21, 2022 at 2:45 PM

I can confirm this is occurring on Horizon 31 as well. Without any foreign policy configured, it is changing snmpCollect flag from UC to N for some of the SNMP interfaces upon a node rescan.

Veena Kannan December 20, 2022 at 3:50 PM

would you please update to Horizon 31 and check if this issue still exist and update this JIRA? Thanks.

Fixed

Details

Assignee

Reporter

Labels

HB Grooming Date

HB Backlog Status

FD#

Sprint

Fix versions

Priority

PagerDuty

Created December 6, 2022 at 6:52 PM
Updated January 5, 2023 at 3:16 PM
Resolved January 5, 2023 at 3:16 PM