Transactional Configuration
54 Basic System Configuration Guide
Transactional Configuration and Configuration Rollback support combine to provide the 
operational model depicted in Figure 5.
Figure 5: Router Configuration with Rollback and Transactions
Basic Operation
In order to edit the candidate configuration the operator must first enter the candidate edit 
mode (edit-cfg). The operator can enter and quit the configuration mode as many times as 
they wish before finally committing the candidate. 
In edit-cfg mode the operator builds a set candidate configuration changes using the same CLI 
tree as standard (line-by-line non-transactional) configuration. Tab completion and keyword 
syntax checking is available.
Just as there is a single operational active configuration that can be modified simultaneously 
by multiple users in the SR OS, there is also a single global candidate configuration instance. 
All users make changes in the same global candidate configuration and a commit operation 
by any user will commit the changes made by all users.
Users have the ability to exclusively create a candidate configuration by blocking other users 
(and sessions of the same user) from entering edit-cfg mode.
Make Changes to the 
Target Config in CLI
(Candidate Edit)
Candidate Commit
Commit Triggers
a Rollback Save
Candidate Save
Rollback Save
Rollback
Revert
CLI
Commands
(Config)
SNMP
(SAM)
Candidate
Configuration
Active
Configuration
Saved
Candidate
Rollback
Checkpoint
Files