There are several solutions to save power on AP’s. Hereby listed 3 possibilities that are widely used implementations and supported in different scenarios:
- Shut down AP’s outside working hours
- Disadvantages: Some clients needs a reboot if wifi loss. AP on/off life impact. RF environment impact. Static
- Advantages: Maximum AP Power saved. Not WLC/AP SW/HW dependent
- Configure Power/Calendar Profiles and apply to AP’s
- Disadvantages: Static. WLC/AP SW/HW dependent
- Advantages: WLC built-in
- Configure Low Power mode and apply to AP’s (Recommended option)
- Disadvantages: WLC/AP SW/HW dependent
- Advantages: WLC built-in
Scenario 1 requires some kind of scripting that shut/open switchports and likely through DNAC
Scenario 2 requires 9xxx AP’s and WLC version 17.9.1 ->
Scenario 3 requires 9xxx AP’s and WLC version 17.10.1 -> (17.12.3/4 recommended. Releashed medio 2024)
Monitoring Power consumption visibility expect to be in CatC 2.3.7 (medio 2024)
Example, Scenario 3:
Two AP Join Profiles created:
KASR-TEST with “reduced capability” settings:
and KASR-TEST01 with “full” settings. Normal mode:
Two AP’s on Controller and 2 Site Tags created with each Join Profile:
Let’s see the different Power consumption on the switch (there are no clients associated):
AP-STAGING-SWITCH-1#sh power inline Gig 1/0/24 detail | i Mea
Measured at the port: 9.2
AP-STAGING-SWITCH-1#sh power inline Gig 1/0/23 detail | i Mea
Measured at the port: 8.0
So a difference of 15% between these two Power Profiles