snmpwalk ip:port doesn't work

Post support questions that directly relate to Linux/Unix operating systems.

Moderators: Developers, Moderators

Post Reply
User avatar
Pumpi
Cacti User
Posts: 259
Joined: Wed Jan 14, 2004 3:23 am
Location: Germany

snmpwalk ip:port doesn't work

Post by Pumpi »

Hello,

I'm using Suse ES 9 with net-snmp version 5.1.3.1

When i try to use snmpwalk -v 2c -c blbla xxx.xxx.xxx.xxx:260
(udp port 260 for Checkpoint SNMP daemon) I get follwing error:

"Timeout: no response from xxx.xxx.xxx.xxx"

No packets are seen in the firewall log. Traffic is allowed and no problem to get the SNMP datas from normal standard udp port 161.

Any ideas :-?

Pumpi
philuxe
Posts: 24
Joined: Fri Jan 07, 2005 6:15 am

Post by philuxe »

Option has been removed from what I know, I have had the same issue here. You can try to NAT incoming 161UDP request to 260UDP
User avatar
Pumpi
Cacti User
Posts: 259
Joined: Wed Jan 14, 2004 3:23 am
Location: Germany

Post by Pumpi »

philuxe,

I can't believe that this option was disabled in the newer net-snmp versions.

From a old net-snmp unix host I can use snmpwalk with the -p port command :cry:
bryancromwell
Posts: 15
Joined: Tue Sep 21, 2004 8:13 pm

Re:

Post by bryancromwell »

This is a old post but for search purposes, if you add the following line to the /etc/snmpd.conf you can poll the Checkpoint Daemon from port 161. I just tested it with Rhel3 + CP ver R62

proxy -v1 -c public 127.0.0.1:260 .1.3.6.1.4.1.2620

Cheers
Bryan
Post Reply

Who is online

Users browsing this forum: No registered users and 1 guest