Cisco Cisco Content Security Management Appliance M380 Guia De Resolução De Problemas

Página de 3
Contents
Introduction
Components Used
Background Information
Understand the communication
Troubleshoot delivery from ESA to SMA
Troubleshoot delivery from SMA to ESA
TLS/Certificates
Related Information
Related Cisco Support Community Discussions
Introduction
This document describes how to troubleshoot delivery and connection problems when centralized
policiy, virus and outbreak quarnatine is enabled.
Components Used
The information in this document is based on these software and hardware versions:
Email Security Appliance (ESA) with AsyncOS 8.1 or later
Security Management Appliance (SMA) with AsyncOS 8.0 or later
The information in this document was created from the devices in a specific lab environment. All of
the devices used in this document started with a cleared (default) configuration. If your network is
live, make sure that you understand the potential impact of any command.
Background Information
The Centralized Policy, Virus and Outbreak (PVO) Quarantines feature was introduced in
AsyncOS 8.0 (ESA) / 8.1 (SMA).  This feature has additional network connectivity requirements,
and poses some new challenges for troubleshooting.
Understand the communication
CPQ communication uses SMTP, but with some extra commands for transferring metadata
The SMA will listen for connections on the interface and port defined under Centralized
Services -> Policy, Virus and Outbreak Quarantines.  By default, the port is 7025, but this may
have been changed by the admin user!
The ESA will listen for connections on the interface and port defined under Security Services -
> Policy, Virus and Outbreak Quarantines.  Again, by default, the port is 7025, but this may
have been changed by the admin user!
The SMA also uses SSH (via command client) to get configuration information from the
ESAs.  In particular, this is used when the SMA delivers released emails to the ESA.  The