Cisco Cisco Email Security Appliance X1050 故障排查指南

下载
页码 4
Upgrade AsyncOS Basic Procedure and Common
Scenarios
Document ID: 118547
Contributed by Matthew Huynh, Cisco TAC Engineer.
Aug 18, 2015
Contents
Introduction
Requirements
     Prepare to upgrade
     Download and install the upgrade
     Upgrade on CLI
     Upgrade on GUI
     Cluster upgrade
Troubleshoot
Related Information
Introduction
This document provides additional insight and steps associated with the upgrade process of AsyncOS for
Email Security on the Cisco Email Security Appliance (ESA).
Requirements
Ensure the appliance RAID status is READY or OPTIMAL in the System Status output. Please do not
initiate an upgrade on an appliance with a RAID status of DEGRADED. Please contact Cisco TAC to
initiate an RMA case for your appliance.
• 
Verify if the ESA is a stand alone appliance or in a clustered environment. If clustered, please be sure
to properly review the Cluster Upgrade section of this document.
• 
Assure Internet connectivity from the ESA on port 80 and 443 with no packet inspections.
• 
Functional DNS server(s) is required.
• 
Review the compatibility of the ESA and SMA systems before upgrading.
• 
Older versions of AsyncOS for Email Security may require more than one upgrade in order to get to the latest
version. For confirmation of the upgrade path and appliance provisioning please contact Cisco TAC.
Prepare to upgrade
Save the XML configuration file off-box. If you need to revert to the pre-upgrade release for any
reason, you will need this file.
1. 
If you are using the Safelist/Blocklist feature, export the list off-box.
2. 
Suspend all listeners. If you perform the upgrade from the CLI, use the suspendlistener command.
If you perform the upgrade from the GUI, listener suspension occurs automatically.
3. 
Wait for the queue to empty. You can use the workqueue command to view the number of messages
in the work queue or the rate command in the CLI to monitor the message throughput on your
appliance.
4. 
If recommended by Cisco, disable reporting. Disabling reporting can only be performed from the
appliance CLI:   
5.