Native Vlan question

[jwillie3]

Trying to find a definitive answer about the Native Vlan setup for Flexconnect AP's.

At my remote site, the switch port is setup as a trunk and the native vlan is set to our 'wifi mgmt' vlan (not vlan1).

The issue I am running into.  On the controller, for some reason, the Native Vlan setting is randomly reverting back to Vlan 1.

We are have numerous reports of clients having random drops, and roaming issues.  Not sure if the Native Vlan mismatch is an issue and the two cases I have had open with TAC, I have not been given a straight answer.

If the controller is setting the native vlan to 1, but the switchport is set to something different.  Could that account for these type of issues?

-Thanks

[Francesco Molino]

Hi

you're right, on flexconnect, lot of times the management vlan of AP is set as native vlan. This is means that the frame is untagged. When it arrives to the switch that have default vlan 1, the frame is untagged too and they can communicate each other.

This true if you wlc AP Manager interface belong to vlan 1 (default, untagged). If on your wlc, the native vlan is let's say 50 and AP manager is tagged on vlan 1, then the communication between AP and WLC is not working.

With the few information you posted, I don't see any relation between drops, roaming and native vlan. Maybe with a drawing and some configs, I will be able to say differently.

Your drops and roaming issues (based on your input) are part of another issue. This issue could be different things based on your design, AireOS version, radio,....

Thanks

PS: Please don't forget to rate and mark as correct answer if this solved your issue