Any possible to utilize extend-vlan feature in VC deployment?

[zlinuxboy]

I have a challenge scenario to accomplish, here is the topology:

1. The firewall uplink to Inernet and downlink to a managed switch(sw-1)
2. There are 2 switch, one is l2 managed switch(sw-1) which connected to firewall, the other is a unmanaged switch(sw-2) connected to the sw-1.
3. 4 APs
  3.1 2 APs(A and B) connected to sw-1, the uplink port are trunk(vlan 7,8,9*,10)
  3.2 2 APs(C and D) connected to sw-2, the uplink port are access(vlan 1*)

4. Both of inter-link ports on sw-1 and sw-2 are access port, sw-1's inter-link port is access(vlan 9*), sw-2's inter-link port is access(vlan 1*)

I know there is extend-vlan feature on wing wireless, but don't know if it could accomplish this scenario:

1. Could AP-C and AP-D serve clients with dynamic vlan through radius policy? such as the client Alice will be assigned vlan 7 and the client Bob will be assigned vlan 8? how to accomplish it?
2. Does the clients could seamless roaming from AP-C/AP-D to AP-A/AP-B?

[ckelly · Accepted solution]

Extended VLANs (tunneled wlans) are not supported with VC deployments. It’s a limitation when using an AP as a virtual controller.