Monitoring Linux problem - SNMP port not reachable

Votes:

0

Your Vote:

Up

Down

I've been following the following instructions to monitor my linux server (dell server - opensuse 11.2)... http://www.paessler.com/support/kb/questions/111

I've installed net-snmp, and I'm following the following instructions as recommended by prtg...

http://www.debianhelp.co.uk/snmp.htm

I changed the snmpd.conf file and I think I've done everything correctly, but when I test with "snmpwalk localhost -c public -v1", I get the following error "timeout: no response from localhost"

Can someone help with this problem?

Thanks

linux networking server-settings snmp snmpd

Created on Jun 7, 2010 3:51:28 PM by  mastr2 (0) 1

Last change on Jul 9, 2010 12:23:42 PM by  Daniel Zobel [Paessler Support] (24,183) 3 3



10 Replies

Votes:

0

Your Vote:

Up

Down

Also I'm getting the following error in the net-snmpd.log...

error on subcontainer 'ia_addr' insert (-1)

Created on Jun 9, 2010 7:12:51 PM by  mastr2 (0) 1

Last change on Jun 10, 2010 12:11:57 PM by  Daniel Zobel [Paessler Support] (24,183) 3 3



Votes:

0

Your Vote:

Up

Down

Hello,

is the SNMP service running on the system at all? Because when we shut down a SNMP service on an Ubuntu - machine we received the same result:

# /etc/init.d/snmpd stop
 * Stopping network management services:
# snmpwalk localhost -c public -v1
Timeout: No Response from localhost

whereas with a running service, the service was correctly listening on port 161:

# /etc/init.d/snmpd start
# netstat -apn|grep snmpd
udp        0      0 0.0.0.0:161            0.0.0.0:*                          21018/snmpd

and also responding with 3424 lines of SNMP counters to the # snmpwalk localhost -c public -v1. Please understand that this we cannot try debugging the issue any deeper in your systems, however, maybe other users experienced something similar.

Best Regards.

Created on Jun 10, 2010 11:58:30 AM by  Torsten Lindner [Paessler Support] (17,330) 3 1



Votes:

0

Your Vote:

Up

Down

seems to be up and running when I type in:

# servcie snmpd status
checking for service snmpd              running

# netstat -apn |grep snmpd
tcp     0     0 127.0.0.1:199            0.0.0.0:*     15364/snmpd
upd    0     0 10.99.108.250:161     0.0.0.0:*     15364/snmpd

#snmpwalk localhost -c public -v1
Timeout: No Response from localhost

Any help with this would be appreciated.

Created on Jun 10, 2010 2:19:55 PM by  mastr2 (0) 1

Last change on Jun 10, 2010 2:43:39 PM by  Torsten Lindner [Paessler Support] (17,330) 3 1



Votes:

0

Your Vote:

Up

Down

Hello,

as SNMP is traditionally UPD, can you please try to do a snmpwalk on 10.99.108.250?

Best regards.

Created on Jun 10, 2010 2:44:17 PM by  Torsten Lindner [Paessler Support] (17,330) 3 1



Votes:

0

Your Vote:

Up

Down

when I do a snmpwalk 10.99.108.250 I get the following...

"snmpwalk: No securityName specified."

Created on Jun 14, 2010 3:14:25 PM by  mastr2 (0) 1



Votes:

0

Your Vote:

Up

Down

Hello,

at first it would be interesting what version of snmpwalk (or what version of the snmp-package on your system) you are using. You could check this by using the following command which is linux distribution independend:

# snmpwalk -V
NET-SNMP version: 5.4.1

"snmpwalk: No securityName specified."

This message seems to appear with older versions of SNMPd-installations. Therefor you would have to adjust the command as follows:

# snmpwalk 10.99.108.250 -c public -v1

If this doesn't succeed try the following command by switching to the SNMP-protocol version 2c:

# snmpwalk 10.99.108.250 -c public -v2c

Best regards.

Created on Jun 15, 2010 8:08:37 AM by  Michael Zeidler [Paessler Support] (112) 3 1



Votes:

0

Your Vote:

Up

Down

Hi thanks for the reply, here is what i get for each command...

  1. snmpwalk -v NET-SNMP version: 5.4.2.1
  1. snmpwalk 10.99.108.250 -c public -v1 Timeout: No Response from 10.99.108.250
  1. snmpwalk 10.99.108.250 -c public -v2c Timeout: No Response from 10.99.108.250

no sure why this happening. would be grateful for any help.

Created on Jun 15, 2010 1:33:21 PM by  mastr2 (0) 1



Votes:

0

Your Vote:

Up

Down

Hello,

I would recommend checking the routing table for the proper entry for the appropriate destination and network device (see "man route"). You could achieve this by using the "route -n" command. If the routing table is right I would afterwards check whether UDP packets are filtered by a possible running firewall blocking those packets by using the "iptables -L" command. As an alternative to check if UDP packets are filtered by a firewall you also could use "nmap -sU -p 161 10.99.108.250" (see "man nmap").

Created on Jun 16, 2010 10:26:35 AM by  Michael Zeidler [Paessler Support] (112) 3 1

Last change on Jun 16, 2010 10:31:09 AM by  Daniel Zobel [Paessler Support] (24,183) 3 3



Votes:

0

Your Vote:

Up

Down

Hi the routing table seems to be correct. In snmpd.conf 10.99.108.0 is being used.

# route -n
Kernel IP routing table

Destination     Gateway         Genmask         Flags Metric Ref    Use Iface

10.99.108.0     0.0.0.0         255.255.255.0   U     0      0        0 eth1

169.254.0.0     0.0.0.0         255.255.0.0      U     0      0        0 eth1

127.0.0.0       0.0.0.0          255.0.0.0         U     0      0        0 lo

0.0.0.0         10.99.108.1     0.0.0.0            UG    0      0        0 eth1

There does not seem to be blocking from a firewall.

# iptables -L
Chain INPUT (policy ACCEPT)

target     prot opt source               destination         

Chain FORWARD (policy ACCEPT)

target     prot opt source               destination         

Chain OUTPUT (policy ACCEPT)

target     prot opt source               destination

# nmap -sU -p 161 10.99.108.250

Starting Nmap 5.00 ( http://nmap.org ) at 2010-06-16 10:11 EDT

Interesting ports on OpenXLX (10.99.108.250):

PORT    STATE         SERVICE

161/udp open|filtered snmp

Nmap done: 1 IP address (1 host up) scanned in 2.10 seconds

In my log files /var/log/net-snmpd.log I'm getting the following errors...

NET-SNMP version 5.4.2.1
error on subcontainer 'ia_addr' insert (-1)
error on subcontainer 'ia_addr' insert (-1)
Connection from UDP: [10.99.108.30]:2884
Connection from UDP: [10.99.108.30]:2891
Connection from UDP: [10.99.108.30]:2900
Connection from UDP: [10.99.108.30]:2908
Connection from UDP: [10.99.108.30]:2930
error on subcontainer 'ia_addr' insert (-1)
Connection from UDP: [10.99.108.30]:2931
Connection from UDP: [10.99.108.30]:2933
Connection from UDP: [10.99.108.30]:2937
Connection from UDP: [10.99.108.30]:2938
Connection from UDP: [10.99.108.30]:2939
Connection from UDP: [10.99.108.30]:2942
error on subcontainer 'ia_addr' insert (-1)
Connection from UDP: [10.99.108.30]:2946
Connection from UDP: [10.99.108.30]:2948
Connection from UDP: [10.99.108.30]:2955
Connection from UDP: [10.99.108.30]:2964
Connection from UDP: [10.99.108.30]:2971
Connection from UDP: [10.99.108.30]:2994
error on subcontainer 'ia_addr' insert (-1)
Connection from UDP: [10.99.108.30]:2995
Connection from UDP: [10.99.108.30]:2997
Connection from UDP: [10.99.108.30]:3001
error on subcontainer 'ia_addr' insert (-1)
Connection from UDP: [10.99.108.250]:35993
Connection from UDP: [10.99.108.250]:45494
error on subcontainer 'ia_addr' insert (-1)
error on subcontainer 'ia_addr' insert (-1)
Connection from UDP: [10.99.108.250]:51412
[init_smux] bind failed: Address already in use
getaddrinfo("10.99.108.250", NULL, ...): Address family for hostname not supported

Created on Jun 16, 2010 2:29:04 PM by  mastr2 (0) 1

Last change on Jun 16, 2010 3:21:48 PM by  Daniel Zobel [Paessler Support] (24,183) 3 3



Votes:

0

Your Vote:

Up

Down

Haven't heard anything from my postings. Does anyone have any other suggestions?

Thanks

Created on Jun 21, 2010 6:29:13 PM by  mastr2 (0) 1



Please log in or register to enter your reply.


Disclaimer: The information in the Paessler Knowledge Base comes without warranty of any kind. Use at your own risk. Before applying any instructions please exercise proper system administrator housekeeping. You must make sure that a proper backup of all your data is available.

PRTG
Network Monitor
Intuitive to Use.
Easy to manage.

150.000 administrators have chosen PRTG to monitor their network. Find out how you can reduce cost, increase QoS and ease planning, as well.

Visit
www.paessler.com

What is this?

This knowledgebase contains questions and answers about PRTG Network Monitor and network monitoring in general. You are invited to get involved by asking and answering questions!

Learn more

Top Tags


View all Tags