Hello! SNMP not worked on RB1000 RouterOS v5.5. Please help!

have you tried 5.6 or 5.7 when released where it is working.

what's in Firewall Filter (input and output chains)?

what's in Firewall Filter (input and output chains)?

There are only two rules

have you tried 5.6 or 5.7 when released where it is working.

updated 5.6 , snmp not worked.

I am also having issues with SNMP on an RB750 with 5.6.

/snmp print
enabled: yes
contact: netops
location: Site 239
engine-id:
trap-target: 0.0.0.0
trap-community: public
trap-version: 1


/snmp community print terse
0 name=public address=0.0.0.0/0 security=none read-access=yes write-access=no authentication-protocol=MD5 encryption-protocol=DES authentication-password="" encryption-password=""

I need to see the CPU usage over time. I can not find the cpu-load oid.

this in turn will allow watch load on each core

I have the same problem.

Snmp stopped responding after I updated from version 4.11 to 5.7

I did not understand the part of the SNMP Security Community
When using None, Authorized Private
I found nothing on the internet regarding this

I have the same problem with rb800 with 5.7. No SNMP response

i have the same problem too 5.11

any help?

Same problem RB800 5.11. It's the only board on our dude without SNMP details. Please advise.

We just started using a brand-new MikroNOC 8400 with RouterOS 5.2 to replace a very stressed RB493AH running RouterOS 3.30, and I'm encountering the same issue. It won't respond to SNMP queries or walks: "Timeout: No Response from xx.xx.xx.xx." The new router was configured from the backup of the old one, which didn't have this problem.

SMNP is enabled, the community string is correct, no security, and it should work with v1, but I get nothing. I even tried setting Authentication and Encryption and using v3, just to cover all the bases, but again, no response.

I see some other SNMP issues covered in the changelog, but not this one. All the other Mikrotiks I am using work just fine. Am I missing something obvious? Has this been solved?

Thanks,
Darren
Western Broadband

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

[admin@loc] /snmp> print
enabled: yes
contact: "www.ecpi.com"
location: "buzzard"
engine-id: ""
trap-target: 0.0.0.0
trap-community: xxxx-xxxx
trap-version: 1
[admin@loc] /snmp> community
[admin@loc] /snmp community> print
# NAME ADDRESS SECURITY READ-ACCESS
0 xxxx-xxxx 0.0.0.0/0 none yes

use 5.11 for SNMP, as 5.10 received SNMP changes.

use 5.11 for SNMP, as 5.10 received SNMP changes.

Here's an update:

This morning, I connected to the other brand-new MikroNOC 8400 with 5.2, with the intent of upgrading this one to 5.11 in hopes that would solve the SNMP problem. Just out of curiosity, before I installed the upgrade, I tried to do an snmpwalk on it, figuring it would not work, and giving me a decent baseline. Nope - this one doesn't have the problem.

I made sure that the SNMP settings (as shown by export) are identical between the two routers, and the only firewall filter rule that appears at all relevant is identical (action=accept chain=input comment=UDP disabled=no protocol=udp).

I can pass an snmpwalk request through the problem router to a device on the other side, and it works - so that also suggests this isn't a firewall blocking issue.

So now, I can still do the upgrade, but it looks as though the RouterOS version 5.2 is not the sole cause of the problem, and I am not confident that the newer OS will solve it. I feel like I am missing the important key to the puzzle, and the solution is just beyond my reach. Any ideas?

---------------
SNMP settings:

/snmp
set contact=ecpi enabled=yes engine-id="" location=Austin trap-target=0.0.0.0 \
trap-version=1
/snmp community
set xxxx-xxxx address=0.0.0.0/0 authentication-password="" \
authentication-protocol=MD5 encryption-password="" encryption-protocol=\
DES name=xxxx-xxxx read-access=yes security=none write-access=no

most probably not.

have you any firewall filters in input or output chain?

also, can you try with sniffer to see if snmp is receiving and responding.

There are no confirmed issues with SNMP in any release of RuterOS, just that some OIDs has been changed to comply with publicly available MIB files.

If anything, try to reinstall router using netinstall tool.

Same here, v5.11 on most everything.

I run torch on the target device and then snmpwalk it, the routeros device receives the packets but doesnt respond.

This is hit-or-miss, some devices replace to the snmpwalk, others dont. Identical setups, zero nat, no blocking firewall rules. Smells like a bug.

FYI, some of the devices that dont work did for a short time, then with no warning just stopped replying to snmp.

Same here, v5.11 on most everything.

I run torch on the target device and then snmpwalk it, the routeros device receives the packets but doesnt respond.

This is hit-or-miss, some devices replace to the snmpwalk, others dont. Identical setups, zero nat, no blocking firewall rules. Smells like a bug.

FYI, some of the devices that dont work did for a short time, then with no warning just stopped replying to snmp.

just that some OIDs has been changed to comply with publicly available MIB files

Which ones?

depends on from what version you want to know.

for example 5.10 to 5.12 was no changes to oids. Some where added for UPS monitoring, and that is it.

also, check how large are data structures you are attempting to get and how often you attempt to do that.

multihomed? are the packets coming and going on the same interface? RouterOS will reply with src ip from whatever route it takes, so if you are not using the default gateway you will get no snmp responses from the router (they dont come from the requested ip). i wish you could bind snmp to the loopback ip or something.

I have this snmp issue on devices that both wlan and ether1 are in bridge1, bridge1 having the only IP. The snmp requests come in the bridge interface but then then the device does not reply. It is like the service is down, but routeros provides me with no way to check if the service is functioning and no way to restart it...

you can disable and then enable the snmp service to restart it. do you only have a single ip on that interface? have you run packet sniffer to confirm its not replying but with wrong source?

single ip, torch says no reply whatsoever

so in following these steps it is possible to achieve that snmp service is not working:

1) clean router w/o ip address
2) enable snmp
3) set up bridge with 2 itnerfaces
4) set up ip on the bridge interface
5) do snmp querry that will fail

is that correct?

multihomed? are the packets coming and going on the same interface? RouterOS will reply with src ip from whatever route it takes, so if you are not using the default gateway you will get no snmp responses from the router (they dont come from the requested ip). i wish you could bind snmp to the loopback ip or something.

That was it!

There was an alternate route which was (accidentally) the default route for traffic from the system we run MRTG on, and once I increased the cost on that route via OSPF to make it prefer the expected route, the router began responding to snmpwalk normally.

Thank you for pointing me in the right direction!

I am also having issues with SNMP on an RB1100AHx2 with 5.20!!!

This works for a short time and stops... (no filters, no firewalls)

This is a BUG, a ooold bug!

I am also having issues with SNMP on an RB1100AHx2 with 5.20!!!

This works for a short time and stops... (no filters, no firewalls)

This is a BUG, a ooold bug!

do you have any dynamic routing?

SNMP has problems on RoS if the routing isn't symmetrical.

I saw a clever "work-around" for it the other day, but can't recall what it was.
Do some searches on SNMP and symmetrical routing - I think you'll find it. [Perhaps that isn't your issue, but something to consider.]

-Greg

[Found it: http://forum.mikrotik.com/viewtopic.php?f=2&t=64439]

pppoe tunnels back to the router the snmp server is located. static route the snmp server's subnet via pppoe tunnel.

I am also having problems with routerboard1100-ahx2 the snmp it does not work. I'm using version 5.20.

Hey,
I got the same problems discribed here:
http://forum.mikrotik.com/viewtopic.php?f=2&t=66397
as it seems it is a bug.

Pls fix!

Thanks
Simon

I just noticed this problem on ROS 5.24.

nmap of working router -sU -p161 says "161/udp open", nmap of problem router says "161/udp open|filtered". No other connectivity problems to router management IP, can winbox and access via port 80 and ping and ssh.

Packet sniff on problem router clarifies that all SNMP packets are being received, no reply packets are being sent. (or possibly it's trying to send them from some unexpected source IP, I didn't test for that I filtered by the IP I was directing requests to. Filtering only for udp port 161 floods me with all snmp traffic flowing through this router to other destinations, which is quite a lot. )

When I got to the part in this thread about asymmetrical routes, I checked and confirmed problem router had asymmetrical routes. I altered the ingress route (eg, no config changes to problem router whatsoever, just to router closer to host originating snmp get request) to match the egress route, and problem miraculously vanished. Now packet sniff at both calling host and router shows snmp get replies sourced from the same management IP address the get requests are addressed to. Said management IP is bound to a loopback (empty bridge affectionately named "lo").

While superficially fixed, I still find this bug (cannot talk SNMP over an asymmetrical route) highly inconvenient. I rely on dynamic routing and prefer the freedom to establish asymmetric routes as circumstances call for them. :/

Is there any workaround for these or roadmap to mikrotik fix it ?