Cisco Cisco Email Security Appliance C160 Mode D'Emploi

Page de 1094
 
29-24
Cisco AsyncOS 8.0.1 for Email User Guide
 
Chapter 29      System Administration
  Reverting to a Previous Version of AsyncOS
setup 
Step 4
Follow the prompts to specify the following: 
The dedicated IP address for this feature, plus netmask and gateway. 
The username and password required to execute the power-cycle command. 
These credentials are independent of other credentials used to access your appliance. 
Step 5
Enter 
commit
 to save your changes. 
Step 6
Test your configuration to be sure that you can remotely manage appliance power. 
Step 7
Ensure that the credentials that you entered will be available to you in the indefinite future. For example, 
store this information in a safe place and ensure that administrators who may need to perform this task 
have access to the required credentials. 
Related Topics 
Reverting to a Previous Version of AsyncOS
AsyncOS includes the ability to revert the AsyncOS operating system to a previous qualified build for 
emergency uses. 
Note
After upgrading to AsyncOS 7.0, you cannot revert to a version of AsyncOS earlier than 6.5.
Available Versions
Because upgrades cause one-way transformation of key subsystems, the reversion process is complex 
and requires qualification by Cisco Quality Assurance teams. Cisco 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 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 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.