Cisco Cisco Email Security Appliance C170 Guia Do Utilizador
15-8
Cisco IronPort AsyncOS 7.6 for Email Configuration Guide
OL-25136-01
Chapter 15 System Administration
Available Versions
Because upgrades cause one-way transformation of key subsystems, the reversion process is complex
and requires qualification by Cisco IronPort Quality Assurance teams. Cisco IronPort certifies specific
versions of CASE, Sophos, Outbreak Filters, and McAfee to AsyncOS versions. Not all prior versions
of the AsyncOS operating system are available for reversion. The earliest AsyncOS version supported
for this functionality is AsyncOS 5.5.0; prior versions of AsyncOS are not supported.
and requires qualification by Cisco IronPort Quality Assurance teams. Cisco IronPort certifies specific
versions of CASE, Sophos, Outbreak Filters, and McAfee to AsyncOS versions. Not all prior versions
of the AsyncOS operating system are available for reversion. The earliest AsyncOS version supported
for this functionality is AsyncOS 5.5.0; prior versions of AsyncOS are not supported.
Important Note About Reversion Impact
Using the
revert
command on a Cisco IronPort appliance is a very destructive action. This command
destroys all configuration logs and databases. Only the network information for the management
interface is preserved--all other network configuration is deleted. In addition, reversion disrupts mail
handling until the appliance is reconfigured. Because this command destroys network configuration, you
may need physical local access to the Cisco IronPort appliance when you want to issue the
interface is preserved--all other network configuration is deleted. In addition, reversion disrupts mail
handling until the appliance is reconfigured. Because this command destroys network configuration, you
may need physical local access to the Cisco IronPort appliance when you want to issue the
revert
command.
Warning
You must have a configuration file for the version you wish to revert to. Configuration files are not
backwards-compatible.
backwards-compatible.
Performing AsyncOS Reversion
Step 1
Ensure that you have the configuration file for the version you wish to revert to. Configuration files are
not backwards-compatible. To do this, you can email the file to yourself or FTP the file. A simple way
to do this is to run the
not backwards-compatible. To do this, you can email the file to yourself or FTP the file. A simple way
to do this is to run the
mailconfig
CLI command.
Step 2
Save a backup copy of the current configuration of your appliance (with passwords unmasked) on
another machine.
another machine.
Note
This is not the configuration file you will load after reverting.
Step 3
If you use the Safelist/Blocklist feature, export the Safelist/Blocklist database to another machine.
Step 4
Wait for the mail queue to empty.
Step 5
Log into the CLI of the appliance you want to revert.
When you run the
revert
command, several warning prompts are issued. After these warning prompts
are accepted, the revert action takes place immediately. Therefore, do not begin the reversion process
until after you have completed the pre-reversion steps.
until after you have completed the pre-reversion steps.
Step 6
From the CLI, Issue the
revert
command.
Note
The reversion process is time-consuming. It may take fifteen to twenty minutes before reversion
is complete and console access to the Cisco IronPort appliance is available again.
is complete and console access to the Cisco IronPort appliance is available again.