MikroTik

Hi,
I have upgraded all our MT 433,600 to 3.25 about week ago.
Because it is about 290 devices I have used perl telnet to command
them to download new os from my ftp and synchrionised to reboot at one time.
On ftp I had only routeros-****3.25.npk common package build on jun/15/2009 10:07:37.
After rebooting 4 of 293 didn't load some modules like wireless or dhcp and
I had toupgrade manually again and load backup.
I have also set in scheduler to reboot with interval 3days - ant it was dramatic decision.
Yesterday I saw a horror All my Dude was RED.
About 40 devices lose their settings excluding some settings like System Name, Ip addresses.
They have 3.10 or 3.18 before. Some have losed only their gateways or had very old ip address
which was used 3 months ago. I thought 3.25 it is stable.
I am writing it to warn other admins.

warn about what exactly? this is not normal and doesn't happen. maybe you did something wrong, quite possible that your script didn't transfer the complete package, maybe transfer was broken. this kind of thing shouldn't be done without care, you need to do planning and use appropriate methods.

As I wrote.
Upgrade - can happend bad upgrade - OK..
But :
Every 3days mikrotik reboots at 2.30 am. What should I do wrong ?

/system reboot
Its normally loses settings. - Something is wrong and I want to see if
other mt users have the same problem with 3.25.

if it's exactly at that time, you should check configuration if it's not scheduled to do so, of if you have any hardware/electricity issues.

if it loses config on reboot, this is completely abnormal and you should inspect hardware. it is so on all devices or only on some? compare them and see what's different.

I'm sorry for pure english.
I set in schedule of every mt to restart at 2.30 every 3days.

After upgrading to 3.25 devices started to lose configuration
on this planned reboots.
I sent supout.rif to support

Hello!

I am sorry to inform you Normis, but I can confirm what ema told you! The RouterBoards with ROS 3.25 are - sometimes - losing configurations after reboots, or power failures.
I upgraded 5 RBs when ROS3.25 was released> RB133C (previous ROS: 3.13), RB532(previous ROS: 3.24), RB333(previous ROS: 3.15) and two RB600s (both were running ROS3.22)
The first three (133C, 532 and 333) lost their wireless cards configurations immediately after the 3.25 upgrade's reboot cycle. They were reset to their defaults, grayed out, and with default names (wlan1,... etc.) The 532 was acting as a small router for a company and it lost its pppoe client settings too. The pppoe-out1 interface simply vanished!
The RB600s are doing just fine. As I stopped the upgrade for other RBs, I can not say whether other RB600s are experiencing the same problems, or not. Maybe I was just lucky with these two...
I have never experienced a behavior like this with previous ROS releases! Every RB with ROS 3.24 is running fine, and never lost any settings!

I had the same problem with another ROS version. When I just included the system.npk package then rebooted, no other package got upgraded. But when i FTP'd every .npk file of the new system; then rebooted, all the old packages got upgraded and all my settings were in-tact (as far as I could tell). So I think if you just match current packages with newer ones when you FTP, I think that might work.

Let me know if this helps,

i have too this problem over 100 cpe ten have lost config

Bye Fr4

We have had the same issue on two of our routers as well. 1 411AH and an X86 router. It happened a day after upgrading to 3.25.

On the 411AH it disabled the discovery protocol on all the interfaces and the IP address detached itself from the interface it was assigned to. Good thing that it was accessible through the serial port.

On the X86 router, we lost our user-manager configuration.

We have a total of 6 routers that we upgraded to 3.25. All of these routers are brand new and not in service as of yet. We are going to create supouts on these routers and downgrade to 3.22 and wait for more feed back.

I just did an upgrade from 3.24 to 3.25 using my above mentioned post and everything went flawless. I even added a second drive and was able to copy the user-manager settings from the main drive to the second drive. It's not enough to just copy system.npk over. You have to copy every single .npk package over that you want upgraded. The packages that are not copied over will not show up because all packages have to be the same version (except dude).

Hope this makes sense,

I just did an upgrade from 3.24 to 3.25 using my above mentioned post and everything went flawless. I even added a second drive and was able to copy the user-manager settings from the main drive to the second drive. It's not enough to just copy system.npk over. You have to copy every single .npk package over that you want upgraded. The packages that are not copied over will not show up because all packages have to be the same version (except dude).

Hope this makes sense,

This is exactly what we did and after 24 hours the user-manager settings got wiped and went to default and on the RB411AH, the IP address got disconnected from the interface as well as all discovery interfaces getting turned off.

I had this problem

After upgrade wireless and ppp set to default settings.

wireless was disabled, ppp client was removed

Strange... I'm using x86 if that helps (probably not though). All the settings should just be stored as settings, read in each time router boots up I'd think, unless a package specifically resets certain settings when it installs. Maybe a difference btw x86 and routerboard packages?

Mine was a routerboard 133

i have other 433 and 133, and 411 that have lost configuration, please resolve this issue, in two days we have go to twentytree customers and two ap for reconfigure hardware

this problem occur over reboot or only over upgrade ? I not know if is better downgrade OS or if i can left 3.25.

I kown only that is better NOT INSTALL 3.25 and i think that 3.25 MUST BE REMOVED to download area

Regards
FR4

I have also mensioned problem with 3.25 verison, I have upgraded about 50 routers to newest version (3.25), the upgrade was successful, but what happened after that was a disaster. After storms with power failures about 5 RouterBoards have their wireless configuration in default and alse their simple queue was corrupted ! During another week about next 5 routers were in the same situatian and it was very disgusting to go to each one and configure it !

Please fix the problem and REMOVE version from stable release list !!!

Thank you for your help and let everyone consider this post like a warning agains upgrading to 3.25.

marxin

Same with me, upgrade went fine but after hard power cycle lost wireless and ppp config

i found this problem also but this is what i found



i upgraded from 3.17 to 3.25


upgraded over 30 boards then rebooted them

no problems at all with 3.25

but 2 days later i did
/system routerboard upgrade
/system reboot


then out of the 30 boards 25 lost configeration

after this i went to my boards and looked to see what was the problem and for some reason it didnt see ether1 all my settings that were set on ether1 were unknow

after system reset config all was fine


so i think its a small bug that need to get fixed up as i would not like to do a system reset on 290 routerboards

Please, anyone who is able to reproduce the problem or at least send us support output file from the previous version, which was upgraded to 3.25 (which packages were used for upgrade ?) and configuration was lost.
Typical AP/station/anything is not enough, we need the exact configuration, which was used on router before.

Send support output file or export file (rsc) to support@mikrotik.com
Thank you for the cooperation.

xezen it would be nice to have some precise information about this problem in form of:
what routerboard type,
what RouterBOOT version before upgrade
what Routeros version before upgrade

what corresponding version after upgrade

i have problem in RB133, RB433 and RB411
i have installed from 3.20, 3.22, 3.24 to 3.25
i have lost in some routers ethernet, bridge, wireless, mpls, dns server, pppoe client configs, in some routers i have lost also scheduler configs

Regards FR4

P.s. in all cpe i use wireless-test package in 433 i use routing-test, wireless-test and mpls-test

We have noticed the same, partial config simply vanished. Not immediately after upgrading to 3.25, but eventually rebooting in few days after that upgrade procedure. We didn't noticed any config missing twice yet, after RE-configuring that device seems it keep its config so far. We was investigating, but now reading this thread seems that 3.25 is quiet a quest for new adventures on ROS.

Its still marked as Stable on the download page

Please notify the version 3.25 as unstable, it will save quiet a lot of people their time and mainly nerves !

As I mensioned, I updated about 50 routers, 4x RB 133 became erased after rebooting caused by power shutdown, onetime RB600, 2x RB 112 + RB 133 after downgrading from 3.25 back to 3.13, which I think is stable.

Thanks, marxin

Please notify the version 3.25 as unstable, it will save quiet a lot of people their time and mainly nerves !

As I mensioned, I updated about 50 routers, 4x RB 133 became erased after rebooting caused by power shutdown, onetime RB600, 2x RB 112 + RB 133 after downgrading from 3.25 back to 3.13, which I think is stable.

Thanks, marxin

BACK TO THE START

Please notify the version 3.25 as unstable, it will save quiet a lot of people their time and mainly nerves !

As I mensioned, I updated about 50 routers, 4x RB 133 became erased after rebooting caused by power shutdown, onetime RB600, 2x RB 112 + RB 133 after downgrading from 3.25 back to 3.13, which I think is stable.

Thanks, marxin

Have you sent supout.rif and detailed information to MiktoTik support? If not - do not expect problem resolving!

OK, so that's my problem that I haven't known about supout.rif, please tell me, does it have sence to send tu support suppouts from RB that have erased their configuration and were manually configured back to their original configuration ?

Is history of changes saved in this file and is it helpfull for Mikrotik support?

marxin

i have to send about 50 supout support ? it have sense if is a isolate problem !!!!!!!!
mikrotik staff can't upgrade five routerboard for his self and reproduce the problem ? it'is not hard to replicate....

please , remove 3.25 from stable download, and do a announcement in newsletter for alert user to not upgrade...

Bye Fr4

P.s. sorry for my bad, bad english

I can assure you, Mikrotik support spent the last days experimenting with upgrades on a multitude of routers, failing to reproduce this. there is something in your routers that we can't repeat. please send those files!

ok, i have some other cpe misconfigurated, i told to my techs to make supout.rif before to recofingure this hardware, i hope that mikrotik staff can resolve this issue.

3.25 is a stupid joke.

RB433AH
The bonding interface lost after reboot, and get back after next reboot, and lost after 3rd reboot, and get back after next reboot....

No supout files

I can assure you, Mikrotik support spent the last days experimenting with upgrades on a multitude of routers, failing to reproduce this. there is something in your routers that we can't repeat. please send those files!

Hey normis!

Don't you see millions of bugreport????

"there is something in your routers"
It means: all routerboard is bad, all administrator is idiot, 3.25 is very good.

normis, tell the truth: 3.25 based on windows

no, in Support I don't see ANY bugreports seriously. we need those supout.rif files

RB433AH
The bonding interface lost after reboot, and get back after next reboot, and lost after 3rd reboot, and get back after next reboot....

This problem is fixed.

RB433AH
The bonding interface lost after reboot, and get back after next reboot, and lost after 3rd reboot, and get back after next reboot....

This problem is fixed.

How can I get?
In download section I don't see new version.

New version is not released yet. I am just informing you that we managed to fix this problem.

so it is fixed now when can we expect to be able to download the new version that has the fix for it as i still have 50 odd boards to upgrade
2 weeks 3 weeks any ideas?

to make it clear, this is fixed:

The bonding interface lost after reboot,

the other problems are not yet fixed, please send supout.rif files!

New version is not released yet. I am just informing you that we managed to fix this problem.

Thank you!

i have send a supout file

Bye Fr4

What changed in 3.25 I mean exactly changed / packages upgraded? This may helps users to help everyone and Mikrotik solve the problem faster maybe?

For ex. ntp-3.24 and ntp-3.25 might be the same exact code, but another package might have been changed in the upgrade.

warn about what exactly? this is not normal and doesn't happen.

Woah there. Given the number of people experiencing this problem, that comment is way out of order.

I can confirm that with a RB450 I have exactly the same problem - I configured it up, put it in the post to a customer and when it got there it had lost its configuration. Luckily they gave me remote access to a box there I could configure it from - if they hadn't, it would have meant a 300KM round trip and I really would not be happy about that.

we still have not received any supout.rif files to support. seriously guys, this looks like a joke. if there is ANYONE with this problem, PLEASE contact support!

You are asking for files before it fails
its hard to know when one will fail.

AFTER it fails is good too!

Ok, I will do a after fail one now

we have found the cause of this issue, and currently I can offer the following:

1. If you have upgraded to v3.25 and you have a RouterBOARD 500, 100, 300 or sometimes another model, do NOT get the new format license until you have rebooted 1-2 times to see if the config is not lost. Otherwise also the license could get lost.

2. Wait until v3.26 where we will fix it, and upgrade only to that version. Don't use v3.25 for now.

The problem is related to how new RouterOS handles NAND, and it will be fixed soon. v3.25 is retracted from the web for now, although it only affects certain RouterBOARD models

Wait until v3.26 where we will fix it, and upgrade only to that version. Don't use v3.25 for now

Ok but don't you think it would be better to remove 3.25 from stable releases on download page?
It is still there

read again

What should I do?
I have 3.25 on 323 devices. I have backup of it on every mt and on my server.
Not every device have new 8-alphanumeric software-id.
Should I downgrade or just pray? They work good since 10 day.
I can command them to get 3.24 ... what is less risky ?

if you ALREADY have 3.25 then there is no problem. the problem only happens during the upgrade

too much effort now will be done to achieve the reputation among users and providers.
otherwise MikroTik - > NekroTik.

how to downgrade to 3.24 without losing configuration?

the problem only happens during the upgrade

Or some time after the upgrade depending on when it's power-cycled.

Or some time after the upgrade depending on when it's power-cycled.

Yes Nick, confirmed. We lost 3 routerboards today. They were working well for 21 days, but today after being restarted for bios update the configuration was completely lost. It was necessary to reach all the sites (some very distant) to reconfigure. Much time wasted, besides the inconvenience to customers.

It sounds like it's still stable only for x86 though not RouterBoards.

how to downgrade to 3.24 without losing configuration?

anyone help please my box running like abnormal iwant to downgrade to 3.24

thought i'd let you know...

we upgraded our main server and high-point to 3.25 and all seemed well for about a week, however our clients all complained about speed issues, and although all clients seemed to be connecting ok there was definitely something wrong - pages hung, ping's DNS resolved but won't actually ping, uploads to mikrotik equipment was painfully slow, speeds varied dramatically (almost as though there were bottlenecks on the system), pppoe dialups would all disconnect occasionally, etc., etc.

we subsequently downgraded to 3.24 and it seems to be resolved.

P.S. and during the downgrade we lost the config on our HP...

hmmmmmm

how to downgrade to 3.24 without losing configuration?

anyone help please my box running like abnormal iwant to downgrade to 3.24

Just make a backup, then do an export to file
Then upload 3.24 and do a downgrade.

thanks it works im now happy with my 3.24

cheers!!!

Hi ...

Should I expect this lost config behaviour after some power cycles at 3.25 fresh installs too? Few WRAPs as APs + 1 X86 machine running it on a vy small net, simple config, but did not lost config - yet - few power outages anyway.

Regards;

weird that you say that i also had that from clients saying the same thing

it does NOT happen on non-routerboard devices, because the problem is with the NAND driver

im running on a 433ah


i was sysing that my clients sed the same i havnt got a x86 system running yet!

sould i downgrade to 2.24?

sould i downgrade to 2.24?

v3.24 you mean. it depends - if you have rebooted your v3.25 routerboard and nothing bad happened - you are fine.

Straightforward question: when will be available bugfixed version?

tomorrow hopefully

how to downgrade to 3.24 without losing configuration?

anyone help please my box running like abnormal iwant to downgrade to 3.24

Just make a backup, then do an export to file
Then upload 3.24 and do a downgrade.

[vaden@EP-AP1] > /system backup

Console has crashed; please log in again.

Same result for /system export filename

Will a downgrade alone solve the problem?

I can't downgrade from 3.25 to 3.13.. this don't work with package downgrade and don't work with netinstall trying to save the configuracion...

I downgraded to 3.24 using netinstall and keeping my old configuration. It seams ok. Downgrade to 3.13 fails because of different filesystem.

They removed 3.25 from the download page

They removed 3.25 from the download page

good morning to you too read the previous page of this thread

How did u notice i just woke up?

How did u notice i just woke up?

because you act surprised on an event that was discussed yesterday

Good point! Anyway i don't have any issue with 3.25.
Mostly because i didn't upgrade the license..

we have found the cause of this issue, and currently I can offer the following:

1. If you have upgraded to v3.25 and you have a RouterBOARD 500, 100, 300 or sometimes another model, do NOT get the new format license until you have rebooted 1-2 times to see if the config is not lost. Otherwise also the license could get lost.

2. Wait until v3.26 where we will fix it, and upgrade only to that version. Don't use v3.25 for now.

The problem is related to how new RouterOS handles NAND, and it will be fixed soon. v3.25 is retracted from the web for now, although it only affects certain RouterBOARD models

...and good morning everyone

Isn't a good morning for me.. I spend 3 days in a RB450G configuration as a proxy+load balancing+hotspot and I can't make the f*** load balancing to work. xD

moral is...
Upgrade to current -1 version. It should be stable. And visit forum for details about it.
Now all of my devices are with v3.24.
And i think you should make stable (ie v3.24 or nevest -1 ), beta (4.0), and "publicaly untestetd" (v3.25 or newest).
After new release, if everything ok for few weeks with newest version, you could put it in stable.

moral is...
Upgrade to current -1 version. It should be stable. And visit forum for details about it.
Now all of my devices are with v3.24.
And i think you should make stable (ie v3.24 or nevest -1 ), beta (4.0), and "publicaly untestetd" (v3.25 or newest).
After new release, if everything ok for few weeks with newest version, you could put it in stable.

This is the way to go with every system you need to rely on.

Additional rules:
Never change a running system
Never change any system before vacation
Kiss (Keep it simple and stupid)

Stefan

Kiss (Keep it simple and stupid)

Stefan

hahaha I make this too xD

Never change any system before vacation

The problem is related to how new RouterOS handles NAND, and it will be fixed soon. v3.25 is retracted from the web for now, although it only affects certain RouterBOARD models

How could such a change not have even made it into the changelog ?

The problem is related to how new RouterOS handles NAND, and it will be fixed soon. v3.25 is retracted from the web for now, although it only affects certain RouterBOARD models

How could such a change not have even made it into the changelog ?

I also would like to see the ChangeLog list any major change, not just features / fixes.

yay, it's horror bug, but I only had 433 and 411, and [thank's god] not all my machine had upgraded to 3.25. I hope 3.26 will coming soon

Additional rules:
Never change a running system
Never change any system before vacation
Kiss (Keep it simple and stupid)

Stefan

100% agree with nod doubt!

tomorrow hopefully

Any update on 3.26 availability?

kind regards/ldv

warn about what exactly? this is not normal and doesn't happen. maybe you did something wrong, quite possible that your script didn't transfer the complete package, maybe transfer was broken. this kind of thing shouldn't be done without care, you need to do planning and use appropriate methods.

I can assure you, Mikrotik support spent the last days experimenting with upgrades on a multitude of routers, failing to reproduce this. there is something in your routers that we can't repeat. please send those files!

v3.25 is retracted from the web for now, although it only affects ....... RouterBOARD 500, 100, 300 or sometimes another model,

The problem is related to how new RouterOS handles NAND, and it will be fixed soon.

First of all it was our fault. Then Mikrotik couldn't reproduce it despite testing on a "multitude of routers". Then, forced to it by overwhelming evidence, they found it but it only affects most of their products.

Now I know why I don't upgrade anything in the field to a version later than five issues before the current one and only then after a close read of all later changelogs. If Mikrotik want me to be a beta tester for them they can take me onto their staff and pay me.

i have too this problem over 100 cpe ten have lost config

Bye Fr4

I have this problem with 133c boards too.

If Mikrotik want me to be a beta tester for them they can take me onto their staff and pay me.

I've emailed and asked, but they refused.

What I can't understand is why things work in previous versions but break in later versions!?
I believe to old saying is "if it isn't broke DON'T FIX IT"

PS. I want my webbox back.. please...?

i not understand... if we lost our configs, if config is stored in nand, and if mikrotik have change nand driver in 3.25 ...
Because mikrotik staff have lost several days for locate the problem ?!?!?!?

i not understand... if we lost our configs, if config is stored in nand, and if mikrotik have change nand driver in 3.25 ...
Because mikrotik staff have lost several days for locate the problem ?!?!?!?

my thoughts exactly. if it was a NAND driver issue, it would've been noticed immediately on most any RouterBoard device with minimal testing required.

I love daily backup.
Wiki has good backup scripts.

I had problem with my rb1000 too, when upgrading to 3.25 it lost most of it's config and i haven't seen mikrotik forum and watch this thread since more than two weeks ago when the process started. i only guessed then perhaps it was because the WinBox menu is changed to better organized, all sub-menus are sorted so they missed for translating config from earlier version so didn't notice later warning and only fixed the config manually to adapt for 3.25 to make it up and run till now.

Today i found this thread hope mikrotik would make a smooth upgrading process to 3.26 not only for 3.24 or earlier version but for 3.25 also, because i had set that rb1000 on remote site with 3.25 and hope it will not accidentally power cycled just like those people say in this thread from beginning page.

and for Normis if i may suggest, you should build a qualified pretesting division and an intensive beta tester forum before launching new routeros, because i see that the mikrotik still use open source paradigm which trow anything new to public and see how they react then. I'm only saying this because i think mikrotik is bigger company now and could be one of the key player in routing device in the future. and the last.. Mikrotik Rocks!!

new version - 3.26 is on the web

ummmm.. we can try or our router will make a thermonuclear explosion ?

v3.25 We found this problem the day it was released.

After trial and error we found that if you write a change to your bridge (ports - add or delete) and reboot it - it will NOT loose any more configs.

Took us awhile to solve problem and we reported ASAP to Normis via the forum.

Rod

PS - I was told the same thing - gotta be your install - you screwed up - like I want to do that on a couple hundred 200ft towers with the equipment at the top