Dell OS10 Transaction-Based Configuration Mode: Candidate Config Workflow - 夜莺博客

Dell OS10 Transaction-Based Configuration Mode: Candidate Config Workflow

Most switch operating systems apply configuration commands the moment you type them, which makes multi-step changes risky: a typo halfway through is already live. Dell OS10 solves this with transaction-based configuration mode, where commands are staged into a candidate configuration and only applied when you explicitly commit. This article explains how the mode works, why it is safer than the default behavior for production changes, and walks through the full command sequence with a real interface-description example. It is one of the most under-used safety features in the OS10 CLI.

Default Behavior vs. Transaction Mode

By default, every OS10 configuration command takes effect immediately in the running configuration. In transaction mode, your commands are stored in a candidate configuration; nothing changes in the running configuration until you commit. This gives you a review point before any change goes live, and a clean way to throw away mistakes with discard.

How to Use Transaction-Based Configuration Mode

Start the transaction from EXEC mode, then make your changes as usual:

OS10# start transaction

Now enter configuration mode and modify the interface — for example, changing the description of ethernet 1/1/1:

OS10# configure terminal
OS10(config)# interface ethernet 1/1/1
OS10(conf-if-eth1/1/1)# description TEST

Review the Difference

Before committing, see exactly what will change:

OS10(conf-if-eth1/1/1)# do show diff candidate-configuration running-configuration
!
interface ethernet1/1/1
 description TEST

Discard or Commit

If the change is wrong, discard the whole candidate:

OS10(conf-if-eth1/1/1)# do discard

If it looks right, commit it to the running configuration:

OS10(conf-if-eth1/1/1)# do commit
OS10(conf-if-eth1/1/1)# do show running-configuration interface ethernet 1/1/1
!
interface ethernet1/1/1
 description TEST
 no shutdown

Persisting the Change

Like normal OS10 changes, a committed change is not permanent until you save it:

OS10(conf-if-eth1/1/1)# do write memory

Key Takeaways

  • start transaction switches to candidate-based configuration editing.
  • show diff candidate-configuration running-configuration reviews pending changes.
  • discard rolls back the candidate; commit applies it; write memory saves it.

Pair this workflow with the basics covered in Dell OS10 基础管理配置 and the port-group guidance in Dell OS10 S5212F 快速入门 to build a safe day-to-day OS10 operating routine.

原文链接:https://www.dell.com/support/kbdoc/en-us/000120163/dell-emc-networking-os10-how-to-use-transaction-based-configuration-mode