Why change? You used the dynamic discovery for the initial setup, when you add APs in the future that will get used again, you aren't going to remove the dynamic discovery settings...why change?
Static discovery has some useful use cases, like when moving to a new controller/cluster, but generally shouldn't be used. If you configure static discovery and get the target incorrect, or for some reason that target becomes unreachable in the future, then you're stuck with a bunch of APs that will only ever target that IP. Dynamic allows for much easier recovery.
------------------------------
Carson Hulcher, ACEX#110
------------------------------
Original Message:
Sent: Jul 31, 2024 12:36 PM
From: Ronin101
Subject: Provision AP - Controller IP
Oh ok, i am just asking out of curiosity. Why keep it dynamic? Normally the ip of the controllers are fixed and static then why keep?
Original Message:
Sent: 7/31/2024 12:27:00 PM
From: chulcher
Subject: RE: Provision AP - Controller IP
Moving from dynamic to static discovery requires re-provisioning the AP which will require a reboot.
Why move to static? The preferred method of discovery is dynamic, using DHCP or DNS.
------------------------------
Carson Hulcher, ACEX#110
Original Message:
Sent: Jul 31, 2024 11:39 AM
From: Ronin101
Subject: Provision AP - Controller IP
Dear Experts,
I have approx 300 APs in AP-Group Test. All these APs are working and in production. Currently they are set to controller discovery dynamic. I want to set the controller IP manual. Is there anyway to do it without restarting the APs? If not do i have to re-provision every single AP individually and restart?
This scenario is without Mobility Master