Three states matter during a change. The working configuration contains proposed edits. The active configuration controls the running router. The saved boot configuration is loaded after a reboot. Review the difference before applying anything; saving and applying are separate actions.
Mode and action reference #
| Command | Context | Effect |
|---|---|---|
| configure | Operational | Enter configuration mode |
| show configuration commands | Operational | Read configuration as set statements |
| compare | Configuration | Review working-versus-active differences |
| run show interfaces | Configuration | Run an operational inspection |
| commit | Configuration | Apply pending edits |
| save | Configuration | Write the active configuration for boot |
| commit-confirm 5 | Configuration | Apply with a five-minute confirmation deadline |
| confirm | Configuration | Cancel the pending confirmation reboot |
Inspect first:
Mode and action reference
EdgeOS · Operational CLI
show configuration commands | no-moreshow interfacesFor a planned change, enter configuration mode and enter only your approved set/delete statements. Review compare before continuing. The next block applies the pending configuration and starts a reboot deadline; use it only after those edits and the saved recovery baseline have been checked.
Applies configuration — run only after reviewing the pending edits:
Mode and action reference
EdgeOS · Configuration mode
comparecommit-confirm 5The confirmation deadline reboots into saved configuration. Confirm and save only after validation; see recovery notes below.
Read and answer the router's confirmation prompt. Validate the changed service and open a fresh management connection. If the checks succeed, run:
Mode and action reference
EdgeOS · Configuration mode
confirmThe confirmation deadline reboots into saved configuration. Confirm and save only after validation; see recovery notes below.
saveThe confirmation deadline reboots into saved configuration. Confirm and save only after validation; see recovery notes below.
exitThe confirmation deadline reboots into saved configuration. Confirm and save only after validation; see recovery notes below.
Understand the recovery mechanism #
If confirmation does not arrive, EdgeOS reboots and loads the saved boot configuration. This is not an in-place, zero-interruption rollback. Before starting, establish that the saved configuration is the baseline you intend to recover. If there are existing unsaved changes, decide explicitly whether they belong in that baseline; do not blindly save an unknown running state.
Do not save an unvalidated change while relying on reboot-to-saved-configuration as the recovery path. Do not confirm solely because the original SSH session remains connected. An established session can survive a policy change that prevents the next login. Test the path a future administrator will actually use.
A rollback timer cannot repair every fault. A wrong saved baseline, power failure or unrelated hardware problem still needs another recovery path. Choose a confirmation interval long enough for your checks and arrange console or onsite access when losing the site would be costly. Keep the diff and the validation result with the change record so a later reboot does not turn an undocumented edit into a surprise.
Sources
Documentation reviewed: 8 October 2026