Cisco Cisco Email Security Appliance C370 Notas de publicación
2
Release Notes for Cisco AsyncOS 7.8 for Email
Resolved Issues
Resolved Issues
Note
This section is relevant only if you were using previous versions of AsyncOS for Email.
lists the issues that were resolved in version 7.8 of AsyncOS for Email. Click a Defect ID in the
table for more information about the defect.
Known Issues
lists the known issues in this release of AsyncOS for Email.
Table 1
Resolved Issues in AsyncOS 7.8 for Email
Defect ID
Description
Temporary directories are not cleanly removed when upgrading the Reputation
Engine.
Engine.
Intermittent application fault with certain SSL/TLS connections.
NIC addresses obtained from
snmpwalk
and
ipcheck
commands are different.
Updated MTU is not displayed in
ifconfig
when MTU of an interface is updated
using
etherconfig
command.
SNMP trap interface index incorrectly identifying interface.
Table 2
Known Issues in AsyncOS 7.8 for Email
Defect ID
Description
CSCzv54743 Network configuration lost while reverting back after an AsyncOS for Email
upgrade
You will lose the network configuration of your Email Security appliance if you are
reverting back after an AsyncOS for Email upgrade. If you lose the network
configuration, emails are not delivered until you reset the network configuration by
physically accessing the Email Security appliance. This is observed when you upgrade
AsyncOS for Email from version 7.5.2-203 to 7.6.3-019, and revert back to version
7.5.2-203.
reverting back after an AsyncOS for Email upgrade. If you lose the network
configuration, emails are not delivered until you reset the network configuration by
physically accessing the Email Security appliance. This is observed when you upgrade
AsyncOS for Email from version 7.5.2-203 to 7.6.3-019, and revert back to version
7.5.2-203.
CSCzv39735 Appliance Misses Incoming Connections When Handling Large Messages
The Email Security appliance may not pick up an incoming connection when it’s
processing a very large message (e.g., greater than 30 MB).
processing a very large message (e.g., greater than 30 MB).
CSCzv41250 Message Tracking Returning Messages with a High Number of Recipients Results
in Excessive Memory Usage
The Email Security appliance may run out of memory if you run a Message Tracking
query in the Web UI that returns messages that have a large number of recipients.
query in the Web UI that returns messages that have a large number of recipients.