I’d a 133C with OS 2.9.46 which had worked perfectly for a couple of months since new, but upgrading it to 2.9.51 seemed to cause it problems as it became very sluggish when responding to Winbox or even PUTTY and the processor seemed stuck at 99% for a long time.
So I tried an upgrade to OS 3.7 and have just spend half an hour on the roof in the dark and the rain changing it for a new board, as the upgrade seems to have crashed it completely.
The new board, with OS 2.9.46, is running perfectly.
The old one is now sitting on the desk beside me and I guess I’m going to have to try to find a couple of hours to salvage it, reset it and downgrade it to OS 2.9.46 again.
OK, I got into it via Winbox and took all configuration off apart from the ethernet.
I’m running the resources page only and it tells me I have Free memory=3852.1KiB from 13.5MiB total, Free HDD of 23.3MiB from a total of 61.4MiB and I’m watching the CPU flick from 100% for 1 second to around 3% for a second, regular as the ticking of a clock even though all it’s doing is running a Winbox server.
According to the RB133 Users Manual I downloaded from Mikrotik a couple of weeks ago I should have S1 a software reset button. No software reset button is to be seen. Ditto the manual Jumper J3 is a user-defined jumper. On the board next to it is printed ‘software reset’.
Oddly all the 3.7 package files I uploaded to it are still listed as files, tho’ usually they disappear after an upgrade.
So do I entrust this thing to a subscriber’s CPE when it’s running its CPU at 100% for one second out of two even before it has a wireless card to control, a radio link to run, encryption and PPP and logging and ntp and etc? Will anybody from Mikrotik send me the software re-set button the User’s Manual says it has? Does the User-defined jumper J3 actually do a software reset like the board says it does, or will it reformat the HDD, launch a denial-of-service attack on Cisco or transport me into an alternate reality where the Mikrotik documentation actually bears some resemblance to what they send out of the factory?
And even if J3 is a software re-set button in disguise, what arcane rituals and desperate initiation rites do I have to undertake in order to be allowed into deepest recesses of the Mikrotik Tower where the secret of what you actually do with it is jealously guarded?
I’m cold, wet, tired, depressed and going to bed. Thanks, Mikrotik, for a great evening.
OK, using the few seconds or so between logging on to the beast and it crashing on me I managed to get rid of some of the 3.7 packages and eventually it stabilised, with just system, routerboard and security left on. Interestingly the file list was still telling me that I had 4294.9GB of 4294.9GB free.
From there I managed to downgrade to 2.9.46 and now it’s working perfectly well, tho’ alas with only 64MB free space on the hdd.
So I think it’s going to be a while before I think about upgrading even from 2.9.46, let alone migrating to v3.
This will act as a simple LAN router/gateway and will connect a maximum of 5 local users either on wireless or on ethernet and the internet access will be via dsl. I’m not even running DHCP so it really is a SOHO router if you like.
This is a common problem, and as far as I know it has not been acknowledged.
I’ve upgraded over 100 x RB133C and RB133C3’s to v3.x all running as wireless CPE’s, if you don’t touch the units (ie. log into them via console, ssh, or winbox) they operate for the most part OK at just passing traffic. BUT if you ever try to login to them its a disaster, 100% CPU usage, doesn’t respond lockups/reboots etc.
None of these issues occur if you run v2.9.51
I’ve recently upgraded about 20 to v3.9 with the v2.14 firmware, and they are working better, though still not as good as the v2.9.51 operates. Of note is that I find the boards operate better after the firmware upgrade and not the v3.9 upgrade.
shouldnt be a problem. Im running one as an AP Sr2 2.4ghz with 8602+ backhaul 5.8ghz. also with user-manager on it sending out bills to my clients. No problems… Also running 3.0rc 7 no problems… love this board but going to be upgrading to an Rb433 soon.. -Jordan
I’ve noticed that the configuration files between the two versions seem to be the problem. If I upgrade a 2.9.XX to 3.X I need to do a system-reset and reconfigure it manually then CPU goes to a more normal level but still seems to be high.
This is a common problem, and as far as I know it has not been acknowledged.
I’ve upgraded over 100 x RB133C and RB133C3’s to v3.x all running as wireless CPE’s, if you don’t touch the units (ie. log into them via console, ssh, or winbox) they operate for the most part OK at just passing traffic. BUT if you ever try to login to them its a disaster, 100% CPU usage, doesn’t respond lockups/reboots etc.
None of these issues occur if you run v2.9.51
I’ve recently upgraded about 20 to v3.9 with the v2.14 firmware, and they are working better, though still not as good as the v2.9.51 operates. Of note is that I find the boards operate better after the firmware upgrade and not the v3.9 upgrade.
Cheers
Should I downgrade? We have several routerboards in our system and only the 133C has problems with version 3.x. The rest are OK.
Dont not even attempt to do an upgrade. better operate the unit with its OS 2.9.X.X but not 3.X at all. It cannot handle this OS it is like having Vista on a P11 machine, it hardly works if it does work.
George Midia