Cisco Cisco Content Security Management Appliance M680 Notas de publicación
14
Release Notes for Cisco IronPort AsyncOS 8.0 for Security Management
Finding Current Information about Known and Fixed Issues
Finding Current Information about Known and Fixed Issues
Use the Cisco Bug Search Tool to find the most current information about known and fixed defects in
shipping releases.
shipping releases.
Before You Begin
Register for a Cisco account if you do not have one. Go to
.
Procedure
Step 1
Go to
.
Step 2
Log in with your Cisco account credentials.
Step 3
Enter search criteria.
For example, to find all issues fixed in a release:
a.
Click Select from list, then navigate to and select your product:
Cisco Email Security Appliance
Cisco Web Security Appliance
Cisco Content Security Management Appliance
b.
For Releases, enter the AsyncOS release number, such as
8.1.1
.
Note
Known issues on Cisco Email Security Appliances and Cisco Web Security Appliances may
appear in or impact functionality of Cisco Content Security Management Appliances.
appear in or impact functionality of Cisco Content Security Management Appliances.
Step 4
If you have questions or problems, click the Help or Feedback links at the top right side of the tool.
There is also an interactive tour; to view it, click the link in the orange bar above the search fields.
CSCzv96976
SMTP Routes behavior is different on SMA than on ESA
On the Security Management appliance, SMTP Routes are used only for sending alerts and emailed reports
(scheduled or generated on-demand). When multiple SMTP Routes are configured, the SMA provides
failover only, not round-robin.
(scheduled or generated on-demand). When multiple SMTP Routes are configured, the SMA provides
failover only, not round-robin.
CSCzv05651
SMA Cannot Communicate with ESA after AsyncOS Reversion on the ESA
If your Email Security appliance is connected to a Security Management appliance, reverting the version of
AsyncOS on the ESA to a previous version prevents the SMA from communicating with it.
AsyncOS on the ESA to a previous version prevents the SMA from communicating with it.
Workaround: Re-authenticate the SMA’s connection to the ESA.
Table 3
Known Issues
Bug ID
Description