node-red-snmp - "RequestTimedOutError: Request timed out"

[Tranquility76]

Hello, same issue as in #397 (which is closed) again:

net-snmp 1.2.4 node-red-node-snmp 0.0.20 npm 6.10.2 node.js 10.16.1 OS Raspbian GNU/Linux 9.9 (stretch) Browser Google Chrome 76.0.3809.100

Downgrade to [email protected] (as mentioned in #397) does NOT solve the problem.

Linux snmpwalk from bash works so it is not an communication / network / ... problem. ( snmpwalk -v2c -c DSLGet 192.168.3.1 1.3.6.1.2.1.10.94.1.1.4.1.2 )

[dceejay]

Hi , have reverted it once again - can you try 0.0.21 ?

[Tranquility76]

Hi,

now with the 0.0.21 and [email protected] - same error. :-(

[Tranquility76]

with [email protected] too

[dceejay]

Is there any way I can recreate this ? Do you have a flow that would show how to recreate it ? I don't use snmp day to day so not is a position to figure it out.

[Tranquility76]

I just started to use snmp with node-red so the flow is more less the first try to move from bash commands to node-red

[ { "id": "b95fc09e.71fcb", "type": "tab", "label": "Flow 1", "disabled": false, "info": "" }, { "id": "a56cf075.87ed4", "type": "inject", "z": "b95fc09e.71fcb", "name": "", "topic": "", "payload": "true", "payloadType": "bool", "repeat": "", "crontab": "", "once": false, "onceDelay": 0.1, "x": 150, "y": 140, "wires": [ [ "2ba51d51.ad58b2" ] ] }, { "id": "2ba51d51.ad58b2", "type": "snmp walker", "z": "b95fc09e.71fcb", "host": "192.168.3.1", "community": "GetDSL", "version": "2c", "oids": "1.3.6.1.2.1.10.94.1.1.4.1.2", "timeout": 5, "name": "", "x": 450, "y": 140, "wires": [ [ "fcd708e4.406e48" ] ] }, { "id": "fcd708e4.406e48", "type": "debug", "z": "b95fc09e.71fcb", "name": "", "active": true, "tosidebar": true, "console": false, "tostatus": false, "complete": "true", "targetType": "full", "x": 720, "y": 140, "wires": [] } ]

[Tranquility76]

The target 192.168.3.1 is Draytek Vigor 130 DSL Modem so maybe for testing you should use a more generic OID...

[dceejay]

Well indeed if I try that I do get time outs as I don't have the target set to any real host. So that seems like a good result so far - the node doesn't crash and I can retry ok. Need to find something here that has snmp turned on.

[Tranquility76]

@dceejay Dave, any news on that issue?

[dceejay]

not from here - been busy on core 1.0 release. I still don't have a way to recreate this - so will really need to rely on the kindness of others to step up.

[DandyDiamond]

@Tranquility76 - Not sure if you solved this or not, but the OID might be incorrect.

I have Vigor 2762 the OID for checking the Tx Rate is documented as: 1.3.6.1.2.1.10.94.1.1.4.1.2 adslAtucChanCurrTxRate (DSL router's Rx Rate)

After using SNMPWALK I found that it is actually: 1.3.6.1.2.1.10.94.1.1.4.1.2.4

This works in Node-RED.

[dceejay]

Thanks - good find.