I have a small setup at home which includes RB5009 acting as a router and a CAPsMAN controller and three AX2s acting as CAPs. RB5009 and CAPs connected to Netgear M4300 switch.
Prior to 7.13 my update procedure looked like this:
1. I uploaded ROS *npk and wifiwave2 update files to RB5009 and made a reboot, then updated RouterBoard and rebooted again.
2. CAPs saw update files and updated themselves automatically.
3. I had to log into each CAP to update their RouterBoards and reboot them manually.
After these steps all components became updated to the same version of RouterOS itself and wifiwave2 package.
Now 7.13 came with completely different structure. I went to System-Packages on RB5009 and initiated downloading and update to 7.13. I thought that way transition will be smooth as the manufacture knows well how to manage its own equipment. However after I did this I lost any wi-fi connection. To solve the issue I took the following steps:
1. Connected to RB5009 via Ethernet and found RouterOS updated to 7.13, no additional packages and RouterBoard that needed update. No surprises so far.
2. Updated RouterBoard and rebooted. Everything went OK here.
After updating I couldn’t neither ping nor log into any CAP. So I went on and did the following:
3. Uploaded QCOM package to RB5009 and rebooted. Package was successfully installed.
Nothing has changed. CAPs remained unreachable. So I:
4. Connected CAPs directly to RB5009 one at a time. This way I was able to find them in Winbox.
5. Logged into each CAP and found two installed packages: RouterOS and QCOM.
6. So I updated RouterBoard of each CAP and rebooted them.
7. Connected all CAPs back to the switch.
8. Removed QCOM package from RB5009 as unnecessary.
After all these steps my config became functional again with up to date packages on all devices.
After all these unexpected hassle several questions remained:
1. Why CAPs became unaccessible after RB5009 update?
2. What’s the right updating procedure? Shouldn’t I use automatic update if I have CAPsMAN-based config?
3. How can I force automatic updates for my CAPs the way it used to be prior to 7.13? Should I install both RouterOS AND (unnecessary on RB5009) QCOM updates on the controller so the CAPs are fully updated and then remove QCOM package from RB5009?
4. If I follow the steps described in (3), how can I be sure that my wi-fi network won’t go down again? It’s rather difficult for me to connect and reconnect devices manually every time I upgrade.
What’s your experience with update to 7.13?
Prior to 7.13 my update procedure looked like this:
1. I uploaded ROS *npk and wifiwave2 update files to RB5009 and made a reboot, then updated RouterBoard and rebooted again.
2. CAPs saw update files and updated themselves automatically.
3. I had to log into each CAP to update their RouterBoards and reboot them manually.
After these steps all components became updated to the same version of RouterOS itself and wifiwave2 package.
Now 7.13 came with completely different structure. I went to System-Packages on RB5009 and initiated downloading and update to 7.13. I thought that way transition will be smooth as the manufacture knows well how to manage its own equipment. However after I did this I lost any wi-fi connection. To solve the issue I took the following steps:
1. Connected to RB5009 via Ethernet and found RouterOS updated to 7.13, no additional packages and RouterBoard that needed update. No surprises so far.
2. Updated RouterBoard and rebooted. Everything went OK here.
After updating I couldn’t neither ping nor log into any CAP. So I went on and did the following:
3. Uploaded QCOM package to RB5009 and rebooted. Package was successfully installed.
Nothing has changed. CAPs remained unreachable. So I:
4. Connected CAPs directly to RB5009 one at a time. This way I was able to find them in Winbox.
5. Logged into each CAP and found two installed packages: RouterOS and QCOM.
6. So I updated RouterBoard of each CAP and rebooted them.
7. Connected all CAPs back to the switch.
8. Removed QCOM package from RB5009 as unnecessary.
After all these steps my config became functional again with up to date packages on all devices.
After all these unexpected hassle several questions remained:
1. Why CAPs became unaccessible after RB5009 update?
2. What’s the right updating procedure? Shouldn’t I use automatic update if I have CAPsMAN-based config?
3. How can I force automatic updates for my CAPs the way it used to be prior to 7.13? Should I install both RouterOS AND (unnecessary on RB5009) QCOM updates on the controller so the CAPs are fully updated and then remove QCOM package from RB5009?
4. If I follow the steps described in (3), how can I be sure that my wi-fi network won’t go down again? It’s rather difficult for me to connect and reconnect devices manually every time I upgrade.
What’s your experience with update to 7.13?
Statistics: Posted by aspen63 — Mon Jan 01, 2024 5:46 pm