Avatar of jostafew
jostafew
Flag for Canada asked on

Cisco WAP forgets schedule after power loss

Hello everyone, I have a number of Cisco access points throughout the company running in standalone mode. The one in question is an AIR-AP1041N which has performed just fine save for one thing; after a power loss it forgets the latest change to the time-range (schedule) I've programmed it with and reverts back to its original schedule.

I don't believe there's anything wrong with the access point as it holds on to the rest of the configuration, it must just be something I'm doing wrong with altering the time-range.

I'm working at the CL because as far as I know I cannot create a time-based ACL through the GUI. My usual workflow is to create a time-range, create the ACL using said time-range, apply the ACL to a network interface. This all works great, but where things break down is when there is a change to the time-range. Originally I was just altering the time-range but during normal operation it would randomly forget my changes and revert back to the original. I eventually clued in that if I remove the time-range as well as the ACL that uses it, then recreate them both it would keep the changes indefinitely... that is until we had a power outage and again my changes were lost. Further testing showed that power cycling the device would consistently undo my changes.

What am I missing, any suggestions on why these changes are not permanent?

BTW I've also included this post in the Routers and Firewalls categories as I'm sure that someone will be using a time-based ACL on a Cisco device in those categories as well.
Wireless HardwareRoutersHardware Firewalls

Avatar of undefined
Last Comment
jostafew

8/22/2022 - Mon
Craig Beck

Cisco IOS APs have a bit of a strange issue where if you make changes in the CLI which aren't supported in the GUI, they will be lost or adjusted when you log in to the GUI.  This might not be what you're seeing, but can you confirm that the changes are gone immediately after you reload the AP?

Sorry to ask the obvious, but are you saving the changes in the CLI?  When you make changes in the GUI they're automatically saved when you hit 'Apply'.
jostafew

ASKER
Hi craigbeck, thanks for the quick reply.

The obvious questions might be the ones that need to be asked. I'm not aware of a need (or even a method) to save changes in the CLI. Here's an example of the commands I would use to set up an AP, maybe you can spot an omission:

configure terminal
time-range BusinessHours
periodic weekdays 7:00 to 17:30
exit

ip access-list extended 101
permit ip any any time-range BusinessHours
exit

interface Dot11Radio0.3
ip access-group 101 out
exit

end

Then I would verify work done:

show time-range BusinessHours
show access-list 101
show running-config

The results of the above reports all look fine, and if it's the initial config will remain that way even after power cycle. But if I were to go back and alter the time-range BusinessHours like this:

configure terminal
no time-range BusinessHours
no access-list 101
exit

show time-range and access list verify that they're gone

configure terminal
time-range BusinessHours
periodic weekdays  6:00 to 21:00
exit

ip access-list extended 101
permit ip any any time-range BusinessHours
exit
exit

Again show time-range, ACL, running config and everything looks good. But if I power cycle the device it reverts to the original version of BusinessHours.
ASKER CERTIFIED SOLUTION
Craig Beck

Log in or sign up to see answer
Become an EE member today7-DAY FREE TRIAL
Members can start a 7-Day Free trial then enjoy unlimited access to the platform
Sign up - Free for 7 days
or
Learn why we charge membership fees
We get it - no one likes a content blocker. Take one extra minute and find out why we block content.
Not exactly the question you had in mind?
Sign up for an EE membership and get your own personalized solution. With an EE membership, you can ask unlimited troubleshooting, research, or opinion questions.
ask a question
jostafew

ASKER
There you go, that did the trick. I've saved the running-config to startup-config and now the device maintains the intended configuration after a power cycle.

Just a simple thing but for someone who's pretty green with Cisco CLI not an obvious one, I assumed these changes were immediately written to permanent memory after the commands complete as they were taking effect immediately.

Thank you for the assistance
I started with Experts Exchange in 2004 and it's been a mainstay of my professional computing life since. It helped me launch a career as a programmer / Oracle data analyst
William Peck