cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1009
Views
10
Helpful
8
Replies

Wlan configuration

jmb09
Level 1
Level 1

Hello,

On cisco aironet 1830 mobility express ther is something i don't understand ....

When i declare a wlan on the vlan&firewall screen i configure "use vlan tagging" it ask me "Native Vlan ID" and "Vlan ID".

I well understanding "Vlan ID" but i don't understand "Native Vlan ID" ....

My Ap is connect to a cisco C2960, on this switch native vlan is vlan 1. So in Wlan declaration should i configure "Natice Vlan ID to 1 or should i declare a "Native Vlan ID"="Vlan ID"

In my case i would configure 2 Wlan one should be connected on vlan 1 and the other should be connected to vlan 2. And i don't undestand wich vlan configure for Native ID. I think i had to put the same native vlan as my switch's native valn but i have a real doubt!

 

Thanks

8 Replies 8

native vlan using to transport untagged frames received on trunk interfaces through the trunk network. you can use VLAN 1 as native in both WLANs.

Please rate this and mark as solution/answer, if this resolved your issue
Good luck
KB

ammahend
VIP
VIP

Agree with Kasun, just to elaborate a little ..

The link between your switch and Mobility express is a trunk, so the native vlan on both side need to match, if the switch side is configured as vlan 1 as native then on ME native vlan should also be 1.

For WLANs your Vlan can be anything I would not recommend 1, use it anything other than 1, use 2 and 3.

if you kept 2 WLANs in vlan 2 and 3, it means WLAN traffic will be tagged in vlan 2 and 3 and all other traffic like management plane traffic, control plane traffic etc will be automatically placed in vlan1, because your native vlan (vlan for untagged traffic) is 1.

-hope this helps-

jmb09
Level 1
Level 1

Hello everybody,

First thanks for your explanation i began to understand !

Wlan1 serve users on VLAN1, so native VLAN is 1.

Wlan2 serve users on VLAN2, so native vlan should be VLAN 1 due to trunk betweek switch and ap.

Wlan3 serve users on VLAN 50, so native vlan should also be 1 for the same reason !

In my configuration i will not arrive to change native vlan on WLAN2 or three and when i arrived it changed on the other Wlan and my wlan didn't runs ...

Thanks...

i'm not yet a pro of cisco's product .... May be one day, so thanks you for your help !

In fact i have 3 Wlan to configure

Rich R
VIP
VIP

You've configured native vlan 1 on WLAN1 and native vlan 2 on WLAN2 and WLAN3.  You cannot do that - you can only have 1 native VLAN which must match the switchport the AP is connected to so it must be vlan 1.  The native vlan is a function of the trunk port not the WLAN.  As the others have explained the native vlan traffic is untagged (no 802.1q VLAN tagging on the frame).  Behaviour for that configuration will be unpredictable and is definitely unsupported.

jmb09
Level 1
Level 1

Hello !

That's what i have understood but it 's impossible for me to change native vlan in one Wlan without the native vlan in the other Wlan change automatically ....

By example if i put native vlan in Wlan 2 to 1, native vlan in Wlan1 change to 2 and so on .....

I really don't understand !

Rich R
VIP
VIP

Ok I think I can see what the problem is...  I've always avoided ME myself so not that familiar with it.

I think for WLAN1 you need to select Use VLAN Tagging NO because you're using vlan 1 which is the native (untagged) VLAN.

Then I think that will allow you to correctly set the native VLAN for the other WLANs to 1.

Try that?

jmb09
Level 1
Level 1

Hello !

Thanks for your answer ...

I just try your solution ! And oj for Wlan 1 i configured it to "user vlan tagging" to no ! But impossible to change native Vlan in the other wlan, modify one modify the other ...

Mobility express version is 8.5.140.0

I have an old backup without the third Wlan, i think i will restore it and create again the last WALN or may be one of my AP have a problem ....

 

Thanks !

Rich R
VIP
VIP

Also try updating to 8.5.182.0 or 8.10.171.0 in case this is a known bug that's been fixed in the latest release.

Review Cisco Networking for a $25 gift card