76-28
Cisco ASA 5500 Series Configuration Guide using ASDM
Chapter 76 Configuring Logging
Feature History for Logging
Enhanced logging and
connection blocking
8.3(2) When you configure a syslog server to use TCP, and the syslog server is
unavailable, the ASA blocks new connections that generate syslog messages
until the server becomes available again (for example, VPN, firewall, and
cut-through-proxy connections). This feature has been enhanced to also block
new connections when the logging queue on the ASA is full; connections resume
when the logging queue is cleared.
This feature was added for compliance with Common Criteria EAL4+. Unless
required, we recommended allowing connections when syslog messages cannot
be sent or received. To allow connections, continue to check the Allow user
traffic to pass when TCP syslog server is down check box on the Configuration
> Device Management > Logging > Syslog Servers pane.
We introduced the following syslog messages: 414005, 414006, 414007, and
414008.
We did not modify any ASDM screens.
Syslog message filtering
and sorting
8.4(1) Support has been added for the following:
• Syslog message filtering based on multiple text strings that correspond to
various columns
• Creation of custom filters
• Column sorting of messages. For detailed information, see the ASDM
configuration guide.
We modified the following screens:
Monitoring > Logging > Real-Time Log Viewer > View.
Monitoring > Logging > Log Buffer Viewer > View.
This feature interoperates with all ASA versions.
Table 76-2 Feature History for Logging (continued)
Feature Name
Platform
Releases Feature Information