VLAN Pooling Issue on ZD3000 firmware 188.8.131.52.216
I have a campus wifi setup consisting of the following:
(1) ZD3000 with 250AP licence running firmware 184.108.40.206.216
(200) ZoneFlex 7363
(15) ZoneFlex 7762
Cisco Catalyst 4507 R+E Sup 7-E Core Switch
Cisco Catalyst 2960 and 3560 10/100 PoE Access Switches
Number of users on the network 3000 ~ 4000
I have setup vlan pooling to eliminate using large subnets and avoid degraded network performance from broadcast and multicast traffic.
I setup (10) VLANS, 10,12,14,16,18,20,22,24,26 and 28 with ip scopes of 510 each (/23 networks) on the vlan pool list and enable dynamic vlan.
When I ran this setup in the campus, I experienced people complaining failure to connect to wifi and cannot grab IP.
When I looked at the Core Switch which is the DHCP server and searched the DHCP pool I saw that dhcp pool for Vlans 10, 12, 26 and 28 were completely exhausted (all ip leased). However, since I configured 10 Vlans on the vlan pool list, I was expecting that users will use be allocated to the other 6 vlans which where not yet used but after several hours the users were not allocated to the remaining vlan.
I have configured ports on the Core Switch for VLAN 14,16,18,20,22 and 24 just to check whether I can get IP from this DHCP pool on my pc and I did. These vlans are functioning properly and can get the IP from the DHCP server.
Have anybody experienced this issue before? Now I'm stuck and unable to figure out why the other vlans were used by the vlan pool list.
Note: From the VLAN Pooling List vlans 10,12,14,16,18,20,22,24,26 and 28 were included
All my access switches has vlans 10,12,14,16,18,20,22,24,26 and 28 configured
All vlans 10,12,14,16,18,20,22,24,26 and 28 has DHCP scopes configured and are pointing to the correct vlan gateway (tested PC connected to Core Switch and confirmed can get IP using wired)