Cisco Cisco Email Security Appliance X1050 Information Guide

Page of 2
Contents
Introduction
What are the requirements for the PVO Migration Wizard when ESA is clustered?
Requirements
Example
Related Information
Related Cisco Support Community Discussions
Introduction
This document describes the requirements for the Policiy, Virus and Outbreak quarantine (PVO)
wizard when clustering is involved on the Email Security Appliance (ESA).
What are the requirements for the PVO Migration Wizard
when ESA is clustered?
To use the Migration Wizrad to move data from clustered ESA to the Security Management
Appliance (SMA) for  the Policy, Virus & Outbreak Quarantine, these requirements must be met:
Note: You can enable centralized policy, virus and outbreak quarantines at any level for
clustered appliances.
Requirements
Before you enable "Centralized policy, virus, and outbreak quarantines" on an Email Security
appliance (ESA) at a particular level (machine, group, or cluster), all appliances that belong to
the same level must first be added to the Security Management appliance
Must use the Administrator account to configure the settings, (not Operator or others) or the
configuration can be set up but the [Enable...] button on the ESA will be grayed out and the
service cannot be enabled
Content and message filters and DLP message actions must be configured at the same level
and not overridden at any level below that level
Centralized policy, virus, and outbreak quarantines settings must be configured at the same
level and not be overridden at any level below the configured level.
Ensure that the interface to be used for communications with the Security Management
appliance has the same name on all appliances in the group or cluster.
Example
If you want to enable centralized policy, virus and outbreak quarantines at the cluster or group
level, but an ESA which is connected to the cluster has these settings defined at the machine
level, you must remove the centralized quarantines settings configured at the machine level before
you can enable the feature at the cluster or group level.
If these are not met, there will be an error similar to this on the SMA side: