Hey Gurus, I'm implementing Solarwinds (snmp udp port 161) as my monitoring tool. I take the following steps:

1- # iptables -A INPUT -p udp --dport 161 -j ACCEPT
# /sbin/service iptables save

2- I edit /etc/hosts.allow and add the IP for the Solarwinds server as follows: snmpd: 129.105.106.0

These two steps usually does the trick, but in some cases it does not. Other than these two steps, what other files need to be edited for this communication to start.

Many thanks in advance for your excellent work.

You'd have to start snmpd on the server so it is LISTENing on port 161.

Running "lsof -i :161" would show you if any ports are LISTENing (or otherwise active) on that port.

Running "service snmpd status" on RHEL6 and below would show you whether the snmpd init script has been started. On RHEL7 you'd run "systemctl status snmpd". Substitute "start" for "status" to run the daemons.

Note: Some things might require other services. e.g. on Dell servers we install Dell's Open Manage and our monitoring interrogates MIBs that provides.

snmpd is also running. Is there anything else you can think of that can be blocking the traffic (other than iptables, hosts.deny, or snmpd)?

[root@bartlett-p etc]# service snmpd status
snmpd (pid 1103) is running...
[root@bartlett-p etc]#

On the Solarwinds server, run this:
and wait to "see" any traffic from 129.105.106.0

Doesn't this also require an
in /etc/hosts.deny?

Where are you getting your info?

I just realized you wrote:
iptables -A INPUT -p udp --dport 161 -j ACCEPT

The "-A" adds to end of chain.

On RHEL5 and RHEL6 the end of the input chain is usually:
REJECT all -- 0.0.0.0/0 0.0.0.0/0 reject-with icmp-host-prohibited

That causes it to ignore any other rules in the chain after that line. Typically the best way to do this is to use "-I" for insert instead. You also have to specify the line number with -I.

If you run "iptables -nL --line-numbers" you should see all the rules with the line numbers. Use "-D" to delete any rules in INPUT chain beneath the above REJECT line then use the "-I" with appropriate line number to insert the rule somehwere above the REJECT line.

By the way you can restrict the rule to a specific IP (e.g. that of your Solar Winds server) to prevent others from accessing the SNMP on this RHEL server.

1 members found this post helpful.