@ClaytonMeyer wrote: Nolan is correct but there is more necessary configuration. You'll need to make sure that all of the corresponding AP switch ports are configured as trunk ports. You'll need to trunk/tag VLANs 100-400 on those ports. Lastly, if the AP itself is in a separate "management" VLAN e.g. 2, you'll need to make VLAN 2 the native VLAN on those switch ports. Also, make sure that the uplink ports from those switches are also tagging those VLANs all the way back to wherever the SVI exists. Mode: Trunk Native: 2 (example) Trunk: 100, 200, 300 400 So your clients' traffic will get tagged for their respective SSID and then that traffic will be properly handled at the switch level. @ClaytonMeyer Tried that even before I posted in the community. I can see devices can associate with the SSIDs but DHCP request fails if the DHCP server is on the MX or a Windows Server. DHCP request from the APs are working. Exploring further, Say, at Ground Floor, I have sub_tenant_A and 1st Floor sub_tenant_B. I have 4 APs on 1st Floor and 2 APs on Ground Floor. 4 x SSIDs configure on the APs (tenants and tenants_guests). When an end device is associated with the AP on Ground floor, choosing the SSID for sub_tenant_A works fine but not if choosing SSID for sub_tenant_B while associated in ground floor. Cannot get DHCP IP allocations. Vice versa. Guests SSIDs are fine anywhere. Giving up, I just turn off the SSID for sub_tenant_A for the APS in 1st Floor and vice-versa. Workable solution but not elegant.
... View more