Shut down access points at night

[christoffer.alftberg]

We have used lightweight templates and scheduled them in Cisco prime, and set "admin status" to "disable" which works well when this has been asked from us in smaller portions. But now it's about 1500 access points, which becomes very difficult to handle as a scheduled task due to the page where you select affected access points. A bit of an administrative nightmare.

Is there anyone else who has done the same thing? How did you solve it?

[Mark Elsen]

 - By not doing that ; we never see such questions in the forum and there is a reason for that. We live in an always connected world. 'layer1 disturbance' may need to lockup in device apps and or devices becoming unusable. Better is to look into Intranet policies albeit enforced by firewall and or  Intranet access policies (e.g.)

M.

[patoberli]

Yes I agree with Marce1000. As soon as you have wireless devices like microphones, cameras and other "low intelligence" things (basically everything that isn't running a full Windows, OSX or Android) they often will not reconnect after the wireless is back in the morning and require a power cycle.

[omz]

Hi 

You can use PI API.

PUT apService/accessPoint

Modifies an Unified Access Point's name, location, controller affinity, or admin status. All parameters should be provided. If some parameter isn't specified it will be considered as an empty value.

https://d1nmyq4gcgsfi5.cloudfront.net/media/pi_3_4_devnet/api/v4/op/apService/accessPoint-PUT@_docs.html