FOR TIPS, gUIDES & TUTORIALS

subscribe to our Youtube

GO TO YOUTUBE

14455 questions

17168 answers

28195 comments

0 members

We are migrating to our new platform at https://community.teltonika.lt. Moving forward, you can continue discussions on this new platform. This current platform will be temporarily maintained for reference purposes.
0 votes
1,445 views 7 comments
by anonymous
I had PRTG network monitor probing these OIDs:

RSRP - 1.3.6.1.4.1.48690.2.2.1.20

SINR - 1.3.6.1.4.1.48690.2.2.1.19

After upgrading to the latest firmware, I get a SNMP 223 error when trying to probe these.

Monitoring CPU load, RAM etc still works.

1 Answer

0 votes
by anonymous

Hi,

I have checked with latest release and seems working correctly:

Try to download MIB file using that new fw release.

If issue persist, try to restore router to default settings

Best answer
by anonymous

Hi,

Here is what I get when I probe the OIDs using the same tool in your screenshot:

Is there anything short of a factory reset which can fix this?

Many thanks,

J

by anonymous

Hmm... the factory reset did not help.

However, it miraculously started working again when I issued /etc/init.d/snmpd restart on the command line.

Probably some kind of bug, maybe?

by anonymous
Hi,

I have checked few times and it was working correctly.

If issue persist, please inform us, and would be great if you could provide details how to reproduce it.

Thank you in advance.
by anonymous

Steps to reproduce:

  1. Configure the SNMP service. Use v2c and set the community string.
  2. Set up the monitoring server to probe the router's LAN IP
This works OK until the router is rebooted or power-cycled for any reason. Whenever this happens, the SNMP monitoring only works on the core Linux parameters (load average, disk space, RAM)
For some reason, the signal level monitors (OIDs) start working again when I manually restart the snmpd service.
Maybe you should make a change in the next firmware release so that the snmpd service waits for 1-2min before starting?
by anonymous
Hi,

Could you send to me (private message) troubleshoot package from router when issue is appeared?
by anonymous
Hi, I've sent you the troubleshooting file in a PM.
by anonymous

Looks like this issue is fixed in firmware version RUTX_R_00.02.00.2