Committing configuration changes
How to commit configuration changes with examples.
In a vRouter, configuration changes do not take effect until you commit them by using the commit command.
vyatta@R1# commitA line that contains uncommitted changes is flagged as follows:
- > to indicate the line has been modified
- + to indicate the line has been added
- - to indicate the line has been deleted
After you commit the changes, the flag disappears, as in the following example.
vyatta@R1# show interfaces dataplane dp0p1p3
-address 192.168.1.100/24
hw-id 00:13:46:e6:f6:87
vyatta@R1# commit
vyatta@R1# show interfaces dataplane dp0p1p3
hw-id 00:13:46:e6:f6:87
vyatta@R1#Note: When you commit changes in the configuration mode, the changes are saved to the startup configuration. As a result, the changes are preserved even after a reboot.
CAUTION: If your login username is not a member of the "secrets" login user group and you either save a configuration through the REST API or use the save command, the encrypted passwords in the configuration file are replaced with the ******** placeholder. If you load this configuration, the replaced password fields trigger validation errors because the placeholder does not match the format for an encrypted password. Do not commit this configuration. If you ignore the error message and perform a commit with this invalid configuration, the passwords are deleted.