Wireless Access

I have a WLAN with 3 x.x.x.x/24 vlans/subnets. I have added a x.x.x.x/22 vlan to the pool, and I want to migrate the users to the /22, hopefully seamlessly. The end goal is that all users will be on the /22.

DHCP is Microsoft. We have Mobility conductor with two 7200's controllers.

I can see two possibilities, but I don't know what ramifications it might cause. 

1. Disable the DHCP scope(s) on the DHCP server. If I do this, will Aruba Controller see that a DHCP request is not fulfilled (assuming it tries on the disabled DHCP scope), and try on one of other vlan/subnets? All users would eventually time out, and I could delete the vlan/subnet from the pool on the conductor.
2. Take out a vlan from the pool. If I do this, I fear all users with that subnet/vlan will lose connectivity.
3. Is there another possibility to force all new (or renew) connections to use the /22 subnet/vlan? 

Thanks for any hints.

Mark

1. If disable DHCP scope the client still gets the vlan from the vlan name/pool and don't get DHCP.

2. If remove a vlan from the pool active client will loose connectivity and need to reconnect to get new vlan and DHCP

I think go for option 2 but manualy kicks all client form the controller to force reconnection.

CLI MD Per Contoller "aaa user delete all"

All users will force to reconnect shortly and get new vlan and dhcp.

------------------------------
Marcel Koedijk | MVP Expert 2023 | ACEP | ACMP | ACCP | ACDP | Ekahau ECSE | Not an HPE Employee | Opinions are my own
------------------------------

Original Message:
Sent: Nov 22, 2023 10:05 AM
From: OCNetAdmin
Subject: migrating users to another vlan

I have a WLAN with 3 x.x.x.x/24 vlans/subnets. I have added a x.x.x.x/22 vlan to the pool, and I want to migrate the users to the /22, hopefully seamlessly. The end goal is that all users will be on the /22.

DHCP is Microsoft. We have Mobility conductor with two 7200's controllers.

I can see two possibilities, but I don't know what ramifications it might cause. 

1. Disable the DHCP scope(s) on the DHCP server. If I do this, will Aruba Controller see that a DHCP request is not fulfilled (assuming it tries on the disabled DHCP scope), and try on one of other vlan/subnets? All users would eventually time out, and I could delete the vlan/subnet from the pool on the conductor.
2. Take out a vlan from the pool. If I do this, I fear all users with that subnet/vlan will lose connectivity.
3. Is there another possibility to force all new (or renew) connections to use the /22 subnet/vlan? 

Thanks for any hints.

Mark