Cisco Cisco Email Security Appliance C170 Guia Do Utilizador

Receive confirmation of the 

commit

 procedure at the CLI.

Changes to configuration that have not been committed will be recorded but not put into effect until the 

commit

 command is run. 

Not all commands in AsyncOS require the 

commit

 command to be run. See Appendix A, “AsyncOS 

Quick Reference Guide,” in the Cisco IronPort AsyncOS for Email Advanced Configuration Guide

 

or 

view the Cisco IronPort AsyncOS CLI Reference Guide 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 Cisco IronPort 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. See Appendix A, “AsyncOS Quick 

Reference Guide,” in the Cisco IronPort AsyncOS for Email Advanced Configuration Guide for more 
information. The 

commit

 command applies configuration changes made to Cisco IronPort AsyncOS 

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.

mail3.example.com> commit

Please enter some comments describing your changes:

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

Changes committed: Wed Jan 01 12:00:01 2003