Cisco Cisco Email Security Appliance X1050 Notas de publicación
9
Release Notes for AsyncOS 9.0 for Cisco Email Security Appliances
Installation and Upgrade Notes
Step 4
Load the configuration file from the hardware appliance onto the virtual appliance.
Getting Technical Support for Virtual Appliances
Requirements for obtaining technical support for your virtual appliance are described in the Cisco
Content Security Virtual Appliance Installation Guide available from
Content Security Virtual Appliance Installation Guide available from
.
Provisioning and Activating Cisco Registered Envelope Service Administrator from Virtual
Appliances
Appliances
Please contact Cisco TAC for information required to provision your virtual appliance.
Upgrading Deployments with Centralized Management (Clustered Appliances)
If a cluster includes C160, C360, C660, or X1060 hardware appliances, remove these appliances from
the cluster before upgrading.
the cluster before upgrading.
All machines in a cluster must be running the same version of AsyncOS, and x60 hardware cannot be
upgraded to this release. If necessary, create a separate cluster for your x60 appliances.
upgraded to this release. If necessary, create a separate cluster for your x60 appliances.
Pre-upgrade Notes
Please be aware of the following upgrade impacts:
•
•
•
•
•
•
•
Email Authentication
For DKIM Authentication, Cisco currently supports version 8 of the Draft Specification of
‘Authentication-Results:’ header.
‘Authentication-Results:’ header.
For SPF/SIDF verification, the
spf-passed
rule is no longer available in content filters. To maintain
backwards compatibility, the spf-passed content filter rule will be accepted from XML configuration
files but it will be converted to the spf-status rule with corresponding arguments. spf-passed will be
changed to spf-status == "Pass" and NOT spf-passed to spf-status != "Pass". You can, however, still
use the spf-passed message filter.
files but it will be converted to the spf-status rule with corresponding arguments. spf-passed will be
changed to spf-status == "Pass" and NOT spf-passed to spf-status != "Pass". You can, however, still
use the spf-passed message filter.