08-12-2014 08:25 AM
Deploying our first Aruba system. We are a K-12 school system so we have to split staff/students for web content filtering. Having issues getting Network Assinged Vlan to work on GUI, Virtual Controller assigned works with one VLAN.
IAP 105 is connected HP Procurve Switch.
VLAN 82 is untagged on port
VLAN 83 is tagged on port
Routing from core is working fine - I can ping a computer with when connected to the HP port (both 82 and 83 subnet)
I'm sure I'm missing something obvious since this is the first deployment.
Was going to attach the show tech-support results but that is still running and probably overkill.
Any assistance would be greatly appreciated.
Solved! Go to Solution.
Re: VLAN issues
Re: VLAN issues
08-12-2014 09:52 AM
Thanks for the quick response.
When I choose Network Assigned as the VLAN type and then try and connect with a client I get varying error messages.
Network is 'slow' on an Android (Retry etc)
Windows 7 PC returns with a Limited connection error after reporting a connection error.
08-15-2014 06:47 AM
The VLAN ID you put in your SSID configuration when you choose "Network assigned" will be tagged. So for the SSID you want to put on your untagged VLAN (same as your access points) You could choose "default" there.
I'm guessing you have a DHCP server on VLAN 82 where the APs get their IP-adresses, it will be the same for your clients ending up in the "default" VLAN. For the clients in VLAN 83, you need to enable a DHCP scope either on the same place your other scope is configured or you can do it on your IAP. Configure a DHCP scope with mode "local" and choose ID 83.
I'm sorry, I don't have an IAP reachable atm so if any of my options are wrong I apolegise :)
Aruba: ACMX #537 ACCP | CWNP: CWNA CWDP CWSP