![]() |
Table Of Contents
Release Notes for Cisco ASDM, Version 6.2(x)
ASDM Client Operating System and Browser Requirements
New Features in ASDM 6.2(5)/ASA 8.2(2)
New Features in ASDM 6.2(3)/ASA 8.0(5)
New Features in ASDM 6.2(1)/ASA 8.2(1)
Upgrading the Adaptive Security Appliance
Ignored and View-Only Commands
Effects of Unsupported Commands
Discontinuous Subnet Masks Not Supported
Interactive User Commands Not Supported by the ASDM CLI Tool
Resolved Caveats for Software Version 6.2(5)
Resolved Caveats for Software Version 6.2(3)
Resolved Caveats for Software Version 6.2(1)
Obtaining Documentation and Submitting a Service Request
Release Notes for Cisco ASDM, Version 6.2(x)
January 2010
This document contains release information for the following Cisco ASDM versions for the Cisco ASA 5500 series:
•
6.2(5)
•
6.2(3)
•
6.2(1)
This document includes the following sections:
•
ASDM Client Operating System and Browser Requirements
•
Upgrading the Adaptive Security Appliance
•
Obtaining Documentation and Submitting a Service Request
Important Notes
•
For Smart Call Home Version 3.0(1), full support for the adaptive security appliance on the backend server is not yet available. The following features are not available, and will only be available in Cisco Smart Call Home Version 3.1 (not yet released):
a.
Web portal reports related to Threat, Telemetry, and Snapshot messages.
b.
Configuration message parsing to generate a feature list on the web portal.
c.
Diagnostic messages that trigger any action, such as to open an SR case.
•
AIP SSC Setup Screen in ASDM—AIP (IPS) users will be unable to use ASDM to set up SSC if you mistype a password in the SSC-setup screen.
•
ASDM Launcher Upgrade Failure—Upgrading from an older version of ASDM, such as ASDM 6.1.5.51, which includes ASDM Launcher 1.5.30, sometimes fails in the following two ways on Windows XP or Vista:
–
CSCsy7572—When using the ASDM Launcher to upgrade, the installer fails, and the following message appears: "The system cannot open the device or file specified." Clicking Retry does not succeed.
–
CSCsz35267—When using a web browser, clicking the "Install ASDM Launcher and Run ASDM" button downloads the dm-launcher.msi installer. Running dm-launcher.msi may produce an error 1307 or 1316 dialog giving the full pathname of the file that either cannot be found or for which a network error occurred.
Workaround : To recover from such events, use the Add or Remove Programs control panel to remove the Cisco ASDM Launcher or Cisco ASDM-IDM Launcher. (Any of the ASDM on IP address programs do not need to be removed.) Afterwards, launch a web browser; access ASDM with a URL such as https://IP_Address /admin; and install the new ASDM-IDM Launcher using the Install ASDM Launcher and Run ASDM button.
ASDM Client Operating System and Browser Requirements
Table 1 lists the supported and recommended client operating systems and Java for ASDM.
Table 1 Operating System and Browser Requirements
Operating System Browser Sun Java SE Plug-in1 Internet Explore Firefox SafariMicrosoft Windows (English and Japanese):
•
72
•
Vista
•
2003 Server
•
XP
•
2000 (Service Pack 4 or higher)3
6.0 or above
1.5 or above
No support.
•
5.0 (1.5.0)
•
6.0
Apple Macintosh OS X:
•
10.62
•
10.5
•
10.4
No support.
1.5 or above
2.0 or above
•
5.0 (1.5.0)
•
6.0
Red Hat Enterprise Linux 54 (GNOME or KDE):
•
Desktop
•
WS
N/A
1.5 or above
N/A
•
5.0 (1.5.0)
•
6.0
1 Obtain Sun Java from java.sun.com.
2 Support added in Version 6.2(3)
3 Windows 2000 is only supported with Version 6.2(1); later ASDM versions are not supported.
4 6.2(1) supports Version 4; 6.2(3) and above support Version 5.
Note
ASDM supports up to a maximum of a 512 KB configuration. If you exceed this amount, you may experience performance issues.
Supported Platforms
See Cisco ASA 5500 Series and PIX 500 Series Security Appliance Hardware and Software Compatibility for the minimum supported version of ASDM for each ASA and SSM version.
Note
ASDM 6.2(1) and above is not supported on the PIX platforms. The last ASDM version supported on the PIX is 6.1(5).
Note
Although ASDM 6.2 supports many ASA versions, the ASDM 6.2 documentation and online help only include features for ASA 8.2. For older ASA versions, you might find that using the ASDM 6.2 documentation is inaccurate for your older feature set. Instead, refer to the ASDM guide in which support for your platform version was added (to see when support was added, see Cisco ASA 5500 Series and PIX 500 Series Security Appliance Hardware and Software Compatibility for the minimum supported version of ASDM for each ASA version; this version is the one where support was added). Although the specific information about the ASDM GUI might be inaccurate in that guide, the platform feature set is documented correctly.
New Features
This section includes the following topics:
•
New Features in ASDM 6.2(5)/ASA 8.2(2)
•
New Features in ASDM 6.2(3)/ASA 8.0(5)
•
New Features in ASDM 6.2(1)/ASA 8.2(1)
New Features in ASDM 6.2(5)/ASA 8.2(2)
Released: January 11, 2010Table 2 lists the new features for ASA Version 8.2(2)/ASDM Version 6.2(5).
New Features in ASDM 6.2(3)/ASA 8.0(5)
Released: November 3, 2009Hi
Table 3 lists the new features for ASA Version 8.0(5)/ASDM Version 6.2(3).
Note
Version 8.0(5) is not supported on the PIX security appliance.
New Features in ASDM 6.2(1)/ASA 8.2(1)
Released: May 6, 2009Hi
Table 4 lists the new features for ASA Version 8.2(1)/ASDM Version 6.2(1).
Table 4 New Features for ASA Version 8.2(1)/ASDM Version 6.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.
In ASDM, see Configuration > Device Management > Management Access > ASDM/HTTPD/Telnet/SSH.
Customizing Secure Desktop
You can use ASDM to customize the Secure Desktop windows displayed to remote users, including the Secure Desktop background (the lock icon) and its text color, and the dialog banners for the Desktop, Cache Cleaner, Keystroke Logger, and Close Secure Desktop windows.
In ASDM, see Configuration > CSD Manager > Secure Desktop Manager.
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.
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.
In ASDM, see Configuration> Remote Access VPN > Network (Client) Access > AnyConnect or Clienltess SSL VPN Connection Profiles > Advanced. Settings are in the Authentication, Secondary Authentication, and Authorization panes.
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.
Note
The RSA/SDI authentication server type cannot be used as the secondary username/password credential. It can only be used for primary authentication.
In ASDM, see Configuration > Remote Access VPN > Network (Client) Access or Clientless SSL VPN > AnyConnect Connection Profiles > Add/Edit > Advanced > Secondary Authentication.
AnyConnect Essentials
AnyConnect Essentials is a separately licensed SSL VPN client, entirely configured on the adaptive security appliance, 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.
Note
This license cannot be used at the same time as the shared SSL VPN premium license.
In ASDM, see Configuration > Remote Access VPN > Network (Client) Access > Advanced > AnyConnect Essentials License. The AnyConnect Essentials license must be installed for ASDM to show this pane.
Disabling Cisco Secure Desktop per Connection Profile
When enabled, Cisco Secure Desktop automatically runs on all computers that make SSL VPN connections to the adaptive security appliance. 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.
In ASDM, see Configuration > Remote Access VPN > Clientless SSL VPN Access > Connection Profiles > Add or Edit > Advanced, Clientless SSL VPN Configuration.
or
Configuration > Remote Access VPN > Network (Client) Access > AnyConnect Connection Profiles > Add or Edit > Advanced > SSL VPN.
Certificate Authentication Per Connection Profile
Previous versions supported certificate authentication for each adaptive security appliance 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.
In ASDM, see Configuration > Remote Access VPN > Network (Client) Access > AnyConnect Connection Profiles > Add/Edit > Basic.
or
Configuraiton > Remote Access VPN > Clientless SSL VPN > Connection Profiles > Add/Edit>Basic.
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.
In ASDM, use the IPSec Certificate to Connection Maps > Rules pane, or Certificate to SSL VPN Connections Profile Maps pane.
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 adaptive security appliances by configuring one of the adaptive security appliances as a shared license server, and the rest as clients.
Note
This license cannot be used at the same time as the AnyConnect Essentials license.
In ASDM, see Configuration > Device Management > Licensing > Shared SSL VPN Licenses. Also see, Monitoring > VPN > Clientless SSL VPN > Shared Licenses.
Updated VPN Wizard
The VPN Wizard (accessible by choosing Wizards > IPSec VPN Wizard) was updated. The step to select IPsec Encryption and Authentication (formerly Step 9 of 11) was removed because the Wizard now generates default values for these settings. In addition, the step to select IPsec Settings (Optional) now includes new fields to enable perfect forwarding secrecy (PFS) and set the Diffie-Hellman Group.
Firewall FeaturesTCP state bypass
If you have asymmetric routing configured on upstream routers, and traffic alternates between two adaptive security appliances, then you can configure TCP state bypass for specific traffic.
In ASDM, see Configuration > Firewall > Service Policy Rules > Rule Actions > Connection Settings.
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 adaptive security appliance. 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.
In ASDM, see Configuration > Firewall > Advanced > Encrypted Traffic Inspection > Media Termination Address.
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.
H.239 Message Support in H.323 Application Inspection
In this release, the adaptive security appliance 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 adaptive security appliance 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.
In ASDM, see Configuration > Firewall > Service Policy Rules > Add Service Policy Rule Wizard > Rule Actions > Protocol Inspection > H.323 H.225. Click Configure and then choose the H.323 Inspect Map.
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 adaptive security appliance propagates OLC media proposal information into the media array and opens a pinhole for the media channel (extendedVideoCapability).
In ASDM, see Configuration > Firewall > Service Policy Rules > Add Service Policy Rule Wizard > Rule Actions > Protocol Inspection > H.323 H.225.
IPv6 in transparent firewall mode
Transparent firewall mode now participates in IPv6 routing. Prior to this release, the adaptive security appliance 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 adaptive security appliance recognizes and passes IPv6 packets.
All IPv6 functionality is supported unless specifically noted.
In ASDM, see Configuration > Device Management > Management Access > Management IP Address.
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.htmlIn ASDM, see Configuration > Firewall > Botnet Traffic Filter.
AIP SSC card for the ASA 5505
The AIP SSC offers IPS for the ASA 5505 adaptive security appliance. Note that the AIP SSM does not support virtual sensors.
In ASDM, see Configuration > Device Setup > SSC Setup and Configuration > IPS.
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.
In ASDM, see Configuration > Firewall > Service Policy Rules.
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).
In ASDM, see Configuration > Device Management > Management Access > SNMP.
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.
In ASDM, see Configuration > Device Management > Logging > Netflow.
Routing FeaturesMulticast NAT
The adaptive security appliance 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 adaptive security appliance.
To enable coredump, use the coredump enable command.
ASDM FeaturesASDM Support for IPv6
All IPv6 functionality is supported unless specifically noted.
Support for Public Server configuration
You can use ASDM to configure a public server. This allows to you define servers and services that you want to expose to an outside interface.
In ASDM, see Configuration > Firewall > Public Servers.
Upgrading the Adaptive Security Appliance
This section describes how to upgrade the adaptive security appliance to a new ASDM release. If you have a Cisco.com login, you can obtain ASDM from one of the following websites:
http://www.cisco.com/pcgi-bin/tablebuild.pl/asa
or
http://www.cisco.com/pcgi-bin/tablebuild.pl/pix
Note
If you are upgrading from PIX Version 6.3, first upgrade to Version 7.0 according to Guide for Cisco PIX 6.2 and 6.3 Users Upgrading to Cisco PIX Software Version 7.0. Then upgrade PDM to ASDM according to the ASDM 5.0 release notes.
If you have a previous release of ASDM on your adaptive security appliance and want to upgrade to the latest release, you can do so from within ASDM. We recommend that you upgrade the ASDM image before the platform image. ASDM is backward compatible, so you can upgrade the platform image using the new ASDM; you cannot use an old ASDM with a new platform image.
Note
If the ASA or PIX is running a version earlier than 8.0, then ASA and ASDM must be upgraded at the same time as the ASA or PIX operating system using the existing version of ASDM. This should be compatible with the existing operating system.
But, if ASA or PIX is running version 8.0 or later, then ASDM 6.2 is backward compatible and may be upgraded before the ASA or PIX operating system.To upgrade ASDM, perform the following steps:
Step 1
Download the new ASDM image to your PC.
Optionally, you can download a new platform image to your PC if the installed image is earlier than 8.0.
Step 2
Launch ASDM.
Step 3
From the Tools menu:
a.
In ASDM 5.0 and 5.1, choose Tools > Upload Image from Local PC.
b.
In ASDM 5.2, choose Tools > Upgrade Software.
c.
In ASDM 6.0 or later, choose Tools > Upload Software from Local Computer.
Step 4
With ASDM selected, click Browse Local to select the new ASDM image.
Step 5
To specify the location in Flash memory where you want to install the new image, enter the directory path in the field or click Browse Flash.
If your adaptive security appliance does not have enough memory to hold two ASDM images, overwrite the old image with the new one by specifying the same destination filename. You can rename the image after it was uploaded using the Tools > File Management tool.
If you have enough memory for both versions, you can specify a different name for the new version. If you need to revert to the old version, it is still in your Flash memory.
Step 6
Click Upload Image.
When ASDM is finished uploading, the following message appears:
"ASDM Image is Uploaded to Flash Successfully."
Step 7
For Version 5.x only: If the new ASDM image has a different name than the old image, then you must configure the adaptive security appliance to load the new image. Use the Configuration > Properties > Device Administration > Boot System/Configuration pane.
Step 8
If installing a new platform image, download the new platform image using the Tools > Upgrade Software tool with ASA or PIX selected.
If your adaptive security appliance does not have enough memory to hold two ASDM images, overwrite the old image with the new one by specifying the same destination filename. You can rename the image after it was uploaded using the Tools > File Management tool.
Step 9
If installing a new image, select ASA as the new image, and reload the security appliance using the
Tools > System Reload tool.Make sure to choose "Save the running configuration at time of reload".
Step 10
To run the new ASDM image, exit ASDM and reconnect.
Unsupported Commands
ASDM supports almost all commands available for the adaptive adaptive security appliance, but ASDM ignores some commands in an existing configuration. Most of these commands can remain in your configuration; see Tools > Show Commands Ignored by ASDM on Device for more information.
This section includes the following topics:
•
Ignored and View-Only Commands
•
Effects of Unsupported Commands
•
Discontinuous Subnet Masks Not Supported
•
Interactive User Commands Not Supported by the ASDM CLI Tool
Ignored and View-Only Commands
Table 5 lists commands that ASDM supports in the configuration when added through the CLI, but that cannot be added or edited in ASDM. If ASDM ignores the command, it does not appear in the ASDM GUI at all. If the command is view-only, then it appears in the GUI, but you cannot edit it.
Effects of Unsupported Commands
•
If ASDM loads an existing running configuration and finds other unsupported commands, ASDM operation is unaffected. To view the unsupported commands, choose Tools > Show Commands Ignored by ASDM on Device.
•
If ASDM loads an existing running configuration and finds the alias command, it enters Monitor-only mode.
Monitor-only mode allows access to the following functions:
–
The Monitoring area
–
The CLI tool (Tools > Command Line Interface), which lets you use the CLI commands
To exit Monitor-only mode, use the CLI tool or access the adaptive security appliance console, and remove the alias command. You can use outside NAT instead of the alias command. See the Cisco Security Appliance Command Reference for more information.
Note
You might also be in Monitor-only mode because your user account privilege level, indicated in the status bar at the bottom of the main ASDM window, was set up as less than or equal to three by your system administrator, which allows Monitor-only mode. For more information, choose Configuration > Device Management > Users/AAA > User Accounts and
Configuration > Device Management > Users/AAA > AAA Access.
Discontinuous Subnet Masks Not Supported
ASDM does not support discontinuous subnet masks such as 255.255.0.255. For example, you cannot use the following:
ip address inside 192.168.2.1 255.255.0.255Interactive User Commands Not Supported by the ASDM CLI Tool
The ASDM CLI tool does not support interactive user commands. If you enter a CLI command that requires interactive confirmation, ASDM prompts you to enter "[yes/no]" but does not recognize your input. ASDM then times out waiting for your response.
For example:
1.
From the ASDM Tools menu, click Command Line Interface.
2.
Enter the crypto key generate rsa command.
ASDM generates the default 1024-bit RSA key.
3.
Enter the crypto key generate rsa command again.
Instead of regenerating the RSA keys by overwriting the previous one, ASDM displays the following error:
Do you really want to replace them? [yes/no]:WARNING: You already have RSA ke0000000000000$A keyInput line must be less than 16 characters in length.%Please answer 'yes' or 'no'.Do you really want to replace them [yes/no]:%ERROR: Timed out waiting for a response.ERROR: Failed to create new RSA keys names <Default-RSA-key>Workaround:
•
You can configure most commands that require user interaction by means of the ASDM panes.
•
For CLI commands that have a noconfirm option, use this option when entering the CLI command. For example:
crypto key generate rsa noconfirmOpen Caveats
This section 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 6.2(3), then you need to add the caveats in this section to the resolved caveats from 6.2(3)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 for Software Version 6.2(5)
•
Resolved Caveats for Software Version 6.2(3)
•
Resolved Caveats for Software Version 6.2(1)
Resolved Caveats for Software Version 6.2(5)
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 for Software Version 6.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 for Software Version 6.2(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/
End-User License Agreement
For information on the end-user license agreement, go to: http://www.cisco.com/univercd/cc/td/doc/es_inpck/eu1jen__.pdf
Related Documentation
For additional information on ASDM or its platforms, 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 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.
©2010 Cisco Systems, Inc. All rights reserved.