That does not sound normal to me, so you say, when you buy a unit with v6.1, that means, they've upgraded the unit 3+ times just to achieve a smooth transition.Upgrade slowly...
Go to 5.26, then upgrade firmware.
Then try to go to like an earlier version of 6, upgrade firmware again.
Then try 6.5, and upgrade firmware. Then restart...
That might make it a smoother transition....
hectic man, I've upgraded from v5.23 to V6rc13, because 5 made my router reboot all the time at random times every day, so the mikroitk support told me, 6 is more stable on a device with multicores, so it got more stable, but I've noticed that the uptime never goes higher then 6+ days and then 1 day I were sitting next to it, and in winbox and then boom, it rebooted by itself, so I installed v6.5 ...and then all nightmares broke loose, the device were so screwup that if you click on reboot, it takes 30sec before it reboots, and the fan says 30rpm and is not working ofcourseuse netinstall to upgrade/install newest firmware (in the package, downgrade firmware to the one included in your package) and ros.
I have no problems (after 6.5 or 5.25) with 1100, and have about 50 in production. However, upgrade from 5.x to 6.x on a unit having config, might "broke" the router. Syntax is a bit different, and some settings might give you strange behaviour. To remove this, do the netinstall. In my opinion, the 5.x is more stable than 6.x, and if you don't need any of the features in 6.x, use 5.x
The gradual upgrade, might reduce the risc of config issues, but the best way is still to "start on a blank net installed router"
Hmm.. I've got 1x 1100AHx2, and wont mind to fix this asap... not sure if I have to netinstall a older version, but the new versions is supposed to work anyway... so there is a problem herehave both device with same ROS version and firmware version - in this case, the problems minimalised.
However, we are backing up "/export compact" instead of configuration backup.
that is human readable and if some problem accours, you will be warned immediately and you can fix it.
No worse thing can happen, than a primery device gone bad, and the backup device is incompatible in config - and you are in a hurry...
I don't understand why there's always!! issue's with new versions of ros with the existing/old features, it tends to get broken, and I've been moaning about this almost forever.. I'm not impressed @mikroitk, don't they test the stuff before releasing updates... dammmmmmImporting certificates is a known problem in 6.5. It is fixed in 6.6 (released soon, look around for links to the beta)
I've upgraded a RB750 to I think v6.5. and thought ok awesome.. lets "export file=blabal"Ehman: as you may read on the forum, importing backup sometimes not working (or producing problems) while configuration after clean install works well. (and this is equivalent of importing export-file from the same ROS version)
#error exporting /mpls ldp #interrupted
I dont have a mikrotik account, I buy my stuff from my local distributor. .. I always send my supout files to firstname.lastname@example.org like in the case of my 1100Ehman, this could be caused by specific configuration, it export fine on our "demo routers". Do you have a supout.rif file from this device? If yes, you can also get the config from there, check your mikrotik.com account, it has a "supout.rif reader"
The RB750: I dont even use /mpls ldp, but it stopped on that line... ...I dont think there's a supout file, and I were not aware of the problem, until I cleaned the device and reloaded the config due to some nat issueEhman, this could be caused by specific configuration
I thought about doing a netinstall on the 1100, with V6.0rc13For stability use 5.26 and upgrade to v6 once its mature. We run 5.25 and 5.26 on all of our 1100's with no issue. v6 is getting there but not something I would put into production for anything other then basic router and AP functions. but thats just my 2 cents. I would have to be very confident from test before I would pull the trigger and unleash v6 on 1000+ routers.