Hi. I have a problem with RB532. I’m using them on the network and now after upgrading new firmware, RB532s stop responding when any of the users wants to search in strongDC++. The only one thing that helps is to unplug RB532 from electricity. The firewall doesn’t help. Does anybody have the same problem or can anybody give any advice?Thanks a lot
Are you monitoring this router with SNMP? I have heard of this issue with 2.9.19 and 2.9.20 and SNMP monitoring. I’ve not experienced it myself, but I have heard others say it is an issue.
Hi, No, I’m not using SNMP. I tried to upgrade 2.9.22 and the problem is still there…
I am beginning to see the same thing here.
Routerboards just stop responding, I cannot verify through serial connection, because they are out on the tower site, but… I changed out one in my office, to X86 based system and it is happy, just the RB532 that I am seeing this issue, so far…
If there is any information you would liek me to post, I would be happy to.
OK problem seems to have moved.. odd..
This problem began occurring after the update of one of my routers (RB532 + RB564) from 2.9.19 to 2.9.22, might I was thinking it was coincidental, but now, I don’t.. It froze every thirty minutes or so. Had to power cycle it each time and then everything was fine again. (the thirty minutes is not precise, seemed to be random) So I first tried to roll it back to 2.9.19, no luck problem persisted. so i built up a computer, put a couple RB44 in it, and installed 2.9.22, it is working great, problem solved i though, however, the problem moved from that router to the next in line on one of the legs, off the initial router. it had also been updated to .22 so i tried to downgrade it to .19 .. of course.. no go. this one i cannot just replace with a pc, it is 100ft in the air, and is a unfortunately a critical point. the first router was the “central” router, this new one is ties two of the wireless legs of my network back in to the “central”.
Hopefully everyone understands, if needed i can supply a diagram, but in essence, the problem moved from the “central” to one of the next in line with the same version (2.9.22) any ideas on what to do? Fortunately this one only freezes about every 2-3 hours instead of every 30 minutes.
I am most likely going to send someone up the tower tomorrow to pull the unit down and replace it with one that has not yet been upgrade to see if that makes a difference. For tonight I have setup the watchdog timer to reboot the box on failure (if it will work, not sure how locked up the box gets)
is there a way to format and reinstall the OS fresh from the ground without access to the serial port? would be interesting to see if a fresh install of an older version makes a difference.
any one else seeing this problem?
also, I am not using SNMP right now.
I just noticed that with the version 2.9.22 there was a BIOS update to 1.12, so i have upgraded it to see the difference.
Just read this thread: http://forum.mikrotik.com/t/rb532-wan-ether1-interface-stopped-responding/6422/1
might be the same issue, but since i do not have another way of getting into the box, I don’t know. if the problem persists, ill try .23 and see…
good news.. seems that the 2.9.23 fixed the issue.
in case anyone else experiences the same.
I have the same issue here. Although, my situation is a little different.
I just switched out a 3 year old EnGenius Senao router to Mikrotik. RB532A running two SR2 cards. (BIOS nor OS has been updated) card 2 is not active. its for future endeavors.
It was working fine this fall. now this winter it is having problems. first I thought it was freezing (temperature changes). But, after a couple of days of it powering down, I watched it. And it would power down roughly about 10am then after figiting with it trying to reboot, it would finally power up. Now it has finally crashed and wont come back up. The modem says that the router is getting power because it detects the router when I plug the POE in. I looked up the pole and noticed in the window of the router case that there is a blue light on (constant). so, the router is getting power. It is not broadcasting a signal, nor is it accessable through winbox over ethernet.
Ether0 is POE only. Ether1 is Internet connection. The router is setup as a hotspot.
As soon as I can get it to come up again, I am going to try my hand at netinstall and try to update the firmware as suggested here. Never updated a mikrotik router before. so this will be my first attempt to do so.
Any help would be appreciated…
Eric
PS… I think I just found my answer online. seems that my first assumption was correct. The boards are freezing due to temp dropping.
see the below threads
http://www.mail-archive.com/mikrotik@mail.butchevans.com/msg04795.html
Going to try taking the radio down tomorrow morning. and either spraying/covering the outside of the box with Great Stuff gap filler/ canned foam insulation… or, some how rigging a christmas tree light bulb either on or inside the box to produce heat… gonna try the insulation method first. Will let you know the outcome.
OK, so far so good.
I took a small plastic bathroom waste can bag and placed it over the box. then, I took some gap filler/canned foam insulation and sprayed it all over the box (seeing how I got the radio mounted to the side of my deck, it looks like a big glob of poop hanging off the trellis…lol). Earlier this afternoon, I noticed a loose connection on the poe. but, the router was getting power so, I doubt it was a blown ethernet port. Just waiting for the insulation to dry. I dont know how long it will take in the cold weather like this. It is getting pretty firm right now. hopefully it wont take long. So far the radio has been operational for 10 hours of uptime, and it is pretty darn cold out there. I only covered the sides and top with insulation (seeing how heat rises) also, so I could get to the connections on the bottom of the box. Incase it start to have a potential of getting too hot inside the box, the open face on the bottom can aid in maintaining a decent temperature if the inside of the box gets too warm. If nothing else, I will have to cover the bottom also.
Its now been 24 hours of uptime. So far so good… No instances where the radio is crashing. When I was in Iraq doing this, it was vice versa. I had to keep the box inside my hooch/living quarters due to the constant situations of 120-130 deg temps and dust storms outside.