Sun Apr 07, 2024 10:05 pm
It looks like Mikrotik ROS might have a bug. I am not sure completely but this was resolved by changing the provisioning from "create-dynamic-enabled" to "create-enabled" (Thanks Sindy!)
/caps-man provisioning
add action=create-dynamic-enabled hw-supported-modes=b,g,gn master-configuration=SFSCS-2G slave-configurations=\
FAFC-2G,FAFC-Guests-2G,SFSCS_Staff-2G
add action=create-dynamic-enabled hw-supported-modes=a,an,ac master-configuration=SFSCS-5G slave-configurations=\
FAFC-5G,FAFC-Guests-5G,SFSCS_Staff-5G
/caps-man provisioning
add action=create-enabled hw-supported-modes=b,g,gn master-configuration=SFSCS-2G name-format=prefix-identity slave-configurations=\
FAFC-2G,FAFC-Guests-2G,SFSCS_Staff-2G
add action=create-enabled hw-supported-modes=a,ac,an master-configuration=SFSCS-5G name-format=prefix-identity slave-configurations=\
FAFC-5G,FAFC-Guests-5G,SFSCS_Staff-5G
ALL AP's were offline but could speak to the CapsMan but would not obtain the SSID's. Once changed to "create-enabled" they all came right back up.
Last edited by
jerryroy1 on Mon Apr 08, 2024 6:25 pm, edited 1 time in total.