I need to replace few rb3011 with newer ccr2004
Few 3011 are running Capsman in industrial/hotel environment with wAP-ac
Honestly I never dealt with capsman in V7
How Is capsman managed in ros V7 ?
Is there any guideline ?
What should I expect in performance/management of whole system ?
Thank you
Check the documentation:
When you install the wireless package on the CCR2004, you can transfer your current config to the new MikroTik. Everything is equal to current config.
If the wAP-ac's contain ARM pricessor, you could consider upgrading to the wifi-qcom-ac driver. More info can be found here on the forum (and on the documentation page):
Do you mean once "wireless" package is installed on V7 "non-wifi-HW-equipped" machine (like a CCR) , CapsMan is identical to V6 version ?
What's the difference/improvement in WiFi Capsman ?
Yes
It's also in the documentation. Higher performance, WPA3 and 802.11 r/k/v support.
But be aware that it requires some additional settings, especially with VLAN it can be a bit complex.
It's not yet clear to me....
If an environment is mixed with old legacy and new wifi HARDWARE access points (both running V7), one must install wireless package into Manager device and run both Capsman (wireless and WiFi) ?
legacy wireless needs old Capsman. Modern wireless needs new Capsman. Easy as that.
With the exception of "legacy" arm device...they support the newer wifi-qcom-ac driver.
@OKNET can you provide exact MikroTik hardware involved? This information is necessary to provide complete advice.
But be aware that it requires some additional settings, especially with VLAN it can be a bit complex.
Now I understand the confusion, this remark was in regards to the arm legacy devices.
Clear, I thought the native V7 wifi capsman could manage old mips devices, so I need wireless package to be installed.
A V7 CCR2004 running wireless Capsman can still manage V6 mipsbe device ? or is it advisable to upgrade them to V7 too ? (old wap-ac RBwAPG-5HacT2HnD)
You need to use the wireless Capsman package. It is not necessary to update devices to v7, but it is desirable to update to the latest v6.
Wireless package is indeed required for the old CAPsMAN. When installed, the CCR2004 can manage wireless-package devices (like mips), both on V6 and V7.
Upgrading to V7 won't provide any benefits...but it depends. What does your upgrade strategy for devices look like? Assuming LTS, both V6 and V7 are available.
I usually keep all devices update to latest version, the actual V6 Capsman upgrade policy is "require same version".
If I decide to keep this policy on new CCR , APs will have to be V7...
IMO the old devices (and I'd say anything non-arm falls into this category) don't benefit much by running ROSv7 compared to running ROSv6 (with exception of CCR line where a few newer functionalities of v7 on non-arm platforms make sense). OTOH ROSv6 is a bit leaner so those devices mostly perform equally or even slightly better when running v6.
Meaning that if you have to run ROS v7 on CAPsMAN device due to other reasons, it is perfectly fine to run CAP devices with ROS v6. What you loose is ability to upgrade CAP devices automatically right after upgrading CAPsMAN device. But then, ROS v6 seems to be stuck at 6.49.19 and is unlikely to get any update any more ... so inability to automatically upgrade all CAP devices is not a big issue any more.
Running CAPsMAN on v7 does, however, offer possibility of gradually upgrading your WiFi network to newer technologies (AC, AX, BE) and still have CAPsMAN (for those devices) running on the same device. Settings are completely separate though, but as far as mobility goes, mobility between CAPs managed by different CAPsMAN entities is as good as mobility between CAPs managed by "wireless" CAPsMAN (i.e. no actual mobility exists).
Ok, not so big headache then, just load wireless pkg into new CCR and transfer the Capsman current config leaving APs as they are, maybe a script would take care of V6 APs update.
Thank you all.