What do you wish to compare? The delivered example is exactly the idea from the documentation for AC. So, the AX and AC configuration for CAP and CAPsMAN is “the same”.
When provisioning, you can (and I’m recommending) check whether you have the CAP AC or AX.
Below you have examples
For CAPsMAN:
/interface wifi provisioning
add action=create-enabled comment=2G disabled=no master-configuration=cfg_lab_main_22 name-format=ax_2G_%I slave-configurations=cfg_lab_iot_33,cfg_lab_guest_44 supported-bands=2ghz-ax identity-regexp=CapAX.*
add action=create-enabled comment=5G disabled=no master-configuration=cfg_lab_main_22 name-format=ax_5G_%I slave-configurations=cfg_lab_iot_33,cfg_lab_guest_44 supported-bands=5ghz-ax identity-regexp=CapAX.*
add action=create-enabled comment=2G disabled=no master-configuration=cfg_lab_main_22 name-format=ac_2G_%I slave-configurations=cfg_lab_iot_33,cfg_lab_guest_44 supported-bands=2ghz-ac identity-regexp=CapAX.*
add action=create-enabled comment=5G disabled=no master-configuration=cfg_lab_main_22 name-format=ac_5G_%I slave-configurations=cfg_lab_iot_33,cfg_lab_guest_44 supported-bands=5ghz-ac identity-regexp=CapAC.*
On CAP AX
/system identity set name=CapAX-lab
On CAP AC
/system identity set name=CapAC-lab
The most important stuff to understand:
- On CAP, you have to create the virtual interfaces with “strict“ MAC
- It is important to order the virtual interfaces as they are “bound “ to VLAN_ID and to provisioning order on CAPsMAN
- On CAPsMAN, “action=create-enabled” is used to avoid recreating Wi-Fi devices.
Still a problem? Mkx perfectly shows that the CAP AX configuration creates dynamic objects, which you don’t find in mine.