We have a few point to point links.
RB411’s
they were running 3.20 with a superchannel licence.
After upgrade to 4.0 wlan was Disabled and all (wlan) settings were overwritten.
This happened on a total of 4 radios.
we also had another set of wireless N links updated from 4.0RC1 to 4.0 and they kept the wlan enabled and worked fine.
Do we need to upgrade to 3.30 first? then 4.0 to assure all settings are kept?
I had one AP that did that upgrading from 3.22 to 3.30.
Wireless package was disabled.
Well, with us, The package was enabled. but all the settings were overwritten and the interface was disabled on both sides. Good thing we had a route to the other side, or it would have been a late night drive.
similar situation here. It was running my sectors, ethernet connection to my backhaul.
One thing Nick didn’t mention was the fact that 100% of our upgrades from v3 to v4 failed with WAN disabled. Not just 4 out of many - but the only 4 attempted all had this problem so it should be real easy to reproduce.
I’d rather not keep reproducing it myself though cause it takes much more effort to reconfigure all the equipment this way. I prefer it to be seamless. Any ideas…
Scott
Maybe export the WAN configuration and paste it into a script, and add a scheduler job to execute the script on startup (probably with a 20 second delay at the beginning to make sure all hardware is up). Then upgrade - the script should execute after the reboot and re-create the WAN configuration.
Don’t know if that really does work, but it should.
While that may work its not desirable. I want an upgrade to be flawless and boring like the rest of them - I don’t like ROS excitement on my upgrades - surprises either. Thanks for the thought though…
Scott
I recal VERY Clearly a BIG RED SCREEN that popped up when you went to the download page, and it had links in there and a very detailed description of WHAT NOT TO DO!!!
One was anything earlier then I believe 3.25 was not advised. Probably becuase they knew about the issue of the WLAN being disabled. Anyways, I read all of the stuff in the BIG RED warning, after all, its the first time I have seen Mikrotik use this BIG RED WARNING, of course you should read what its about, if not, your WLan was disabled!
Just my half cent..