What is the recommended remote upgrade procedure for routers that are on thetop of towers. I tried our first upgrade tonight on a RB153 from 2.9.28 to 2.9.35. I FTPs the systems and packages to the router and die a reboot. That was the last I heard from it. I had to go to the tower, get a serial cable attaced to find out what the issue was. It couldn’t find the kernel. After doing a netinstall and reinstalling 2.9.35, I got it up and running.
What is the recommended process for an upgrade? We have routers at the top of 40m+ towers without serial cables.
We have had the same issues with RB532.. Now i use upgrade via HTTP, test on local unit first and after that is ok and tests fine, then i use HTTP to upgrade the rest. That has proven stable the last 10-15 versions.. It really should’nt differ from FTP, but i like this way
But doesn’t this mean doing them individually? If it works with one via HTTP is using Winbox auto-upgrade for the rest going to add any snags?
Firebat - to upgrade via HTTP use Webbox to log into the Router, choose ‘upgrade’ from the Menu on the left, upload the npk files to the router and hit the ‘upgrade’ button.
Thanks for the procedure. Can the wame procedure be used with WinBox also? I see the upgrade option there as well. What is the difference between FTPing the files and using the upgrade function in Webbox vs FTPing the files and simply issuing a /system reboot? Is upgrade info displayed?
I uploaded 2.9.37 via FTP to a RB112 and everything worked fine but when I try to FTP the identical routeros-rb500-2.9.37.npk file to a RB532 only the first 32.1kbytes gets transferred and then the FTP process stalls. I have also tried with Webbox and again only a small portion of the file gets transferred. Upgrading via FTP has always worked on this RB532 unit until now.
Problem is located only at this particular board, probably you have some firewall rules, that might drop FTP traffic. Check that drive has enough space to place the packages. There are not any problems with upgrade.
There were no problems with space. It turns out that replacing the 10Mbit hub with a 10/100 switch fixes this issue. Putting the 10Mbit hub back again reproduces the problem. When FTP’ing the file there appeared to be a lot of collisions on the hub but with the 10/100 switch everything works fine. Note that this only happens with the RB532 and the RB112 does not have this problem at all.
