Cisco Cisco Email Security Appliance C170 Guia Do Utilizador

Página de 1211
 
2-7
AsyncOS 9.1.2 for Cisco Email Security Appliances User Guide
 
Chapter 2      Accessing the Appliance
  Command Line Interface (CLI)
Changes to configuration that have not been committed will be recorded but not put into effect until the 
commit
 command is run. 
Note
Not all commands in AsyncOS require the 
commit
 command to be run. See the Cisco 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.
General Purpose CLI Commands
This section describes the commands used to commit or clear changes, to get help, and to quit the 
command-line interface.
Committing Configuration Changes
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 to Cisco 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.
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