topic Re: Why VLAN carries LWAPP/CAPWAP and LWAP management should be untagg in Wireless

Why VLAN carries LWAPP/CAPWAP and LWAP management should be untagged ?

Manindersinghnegi — Mon, 06 May 2024 05:37:21 GMT

I have configuration in which port which is connect to cisco AP is trunk port, but management VLAN is configured as native.

I want to know what is rationale behind this?

Re: Why VLAN carries LWAPP/CAPWAP and LWAP management should be untagg

Mark Elsen — Mon, 06 May 2024 06:22:03 GMT

- FYI : https://community.cisco.com/t5/wireless/tagging-management-vlan-mobility-express/m-p/4664689#M244935

Re: Why VLAN carries LWAPP/CAPWAP and LWAP management should be untagg

Rich R — Mon, 06 May 2024 23:33:30 GMT

It's a design requirement for Cisco APs:
https://www.cisco.com/c/en/us/support/docs/wireless/4400-series-wireless-lan-controllers/69719-wlc-lwap-config.html#toc-hId--1790699332
The port must either be in access mode (untagged) or trunk mode with the management vlan untagged (native).

Trunk port is used when the AP will be used in flexconnect mode with local switching. The locally switched VLAN traffic is tagged by the AP according to the WLAN flexconnect configuration.