16, but RF spectrum wastage starts to increase a lot after 4 (not a Meraki issue, just the way WiFi works). So good practice recommends you don't create more than 4.
The default screen shows four SSIDs. If you need another just configure it up.
But we have a requirement to create 18 WLAN for the organization. They are requested to create SSIDs base on the 18 no's department. Can I go ahead with Meraki or what is your suggestion?
>But we have a requirement to create 18 WLAN for the organization.
Assuming this is for internal users ...
Are you saying you want an AP to advertise 18 SSIDs? The performance will be terrible - regardless of vendor. Check out this article on the huge overhead that will create.
You would be better to create a single SSID using RADIUS and then drop the users into different VLANs or apply different group policies.
Having one AP broadcasting 18 SSIDs at the same time is a bad design, leading to low performance.
No vendor will recommend this kind of deployment.
Only one SSID will broadcast in each division and we have 18 divisions with 18 SSID. We do VLAN tagging for each AP and then AP will issue the IPs from the relevant division subnet pool.
That makes more sense.
Since the dashboard doesn't allow for more than 15 SSIDs, you would then need to create more then one dashboard networks.
Depending on your case, you could go for one network per division or get more creative with the SSID availability feature and assign SSIDs to APs using AP tags.
The best solution however as mentioned above, would be a single SSID with Radius policies.
we have a requirement to create 18 WLAN for the organization. They are requested to create SSIDs base on the 18 no's department. Can I go ahead with Meraki or what is your suggestion?
Having to have 18 different physical Wireless LANs is a sign that the underlying logical WLAN/VLAN schema is insufficiently refined/faulty.