Currently our network has a Native VLAN of X set on the trunk links.
We have a management VLAN of Y for all our management traffic.
I have read 2 separate recommendations regarding how to handle these VLAN's.
The first recommends using the Native VLAN as the Management VLAN.
The second recommends keeping these VLAN's separate as I currently have it designed.
Both recommendations came from reputable sources.
What is the best practice, and just as importantly, why is it better than the other option?
Thanks in advance.
Sorry for interrupt :-)
But I have a simmilar question.
Have backbone/trunk with VLAN 10(Management) 20(IP phones) 30(Internet access) 990(Native).
Connecting to Standalone AP1242AG AccessPoint SSID1 is member of VLAN20, SSID2 is member of VLAN30.
I want to use VLAN10 as management on the AP.
So what should I do regarding BVI1 interface on the AP ???
Is it possible to assign ip addresses beloging to VLAN10 to BVI1, and do management that way ?? And what about native VLAN ??
Or is it just to put VLAN10 on AP an mark it as native ???
Yep. This is an unfortunate case where Cisco's best practice recommendation should not be followed. You MUST use the native VLAN for LWAP management.
RLANs need to be trunked, the VLAN that carries LWAPP/CAPWAP and carries LWAP management must be untagged. This is fine if there's no RLANs, just make it an access port, but otherwise you need to use the native VLAN to carry WLANs over LWAPP/CAPWAP and to carry LWAP management data.