We have a lot of different RB’s (age, type) with various versions 2.9.x. Before v3, we were normally upgrading as soon as this forum indicated that there were no major problems. With V3, it is another situation.
Many upgrade attempts from 2.9.x to 3.x has resulted in broken links, climbing, unbootable boards etc. Generally very unpredictable…
We have found one way to succeed every time. It is a little more complicated than normally, but it works 100 %. The requirement is a connection to ether1 on the board to be upgraded - either indirectly from a neighbor in the same tower, or directly with a pc at the end of the cable. The required steps are: 1) Reboot the RB, 2) make a backup and copy it to your pc, 3) make a “system reset”, 4) copy the new firmware to the board, boot and make a “sys rou upg” and boot again, 5) Restore the backup.
Our conclusion is, that v3 is not always able to make the conversion of the custom setup from v2 on-the-fly. Luckily, the back-up/restore works well !
We can’t see any pattern. The problems has been with many RB532 of different age and hardware version. However, it seems to be worse with a more complicated set of firewall and mangle rules. All units are with wireless interfaces (a mix of mt-cards and various ubnt cards in g/a/a-turbo).
But my point is: Backup/restore works and the upgrade conversion fails ! You can only be sure to succeed an upgrade, when a routerboard is in the factory default state.
Well, a CPE setup is not exactly our typical setup. It is very close to a factory default.
We are using MT for infrastructure only. I would like to hear from experienced users with installations beyond “vanilla” setups, using wds, nstreme, bonding, firewall, nat, multiple ip, routing, dns-cache, multiple wireless interfaces etc etc..
I simply don’t believe, that we are the only ones with these problems.
