Skip to main content
Cisco SD-WAN
Support
Product Documentation
Viptela Documentation

commit

commit—Activate the commands in the configuration on the Viptela device and make it the running configuration. You issue this commit command from configuration mode.

Command Syntax

commit (abort | and-quit | check | confirmed [timeout] [persist] | no-confirm)
[comment text] [label text] [persist-id id] [save-running filename]

Options

None
Activate the commands in the configuration and remain at the same hierarchy in configuration mode.
Add a Command about the Commit Operation
comment text
Add a text comment about the commit operation. If the text string contains spaces, enclose the entire string in quotation marks (" "). Any comments are display in the output of the show configuration commit list command.
Add a Label about the Commit Operation
label text
Add a text label that describes the commit operation. If the text string contains spaces, enclose the entire string in quotation marks (" "). Any labels are display in the output of the show configuration commit list command.
Exit from Configuration Mode
and-quit
Active the configuration and return to operational mode.
Halt a Commit Operation
abort
Halt a provisional commit operation.
Provisional Commit Operation
confirmed [timeout] [persist]
Commit the current configuration to the running configuration. If no commit confirm command is issued before the timeout period, specified in minutes, expires, the configuration reverts to what was active before the commit confirmed command was issued. The default timeout is 10 minutes. The configuration session terminates after you issue this command, because no further editing is possible. This command is available only in configure exclusive and configure shared mode when the system has been configured with a candidate configuration.
If the CLI session is terminated before the commit confirm command is issued, the configuration reverts to the previously active configuration. If you include the persist option, you can terminate the CLI session before you issue the commit confirm command, and you can then confirm the pending commit in a later session by supplying the persist token as an argument to the commit command using the persist-id option.
Persist Token
persist-id id
If a prior confirming commit operation has been performed with the persist argument, include the persist-id option, specifying the same persist token, to modify the ongoing confirming commit process. This allows you, for example, to abort an ongoing persist commit operation or extend the timeout.
Save the Configuration to a File
save-running filename
Save a text copy of the running configuration to the specified file.
Validate the Configuration
check
Validate current configuration and indicate any configuration errors.

Output Fields

If the configuration on a Viptela device has been downloaded from the vManage NMS, the device is attached to a configuration template and the device is being managed by the vManage server. In this situation, you cannot modify the device's configuration from the CLI. When you issue the commit command (or the validate command), the following message is displayed:

vEdge(config)# commit
Aborted: 'system is-vmanaged': This device is being managed by the vManage. Configuration through the CLI is not allowed.
vEdge(config)#

To determine whether the device is attached to a configuration template, use the show system status command. Check the values in the vManaged and Configuration template output fields. For example:

vEdge-1# show system status
...
Personality:            vedge
Model name:             vedge-cloud
Services:               None
vManaged:               false
Commit pending:         false
Configuration template: None

vEdge-2# show system status
...
Personality:            vedge
Model name:             vedge-cloud
Services:               None
vManaged:               true
Commit pending:         false
Configuration template: vedge

If the vManaged field is false, the device is not attached to a configuration template, and the Configuration template field says None. You can configure such a device from the CLI.

If the vManaged field is true, the device's configuration has been downloaded by the vManage server, and the Configuration template field shows the name of the configuration template. You cannot configure such a device from the CLI.

Example Output

vedge1(config-system)# commit and-quit
Commit complete.
vedge1#

Release Information

Command introduced in Viptela Software Release 14.1.
"system is-vmanaged" warning added in Release 15.2.

Additional Information

commit (operational mode command)
show configuration commit list
validate

  • Was this article helpful?