![]() |
Table Of Contents
Release Notes for the Cisco ASA 5500 Series, Version 8.2(x)
Downloading Software from Cisco.com
Upgrading Between Major Releases
Upgrading the Phone Proxy and MTA Instance
Activation Key Compatibility When Upgrading
Standard DRAM and Internal Flash Memory
DRAM, Flash Memory, and Failover
ASDM, Module, and VPN Compatibility
New Features in Version 8.2(5.13)
New Features in Version 8.2(5)
New Features in Version 8.2(4.4)
New Features in Version 8.2(4.1)
New Features in Version 8.2(4)
New Features in Version 8.2(3.9)
New Features in Version 8.2(3)
New Features in Version 8.2(2)
New Features in Version 8.2(1)
Resolved Caveats in Version 8.2(5)
Resolved Caveats in Version 8.2(4)
Resolved Caveats in Version 8.2(3)
Resolved Caveats in Version 8.2(2)
Obtaining Documentation and Submitting a Service Request
Release Notes for the Cisco ASA 5500 Series, Version 8.2(x)
Released: May 8, 2009Updated: February 19, 2013This document contains release information for Cisco ASA 5500 Versions 8.2(1) through 8.2(5.13).
This document includes the following sections:
•
Obtaining Documentation and Submitting a Service Request
Important Notes
•
The Advanced Inspection and Prevention Security Services Card (AIP SSC) can take up to 20 minutes to initialize the first time it boots after a new image is applied. This initialization process must complete before configuration changes can be made to the sensor. Attempts to modify and save configuration changes before the initialization completes will result in an error.
•
See the "Upgrading the Software" section for downgrade issues after you upgrade the Phone Proxy and MTA instance, or if you upgrade the activation key with new 8.2 features.
•
For detailed information and FAQs about feature licenses, including shared licenses and temporary licenses, see Managing Feature Licenses for Cisco ASA 5500 Version 8.2 at http://www.cisco.com/en/US/docs/security/asa/asa82/license/license82.html.
•
When using Clientless SSL VPN Post-SSO parameters for the Citrix Web interface bookmark, Single Sign On (SSO) works, but the Citrix portal is missing the Reconnect and Disconnect buttons. Only the Log Off button appears. When not using SSO over Clientless, all three buttons show up correctly.
Workaround: Use the Cisco HTTP-POST plug-in to provide SSO and correct Citrix portal behavior.
•
On the ASA 5510, Version 8.2 uses more base memory than previous releases. This might cause problems for some ASA 5510 users who are currently running low on free memory (as indicated in the show memory command output). If your current show memory command output displays less than 20% free, we recommend upgrading the memory on the ASA 5510 from 256 MB to 1 GB before proceeding with the Version 8.2 upgrade. See the "Memory Requirements" section.
•
On the ASA 5580, Version 8.2 shows increased CPU usage under stressed conditions than Version 8.1.
•
Connection Profile/Tunnel Group terminology in CLI vs. ASDM—The ASA tunnel groups define the initial connection parameters and attributes (such as AAA, client address assignment, and connection alias/group-url) for a remote access VPN session. In the CLI, they are referred to as tunnel groups, whereas in ASDM they are referred to as Connection Profiles. A VPN policy is an aggregation of Connection Profile, Group Policy, and Dynamic Access Policy authorization attributes.
•
Cosmetic startup message issue on the ASA 5585-X—Cisco manufacturing recently discovered a process error that resulted in loading a test build of BIOS firmware on many early shipments of the ASA 5585-X. On the affected units, more text than usual displays on the console during startup before reaching the "rommon>" prompt. Included in the extra output is the following message banner:
CISCO SYSTEMS Spyker Build, TEST build not for Customer ReleaseEmbedded BIOS Version 2.0(7)2 19:59:57 01/04/11While you may see this additional text, there is no functional impact to the ASA operation; you can ignore the additional text. The test build provides additional information that can be used by engineers to pinpoint hardware problems during the manufacturing process. Unfortunately, there is no field-upgradeable resolution to eliminate this message that does not require replacing the hardware.
Hardware with a serial number that falls within the following ranges could be impacted by this cosmetic issue. Note that not all serial numbers within these ranges are impacted.
–
JMX1449xxxx - JMX1520xxxx
–
JAF1450xxxx - JAF1516xxxx (for ASA-SSP-20-K8= only)
Hardware with the following Product IDs for the above serial numbers could be impacted by this cosmetic issue:
–
ASA5585-S20-K8
–
ASA5585-S20-K9
–
ASA5585-S20P20-K8
–
ASA5585-S20P20-K9
–
ASA5585-S20P20XK9
–
ASA5585-S20X-K9
–
ASA-SSP-20-K8=
•
Only 4 GB of memory is available in ASA 8.2(5) for the ASA 5580 and 5585-X platforms.
•
All available memory in multi-core platforms (ASA 5580 and 5585-X) in ASA 8.2(5) are also available in ASA 8.4(1). To take advantage of the enhanced capability, you should upgrade your devices to the ASA 8.4.4(1) release.
Limitations and Restrictions
•
The SSL SHA-2 digital signature capability for authentication of AnyConnect SSL VPN sessions (Versions 2.5.1 and above) is not currently supported on ASA Version 8.2.4, yet it is supported in all 8.2.4.x interim releases. The feature was introduced in ASA interim Version 8.2.3.9.
•
Stateful Failover with Phone Proxy—When using Stateful Failover with phone proxy, information is not passed to the standby unit; when the active unit goes down, the call fails, media stops flowing, and the call must be re-established.
•
No .NET over Clientless sessions—Clientless sessions do not support .NET framework applications (CSCsv29942).
•
The ASA does not support phone proxy and CIPC for remote access.
•
The AIP SSC-5 does not support virtualization, unretiring default retired signatures, creating custom signatures, adding signatures, cloning signatures, or anomaly detection.
•
The ASA cannot fully support domain-based DFS. To support this, the ASA would need to join the Active Directory and query the Active Directory server for DFS referral. Instead the ASA sends the DFS referral to the DNS servers configured for the users. Since the AD server is the DNS server in most cases, the majority of customer configurations are covered.
•
(ASA 5510, ASA 5520, ASA 5540, and ASA 5550 only) We strongly recommend that you enable hardware processing using the crypto engine large-mod-accel command instead of software for large modulus operations such as 2048-bit certificates and DH5 keys. If you continue to use software processing for large keys, you could experience significant performance degradation due to slow session establishment for IPsec and SSL VPN connections. We recommend that you initially enable hardware processing during a low-use or maintenance period to minimize a temporary packet loss that can occur during the transition of processing from software to hardware.
Note
For the ASA 5540 and ASA 5550 using SSL VPN, in specific load conditions, you may want to continue to use software processing for large keys. If VPN sessions are added very slowly and the ASA runs at capacity, then the negative impact to data throughput is larger than the positive impact for session establishment.
The ASA 5580/5585-X platforms already integrate this capability; therefore, crypto engine commands are not applicable on these platforms.•
Only users with a privilege level of 15 may copy files to the ASA using the the secure copy protocol (SCP).
Upgrading the Software
To upgrade to 8.2, see the "Managing Software and Configurations" chapter in Cisco ASA 5500 Series Configuration Guide using the CLI. Be sure to back up your configuration before upgrading.
Use the show version command to verify the software version of your adaptive security appliance. Alternatively, the software version appears on the ASDM home page.
This section includes the following topics:
•
Downloading Software from Cisco.com
•
Upgrading Between Major Releases
•
Upgrading the Phone Proxy and MTA Instance
•
Activation Key Compatibility When Upgrading
Downloading Software from Cisco.com
If you have a Cisco service contract, you can obtain software from the following website:
http://www.cisco.com/cisco/software/navigator.html
Upgrading Between Major Releases
To ensure that your configuration updates correctly, you must upgrade to each major release in turn. Therefore, to upgrade from Version 7.0 to Version 8.2, first upgrade from 7.0 to 7.1, then from 7.1 to 7.2, and finally from Version 7.2 to Version 8.2 (8.1 was only available on the ASA 5580).
Upgrading the Phone Proxy and MTA Instance
In Version 8.0(4), you configured a global media-termination address (MTA) on the ASA. In Version 8.2, you can now configure MTAs for individual interfaces (with a minimum of two MTAs). As a result of this enhancement, the old CLI has been deprecated. You can continue to use the old configuration if desired. However, if you need to change the configuration at all, only the new configuration method is accepted; you cannot later restore the old configuration.
Note
If you need to maintain downgrade compatibility, you should keep the old configuration as is.
To upgrade the Phone Proxy, perform the following steps:
Step 1
Create the MTA instance to apply to the phone proxy instance for this release. See "Creating the Media Termination Instance" section in the Cisco ASA 5500 Series Configuration Guide using the CLI.
Step 2
To modify the existing Phone Proxy, enter the following command:
hostname(config)# phone-proxy phone_proxy_nameWhere phone_proxy_name is the name of the existing Phone Proxy.
Step 3
To remove the configured MTA on the phone proxy, enter the following command:
hostname(config)# no media-termination address ip_addressStep 4
Apply the new MTA instance to the phone proxy by entering the following command:
hostname(config)# media-termination instance_nameWhere instance_name is the name of the MTA that you created in Step 1.
Activation Key Compatibility When Upgrading
Your activation key remains compatible if you upgrade to Version 8.2 or later, and also if you later downgrade. After you upgrade, if you activate additional feature licenses that were introduced before 8.2, then the activation key continues to be compatible with earlier versions if you downgrade. However if you activate feature licenses that were introduced in 8.2 or later, then the activation key is not backwards compatible. If you have an incompatible license key, then see the following guidelines:
•
If you previously entered an activation key in an earlier version, then the adaptive security appliance uses that key (without any of the new licenses you activated in Version 8.2 or later).
•
If you have a new system and do not have an earlier activation key, then you need to request a new activation key compatible with the earlier version.
System Requirements
The sections that follow list the system requirements for operating an adaptive security appliance. This section includes the following topics:
•
ASDM, Module, and VPN Compatibility
Memory Requirements
The adaptive security appliance includes DRAM and an internal CompactFlash card. You can optionally use an external CompactFlash card as well. This section includes the following topics:
•
Standard DRAM and Internal Flash Memory
•
DRAM, Flash Memory, and Failover
Standard DRAM and Internal Flash Memory
Table 1 lists the standard memory shipped with the adaptive security appliance.
Table 1 Standard Memory
ASA Model Default DRAM Before Feb. 2010 Default DRAM After Feb. 20105505
256
512
5510
2561
1 GB
5520
512
2 GB
5540
1024
2 GB
5550
4096
4 GB
5580
4096
8 GB
1 For the ASA 5510—Version 8.2 uses more base memory than previous releases, which might cause problems for some ASA 5510 users who are currently running low on free memory (as indicated in the show memory output). If your current show memory output displays less than 20% free, we recommend upgrading the memory on the ASA 5510 from 256 MB to 1 GB before proceeding with the release 8.2 upgrade.
Note
If your ASA has only 64 MB of internal CompactFlash (which shipped standard in the past), you should not store multiple system images, or multiple images of the new AnyConnect VPN client components, client/server plugins, or Cisco Secure Desktop.
ASA 5520 and ASA 5540 adaptive security appliances that were manufactured before August 2011 have 4 DIMM sockets. ASA 5520 and ASA 5540 adaptive security appliances manufactured after this date have 2 DIMM sockets.
Memory Upgrade Kits
Table 2 shows the memory upgrade kits that are available from Cisco with their corresponding part numbers.
Table 3 shows the CompactFlash upgrades that are available from Cisco with their corresponding part numbers.
Viewing Flash Memory
You can check the size of internal flash and the amount of free flash memory on the ASA by doing the following:
•
ASDM—Choose Tools > File Management. The amounts of total and available flash memory appear on the bottom left in the pane.
•
CLI—In privileged EXEC mode, enter the dir command. The amounts of total and available flash memory appear on the bottom of the output.
For example:
hostname # dir
Directory of disk0:/43 -rwx 14358528 08:46:02 Feb 19 2007 cdisk.bin136 -rwx 12456368 10:25:08 Feb 20 2007 asdmfile58 -rwx 6342320 08:44:54 Feb 19 2007 asdm-600110.bin61 -rwx 416354 11:50:58 Feb 07 2007 sslclient-win-1.1.3.173.pkg62 -rwx 23689 08:48:04 Jan 30 2007 asa1_backup.cfg66 -rwx 425 11:45:52 Dec 05 2006 anyconnect70 -rwx 774 05:57:48 Nov 22 2006 cvcprofile.xml71 -rwx 338 15:48:40 Nov 29 2006 tmpAsdmCustomization43040652672 -rwx 32 09:35:40 Dec 08 2006 LOCAL-CA-SERVER.ser73 -rwx 2205678 07:19:22 Jan 05 2007 vpn-win32-Release-2.0.0156-k9.pkg74 -rwx 3380111 11:39:36 Feb 12 2007 securedesktop_asa_3_2_0_56.pkg62881792 bytes total (3854336 bytes free)hostname #
DRAM, Flash Memory, and Failover
In a failover configuration, the two units must have the same hardware configuration, must be the same model, must have the same number and types of interfaces, must have the same feature licenses, and must have the same amount of DRAM. You do not have to have the same amount of flash memory. For more information, see the failover chapters in Cisco ASA 5500 Series Configuration Guide using the CLI.
Note
If you use two units with different flash memory sizes, make sure that the unit with the smaller flash memory has enough space for the software images and configuration files.
ASDM, Module, and VPN Compatibility
Table 4 lists information about ASDM, Module, and VPN compatibility with the ASA 5500 series.
Table 4 ASDM, SSM, SSC, and VPN Compatibility
Application DescriptionASDM
The following list shows the ASA and ASDM compatibility:
•
ASA 8.2(1) requires ASDM 6.2(1) or later
•
ASA 8.2(2) requires ASDM 6.2(5) or later
•
ASA 8.2(3) requires ASDM 6.3(4) or later
•
ASA 8.2(4) requires ASDM 6.3(5) or later
•
ASA 8.2(5) requires ASDM 6.4(3) or later
For information about ASDM requirements for other releases, see Cisco ASA Hardware and Software Compatibility:
http://www.cisco.com/en/US/docs/security/asa/compatibility/asamatrx.html
VPN
For the latest OS and browser test results, see the Supported VPN Platforms, Cisco ASA 5500 Series:
http://www.cisco.com/en/US/docs/security/asa/compatibility/asa-vpn-compatibility.html
Module applications
For information about SSM and SSC application requirements, see Cisco ASA Hardware and Software Compatibility:
http://www.cisco.com/en/US/docs/security/asa/compatibility/asamatrx.html
New Features
Note
New, changed, and deprecated syslog messages are listed in Cisco ASA 5500 Series System Log Messages.
This section includes the following topics:
•
New Features in Version 8.2(5.13)
•
New Features in Version 8.2(5)
•
New Features in Version 8.2(4.4)
•
New Features in Version 8.2(4.1)
•
New Features in Version 8.2(4)
•
New Features in Version 8.2(3.9)
•
New Features in Version 8.2(3)
•
New Features in Version 8.2(2)
•
New Features in Version 8.2(1)
New Features in Version 8.2(5.13)
Released: September 18, 2011Table 5 lists the new features for ASA interim Version 8.2(5.13).
Note
We recommend that you upgrade to a Cisco.com-posted ASA interim release only if you have a specific problem that it resolves. If you decide to run an interim release in a production environment, keep in mind that only targeted testing is performed on interim releases. Interim releases are fully supported by Cisco TAC and will usually remain on the download site only until the next maintenance release is available. If you choose to run an interim release, we strongly encourage you to upgrade to a fully-tested maintenance or feature release when it becomes available.
We will document interim release features at the time of the next maintenance or feature release. For a list of resolved caveats for each ASA interim release, see the interim release notes available on the Cisco.com software download site.
New Features in Version 8.2(5)
Released: May 23, 2011Table 6 lists the new features for ASA Version 8.2(5).
New Features in Version 8.2(4.4)
Released: March 4, 2011Table 7 lists the new features for ASA Version 8.2(4.4).
Note
We recommend that you upgrade to a Cisco.com-posted interim release only if you have a specific problem that it resolves. If you decide to run an interim release in a production environment, keep in mind that only targeted testing is performed on interim releases. Interim releases are fully supported by Cisco TAC and will remain on the download site only until the next maintenance release is available. If you choose to run an interim release, we strongly encourage you to upgrade to a fully-tested maintenance or feature release when it becomes available. We will document interim release features at the time of the next maintenance or feature release. For a list of resolved caveats for each interim release, see the Cisco ASA Interim Release Notes available on the Cisco.com software download site.
New Features in Version 8.2(4.1)
Released: January 18, 2011Table 8 lists the new features for ASA Version 8.2(4.1).
Note
We recommend that you upgrade to a Cisco.com-posted interim release only if you have a specific problem that it resolves. If you decide to run an interim release in a production environment, keep in mind that only targeted testing is performed on interim releases. Interim releases are fully supported by Cisco TAC and will remain on the download site only until the next maintenance release is available. If you choose to run an interim release, we strongly encourage you to upgrade to a fully-tested maintenance or feature release when it becomes available. We will document interim release features at the time of the next maintenance or feature release. For a list of resolved caveats for each interim release, see the Cisco ASA Interim Release Notes available on the Cisco.com software download site.
New Features in Version 8.2(4)
Released: December 15, 2010Table 9 lists the new features for ASA Version 8.2(4).
New Features in Version 8.2(3.9)
Released: November 2, 2010Table 10 lists the new features for ASA interim Version 8.2(3.9).
Note
We recommend that you upgrade to a Cisco.com-posted interim release only if you have a specific problem that it resolves. If you decide to run an interim release in a production environment, keep in mind that only targeted testing is performed on interim releases. Interim releases are fully supported by Cisco TAC and will remain on the download site only until the next maintenance release is available. If you choose to run an interim release, we strongly encourage you to upgrade to a fully-tested maintenance or feature release when it becomes available. We will document interim release features at the time of the next maintenance or feature release. For a list of resolved caveats for each interim release, see the Cisco ASA Interim Release Notes available on the Cisco.com software download site.
New Features in Version 8.2(3)
Released: August 9, 2010Table 11Table 11 lists the new features for ASA Version 8.2(3).
New Features in Version 8.2(2)
Released: January 11, 2010Table 12 lists the new features forASA Version 8.2(2).
New Features in Version 8.2(1)
Released: May 6, 2009Hi
Table 13 lists the new features for ASA Version 8.2(1).
Table 13 New Features for ASA Version 8.2(1)
Feature Description Remote Access FeaturesOne Time Password Support for ASDM Authentication
ASDM now supports administrator authentication using one time passwords (OTPs) supported by RSA SecurID (SDI). This feature addresses security concerns about administrators authenticating with static passwords.
New session controls for ASDM users include the ability to limit the session time and the idle time. When the password used by the ASDM administrator times out, ASDM prompts the administrator to re-authenticate.
The following commands were introduced: http server idle-timeout and http server session-timeout. The http server idle-timeout default is 20 minutes, and can be increased up to a maximum of 1440 minutes.
Pre-fill Username from Certificate
The pre-fill username feature enables the use of a username extracted from a certificate for username/password authentication. With this feature enabled, the username is "pre-filled" on the login screen, with the user being prompted only for the password. To use this feature, you must configure both the pre-fill username and the username-from-certificate commands in tunnel-group configuration mode.
The double-authentication feature is compatible with the pre-fill username feature, as the pre-fill username feature can support extracting a primary username and a secondary username from the certificate to serve as the usernames for double authentication when two usernames are required. When configuring the pre-fill username feature for double authentication, the administrator uses the following new tunnel-group general-attributes configuration mode commands:
•
secondary-pre-fill-username—Enables username extraction for Clientless or AnyConnect client connection.
•
secondary-username-from-certificate—Allows for extraction of a few standard DN fields from a certificate for use as a username.
Double Authentication
The double authentication feature implements two-factor authentication for remote access to the network, in accordance with the Payment Card Industry Standards Council Data Security Standard. This feature requires that the user enter two separate sets of login credentials at the login page. For example, the primary authentication might be a one-time password, and the secondary authentication might be a domain (Active Directory) credential. If either authentication fails, the connection is denied.
Both the AnyConnect VPN client and Clientless SSL VPN support double authentication. The AnyConnect client supports double authentication on Windows computers (including supported Windows Mobile devices and Start Before Logon), Mac computers, and Linux computers. The IPsec VPN client, SVC client, cut-through-proxy authentication, hardware client authentication, and management authentication do not support double authentication.
Double authentication requires the following new tunnel-group general-attributes configuration mode commands:
•
secondary-authentication-server-group—Specifies the secondary AAA server group, which cannot be an SDI server group.
•
secondary-username-from-certificate—Allows for extraction of a few standard DN fields from a certificate for use as a username.
•
secondary-pre-fill-username—Enables username extraction for Clientless or AnyConnect client connection.
•
authentication-attr-from-server—Specifies which authentication server authorization attributes are applied to the connection.
•
authenticated-session-username—Specifies which authentication username is associated with the session.
Note
The RSA/SDI authentication server type cannot be used as the secondary username/password credential. It can only be used for primary authentication.
AnyConnect Essentials
AnyConnect Essentials is a separately licensed SSL VPN client, entirely configured on the ASA, that provides the full AnyConnect capability, with the following exceptions:
•
No CSD (including HostScan/Vault/Cache Cleaner)
•
No clientless SSL VPN
•
Optional Windows Mobile Support
The AnyConnect Essentials client provides remote end users running Microsoft Windows Vista, Windows Mobile, Windows XP or Windows 2000, Linux, or Macintosh OS X, with the benefits of a Cisco SSL VPN client.
To configure AnyConnect Essentials, the administrator uses the following command:
anyconnect-essentials—Enables the AnyConnect Essentials feature. If this feature is disabled (using the no form of this command), the SSL Premium license is used. This feature is enabled by default.
Note
This license cannot be used at the same time as the shared SSL VPN premium license.
Disabling Cisco Secure Desktop per Connection Profile
When enabled, Cisco Secure Desktop automatically runs on all computers that make SSL VPN connections to the ASA. This new feature lets you exempt certain users from running Cisco Secure Desktop on a per connection profile basis. It prevents the detection of endpoint attributes for these sessions, so you might need to adjust the Dynamic Access Policy (DAP) configuration.
CLI: [no] without-csd command
Note
"Connect Profile" in ASDM is also known as "Tunnel Group" in the CLI. Additionally, the group-url command is required for this feature. If the SSL VPN session uses connection-alias, this feature will not take effect.
Certificate Authentication Per Connection Profile
Previous versions supported certificate authentication for each ASA interface, so users received certificate prompts even if they did not need a certificate. With this new feature, users receive a certificate prompt only if the connection profile configuration requires a certificate. This feature is automatic; the ssl certificate authentication command is no longer needed, but the ASA retains it for backward compatibility.
EKU Extensions for Certificate Mapping
This feature adds the ability to create certificate maps that look at the Extended Key Usage extension of a client certificate and use these values in determining what connection profile the client should use. If the client does not match that profile, it uses the default group. The outcome of the connection then depends on whether or not the certificate is valid and the authentication settings of the connection profile.
The following command was introduced: extended-key-usage.
SSL VPN SharePoint Support for Win 2007 Server
Clientless SSL VPN sessions now support Microsoft Office SharePoint Server 2007.
Shared license for SSL VPN sessions
You can purchase a shared license with a large number of SSL VPN sessions and share the sessions as needed among a group of ASAs by configuring one of the ASAs as a shared license server, and the rest as clients. The following commands were introduced: license-server commands (various), show shared license.
Note
This license cannot be used at the same time as the AnyConnect Essentials license.
Firewall FeaturesTCP state bypass
If you have asymmetric routing configured on upstream routers, and traffic alternates between two ASAs, then you can configure TCP state bypass for specific traffic. The following command was introduced: set connection advanced tcp-state-bypass.
Per-Interface IP Addresses for the Media-Termination Instance Used by the Phone Proxy
In Version 8.0(4), you configured a global media-termination address (MTA) on the ASA. In Version 8.2, you can now configure MTAs for individual interfaces (with a minimum of two MTAs). As a result of this enhancement, the old CLI has been deprecated. You can continue to use the old configuration if desired. However, if you need to change the configuration at all, only the new configuration method is accepted; you cannot later restore the old configuration.
Displaying the CTL File for the Phone Proxy
The Cisco Phone Proxy feature includes the show ctl-file command, which shows the contents of the CTL file used by the phone proxy. Using the show ctl-file command is useful for debugging when configuring the phone proxy instance.
This command is not supported in ASDM.
Clearing Secure-phone Entries from the Phone Proxy Database
The Cisco Phone Proxy feature includes the clear phone-proxy secure-phones command, which clears the secure-phone entries in the phone proxy database. Because secure IP phones always request a CTL file upon bootup, the phone proxy creates a database that marks the IP phones as secure. The entries in the secure phone database are removed after a specified configured timeout (via the timeout secure-phones command). Alternatively, you can use the clear phone-proxy secure-phones command to clear the phone proxy database without waiting for the configured timeout.
This command is not supported in ASDM.
H.239 Message Support in H.323 Application Inspection
In this release, the ASA supports the H.239 standard as part of H.323 application inspection. H.239 is a standard that provides the ability for H.300 series endpoints to open an additional video channel in a single call. In a call, an endpoint (such as a video phone), sends a channel for video and a channel for data presentation. The H.239 negotiation occurs on the H.245 channel. The ASA opens a pinhole for the additional media channel. The endpoints use open logical channel message (OLC) to signal a new channel creation. The message extension is part of H.245 version 13. The decoding and encoding of the telepresentation session is enabled by default. H.239 encoding and decoding is preformed by ASN.1 coder.
Processing H.323 Endpoints When the Endpoints Do Not Send OLCAck
H.323 application inspection has been enhanced to process common H.323 endpoints. The enhancement affects endpoints using the extendedVideoCapability OLC with the H.239 protocol identifier. Even when an H.323 endpoint does not send OLCAck after receiving an OLC message from a peer, the ASA propagates OLC media proposal information into the media array and opens a pinhole for the media channel (extendedVideoCapability).
IPv6 in transparent firewall mode
Transparent firewall mode now participates in IPv6 routing. Prior to this release, the ASA could not pass IPv6 traffic in transparent mode. You can now configure an IPv6 management address in transparent mode, create IPv6 access lists, and configure other IPv6 features; the ASA recognizes and passes IPv6 packets.
All IPv6 functionality is supported unless specifically noted.
Botnet Traffic Filter
Malware is malicious software that is installed on an unknowing host. Malware that attempts network activity such as sending private data (passwords, credit card numbers, key strokes, or proprietary data) can be detected by the Botnet Traffic Filter when the malware starts a connection to a known bad IP address. The Botnet Traffic Filter checks incoming and outgoing connections against a dynamic database of known bad domain names and IP addresses, and then logs any suspicious activity. You can also supplement the dynamic database with a static database by entering IP addresses or domain names in a local "blacklist" or "whitelist."
Note
This feature requires the Botnet Traffic Filter license. See the following licensing document for more information:
http://www.cisco.com/en/US/docs/security/asa/asa82/license/license82.htmlThe following commands were introduced: dynamic-filter commands (various), and the inspect dns dynamic-filter-snoop keyword.
AIP SSC card for the ASA 5505
The AIP SSC offers IPS for the ASA 5505 ASA. Note that the AIP SSM does not support virtual sensors. The following commands were introduced: allow-ssc-mgmt, hw-module module ip, and hw-module module allow-ip.
IPv6 support for IPS
You can now send IPv6 traffic to the AIP SSM or SSC when your traffic class uses the match any command, and the policy map specifies the ips command.
Management FeaturesSNMP version 3 and encryption
This release provides DES, 3DES, or AES encryption and support for SNMP Version 3, the most secure form of the supported security models. This version allows you to configure authentication characteristics by using the User-based Security Model (USM).
The following commands were introduced:
•
show snmp engineid
•
show snmp group
•
show snmp-server group
•
show snmp-server user
•
snmp-server group
•
snmp-server user
The following command was modified:
•
snmp-server host
NetFlow
This feature was introduced in Version 8.1(1) for the ASA 5580; this version introduces the feature to the other platforms. The new NetFlow feature enhances the ASA logging capabilities by logging flow-based events through the NetFlow protocol.
Routing FeaturesMulticast NAT
The ASA now offers Multicast NAT support for group addresses.
Troubleshooting FeaturesCoredump functionality
A coredump is a snapshot of the running program when the program has terminated abnormally. Coredumps are used to diagnose or debug errors and save a crash for later or off-site analysis. Cisco TAC may request that users enable the coredump feature to troubleshoot application or system crashes on the ASA.
To enable coredump, use the coredump enable command.
Open Caveats
Table 14 contains open caveats in the latest maintenance release.
If you are running an older release, and you need to determine the open caveats for your release, then add the caveats in these sections to the resolved caveats from later releases. For example, if you are running Release 8.2(1), then you need to add the caveats in this section to the resolved caveats from 8.2(2) and above to determine the complete list of open caveats.
If you are a registered Cisco.com user, view more information about each caveat using the Bug Toolkit at the following website:
http://tools.cisco.com/Support/BugToolKit/
Resolved Caveats
This section includes the following topics:
•
Resolved Caveats in Version 8.2(5)
•
Resolved Caveats in Version 8.2(4)
•
Resolved Caveats in Version 8.2(3)
•
Resolved Caveats in Version 8.2(2)
Resolved Caveats in Version 8.2(5)
The caveats listed in Table 15 were resolved in software Version 8.2(5). If you are a registered Cisco.com user you can view more information about each caveat using the Bug Toolkit at the following website:
http://tools.cisco.com/Support/BugToolKit
Resolved Caveats in Version 8.2(4)
The caveats listed in Table 16 were resolved in software Version 8.2(4). If you are a registered Cisco.com user, view more information about each caveat using the Bug Toolkit at the following website:
http://tools.cisco.com/Support/BugToolKit/
Resolved Caveats in Version 8.2(3)
The caveats listed in Table 17 were resolved in software Version 8.2(3). If you are a registered Cisco.com user, view more information about each caveat using the Bug Toolkit at the following website:
http://tools.cisco.com/Support/BugToolKit/
Resolved Caveats in Version 8.2(2)
The caveats listed in Table 18 were resolved in software Version 8.2(2). If you are a registered Cisco.com user, view more information about each caveat using the Bug Toolkit at the following website:
http://tools.cisco.com/Support/BugToolKit/
Related Documentation
For additional information on the adaptive security appliance, see Navigating the Cisco ASA 5500 Series Documentation:
http://www.cisco.com/en/US/docs/security/asa/roadmap/asaroadmap.html
Obtaining Documentation and Submitting a Service Request
For information on obtaining documentation, submitting a service request, and gathering additional information, see What's New in Cisco Product Documentation at: http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html.
Subscribe to What's New in Cisco Product Documentation, which lists all new and revised Cisco technical documentation, as an RSS feed and deliver content directly to your desktop using a reader application. The RSS feeds are a free service.
This document is to be used in conjunction with the documents listed in the "Related Documentation" section.
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1110R)
Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental.
©2009-2013 Cisco Systems, Inc. All rights reserved.