09-14-2020 10:00 PM
Hello, i just moved to WAP150 from an Aruba solution, and I am facing one problem that I can't recreate the same config I had on Aruba.
on my Aruba, I had 2 ssids, one for employees in the normal subnet, and a guest one with 172.16 subnet. i found no way to do this on my Cisco. Am I missing something? or is this not supported?
thanks!
09-23-2020 02:26 AM
Hello Michael,
Firstly I would recommend upgrading the WAP150 firmware to the latest 1.1.2.4 version which is the most stable one.
You can configure up to 8 WLANs and map them to a certain SSID in your network. The point here is the WAP does not have DHCP server embedded so you have to rely on the DHCP server in your network (router, security appliance, etc.). So you have to configure the VLANs respectively DHCP servers for your employees and guest networks first and then those will be propagated to the WAP150. This way you will have for instance your employee network with the 192.168.1.0 address and guest network with 192.168.3.0 address. Additionally, you can enable guest portal, band steering and channel isolation for better security and flexibility.
Regards,
Martin
09-23-2020 03:01 AM
Hey, thanks for replying. the first thing I did was upgrade to the latest firmware, and a good thing that I did because the whole UI changed.
Anyway, do you remember where in the UI I tag ssids with a vlan number? because If i understand you correctly i need to assign a number to the said and then on my router assign a dhcp to that vlan traffic.
thanks in advance!
09-23-2020 04:29 AM
Hello Michael,
That is correct.
On your router, you create both VLANs (for example Employee VLAN ID 1 and GuestWiFi VLAN ID 2) and enable DHCP server on each VLAN having different subnets. Then on WAP150 you go to Wireless->Networks and add WLANs respectively WLAN with SSID Employee and VLAN ID 1 and then WLAN with SSID GuestwiFi and VLAN ID 2.
Hope that helps.
Regards,
Martin
09-23-2020 06:20 AM
Hey Martin,
so I've done all you suggested, the guest wifi is now vlan 172. the router has a config for this vlan and is giving out addresses in the 172 range, but when one client tried to connect they got the message the network is temporarily full.
any idea why? also I saw the same device trying to connect with AC and N at the same time.
thanks!
09-23-2020 07:50 AM
Michael,
What type of device is using the client? You should have more than 32 connective users per radio before even start getting such a message. What is the wireless clients' density on your network and how many APs you have deployed? Also, make sure you have the SSID and VLAN ID mapped on one radio i.e. 2.4GHz or 5Ghz only. If you had enabled the same SSID on both radios, then the client's device would keep trying to connect to both.
Regards,
Martin
09-23-2020 10:50 PM
My previous example was an android client, and he was the only one on the network.
i did what you told me with the VLANs now my phone can connect but does not get an ipv4 address on the phone but when I check the WAP it is getting an IP in the normal network and not the 172 network.
So I checked the VLAN Table under the LAN settings, and there's only 1 VLAN and not 3 like I specified in the SSIDs. is there a step I'm missing? or is that table not editable for more VLANS?
Thanks!
09-24-2020 12:38 AM
Hi,
Your WAP should get an IP address from your VLAN 1 which is the default VLAN. Check out and see to which SSID (VLAN) is your phone connected to - it should be either connected to VLAN 1 or VLAN 2 (your Guest VLAN). Make sure you have disabled the IPv6 DHCP server on the router and set the port which is connected to the WAP to be trunk allowing VLAN 2 traffic in your case.
In the WAP's VLANs table you can only decide which VLAN to be management (untagged)
09-24-2020 01:07 AM
Hey,
the ssid has a different name so I know that I'm connecting to the guest ssid and have no way of knowing which vlan it is, since the phones don't report that and I don't have ipv6 dhcp running.
so now I tried with a 2.4 client andit is stuck on obtaining IP and then fail.
09-24-2020 01:29 AM
Hey,
Did you check the port on your router? Is it configured as a trunk? Double-check the VLAN IDs to SSID mapping and if DHCP servers are configured correctly. If the problem persists please contact our technical support service so you can get verified your configuration and further troubleshoot. The contacts are available at https://www.cisco.com/c/en/us/support/web/tsd-cisco-small-business-support-center-contacts.html
Regards,
Martin
09-24-2020 03:10 AM
Hey,
so it looks like my router (a fortigate) is having issues with assigning dhcp to vlan tags even though I created the vlan correctly on the plan interface.
i tested this by manually tagging a windows machine to one of the vlans of the guest network and did not get a valid dhcp response.
09-24-2020 03:55 AM
Hi,
I am glad you managed to find the problem. That is why the clients are not getting an IP address for both VLANs. Should you have any other doubts or issues with the configuration, please let us know.
Regards,
Martin
09-24-2020 06:41 AM
Turns out, i forgot that the POE switch that runs WAP is a dump switch that I can't enable trunking on.
so I'm thinking about buying https://www.zyxel.com/products_services/5-Port-8-Port-Web-Managed-PoE-Gigabit-Switch-GS1200-5HP-v2-GS1200-8HP-v2/ to replace it, question is can it do the job...
09-24-2020 07:13 AM
Hey,
Yes, this switch will do the job since it is managed and does support VLANs and PoE. Another option would be any of the Cisco Sx220 or Sx250 PoE models.
Regards,
Martin
09-28-2020 09:41 PM
hey,
sadly those cisco models aren't sold near me, while the other one is.
will update when we return to the office and buy that poe, and will mark this as solved if that is the solution.
thanks!
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide