Cisco Cisco Email Security Appliance C190 Technical References

Not all commands require the 

commit

 command to be run. See 

 

for a summary of commands that require commit to be run before their changes take effect. 

Exiting the CLI session, system shutdown, reboot, failure, or issuing the 

clear

 command clears changes 

that have not yet been committed.

This section describes the commands used to commit or clear changes, to get help, and to quit the 
command-line interface.

The 

commit

 command is critical to saving configuration changes to the appliance. Many configuration 

changes are not effective until you enter the 

commit

 command. (A few commands do not require you to 

use the 

commit

 command for changes to take effect. The 

commit

 command applies configuration changes 

made since the last 

commit

 command or the last 

clear

 command was issued. You may include comments 

up to 255 characters. Changes are not verified as committed until you receive confirmation along with a 
timestamp.

Entering comments after the commit command is optional.

To successfully commit changes, you must be at the top-level command prompt. Type Return at an empty 
prompt to move up one level in the command line hierarchy.

The 

clear

 command clears any configuration changes made since the last 

commit

 or 

clear

 command 

was issued. 

mail3.example.com> commit

Please enter some comments describing your changes:

[]> Changed "psinet" IP Interface to a different IP address

Do you want to save the current configuration for rollback? [Y]> n

Changes committed: Fri May 23 11:42:12 2014 GMT

mail3.example.com> clear

Are you sure you want to clear all changes since the last commit?  [Y]> y

Changes cleared: Mon Jan 01 12:00:01 2003

mail3.example.com>