Cisco Cisco Email Security Appliance C370D Release Notes
17
Release Notes for Cisco IronPort AsyncOS 7.5.2 for Email
OL-25139-02
Fixed Issues in Release 7.5
68527
Fixed: Misleading Message When Trying to Run DLP Assessment Wizard in
Cluster Mode.
Cluster Mode.
Previously, AsyncOS displayed an incorrect error message when you attempted to run
DLP Assessment Wizard a clustered environment, stating that the wizard must be run
from the “login host” level. This error message has been corrected. The message now
correctly states that the appliance must be removed from the cluster to run the DLP
Assessment Wizard.
DLP Assessment Wizard a clustered environment, stating that the wizard must be run
from the “login host” level. This error message has been corrected. The message now
correctly states that the appliance must be removed from the cluster to run the DLP
Assessment Wizard.
29829
Fixed: updateconfig Command Does Not Allow User to Specify Interface for
Certain Service Updates.
Certain Service Updates.
Previously, you could not correctly apply which of IP interfaces assigned to the same
physical network interface to use when connecting to the update server. That was a
reason of failed updates/upgrades. This issue has been resolved. Now, when you run
the updateconfig -> setup command and choose which particular IP interface connects
to the update server the selected IP interface is applied properly and updates/upgrades
are always completed successfully.
physical network interface to use when connecting to the update server. That was a
reason of failed updates/upgrades. This issue has been resolved. Now, when you run
the updateconfig -> setup command and choose which particular IP interface connects
to the update server the selected IP interface is applied properly and updates/upgrades
are always completed successfully.
71406
Fixed: Error Occurs When Using the Default Client or Server IP Address for the
packetcapture Predefined Filter.
packetcapture Predefined Filter.
Previously, configuring the client and server IPs addresses for the packetcapture
feature’s predefined filter could result in a configuration error. The error occurred if
an IP address was specified for one of the client or server IP addresses and the default
address was used for the other. For example, if your configuration specified an IP
address for the client IP but used the default IP address for the server IP. In these cases,
AsyncOS saved a comma-separated string value for the packetcapture configuration
instead of a list, which resulted in a error message after saving.
feature’s predefined filter could result in a configuration error. The error occurred if
an IP address was specified for one of the client or server IP addresses and the default
address was used for the other. For example, if your configuration specified an IP
address for the client IP but used the default IP address for the server IP. In these cases,
AsyncOS saved a comma-separated string value for the packetcapture configuration
instead of a list, which resulted in a error message after saving.
This issue has been resolved. When configuring packetcapture in AsyncOS 7.5, the
system uses a comma-separated string for the client and server IP addresses. However,
AsyncOS 7.5 cannot fix a broken, existing XML configuration as there is no single
way to fix the broken packetcapture settings. These settings may let the loadconfig fail
or result into loading inappropriate settings for client or server IP addresses. The
packetcapture will fail to start with these settings and user will have to manually
correct settings using
system uses a comma-separated string for the client and server IP addresses. However,
AsyncOS 7.5 cannot fix a broken, existing XML configuration as there is no single
way to fix the broken packetcapture settings. These settings may let the loadconfig fail
or result into loading inappropriate settings for client or server IP addresses. The
packetcapture will fail to start with these settings and user will have to manually
correct settings using
packetcapture -> setup
command.
Table 4
Resolved Issues in Version 7.5 (continued)
Defect ID
Description