An engineer changes a Catalyst 9800 policy tag, does not save, and reloads during a maintenance window. After the reload the previous policy tag is back. What was skipped?
Select an answer to reveal the explanation.
Short Explanation
The change lived only in the running configuration, and the reload threw that away. You have to save if you want the policy tag to be there when the controller comes back. A beacon timer is not a save button.
Full Explanation
On IOS XE the running configuration is what is active, and a reload returns to the saved configuration. The policy-tag change was never saved, so the reload restored the previous one. The skipped maintenance step is the save. Clearing the country code disables radios. It does not write policy tags into the saved configuration. Client exclusion is a timer that rejects a client. It does not store configuration edits across a reload. The beacon interval does not commit a configuration when it expires. Nothing about the over-the-air timer writes NVRAM. A reload keeps the saved configuration. An unsaved policy-tag edit exists only in the running configuration and disappears on the reload. Exam caveat: a save after a bad change makes the bad change the one that survives the next reload. Save when the change is the one you mean to keep, and keep the backup you took before it. Operational check: save, reload a lab controller or compare the saved configuration with the running one, and confirm the new policy tag is in the saved copy.