different Vlan configuration

[Malik]

how can configure  different VLANs for Access Points and WLANs for clients ??

[Christoph_S]

Hello Malik,

if you already have the vlans configured on you network (switch) you'll have to do the following in the AP profile:

Note: Make sure that all vlans are allowed through the switchports the APs are connected to

1. Create native vlan if other than  vlan 1
2. Map the vlans to the WLANs
3. Trunk the ge 1 port and allow all vlans through

1 - Create Native vlan if other than vlan 1.

#config
#profile <ap model> <profile name>
#int vlan1
#no ip dhcp client request options all
#interface vlan<new native vlan ID>
#IP address DHCP
#ip address zeroconf secondary                              (only if you'd like to be able to access the APs via the APIPA zeroconfig address)
#ip dhcp client request options all
#com wr
#..

2 - Trunk the ge 1 port (still in AP profile):

#int ge 1
#switchport mode trunk
#switchport trunk allowed vlan <vlan IDs>                                             (The List of the VLAN IDs and aliases e.g. 10-20,25,30-35,$GUEST)
#switchport trunk native vlan <native vlan ID>
# com wr

Article on same: https://extremeportal.force.com/ExtrArticleDetail?an=000080209

3 - Map vlans to wlans:

#config
#wlan <wlan name>
#vlan <vlan id>
#com wr

I hope this helps,

Christoph





​​​​​​​​​​​​​​​​​​​​​

[ckelly]

Malik, to configure a VLAN for an SSID, see this article.

For configuring the port, see this thread.

[Malik]

many thanks @rmu please find the below answer :

do you need a vlan for ap management and separate vlans for ssid traffic? yes exactly, I need vlan for management and other vlan for ssid traffic
do you have a static mapping ssid<>vlan or should this be dynamic? by dynamic

already I have  vlan for management and ssid so When clients connect to the SSID, they get an IP address from the same vlan 
So I want clients to have an IP ,but from another VLAN.

​

[Karol_Radosovsk]

If you are new to WING, I strongly recommend read through the "How to" materials, which were created some time ago, but they are still mostly relevant, as Extreme & Zebra didn't add anything revolutionary to the whole system. 
This is, where it's currently stored:
https://www.extremenetworks.com/support/documentation/wing-5-x-how-to-guides/
I "must read" would be this document: "Best practices and Recommendations".
https://documentation.extremenetworks.com/WiNG/Implementation_Guides/WING5X_Reference_Best_Practices_and_Recommendations_Rebranded-Final.pdf
I also recommend to have both GUI and CLI reference guides "on hand". Extreme is somewhat late with versions, but the most of if doesn't change significantly anyway. Here's for 5.9.7 version: https://www.extremenetworks.com/support/documentation/extremewireless-wing-software-5-9-7/

[ckelly]

Malik, in the simplest form, you assign a static VLAN to a wlan profile (make ge1 a trunk and add that VLAN to the allowed VLAN list in the ge1 config). Then when clients associate to that wlan, they are mapped to that VLAN.
Beyond that, there are more ways to set this up depending on how you need it to work.