![]() |
Table Of Contents
Cisco ASA 5580 Series Release Notes Version 8.1(2)
Determining the Software Version
Installing or Upgrading Cisco Secure Desktop
Resolved Caveats - Version 8.1(2)
Obtaining Documentation and Submitting a Service Request
Cisco ASA 5580 Series Release Notes Version 8.1(2)
April 6, 2009
These release notes describe the features and caveats for Cisco ASA 5580 software Version 8.1(2). This document includes the following sections:
•
Obtaining Documentation and Submitting a Service Request
System Requirements
This section lists the system requirements for operating an adaptive security appliance, and includes the following topics:
•
Determining the Software Version
•
Installing or Upgrading Cisco Secure Desktop
Supported Models
Software Version 8.1(2) supports the following platform models:
•
ASA 5580-20
•
ASA 5580-40
Management Support
Software Version 8.1(2) is supported by ASDM Version 6.1(5).
Memory Requirements
Table 1 lists the DRAM memory requirements for the adaptive security appliance. The memory listed in this table is the default value that ships with each adaptive security appliance.
Note
On both the ASA 5580-20 and the ASA 5580-40 adaptive security appliances only 4 GB of memory is available for features. The rest are reserved or used by the OS. The show memory command will only display values relative to 4GB.
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 at the bottom of the output.
For example:
hostname # dirDirectory of disk0:/2 drwx 4096 11:22:00 Dec 01 2006 csco_config43 -rwx 14358528 08:46:02 Feb 19 2007 cdisk.bin44 -rwx 4634 14:32:48 Sep 17 2004 first-backup45 -rwx 4096 09:55:02 Sep 21 2004 fsck-245146 -rwx 4096 09:55:02 Sep 21 2004 fsck-250547 -rwx 774 10:48:04 Nov 21 2006 profile.tmpl48 -rwx 406963 12:45:34 Feb 06 2007 svc3 drwx 8192 03:35:24 Feb 02 2007 log49 drwx 4096 07:10:54 Aug 09 2006 150 -rwx 21601 14:20:40 Dec 17 2004 tftp51 -rwx 17489 06:36:40 Dec 06 2006 custom.xml136 -rwx 12456368 10:25:08 Feb 20 2007 asdmfile53 -rwx 20498 13:04:54 Feb 12 2007 tomm_english54 drwx 4096 14:18:56 Jan 14 2007 sdesktop56 -rwx 14358528 08:32:30 Feb 19 2007 asa800-215-k8.bin57 -rwx 10971 09:38:54 Apr 20 2006 cli.lua58 -rwx 6342320 08:44:54 Feb 19 2007 asdm-600110.bin59 -rwx 0 04:38:52 Feb 12 2007 LOCAL-CA-SERVER.udb60 -rwx 322 15:47:42 Nov 29 2006 tmpAsdmCustomization18486124008 -rwx 65111 10:27:48 Feb 20 2007 tomm_backup.cfg61 -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.cfg63 -rwx 45106 07:19:18 Feb 12 2007 securedesktop_asa_3_2_0_54.pkg64 -rwx 224 01:22:44 Oct 02 2006 LOCAL-CA-SERVER.crl65 drwx 4096 12:37:24 Feb 20 2007 LOCAL-CA-SERVER66 -rwx 425 11:45:52 Dec 05 2006 anyconnect67 -rwx 1555 10:18:04 Sep 29 2006 LOCAL-CA-SERVER_00001.p1268 -rwx 0 12:33:54 Oct 01 2006 LOCAL-CA-SERVER.cdb69 -rwx 3384309 07:21:46 Feb 12 2007 securedesktop_asa_3_2_0_57.pkg70 -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 #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, and must have the same amount of RAM. For more information, see the Configuring Failover" chapter in the Cisco Security Appliance Command Line Configuration Guide.
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.
Determining the Software Version
Use the show version command to verify the software version of your adaptive security appliance. Alternatively, the software version appears on the Cisco ASDM home page.
Downloading the Software
You can download the software from the following URL:
http://www.cisco.com/cisco/software/navigator.html
To download the software to flash memory, choose one of the following commands for the appropriate download server type:
•
To copy from a TFTP server, enter the following command:
hostname# copy tftp://server[/path]/filename {flash:/ | disk0:/ | disk1:/}[path/]filenameYou can enter flash:/ or disk0:/ for the internal flash memory on the adaptive security appliance. The disk1:/ keyword represents the external flash memory on the adaptive security appliance.
•
To copy from an FTP server, enter the following command:
hostname# copy ftp://[user[:password]@]server[/path]/filename {flash:/ | disk0:/ | disk1:/}[path/]filename•
To copy from an HTTP or HTTPS server, enter the following command:
hostname# copy http[s]://[user[:password]@]server[:port][/path]/filename {flash:/ | disk0:/ | disk1:/}[path/]filename•
To use secure copy, first enable SSH, then enter the following command:
hostname# ssh scopy enableThen from a Linux client, enter the following command:
scp -v -pw password filename username@asa_addressThe -v specifies verbose. If -pw is not specified, you are prompted for a password.
Installing or Upgrading Cisco Secure Desktop
Cisco Secure Desktop Release 3.2 requires ASA Version 8.1. You do not need to restart the adaptive security appliance after you install or upgrade Cisco Secure Desktop.
Note
Archive and delete the Secure Desktop desktop/data.xml configuration file before upgrading to Cisco Secure Desktop 3.2. To create a clean configuration file, uninstall Cisco Secure Desktop before reinstalling it.
The expanded flexibility provided by a prelogin assessment sequence editor, and replacement of the Cisco Secure Desktop feature policies with a dynamic access policy (DAP) configured on the adaptive security appliance, are incompatible with Cisco Secure Desktop 3.1.1 configurations. Cisco Secure Desktop automatically inserts a new, default configuration file when it detects that one is not present.
For consistency with the previous release notes, these instructions provide the CLI commands needed to install Secure Desktop. You may, however, prefer to use ASDM. To do so, choose Configuration > Remote Access VPN > Secure Desktop Manager > Setup and click Help.
To install or upgrade the Cisco Secure Desktop software, perform the following steps:
Step 1
Download the latest Cisco Secure Desktop package file from the following website and install it on the flash memory card of the adaptive security appliance:
http://www.cisco.com/cisco/software/navigator.html
Step 2
Enter the following commands to access webvpn configuration mode:
hostname# config terminalhostname(config)# webvpnhostname(config-webvpn)#Step 3
To validate the Cisco Secure Desktop distribution package and add it to the running configuration, enter the following command in webvpn configuration mode:
hostname(config-webvpn)# csd image disk0:/securedesktop_asa_3_2_0_build.pkghostname(config-webvpn)#Step 4
To enable Cisco Secure Desktop for management and remote user access, use the csd enable command in webvpn configuration mode. To disable Cisco Secure Desktop, use the no form of this command.
hostname(config-webvpn)# csd enablehostname(config-webvpn)#
New Features
Released: October 10, 2008Table 2 lists the new features forASA Version 8.1(2). This ASA software version is only supported on the ASA 5580.
SNMP Changes
This section describes the updated approach used by SNMP to display adaptive security appliance interfaces, and the additional link state traps that are sent for interfaces.
Before Version 7.2(5)/8.0(4)/8.1(2), SNMP only provided information about interfaces that were configured using the nameif command. For example, SNMP only sent traps and performed walks on the IF MIB and IP MIB for interfaces that were named. SNMP was enhanced to show information about all physical interfaces and logical interfaces; a nameif command is no longer required to display the interfaces using SNMP.
This section includes the following topics:
IF MIB Output Changes
SNMP was enhanced to show information about all physical interfaces and logical interfaces, including internal interfaces; a nameif command is no longer required to display the interfaces using SNMP.
You might see information about the following internal interfaces:
•
Null0—Not currently in use.
•
Internal-Data or Internal-Control—Internal interfaces for communicating with SSMs or SSCs.
•
_internal_loopback—The loopback interface.
•
Virtual—Used for phone proxy media termination functions.
The following topics show a sample interface configuration on the ASA 5505, and sample ifDescr output:
•
Sample Interface Configuration
Note
Although these examples show the ASA 5505, Version 8.1 only supports the ASA 5580. The SNMP changes apply to all supported platforms.
Sample Interface Configuration
The following example shows the interface configuration for an ASA 5505; refer to this example when looking at the ipDescr sample output in the "Sample ifDescr Output" section.
interface Vlan1nameif usersecurity-level 40ip address 192.168.4.1 255.255.255.0interface Vlan40no nameifsecurity-level 0no ip addressinterface Vlan41no nameifsecurity-level 100no ip addressinterface Vlan46no nameifsecurity-level 0no ip addressinterface Vlan47no nameifsecurity-level 100no ip addressinterface Vlan100nameif insidesecurity-level 100ip address 10.7.1.80 255.255.255.0interface Vlan112no nameifsecurity-level 10no ip addressinterface Vlan114nameif mgmtsecurity-level 10ip address 10.8.1.80 255.255.255.0interface Vlan200nameif outsidesecurity-level 0ip address 10.9.1.80 255.255.255.0interface Ethernet0/0switchport trunk allowed vlan 100switchport mode trunkinterface Ethernet0/1switchport trunk allowed vlan 1,200switchport mode trunkinterface Ethernet0/2switchport access vlan 114interface Ethernet0/3interface Ethernet0/4interface Ethernet0/5interface Ethernet0/6interface Ethernet0/7Sample ifDescr Output
The following ifDescr output shows the difference before and after the SNMP changes (changes are shown in bold):
Before:
IF-MIB::ifDescr.1 = Adaptive Security Appliance 'user' interfaceIF-MIB::ifDescr.2 = Adaptive Security Appliance 'inside' interfaceIF-MIB::ifDescr.3 = Adaptive Security Appliance 'mgmt' interfaceIF-MIB::ifDescr.4 = Adaptive Security Appliance 'outside' interfaceAfter:
IF-MIB::ifDescr.1 = Adaptive Security Appliance 'Null0' interfaceIF-MIB::ifDescr.2 = Adaptive Security Appliance 'Internal-Data0/0'interfaceIF-MIB::ifDescr.3 = Adaptive Security Appliance 'Ethernet0/0' interfaceIF-MIB::ifDescr.4 = Adaptive Security Appliance 'Ethernet0/1' interfaceIF-MIB::ifDescr.5 = Adaptive Security Appliance 'Ethernet0/2' interfaceIF-MIB::ifDescr.6 = Adaptive Security Appliance 'Ethernet0/3' interfaceIF-MIB::ifDescr.7 = Adaptive Security Appliance 'Ethernet0/4' interfaceIF-MIB::ifDescr.8 = Adaptive Security Appliance 'Ethernet0/5' interfaceIF-MIB::ifDescr.9 = Adaptive Security Appliance 'Ethernet0/6' interfaceIF-MIB::ifDescr.10 = Adaptive Security Appliance 'Ethernet0/7' interfaceIF-MIB::ifDescr.11 = Adaptive Security Appliance 'Internal-Data0/1' interfaceIF-MIB::ifDescr.12 = Adaptive Security Appliance '_internal_loopback' interfaceIF-MIB::ifDescr.13 = Adaptive Security Appliance 'Virtual254' interfaceIF-MIB::ifDescr.14 = Adaptive Security Appliance 'user' interfaceIF-MIB::ifDescr.15 = Adaptive Security Appliance 'Vlan40' interfaceIF-MIB::ifDescr.16 = Adaptive Security Appliance 'Vlan41' interfaceIF-MIB::ifDescr.17 = Adaptive Security Appliance 'Vlan46' interfaceIF-MIB::ifDescr.18 = Adaptive Security Appliance 'Vlan47' interfaceIF-MIB::ifDescr.19 = Adaptive Security Appliance 'inside' interfaceIF-MIB::ifDescr.20 = Adaptive Security Appliance 'Vlan112' interfaceIF-MIB::ifDescr.21 = Adaptive Security Appliance 'mgmt' interfaceIF-MIB::ifDescr.22 = Adaptive Security Appliance 'outside' interfaceIP MIB Output Changes
Walking the IP MIB now shows IP addresses assigned to all interfaces, not just those configured using the nameif command.
SNMP Link State Trap Changes
SNMP now sends traps at bootup, when an interface is shut down, or when an interface is brought up for all physical interfaces and logical interfaces; a nameif command is no longer required to send traps about interfaces. Before this enhancement, traps were sent only for interfaces that had a name configured.
Important Notes
Please note the following upgrade and operational considerations:
•
flow-export enable Command Conversion—If you are upgrading from Version 8.1(1) to 8.1(2), and you configured the flow-export enable command, then it is converted to the Modular Policy Framework flow-export event-type all destination command. It is added to the class-default class map in the global service policy. If a global service policy does not exist, one is created. For example, the flow-export enable command is converted to the following:
hostname(config-pmap)# policy-map global_policyhostname(config-pmap)# class class-defaulthostname(config-pmap-c)# flow-export event-type all destination flow_export_host1 flow_export_host2hostname(config-pmap-c)# service-policy global_policy globalThe flow_export_host1 and flow_export_host1 arguments are populated by the flow-export destination commands.
•
No .NET over Clientless—Clientless sessions do not support .NET framework applications (CSCsv29942).
•
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.
Caveats
The following sections describe the caveats for Version 8.1(2):
•
Open Caveats - Version 8.1(2)
•
Resolved Caveats - Version 8.1(2)
For your convenience in locating caveats in the Cisco Bug Toolkit, the caveat titles listed in this section are drawn directly from the Bug Toolkit database. These caveat titles are not intended to be read as complete sentences because the title field length is limited. In the caveat titles, some truncation of wording or punctuation may be necessary to provide the most complete and concise description.
Note
If you are a registered cisco.com user, view Bug Toolkit on cisco.com at the following website:
http://tools.cisco.com/Support/BugToolKit/
To become a registered cisco.com user, go to the following website:
http://tools.cisco.com/RPF/register/register.do
Open Caveats - Version 8.1(2)
Resolved Caveats - Version 8.1(2)
End-User License Agreement
For information on the end-user license agreement, go to:
https://www.cisco.com/en/US/docs/general/warranty/English/EU1KEN_.html
Related Documentation
See Navigating the Cisco ASA 5500 Series Documentation at 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 a Really Simple Syndication (RSS) feed and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free service and 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 of Cisco Systems, Inc. and/or its affiliates in the U.S. and other countries. A listing of Cisco's trademarks can be found at 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. (1005R)
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.
© 2008 Cisco Systems, Inc.
All rights reserved.