Cisco Cisco Email Security Appliance C160

Page de 13
 
9
Release Notes for Cisco AsyncOS 8.0.1 for Email
 
  Installation and Upgrade Notes
You specify the hostname from the CLI command listenerconfig-> setup. You cannot configure the 
hostname from the GUI.
If you configure the received header to display the hostname of the interface the message is received on, 
strip-header filter action configured to strip received headers will strip the received header inserted 
by AsyncOS.
Known Issues
Verify you read the list of known issues and limitations before you upgrade AsyncOS for Email. See 
.
Feature Keys
The AsyncOS appliance checks for and applies feature keys at one minute intervals. Therefore, when 
you add a feature key, it may take up to a minute to view the changes.
Upgrading to the AsyncOS 8.0.1 Release
For the AsyncOS 8.0.1 release, please use the following instructions to upgrade your Email Security 
appliance.
Step 1
Save the XML configuration file off the IronPort appliance. 
Step 2
If you are using the Safelist/Blocklist feature, export the Safelist/Blocklist database off the IronPort 
appliance. 
Step 3
Suspend all listeners.
Step 4
Wait for the queue to empty.
Step 5
From the System Administration tab, select the System Upgrade page. 
Step 6
Click the Available Upgrades button. The page refreshes with a list of available AsyncOS upgrade 
versions.
Step 7
Click the Begin Upgrade button and your upgrade will begin. Answer the questions as they appear.
Step 8
When the upgrade is complete, click the Reboot Now button to reboot your IronPort appliance. 
Step 9
Resume all listeners.
Performance Advisory
RSA Email DLP - Enabling RSA Email DLP for outbound traffic on an appliance that is also running 
anti-spam and anti-virus scanning on inbound traffic can cause a performance decrease of less than 10%. 
Appliances that are only running outbound messages and are not running anti-spam and anti-virus may 
experience a significant performance decline.
DomainKeys - DomainKeys signing outgoing email can cause a decrease in the message throughput 
capacity. Using smaller signing keys (512 byte or 768 byte) can mitigate this.