Bug 868670 - No Interface Enumeration on snmp
Summary: No Interface Enumeration on snmp
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: net-snmp
Version: 17
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Jan Safranek
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-10-21 15:18 UTC by galen
Modified: 2013-05-21 07:15 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-05-21 07:15:08 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description galen 2012-10-21 15:18:22 UTC
Description of problem: Network Interfaces Can Not Be Enumerated


Version-Release number of selected component (if applicable): 5.7.1-4


How reproducible: Attempt to enumerate interfaces.  Every time it fails.


Steps to Reproduce:
1. With snmpcheck, target localhost and the network information is not populated. Attempting snmpget produces a nosuchname error.
2.
3.
  
Actual results: NoSuchName


Expected results: Network Interface Statistics


Additional info:

Comment 1 Jan Safranek 2012-10-22 08:21:35 UTC
(In reply to comment #0)
> 1. With snmpcheck, target localhost and the network information is not
> populated. Attempting snmpget produces a nosuchname error.


snmpcheck -t 127.0.0.1 shows all network interfaces to me of F17. In addition, "snmpwalk locahost ifTable" shows all interfaces.

Is your snmpd configured properly? Default /etc/snmp/snmpd.conf is quite strict and does not make interface information public. Try /etc/snmp/snmpd.conf with only one line:
  rocommunity public

(beware, this is very benevolent configuration, use for testing only).

If snmpcheck still does not work with the above configuration file and "snmpwalk -v2c -c public localhost ifTable" does not show anything useful, look at /var/log/messages and attach any snmpd lines to this bug.

Comment 2 Jan Safranek 2013-05-21 07:15:08 UTC
Closing the bug as the  reporter did not provide additional information.


Note You need to log in before you can comment on or make changes to this bug.