Project

General

Profile

Actions
Copy link

Bug #8600

closed

"snmpd SIOCGIFDESCR (e6000sw0port1): Device not configured"

Added by Vladimir Lind over 6 years ago. Updated over 1 year ago.

Status:
Resolved
Priority:
Normal
Assignee:
Luiz Souza
Category:
SNMP
Target version:
pfSense - 2.4.4
Start date:
06/26/2018
Due date:
% Done:

100%

Estimated time:
Release Notes:
Affected Plus Version:
Affected Architecture:

Description

When enabling SNMP on SG-3100 and XG-7100 following messages appear on every SNMP service change:

SG3100:

Jun 26 06:32:45 snmpd 46667 SIOCGIFDESCR (e6000sw0port1): Device not configured
Jun 26 06:32:45 snmpd 46667 SIOCGIFDESCR (e6000sw0port2): Device not configured
Jun 26 06:32:45 snmpd 46667 SIOCGIFDESCR (e6000sw0port3): Device not configured
Jun 26 06:32:45 snmpd 46667 SIOCGIFDESCR (e6000sw0port4): Device not configured
Jun 26 06:32:45 snmpd 46667 SIOCGIFDESCR (e6000sw0port5): Device not configured

XG7100:

Jun 26 06:37:49 snmpd 78243 SIOCGIFDESCR (e6000sw0port1): Device not configured
Jun 26 06:37:49 snmpd 78243 SIOCGIFDESCR (e6000sw0port2): Device not configured
Jun 26 06:37:49 snmpd 78243 SIOCGIFDESCR (e6000sw0port3): Device not configured
Jun 26 06:37:49 snmpd 78243 SIOCGIFDESCR (e6000sw0port4): Device not configured
Jun 26 06:37:49 snmpd 78243 SIOCGIFDESCR (e6000sw0port5): Device not configured
Jun 26 06:37:49 snmpd 78243 SIOCGIFDESCR (e6000sw0port6): Device not configured
Jun 26 06:37:49 snmpd 78243 SIOCGIFDESCR (e6000sw0port7): Device not configured
Jun 26 06:37:49 snmpd 78243 SIOCGIFDESCR (e6000sw0port8): Device not configured
Jun 26 06:37:49 snmpd 78243 SIOCGIFDESCR (e6000sw0port9): Device not configured
Jun 26 06:37:49 snmpd 78243 SIOCGIFDESCR (e6000sw0port10): Device not configured

Would be nice not to see them at all.

Related issues

Related to Bug #13976: SNMP logs "Device not configured" error message when queries involve built-in switch port interfacesResolvedLuiz Souza

Actions
Actions
Copy link
 #1

Updated by Constantine Kormashev over 6 years ago

The bug also affects 7100

Actions
Copy link
 #2

Updated by Luiz Souza over 6 years ago

  • Assignee set to Luiz Souza
Actions
Copy link
 #3

Updated by Luiz Souza over 6 years ago

  • Status changed from New to Feedback
  • % Done changed from 0 to 100

The warning is now silenced.

Please test with the next snapshot.

Actions
Copy link
 #4

Updated by Vladimir Lind over 6 years ago

Tested on latest snap on 3100 and 7100 - looks good, thanks!

Actions
Copy link
 #5

Updated by Vladimir Lind over 6 years ago

  • Status changed from Feedback to Resolved
Actions
Copy link
 #6

Updated by Björn Bylander almost 2 years ago

This bug seems to have popped up again on my SG-3100 after upgrading to 23.01.

Actions
Copy link
 #7

Updated by Jim Pingle almost 2 years ago

  • Project changed from pfSense to pfSense Plus
  • Category changed from SNMP to SNMP
  • Affected Version deleted (2.4.4)
Actions
Copy link
 #8

Updated by Jim Pingle almost 2 years ago

  • Related to Bug #13976: SNMP logs "Device not configured" error message when queries involve built-in switch port interfaces added
Actions
Copy link
 #9

Updated by Martin Stockzell over 1 year ago

Unfortunatly it's back...

May 5 21:20:06 snmpd 15562 SIOCGIFDESCR (e6000sw0port3): Device not configured
May 5 21:20:06 snmpd 15562 SIOCGIFDESCR (e6000sw0port2): Device not configured
May 5 21:20:06 snmpd 15562 SIOCGIFDESCR (e6000sw0port1): Device not configured
May 5 21:20:06 snmpd 15562 SIOCGIFDESCR (e6000sw0port5): Device not configured
May 5 21:20:06 snmpd 15562 SIOCGIFDESCR (e6000sw0port4): Device not configured
May 5 21:20:06 snmpd 15562 SIOCGIFDESCR (e6000sw0port3): Device not configured
May 5 21:20:06 snmpd 15562 SIOCGIFDESCR (e6000sw0port2): Device not configured
May 5 21:20:06 snmpd 15562 SIOCGIFDESCR (e6000sw0port1): Device not configured

Actions
Copy link
 #10

Updated by Jim Pingle over 1 year ago

See #13976 -- it's already fixed on 23.05 snapshots

Actions
Copy link
 #11

Updated by Martin Stockzell over 1 year ago

Jim Pingle wrote in #note-10:

See #13976 -- it's already fixed on 23.05 snapshots

My bad I actually thought it was solved with a patch - Any ETA for a full update instead of just a dev snapshot?

Actions
Copy link
 #12

Updated by Jim Pingle over 1 year ago

Martin Stockzell wrote in #note-11:

Jim Pingle wrote in #note-10:

See #13976 -- it's already fixed on 23.05 snapshots

My bad I actually thought it was solved with a patch - Any ETA for a full update instead of just a dev snapshot?

Very soon, 23.05 is current in RC testing.

Actions
Copy link
 #13

Updated by Martin Stockzell over 1 year ago

Jim Pingle wrote in #note-12:

Martin Stockzell wrote in #note-11:

Jim Pingle wrote in #note-10:

See #13976 -- it's already fixed on 23.05 snapshots

My bad I actually thought it was solved with a patch - Any ETA for a full update instead of just a dev snapshot?

Very soon, 23.05 is current in RC testing.

Much appreciated!

Actions
Copy link

Also available in: Atom PDF