Community discussions

MikroTik App
 
h1ghrise
just joined
Topic Author
Posts: 19
Joined: Fri Apr 14, 2023 5:05 pm

Update Cap-AC in CAPS mode

Mon May 08, 2023 5:55 pm

Hi Forum,

i'm running a Mikrotik HEX-S and 2 Cap-ACs.
HEX-S is running ROS 7.8.

Both CAP-AC's are running in CAPS mode (All traffic is routed back to Hex-S (Manager Forwarding mode), hence they do not have any L3 configuration.
Now, I would like to upgrade the Firmware of those CAP's, as they are running 6.48 and 6.49 respectively.
How does one do that? Currently they are managed via Romon on L2.
My idea is to switch from Manager Forwarding Mode to Local Forwarding, reconfigure appropriate VLANS and route the traffic through ether1 of the corresponding CAP to the HEX-S.

Thanks in advance :)
 
holvoetn
Forum Guru
Forum Guru
Posts: 5327
Joined: Tue Apr 13, 2021 2:14 am
Location: Belgium

Re: Update Cap-AC in CAPS mode

Mon May 08, 2023 6:13 pm

Simply open winbox on each cap via Hex-Romon and system - packages - check - Download and install, I would think.
No need to make it more complicated. It's only for 2 devices.

Upgrade to which version ?
 
User avatar
mkx
Forum Guru
Forum Guru
Posts: 11383
Joined: Thu Mar 03, 2016 10:23 pm

Re: Update Cap-AC in CAPS mode  [SOLVED]

Mon May 08, 2023 7:18 pm

Another (pretty elegant IMO) possibility, which is there in legacy capsman (I don't know if it exists in capsman2): host necessary package files on capsman device and configure capsman to offer them to CAP devices.

Example:
  1. add some storage to capsman device, an USB stick will do. Get it mounted (for the education purposes I'll assume it'll be mounted under /disk1, in v7 reality it'll be something in line of /usb1-part1 or some such)
  2. create directory (e.g. packages) ... CLI (AFAIK) doesn't offer this possibility, so you have to retort to other ways (FTP connection to ROS device allows running mkdir command). Then copy all necessary package files to that directory. They have to be for architecture of CAP devices. It's safe to copy main package file as well as all of package files from "Extra packages" ZIP archive. CAP will only pick package files it needs for upgrading.
    As far as my experience goes it's safe to mix files for different ROS versions as well as different architectures.
  3. configure capsman, point it to package directory, e.g.
    /caps-man manager
    set package-path=/disk1/packages upgrade-policy=suggest-same-version
    
This will try to upgrade CAP devices to same version as CAPsMAN. To make things trully automagical, you have to make package files for CAP devices available before you upgrade CAPsMAN device itself. In this case ... after CAPsMAN device upgrades, capsman process will make CAP devices to upgrade right after.
The "suggest-same-version" part is there to offer upgrade but allows CAPs with other verdions to work with capsman regardless. The other option ("require-same-version") is way more brutal - if upgrade of CAP doesn't succeed, then CAP is left in void (until manual fix of the problem).

One thing is then missing in the picture above: updating routerboot. To automate this as well, you have to change setting on CAP devices manually (once and forever):
/system routerboard settings set auto-upgrade=yes
or you can manually update it from time to time.

And the problem you currently face: different generation of ROS on CAPsMAN vs. CAP devices. As a precaution I'd manually upgrade one of CAP devices to v7.8 first to verify that it still works fine as CAP after upgrade to v7. If it does, then follow the procedure above and observe the other CAP get upgraded.

@holvoetn: if CAP devices don't have any L3 config (hence management is not possible via IP), then they won't be able to check for upgrades as per your suggestion. The only manual way would be to connect using winbox via MAC and upload package files ... then reboot devices and if all package files are there, device would upgrade at reboot.
 
h1ghrise
just joined
Topic Author
Posts: 19
Joined: Fri Apr 14, 2023 5:05 pm

Re: Update Cap-AC in CAPS mode

Mon May 08, 2023 7:38 pm

Thanks for your suggestions.
As mkx wrote already, unfortunately without IP configuration, I cannot request a package via CapsMan. Update fails on requesting.
I was thinking about downloading the packages and providing them via Capsman. Unfortunately HexS is mmips arch, and CAP ac is arm. So I have to take an extra step and download the packages for the correct arch first, uploading them to the router and offer them to the CAPs. This is surely possible, but I was looking for an easy and convenient way.

I will look into the suggestions - thanks a lot.
 
holvoetn
Forum Guru
Forum Guru
Posts: 5327
Joined: Tue Apr 13, 2021 2:14 am
Location: Belgium

Re: Update Cap-AC in CAPS mode

Mon May 08, 2023 7:52 pm

Ah... wasn't aware of that little roadblock.
My caps always had valid ip config but for upgrading remotely ( via wireguard to SXT as capsman) I always used Romon.

Something new learned. Nice.
 
User avatar
mkx
Forum Guru
Forum Guru
Posts: 11383
Joined: Thu Mar 03, 2016 10:23 pm

Re: Update Cap-AC in CAPS mode

Mon May 08, 2023 9:14 pm

.... I was looking for an easy and convenient way.

Well, if the CAP network is large (e.g. tens of units), then this is convenient (compared to manually upgrade every CAP separately). So it really does depend on viewpoint :wink:

As @holvoetn already noted, running capsman for only two caps doesn't make much sense from management overhead point of view.

Who is online

Users browsing this forum: menyarito, morphema and 51 guests