![]() |
Table Of Contents
Release Notes for the Cisco ASA 5500 Series, Version 8.3(x)
DRAM, Flash Memory, and Failover
ASDM, SSM, SSC, and VPN Compatibility
New Features in Version 8.3(2.25)
New Features in Version 8.3(2)
New Features in Version 8.3(1)
Upgrading the Operating System and ASDM Images
Resolved Caveats in Version 8.3(2)
Resolved Caveats in Version 8.3(1)
Obtaining Documentation and Submitting a Service Request
Release Notes for the Cisco ASA 5500 Series, Version 8.3(x)
Released: August 2010
Note Updated: August 31, 2011
This document contains release information for Cisco ASA 5500 Versions 8.3(1) and 8.3(2).
This document includes the following sections:
•
Obtaining Documentation and Submitting a Service Request
Note
Before you upgrade to 8.3(x), be sure to see the Cisco ASA 5500 Migration Guide for Version 8.3. The following major changes require configuration migration:
•
NAT redesign.
•
Real IP addresses in access rules instead of mapped addresses.
•
Named network objects and service objects.
See also the "Important Notes" section.
Important Notes
•
(For upgrading from Version 8.2 and earlier to Version 8.3(2) and later) NAT exemption (the nat 0 access-list command) is migrated to a twice NAT rule with the unidirectional keyword. The unidirectional keyword only allows traffic on the source network to initiate connections. This migration change was made to fix CSCtf89372. Upgrading to Version 8.3(1) does not add the unidirectional keyword.
Note
Because NAT exemption is normally bidirectional, you might need to remove the unidirectional keyword to restore the original function. Specifically, this change adversely affects many VPN configurations that include NAT exemption rules (see CSCti36048 for this new issue). To avoid manual intervention, we recommend upgrading to 8.3(1) first, and then upgrade to a later release.
If you are impacted by this issue, you will see a syslog message like the following:%ASA-5-305013: Asymmetric NAT rules matched for forward and reverse flows; Connection for icmp src Outside:192.168.1.5 dst inside:10.10.5.20 (type 8, code 0) denied due to NAT reverse path failure
•
To run Version 8.3 in a production environment, you need to upgrade the memory on the Cisco ASA 5505, 5510, 5520, or 5540. See the "Memory Information" section for more information. If you do not install a memory upgrade, you receive the following message upon logging in:
*************************************************************************** *** WARNING *** WARNING *** WARNING *** WARNING *** WARNING ******* ----> Minimum Memory Requirements NOT Met! <----**** Installed RAM: 512 MB** Required RAM: 2048 MB** Upgrade part#: ASA5520-MEM-2GB=**** This ASA does not meet the minimum memory requirements needed to** run this image. Please install additional memory (part number** listed above) or downgrade to ASA version 8.2 or earlier.** Continuing to run without a memory upgrade is unsupported, and** critical system features will not function properly.***************************************************************************•
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.
•
If you are upgrading from a pre-8.2 release, see the 8.2 release notes for downgrade issues after you upgrade the Phone Proxy and MTA instance, or for downgrade issues if you upgrade the activation key with new 8.2 features.
•
When using Clientless SSL VPN Post-SSO parameters for the Citrix Web interface bookmark, Single-Signon (SSO) works, but the Citrix portal is missing the Reconnect and Disconnect buttons. Only the Log Off button shows. When not using SSO over Clientless, all three buttons show up correctly.
Workaround: Use the Cisco HTTP-POST plugin to provide single signon and correct Citrix portal behavior.
•
Connection Profile/Tunnel Group terminology in CLI vs. ASDM—The adaptive security appliance 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 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.
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.3.x. 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.
•
Clientless SSL VPN .NET limitation—Clientless SSL sessions might not properly support .NET framework applications. In some cases you need to enable the application for use with Smart Tunnels; however, there is a chance it could still fail. For example, it might fail when an executable binary (.exe) is created using the .NET framework (CSCsv29942).
•
The adaptive security appliance does not support phone proxy with 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.
•
An IPv6 Site-to-Site tunnel between an adaptive security appliance and an IOS router will fail during phase 2 negotiation. (CSCtd38078)
•
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.
System Requirements
The sections that follow list the system requirements for operating an adaptive security appliance. This section includes the following topics:
•
ASDM, SSM, SSC, and VPN Compatibility
Memory Information
The adaptive security appliance includes DRAM and an internal CompactFlash card. On some models, you can optionally use an external CompactFlash card as well. This section includes the following topics:
•
DRAM, Flash Memory, and Failover
Memory Requirements
Table 1 lists the standard and recommended flash memory and DRAM. Note that the shipping DRAM increased after February 2010; the DRAM requirements for 8.3 and higher match the newer default shipping sizes. See the "Memory Upgrade Kits" section to order an upgrade kit.
Note
If a memory upgrade might be required, the required memory is in bold. See the "Memory Upgrade Kits" section.
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.
Table 1 Standard Memory and Memory Requirements for the Cisco ASA 5500 Series
ASA Model DRAM (Default Shipping) Before Feb. 2010 After Feb. 2010 (Required for 8.3 and Higher)5505
128 MB
256 MB
512 MB3
5510
256 MB
256 MB
1 GB
5520
256 MB
512 MB
2 GB
5540
256 MB
1 GB
2 GB
5550
256 MB
4 GB
4GB
5580-20
1 GB
8 GB
8GB
5580-40
1 GB
12 GB
12 GB
5585-X wih SSP-10
2 GB
N/A
6 GB
5585-X wih SSP-20
2 GB
N/A
12 GB
5585-X wih SSP-40
2 GB
N/A
12 GB
5585-X wih SSP-60
2 GB
N/A
24 GB
1 For the ASA 5510 through 5550, you might need to upgrade the internal flash memory to 512 MB or add external flash memory if you load multiple images of the AnyConnect client along with one or more images of the ASA software, ASDM, client/server plugins, or Cisco Secure Desktop. In particular, you might need to upgrade for multiple AnyConnect 3.0 and higher clients with optional modules. The ASA 5505 does not have a flash memory upgrade available.
2 The default internal flash memory for some models was 64 MB in the past; if you have one of these early units, we recommend upgrading your flash memory to at least the new shipping default.
3 For the ASA 5505, only the Unlimited Hosts license and the Security Plus license with failover enabled require 512 MB; other licenses can use 256 MB.
Memory Upgrade Kits
Table 2 lists the DRAM upgrade kits.
Table 2 DRAM Upgrade Kits
Model Size Part NumberASA 5505
512 MB
ASA5505-MEM-512=
ASA 55101
1 GB
ASA5510-MEM-1GB=
ASA 5520
2 GB
ASA5520-MEM-2GB=
ASA 5540
2 GB
ASA5540-MEM-2GB=
1 If you previously purchased the 512 MB upgrade kit for the ASA 5510 (ASA5510-MEM-512=), you must upgrade to the 1 GB memory upgrade kit to run Version 8.3.
Table 3 lists the CompactFlash upgrade kits available for the ASA 5510 through ASA 5550, for use as internal or external flash memory.
Table 3 CompactFlash Upgrade Kits
Model Size Part NumberASA 5510 through ASA 5550
256 MB
ASA5500-CF-256MB=
ASA 5510 through ASA 5550
512 MB
ASA5500-CF-512MB=
Viewing Flash Memory
You can check the size of internal flash and the amount of free flash memory on the adaptive security appliance 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 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, SSM, SSC, and VPN Compatibility
Table 4 lists information about ASDM, SSM, SSC, and VPN compatibility with the ASA 5500 series.
Table 4 ASDM, SSM, SSC, and VPN Compatibility
Application DescriptionASDM
ASA 5500 Version 8.3 requires ASDM Version 6.3 or later.
For information about ASDM requirements for other releases, see Cisco ASA 5500 Series 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
SSM and SSC applications
For information about SSM and SSC application requirements, see Cisco ASA 5500 Series Hardware and Software Compatibility:
http://www.cisco.com/en/US/docs/security/asa/compatibility/asamatrx.html
New Features
This section lists new features for each maintenance release, and includes the following topics:
•
New Features in Version 8.3(2.25)
•
New Features in Version 8.3(2)
•
New Features in Version 8.3(1)
Note
New, changed, and deprecated syslog messages are listed in Cisco ASA 5500 Series System Log Messages.
New Features in Version 8.3(2.25)
Released: August 31, 2011Table 5 lists the new features for ASA interim Version 8.3(2.25).
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.3(2)
Released: August 2, 2010Table 6 lists the new features forASA Version 8.3(2).
New Features in Version 8.3(1)
Released: March 8, 2010Table 7 lists the new features forASA Version 8.3(1).
Upgrading the Software
Note
Before you upgrade, be sure to see the Cisco ASA 5500 Migration Guide for Version 8.3. The following major changes require configuration migration:
•
NAT redesign.
•
Real IP addresses in access rules instead of mapped addresses.
•
Named network objects and service objects.
The Cisco ASA 5500 Migration Guide for Version 8.3 also describes how to downgrade.
This section describes how to upgrade to the latest version, and includes the following topics:
•
Upgrading the Operating System and ASDM Images
Note
For ASDM procedures, see the ASDM release notes.
Viewing Your Current Version
Use the show version command to verify the software version of your adaptive security appliance.
Upgrading the Operating System and ASDM Images
This section describes how to install the ASDM and operating system (OS) images using TFTP. For FTP or HTTP, see the "Managing Software and Configurations" chapter in Cisco ASA 5500 Series Configuration Guide using the CLI.
We recommend that you upgrade the ASDM image before the OS image. ASDM is backward compatible, so you can upgrade the OS using the new ASDM; however you cannot use an old ASDM image with a new OS.
Detailed Steps
Step 1
If you have a Cisco.com login, you can obtain the OS and ASDM images from the following website:
http://www.cisco.com/cisco/software/navigator.html
Step 2
Back up your configuration file. To print the configuration to the terminal, enter the following command:
hostname# show running-configCopy the output from this command, then paste the configuration in to a text file.
Note
If you are upgrading from a pre-8.3 version, then the running configuration is backed up automatically.
For other methods of backing up, see the "Managing Software and Configurations" chapter in Cisco ASA 5500 Series Configuration Guide using the CLI.
Step 3
Install the new images using TFTP. Enter this command separately for the OS image and the ASDM image:
hostname# copy tftp://server[/path]/filename {disk0:/ | disk1:/}[path/]filenameFor example:
hostname# copy tftp://10.1.1.1/asa830-4-k8.bin disk0:/asa831-k8.bin...hostname# copy tftp://10.1.1.1/asdm-63096.bin disk0:/asdm-631.binIf your adaptive security appliance does not have enough memory to hold two images, overwrite the old image with the new one by specifying the same destination filename as the existing image.
Step 4
To change the OS boot image to the new image name, enter the following commands:
hostname(config)# clear configure boothostname(config)# boot system {disk0:/ | disk1:/}[path/]new_filename
For example:
hostname(config)# clear configure boothostname(config)# boot system disk0:/asa831-k8.binStep 5
To configure the ASDM image to the new image name, enter the following command:
hostname(config)# asdm image {disk0:/ | disk1:/}[path/]new_filename
Step 6
To save the configuration and reload, enter the following commands:
hostname(config)# write memoryhostname(config)# reload
Open Caveats
Table 8 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 this section to the resolved caveats from later releases. For example, if you are running Release 8.3(1), then you need to add the caveats in this section to the resolved caveats from 8.3(2) and later 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.3(2)
•
Resolved Caveats in Version 8.3(1)
Resolved Caveats in Version 8.3(2)
Table 9 lists the resolved caveats for Version 8.3(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/
Resolved Caveats in Version 8.3(1)
Table 10 lists the resolved caveats for Version 8.3(1). 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 the monthly What's New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at:
http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html
Subscribe to the What's New in Cisco Product Documentation as an RSS feed and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free service. Cisco currently supports RSS Version 2.0.
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.
©2011 Cisco Systems, Inc. All rights reserved.