05-08-2017 01:40 PM
I have several AP groups need to assign vlans for each group
4550(0/0/2-)---L3 switch(1/1/13)-----L2 switch(1/1/1)--AP----Wireless clients
Controller Uplink -vlan 2222 (Ap vlan asame)
Core switch - vlan 858 (tagged in uplink ports of controller connecting to coreswitch & )
Internet Uplink -vlan 1002 (IP for wireless clients)
VAP profile - for eg AP group : Ground floor(vlan 858)
If the above is like this means where in VAP profile should i need to add vlans 858 & 1002
05-08-2017 02:36 PM
Get Outlook for iOS
Lead Mobility Engineer @ Integration Partners
AMFX | ACMX | ACDX | ACCX | CWAP | CWDP | CWNA
05-16-2017 02:10 AM
It is achievable, but it creates unintended issues. If a user roams from the first floor to the second floor, they will get a different ip address and break their existing connection to applications. There are times when a user can be on the first floor and connect to an access point on the second floor. It makes more sense to have everyone in the same wireless VLAN on both floors.
In addition, you have to create and manage a configuration that detects what floor a user is on and switch vlans; that adds complexity and administrative overhead. You also have to add and manage another VLAN to your routing infrastructure, which will waste ip addresses if the VLANs are not full.
Aruba Customer Engineering
Looking for an Answer? Search the Community Knowledge Base Here: Community Knowledge Base
05-17-2017 07:49 PM - edited 05-17-2017 07:50 PM
You need to remember that the APs on the 2nd floor will support some of your clients on the first floor. Unless there is a security issue there is no reason to have floor 1 and floor 2 on a separate VLAN.