Q: How is Local DHCP scope different from Virtual Controller assigned scope?
A: Virtual Controller(VC) Assigned Scope:
VC Assigned Scope is nothing but a private VLAN on the IAP that acts as a DHCP server for the wireless clients. It is also called as Magic VLAN. Selecting this "Virtual Controller Assigned" option, the client obtains IP address from the Virtual Controller i.e from the Master IAP. Any DHCP request from Slave IAPs will be relayed/forwarded without tagging VLAN ID, therefore the DHCP packet from slave IAP will be forwarded to Master IAP via uplink native VLAN.
Executing "show dhcp-allocation" would show the Magic VLAN and associated parameters.
Local DHCP Scope:
Local DHCP scope is also an in-built DHCP server which allows wireless administrator to create multiple DHCP scopes with unique subnet and define VLAN ID. In this case, any DHCP request from forwarded by Slave IAPs will be tagged with the defined VLAN ID, hence VLAN ID needs to be allowed on the uplink switch, else DHCP request from slave would not reach out to the Master IAP as it will be dropped by the uplink switch.
Executing "show dhcp-allocation" would show the Magic VLAN and associated parameters.
