Hot answers tagged

12

dontLogTCPWrappersConnects If the snmpd was compiled with TCP Wrapper support, it logs every connection made to the agent. This setting disables the log messages for accepted connections. Denied connections will still be logged. I.e. add dontLogTCPWrappersConnects true to snmpd.conf. I'm puzzled why this log message is considered ...


5

Including the standard (included in the default /etc/snmp/snmp.conf file for CentOS 6.5) line worked for me to reduce the verbosity specifically with respect to TCP/UDP SNMP connection logging: dontLogTCPWrappersConnects yes Here is a more "verbose" excerpt from the default snmp.conf file: # We do not want annoying "Connection from UDP: " messages in ...


5

rocommunity public default -V systemonly Your read-only community string is public. default represents what traffic will be accepted, which is to say all traffic will be accepted. Change default to be a hostname or a network address and slash annotated subnet to restrict it further (e.g. 10.4.0.0/16). The read-only context will be restricted to the -V ...


5

Snmpbulkwalk initiates internal server repetitions to walk through mib tree. Server does not respond untill it retrives "max-repetitions" number of variables or end of mib tree is reached. Retrieving some variables may demand valuable time. Important note: snmpwalk walks trough a requested subtree exactly but snmpbulkwalk may retreive additional variables (...


4

In RHEL there're two configuration options, according to "man snmp_config", added in BZ#917816 enhancement. # include site specific config includeFile site.conf # include a all *.conf files in a directory includeDir /etc/snmp/config.d


4

Sounds like you are missing the MIB files that do the translation. To install them run: apt-get install snmp-mibs-downloader For licensing reasons they arent included by default. Installing that package will go download the standard ones from the internet. For specific manufactuer's custom SNMP values you will need to find their .mib files from the ...


3

The problem seems to be here: -c /etc/snmp/snmpd.conf Remove that from your /etc/default/snmpd so it looks like this: SNMPDOPTS='-Lsd -Lf /dev/null -u snmp -g snmp -I -smux,mteTrigger,mteTriggerConf -p /var/run/snmpd.pid' If you want to get snmpd to listen on 0.0.0.0 (or all interfaces) then edit: /etc/snmp/snmpd.conf So it looks like this: # ...


2

This may be an old question, but the documentation out there isn't very forthcoming as to why SNMP is acting like it is, and I've been struggling with this mess for a while, so here goes. The extend stanza creates a new MIB structure at the OID you specify, and appends a number of values from NET-SNMP-EXTEND-MIB, then appends more values depending on the ...


2

After digging through NetSNMP code a bit, it looks like it processes the config file line-by-line, and appends to the agent address data if it finds something. Thus, you are able to add multiple lines in the config file with multiple agent addresses: agentAddress udp:127.0.0.1:29032 agentAddress udp:127.0.0.1:22032 I was able to test this on my own agent ...


2

tcpConnState is part of the TCP-MIB and retrieves information on active tcp connections on the remote host (similar to the information available from netstat). The first five digits are the server's local address & port for the tcp connection, and the last five are the remote address and port. For example an active ssh connection looks as follows, with ...


1

"Cannot statfs" likely comes from the disk usage monitor in snmpd, that iterates the mounted file systems and asks for the amount of free space left. If a statfs(2) call fails, that is a serious problem on the machine, this is one of the syscalls that basically just look up information in a shared structure and return it, the only way this can fail ...


1

It seems that snmpd on Ubuntu Xenial has a bug, the agentx dowsn't start even if it is specified in the snmpd.conf. I had to specifiy it in /etc/default/snmpd and I can totally omit it in /etc/snmp/snmpd.conf so that I have only one line in the file. Here is the working configurations for me: /etc/default/snmpd SNMPDOPTS='-Lsd -Lf /dev/null -u snmp -g snmp ...


1

Your parameter -v is not doing what you think it would do: From the manual: -v, --version Print version information for the trap daemon and then exit. I don't know what you want to set to 1, but it's a different parameter. The parameter -c does not exist either for snmptrapd. Both parameters exist for snmptrap though (notice the missing d). Looks like ...


1

syscontact is a value that can be retrieved via SNMP. It may be useful to get this data via SNMP, on the other hand it may just be an information leak or a value that is going to quickly go stale. Organizationally you have to decide if you want to use SNMP as a way of determining a contact for the host, or not. Syscontact has no other effect. You'd most ...


1

https://www.debian.org/distrib/archive If you are using APT the relevant sources.list entries are like: deb http://archive.debian.org/debian/ hamm contrib main non-free or deb http://archive.debian.org/debian/ bo bo-unstable contrib main non-free


1

I'd suggest that you can modify the systemd script rather than doing it manually on the command line. For example, the current snmpd.service located in /usr/lib/systemd/system/ contains the following: [Unit] Description=Simple Network Management Protocol (SNMP) Daemon. After=syslog.target network.target [Service] Type=notify Environment=OPTIONS="-LS0-6d" ...


1

Apparently, the only way to specify multiple interfaces for version Net-SNMP 5.7.2.1 is by specifying multiple IP addresses at the command line for snmpd. I've yet to find a workable solution of specifying multiple interfaces using the snmpd configuration (snmpd.conf) file approach. # /usr/sbin/snmpd 127.0.0.1 192.168.1.1 It is there (at the command line) ...


1

This might be a Permission problem. under normal situations non-root users are not able to bind to ports <1024 in linux. However if the SNMPD drops it privileges after creating the socket/endpoint then this should not be your issue.


1

snmpget -v 2c -c PUBLIC 10.38.2.24 1.3.6.1.2.1.2.2.1.10 snmpget -v 2c -c PUBLIC 10.38.2.24 1.3.6.1.2.1.2.2.1.16 -c communityname, default to PUBLIC -v version, probably 2c SNMPget: Net-SNMP


1

snmpd does not export any metrics for subinterfaces. I'm pretty sure linux doesn't even record those metrics. Observe: $ ifconfig -a <cut non-eth1 data> eth1 Link encap:Ethernet HWaddr E4:11:5B:E0:14:5C inet addr:87.233.215.178 Bcast:87.233.215.191 Mask:255.255.255.240 inet6 addr: fe80::e611:5bff:fee0:145c/64 Scope:Link ...


1

You'll want the cron job to look more like this: /usr/sbin/service bsnmpd status >/dev/null ; if [ $? != 0 ] ; then /usr/sbin/service bsnmpd start ; fi Anyway, let's figure out why bsnmpd is core dumping. See if you can find the bsnmpd.core file, then run /usr/bin/gdb /usr/sbin/bsnmpd bsnmpd.core then run bt and paste the output.


1

Turns out the issue was DNS look ups timing out so I just pushed the -n flag to the options lines in /etc/defaults/snmpd. This was on Debian 6.0. # snmpd options (use syslog, close stdin/out/err). SNMPDOPTS='-Lsd -Lf /var/log/snmpd.log -n -u snmp -g snmp -I -smux -p /var/run/snmpd.pid' # snmptrapd options (use syslog). TRAPDOPTS='-Lsd -Lf ...


1

Not sure, that it is exactly your problem. We ran into the same one but with extend, where name is required and OID isn't. So our misconfigured snmp was executing only the last part of command line which wasn't executable file. Your variant: exec 1.3.6.1.4.1.2021.8 /usr/bin/python /tmp/check-syslog.py will define /usr/bin/python and name and try to ...


Only top voted, non community-wiki answers of a minimum length are eligible