Re: RV 345 SNMP timeout

w1gx · ‎06-07-2021

SNMP on my RV345 with FW 1.0.03.21 keeps timing out. A simple snmpwalk yields the following:

SNMPv2-MIB::sysDescr.0 = STRING: Linux, Cisco Small Business RV345-K9, Version 1.0.03.21 Wed Mar 10 04:42:23 IST 2021
SNMPv2-MIB::sysObjectID.0 = OID: SNMPv2-SMI::enterprises.9.6.1.23.3.18.0.0
DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (33242771) 3 days, 20:20:27.71
SNMPv2-MIB::sysContact.0 = STRING: 
SNMPv2-MIB::sysName.0 = STRING: RV345
SNMPv2-MIB::sysLocation.0 = STRING: 
SNMPv2-MIB::sysServices.0 = INTEGER: 72
SNMPv2-MIB::sysORLastChange.0 = Timeticks: (0) 0:00:00.00
IF-MIB::ifNumber.0 = INTEGER: 31
Timeout: No Response from cisco

SNMP is enabled for version 2c. Is there another setting or could this be a firmware issue?

nagrajk1969 · ‎07-26-2021

From where are you running the snmpwalk?

a) Is the host (on which you are running the snmpwalk) connected on the lan-side or wan-side of the router?

I did a check using the below snmpwalk (of the whole mib tree) from a host connected on the lan-side of RV345, and as of now i did not see any timeouts...

Note: The lan-host is a ubuntu-14.x machine

------------------------------------

snmpwalk -v 2c -c public 192.168.1.1 .

Note: there is a dot"." at the end of the above command

......and below is the traces of the output at the end of the snmpwalk done:

iso.3.6.1.4.1.2021.2.1.5.121 = INTEGER: 1
iso.3.6.1.4.1.2021.2.1.5.122 = INTEGER: 1
iso.3.6.1.4.1.2021.2.1.5.123 = INTEGER: 3
iso.3.6.1.4.1.2021.2.1.5.124 = INTEGER: 3
iso.3.6.1.4.1.2021.4.1.0 = INTEGER: 0
iso.3.6.1.4.1.2021.4.2.0 = STRING: "swap"
iso.3.6.1.4.1.2021.4.3.0 = INTEGER: 0
iso.3.6.1.4.1.2021.4.4.0 = INTEGER: 0
iso.3.6.1.4.1.2021.4.5.0 = INTEGER: 1012884
iso.3.6.1.4.1.2021.4.6.0 = INTEGER: 623232
iso.3.6.1.4.1.2021.4.11.0 = INTEGER: 623232
iso.3.6.1.4.1.2021.4.13.0 = INTEGER: 42064
iso.3.6.1.4.1.2021.4.14.0 = INTEGER: 0
iso.3.6.1.4.1.2021.4.15.0 = INTEGER: 0
iso.3.6.1.4.1.2021.11.1.0 = INTEGER: 1
iso.3.6.1.4.1.2021.11.2.0 = STRING: "systemStats"
iso.3.6.1.4.1.2021.11.3.0 = INTEGER: 0
iso.3.6.1.4.1.2021.11.4.0 = INTEGER: 0
iso.3.6.1.4.1.2021.11.7.0 = INTEGER: 0
iso.3.6.1.4.1.2021.11.8.0 = INTEGER: 172475306
iso.3.6.1.4.1.2021.11.9.0 = INTEGER: 525261
iso.3.6.1.4.1.2021.11.10.0 = INTEGER: 1112522
iso.3.6.1.4.1.2021.11.11.0 = INTEGER: 48430625
iso.3.6.1.4.1.2021.100.2.0 = STRING: "4.1.8"
iso.3.6.1.4.1.2021.100.3.0 = STRING: "Mon Jun 14 02:43:39 IST 2021
"
iso.3.6.1.4.1.2021.100.4.0 = STRING: "Mon Jul 26 12:03:20 2021"
iso.3.6.1.6.3.1.1.6.1.0 = INTEGER: 412777413
iso.3.6.1.6.3.1.1.6.1.0 = No more variables left in this MIB View (It is past the end of the MIB tree)
root@lanhost:~/workdir1#

---------------------------------------------------

w1gx · ‎07-26-2021

Thank you for looking into this on your end. I am running snmpwalk from the lan side on an ubuntu 20.x machine, and do the exact same thing - only that it results in a timeout.

snmpwalk -v2c -cpublic_MAU 172.21.84.1 .

iso.3.6.1.2.1.1.1.0 = STRING: "Linux, Cisco Small Business RV345-K9, Version 1.0.03.21 Wed Mar 10 04:42:23 IST 2021"

iso.3.6.1.2.1.1.2.0 = OID: iso.3.6.1.4.1.9.6.1.23.3.18.0.0

iso.3.6.1.2.1.1.3.0 = Timeticks: (87652928) 10 days, 3:28:49.28

iso.3.6.1.2.1.1.4.0 = ""

iso.3.6.1.2.1.1.5.0 = STRING: "RV345"

iso.3.6.1.2.1.1.6.0 = ""

iso.3.6.1.2.1.1.7.0 = INTEGER: 72

iso.3.6.1.2.1.1.8.0 = Timeticks: (0) 0:00:00.00

iso.3.6.1.2.1.2.1.0 = INTEGER: 31

Timeout: No Response from 172.21.84.1

Here's the configuration:

nagrajk1969 · ‎07-27-2021

Hi

That is strange.

1. Could you attach the router config file ( xml file) here ? I would like to import it as is on my router in my network and try the snmp walk in my setup. Maybe it will give us some info on whats causing the timeout

Note: After saving the running config as xml file to pc, you may please edit the file and change your WAN public ipaddresses on wan1/wan2

All other config settings are generic enough using RFC1918 private ip addresses, so there is no harm done in keeping the info as is in the config file

2. Could give a block schematic of your network deployment?

snmp-host----(lan network)----(rv345)wan----isp----(internet)

is the snmp host (running snmpwalk) directly connected to Rv345 or whats in between them?

Unless the Rv345 is under heavy load at the instance when you run the snmp queries for the mib tree browsing....there must be some issue with the routing on the lan-side that results in the snmp udp session getting timedout...