![]() |
Table Of Contents
Cisco ASDM Release Notes Version 6.1(3)
ASDM Client PC Operating System and Browser Requirements
Starting ASDM from the ASDM Launcher
Starting ASDM from a Web Browser
Effects of Unsupported Commands
Ignored and View-Only Commands
Discontinuous Subnet Masks Not Supported
Interactive User Commands Not Supported in ASDM CLI Tool
Resolved Caveats - Version 6.1(3)
Obtaining Documentation and Submitting a Service Request
Cisco ASDM Release Notes Version 6.1(3)
August 2008
This document contains release information for Cisco ASDM Version 6.1(3) on Cisco PIX 500 series and Cisco ASA 5500 Adaptive Series Security Appliances. It includes the following sections:
•
Obtaining Documentation and Submitting a Service Request
Introduction
Cisco Adaptive Security Device Manager (ASDM) delivers world-class security management and monitoring services for Cisco PIX 500 and Cisco ASA 5500 series adaptive security appliances through an intuitive, easy-to-use, web-based management interface. Bundled with supported security appliances, the device manager accelerates security appliance deployment with intelligent wizards, robust administration tools, and versatile monitoring services that complement the advanced security and networking features offered byPIX 500 and Cisco ASA 5500 series adaptive security appliance software. Its secure, web-based design enables anytime, anywhere access to security appliances.
New Features
Released: August 11, 2008Table 1 lists the new features for ASA or PIX Version 8.0(4)/ASDM Version 6.1(3).
Table 1 New Features for ASA and PIX Version 8.0(4)/ASDM Version 6.1(3)
Feature Description Unified Communications Features1Phone Proxy
Phone Proxy functionality is supported. ASA Phone Proxy provides similar features to those of the Metreos Cisco Unified Phone Proxy with additional support for SIP inspection and enhanced security. The ASA Phone Proxy has the following key features:
•
Secures remote IP phones by forcing the phones to encrypt signaling and media
•
Performs certificate-based authentication with remote IP phones
•
Terminates TLS signaling from IP phones and initiates TCP and TLS to Cisco Unified Mobility Advantage servers
•
Terminates SRTP and initiates RTP/SRTP to the called party
In ASDM, see Configuration > Firewall > Advanced > Encrypted Traffic Inspection > Phone Proxy.
Mobility Proxy
Secure connectivity (mobility proxy) between Cisco Unified Mobility Advantage clients and servers is supported.
Cisco Unified Mobility Advantage solutions include the Cisco Unified Mobile Communicator, an easy-to-use software application for mobile handsets that extends enterprise communications applications and services to mobile phones and smart phones and the Cisco Unified Mobility Advantage server. The mobility solution streamlines the communication experience, enabling real-time collaboration across the enterprise.
The ASA in this solution delivers inspection for the MMP (formerly called OLWP) protocol, the proprietary protocol between Cisco Unified Mobile Communicator and Cisco Unified Mobility Advantage. The ASA also acts as a TLS proxy, terminating and reoriginating the TLS signaling between the Cisco Unified Mobile Communicator and Cisco Unified Mobility Advantage.
In ASDM, see Configuration > Firewall > Advanced > Encrypted Traffic Inspection > TLS Proxy.
Presence Federation Proxy
Secure connectivity (presence federation proxy) between Cisco Unified Presence servers and Cisco/Microsoft Presence servers is supported. With the Presence solution, businesses can securely connect their Cisco Unified Presence clients back to their enterprise networks, or share Presence information between Presence servers in different enterprises.
The ASA delivers functionality to enable Presence for Internet and intra-enterprise communications. An SSL-enabled Cisco Unified Presence client can establish an SSL connection to the Presence Server. The ASA enables SSL connectivity between server to server communication including third-party Presence servers communicating with Cisco Unified Presence servers. Enterprises share Presence information, and can use IM applications. The ASA inspects SIP messages between the servers.
In ASDM, see Configuration > Firewall > Service Policy Rules > Add/Edit Service Policy Rule > Rule Actions > Protocol Inspection or Configuration > Firewall > Advanced > Encrypted Traffic Inspection > TLS Proxy > Add > Client Configuration.
Remote Access FeaturesAuto Sign-On with Smart Tunnels for IE1
This feature lets you enable the replacement of logon credentials for WININET connections. Most Microsoft applications use WININET, including Internet Explorer. Mozilla Firefox does not, so it is not supported by this feature. It also supports HTTP-based authentication, therefore form-based authentication does not work with this feature.
Credentials are statically associated to destination hosts, not services, so if initial credentials are wrong, they cannot be dynamically corrected during runtime. Also, because of the association with destinations hosts, providing support for an auto sign-on enabled host may not be desirable if you want to deny access to some of the services on that host.
To configure a group auto sign-on for smart tunnels, you create a global list of auto sign-on sites, then assign the list to group policies or user names. This feature is not supported with Dynamic Access Policy.
In ASDM, see Firewall > Advanced > ACL Manager.
Entrust Certificate Provisioning1
ASDM includes a link to the Entrust website to apply for temporary (test) or discounted permanent SSL identity certificates for your ASA.
In ASDM, see Configuration > Remote Access VPN > Certificate Management > Identity Certificates. Click Enroll ASA SSL VPN head-end with Entrust.
Extended Time for User Reauthentication on IKE Rekey
You can configure the security appliance to give remote users more time to enter their credentials on a Phase 1 SA rekey. Previously, when reauthenticate-on-rekey was configured for IKE tunnels and a phase 1 rekey occurred, the security appliance prompted the user to authenticate and only gave the user approximately 2 minutes to enter their credentials. If the user did not enter their credentials in that 2 minute window, the tunnel would be terminated. With this new feature enabled, users now have more time to enter credentials before the tunnel drops. The total amount of time is the difference between the new Phase 1 SA being established, when the rekey actually takes place, and the old Phase 1 SA expiring. With default Phase 1 rekey times set, the difference is roughly 3 hours, or about 15% of the rekey interval.
In ASDM, see Configuration > Device Management > Certificate Management > Identity Certificates.
Persistent IPsec Tunneled Flows
With the persistent IPsec tunneled flows feature enabled, the security appliance preserves and resumes stateful (TCP) tunneled flows after the tunnel drops, then recovers. All other flows are dropped when the tunnel drops and must reestablish when a new tunnel comes up. Preserving the TCP flows allows some older or sensitive applications to keep working through a short-lived tunnel drop. This feature supports IPsec LAN-to-LAN tunnels and Network Extension Mode tunnels from a Hardware Client. It does not support IPsec or AnyConnect/SSL VPN remote access tunnels. See the [no] sysopt connection preserve-vpn-flows command. This option is disabled by default.
In ASDM, see Configuration > Remote Access VPN > Network (Client) Access > Advanced > IPsec > System Options. Check the Preserve stateful VPN flows when the tunnel drops for Network Extension Mode (NEM) checkbox to enable persistent IPsec tunneled flows.
Show Active Directory Groups
The CLI command show ad-groups was added to list the active directory groups. ASDM Dynamic Access Policy uses this command to present the administrator with a list of MS AD groups that can be used to define the VPN policy.
In ASDM, see Configuration > Remote Access VPN > Clientless SSL VPN Access > Dynamic Access Policies > Add/Edit DAP > Add/Edit AAA Attribute.
Smart Tunnel over Mac OS1
Smart tunnels now support Mac OS.
In ASDM, see Configuration > Remote Access VPN > Clientless SSL VPN Access > Portal > Smart Tunnels.
Local Address Pool Edit
Address pools can be edited without affecting the desired connection. If an address in use is not being eliminated from the pool, the connection is not affected. However, if the address in use is being eliminated from the pool, the connection is brought down.
Also available in Version 7.0(8) and 7.2(4).
Firewall FeaturesQoS Traffic Shaping
If you have a device that transmits packets at a high speed, such as the security appliance with Fast Ethernet, and it is connected to a low speed device such as a cable modem, then the cable modem is a bottleneck at which packets are frequently dropped. To manage networks with differing line speeds, you can configure the security appliance to transmit packets at a fixed slower rate. See the shape command. See also the crypto ipsec security-association replay command, which lets you configure the IPSec anti-replay window size. One side-effect of priority queueing is packet re-ordering. For IPSec packets, out-of-order packets that are not within the anti-replay window generate warning syslog messages. These warnings become false alarms in the case of priority queueing. This new command avoids possible false alarms.
In ASDM, see Configuration > Firewall > Security Policy > Service Policy Rules > Add/Edit Service Policy Rule > Rule Actions > QoS. Note that the only traffic class supported for traffic shaping is class-default, which matches all traffic.
Also available in Version 7.2(4).
TCP Normalization Enhancements
You can now configure TCP normalization actions for certain packet types. Previously, the default actions for these kinds of packets was to drop the packet. Now you can set the TCP normalizer to allow the packets.
•
TCP invalid ACK check (the invalid-ack command)
•
TCP packet sequence past window check (the seq-past-window command)
•
TCP SYN-ACK with data check (the synack-data command)
You can also set the TCP out-of-order packet buffer timeout (the queue command timeout keyword). Previously, the timeout was 4 seconds. You can now set the timeout to another value.
The default action for packets that exceed MSS has changed from drop to allow (the exceed-mss command).
The following non-configurable actions have changed from drop to clear for these packet types:
•
Bad option length in TCP
•
TCP Window scale on non-SYN
•
Bad TCP window scale value
•
Bad TCP SACK ALLOW option
In ASDM, see Configuration > Firewall > Objects > TCP Maps.
Also available in Version 7.2(4).
TCP Intercept statistics
You can enable collection for TCP Intercept statistics using the threat-detection statistics tcp-intercept command, and view them using the show threat-detection statistics command.
In ASDM 6.1(5) and later, see Configuration > Firewall > Threat Detection. This command was not supported in ASDM 6.1(3).
Threat detection shun timeout
You can now configure the shun timeout for threat detection using the threat-detection scanning-threat shun duration command.
In ASDM 6.1(5) and later, see Configuration > Firewall > Threat Detection. This command was not supported in ASDM 6.1(3).
Timeout for SIP Provisional Media
You can now configure the timeout for SIP provisional media using the timeout sip-provisional-media command.
In ASDM, see Configuration > Firewall > Advanced > Global Timeouts.
Also available in Version 7.2(4).
clear conn Command
The clear conn command was added to remove connections.
Also available in Version 7.0(8) and 7.2(4).
Fragment full reassembly
The fragment command was enhanced with the reassembly full keywords to enable full reassembly for fragments that are routed through the device. Fragments that terminate at the device are always fully reassembled.
Also available in Version 7.0(8) and 7.2(4).
Ethertype ACL MAC Enhancement
EtherType ACLs have been enhanced to allow non-standard MACs. Existing default rules are retained, but no new ones need to be added.
Also available in Version 7.0(8) and 7.2(4).
Troubleshooting and Monitoring Featurescapture command Enhancement
The capture type asp-drop drop_code command now accepts all as the drop_code, so you can now capture all packets that the security appliance drops, including those dropped due to security checks.
Also available in Version 7.0(8) and 7.2(4).
show asp drop Command Enhancement
Output now includes a timestamp indicating when the counters were last cleared (see the clear asp drop command). It also displays the drop reason keywords next to the description, so you can easily use the capture asp-drop command using the keyword.
Also available in Version 7.0(8) and 8.0(4).
clear asp table Command
Added the clear asp table command to clear the hits output by the show asp table commands.
Also available in Version 7.0(8) and 7.2(4).
show asp table classify hits Command Enhancement
The hits option was added to the show asp table classify command, showing the timestamp indicating the last time the asp table counters were cleared. It also shows rules with hits values not equal to zero. This permits users to quickly see what rules are being hit, especially since a simple configuration may end up with hundreds of entries in the show asp table classify command.
Also available in Version 7.0(8) and 8.0(4).
MIB Enhancement
The CISCO-REMOTE-ACCESS-MONITOR-MIB is implemented more completely.
Also available in 8.0(4).
show perfmon Command
Added the following rate outputs: TCP Intercept Connections Established, TCP Intercept Attempts, TCP Embryonic Connections Timeout, and Valid Connections Rate in TCP Intercept.
Also available in Version 7.0(8) and 7.2(4).
memory tracking Commands
The following new commands are introduced in this release:
•
memory tracking enable-This command enables the tracking of heap memory requests.
•
no memory tracking enable-This command disables tracking of heap memory requests, cleans up all currently gathered information, and returns all heap memory used by the tool itself to the system.
•
clear memory tracking-This command clears out all currently gathered information but continues to track further memory requests.
•
show memory tracking-This command shows currently allocated memory tracked by the tool, broken down by the topmost caller function address.
•
show memory tracking address-This command shows currently allocated memory broken down by each individual piece of memory. The output lists the size, location, and topmost caller function of each currently allocated piece memory tracked by the tool.
•
show memory tracking dump-This command shows the size, location, partial callstack, and a memory dump of the given memory address.
•
show memory tracking detail-This command shows various internal details to be used in gaining insight into the internal behavior of the tool.
Also available in Version 7.0(8) and 7.2(4).
Routing FeaturesIPv6 Multicast Listener Discovery Protocol v2 Support
The security appliance now supports the Multicast Listener Discovery Protocol (MLD) Version 2, to discover the presence of multicast address listeners on their directly attached links, and to discover specifically which multicast addresses are of interest to those neighboring nodes. The security appliance becomes a multicast address listener, or a host, but not a a multicast router, and responds to Multicast Listener Queries and sends Multicast Listener Reports only.
The following commands support this feature:
•
clear ipv6 mld traffic
The clear ipv6 mld traffic command allows you to reset all the Multicast Listener Discovery traffic counters.
•
show ipv6 mld traffic
The show ipv6 mld command allows you to display all the Multicast Listener Discovery traffic counters.
•
debug ipv6 mld
The enhancement to the debug ipv6 command allows the user to display the debug messages for MLD, to see whether the MLD protocol activities are working properly.
•
show debug ipv6 mld
The enhancement to the show debug ipv6 command allows the user to display whether debug ipv6 mld is enabled or disabled.
Also available in Version 7.2(4).
Platform FeaturesNative VLAN support for the ASA 5505
You can now include the native VLAN in an ASA 5505 trunk port using the switchport trunk native vlan command.
In ASDM, see Configuration > Device Setup > Interfaces > Switch Ports > Edit dialog.
Also available in Version 7.2(4).
SNMP support for unnamed interfaces
Previously, 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. Because the ASA 5505 has both unnamed switch ports and named VLAN interfaces, 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. These changes affect all models, and not just the ASA 5505.
Failover Featuresfailover timeout Command
The failover timeout command no longer requires a failover license for use with the static nailed feature.
Also available in Version 7.0(8) and 7.2(4).
ASDM FeaturesSimplify DNS Panel
The DNS Panel on the ASDM GUI has been modified for ease of use. See Configuration > Device Management > DNS.
Redesign the File Transfer Dialog box
You can drag-and-drop files in the File Transfer dialog box. To access this dialog box, go to Tools > File Management, and then click File Transfer.
Clear ACL Hit Counters
Added functionality enabling users to clear ACL hit counters. See the Firewall > Advanced > ACL Manager panel.
Renaming ACLs
Added the ability to rename ACLs from ASDM.
See the Firewall > Advanced > ACL Manager panel.
Combine ASDM/HTTPS, SSH, Telnet into One Panel
ASDM has combined the ASDM, HTTPS, SSH, Telnet into one panel. See the Monitoring > Properties > Device Access > ASDM/HTTPS/Telnet/SSH Sessions panel.
Display all standard ACLs in ACL Manager
Added functionality enabling users to display all standard ACL in the ACL Manager.
See the Firewall > Advanced > ACL Manager panel.
1 This feature is not supported on the PIX security appliance.
ASDM Client PC Operating System and Browser Requirements
Table 2 lists the supported and recommended PC operating systems and browsers for ASDM Version 6.1(3).
Table 2 Operating System and Browser Requirements
Operating System Version BrowserMicrosoft Windows1
Windows Vista
Windows 2003 Server
Windows XP
Windows 2000 (Service Pack 4 or higher)
Internet Explorer 6.0 or higher with Sun Java (JRE)2 1.4.2, 5.0 (1.5), or 6.0
Firefox 1.5 or higher with Sun Java (JRE) 1.4.2, 5.0 (1.5), or 6.0
Apple Macintosh®
Apple Macintosh OS X
Firefox 1.5 or higher or Safari 2.0 or higher withSun Java (JRE) 5.0 (1.5).
Linux
Red Hat Linux, Red Hat Enterprise Linux WS version 4 running GNOME or KDE
Firefox 1.5 or higher with Sun Java (JRE) 1.4.2, 5.0 (1.5), or 6.0
1 ASDM is not supported on Windows 3.1, Windows 95, Windows 98, Windows ME, or Windows NT4.
2 Obtain Sun Java from java.sun.com.
Table 3 lists the supported and recommended client operating systems and Java for ASDM.
Table 3 Operating System and Browser Requirements
Operating System Browser Sun Java SE Plug-in1 Internet Explorer Firefox2 SafariMicrosoft Windows (English and Japanese):
•
7
•
Vista
•
2008 Server
•
XP
6.0 or later
1.5 or later
No support
6.0
Apple Macintosh OS X:
•
10.6
•
10.5
•
10.4
No support
1.5 or later
2.0 or later
6.0
Red Hat Enterprise Linux 5 (GNOME or KDE):
•
Desktop
•
Desktop with Workstation
N/A
1.5 or later
N/A
6.0
1 Support for Java 5.0 was removed in ASDM 6.4. Obtain Sun Java updates from java.sun.com.
2 ASDM requires an SSL connection from the browser to the security appliance. By default, Firefox does not support base encryption (DES) for SSL and therefore requires the security appliance to have a strong encryption (3DES/AES) license. As a workaround, you can enable the security.ssl3.dhe_dss_des_sha setting in Firefox. See http://kb.mozillazine.org/About:config to learn how to change hidden configuration preferences.
ASDM 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
ASA Version 8.0(4) requires ASDM Version 6.1(3) or later.
For information about ASDM requirements for other releases, see Cisco ASA 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 module application requirements, see Cisco ASA Compatibility:
http://www.cisco.com/en/US/docs/security/asa/compatibility/asamatrx.html
Upgrading ASDM and ASA
This section describes how to upgrade ASDM and ASA to a new ASDM release. If you have a Cisco.com login, you can obtain ASDM from the following website:
http://www.cisco.com/public/sw-center/index.shtml
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 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 backwards compatible, so you can upgrade the platform image using the new ASDM; you cannot use an old ASDM with a new platform image.
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, click Tools > Upload Image from Local PC.
b.
In ASDM 5.2, click Tools > Upgrade Software.
c.
In ASDM 6.0, click 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 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 security appliance to load the new image. Use the Configuration > Properties > Device Administration > Boot System/Configuration panel.
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 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.
Getting Started with ASDM
This section describes how to connect to ASDM and start your configuration. If you are using the security appliance for the first time, your security appliance might include a default configuration. You can connect to a default IP address with ASDM so that you can immediately start to configure the security appliance from ASDM. If your platform does not support a default configuration, you can log in to the CLI and run the setup command to establish connectivity. See Before You Begin for more detailed information about networking.
This section includes the following topics:
•
Downloading the ASDM Launcher
•
Starting ASDM from the ASDM Launcher
•
Starting ASDM from a Web Browser
Before You Begin
If your security appliance includes a factory default configuration, you can connect to the default management address of 192.168.1.1 with ASDM. On the ASA 5500 series Adaptive Security Appliance, the interface to which you connect with ASDM is Management 0/0. To restore the default configuration, enter the configure factory-default command at the security appliance CLI.
It is also recommended that you install the recommended version of Java before you begin the installation.
Make sure the PC is on the same network as the security appliance. You can use DHCP on the client to obtain an IP address from the security appliance, or you can set the IP address to a 192.168.1.0/24 network address.
If your platform does not support the factory default configuration, or you want to add to an existing configuration to make it accessible for ASDM, access the security appliance CLI according to the Cisco Security Appliance Command Line Configuration Guide, and enter the setup command.
Note
If your platform does not support the factory default configuration, running the setup command may remove any existing configuration.
You must have an inside interface already configured to use the setup command. The Cisco PIX security appliance default configuration includes an inside interface, but the Cisco ASA adaptive security appliance default configuration does not. Before using the setup command, enter the interface gigabitethernet slot/port command, and then the nameif inside command. The slot for interfaces that are built in to the chassis is 0. For example, enter interface gigabitethernet 0/1.
The Cisco PIX 500 series and the ASA 5510 Adaptive Security Appliance has an Ethernet-type interface. When using the using the setup command, remember that the interface ID is dependent upon the platform. For example, on PIX 500 series, enter the interface ethernet slot/port. On ASA, enter interface gigabitethernet slot/port command.
Downloading the ASDM Launcher
The ASDM Launcher is for Windows only. The ASDM Launcher is an improvement over running ASDM in a browser. The ASDM Launcher avoids double authentication and certificate dialog boxes, launches faster, and caches previously-entered IP addresses and usernames.
To download the ASDM Launcher, perform the following steps:
Step 1
From a supported web browser on the security appliance network, enter the following URL:
https://interface_ip_address/adminIn transparent firewall mode, enter the management IP address.
Note
Be sure to enter https, not http.
Step 2
Click OK or Yes to all prompts, including the name and password prompt. By default, leave the name and password blank.
A page displays with the following buttons:
•
Download ASDM Launcher and Start ASDM
•
Run ASDM in a browser
Step 3
Click Download ASDM Launcher and Start ASDM.
The installer downloads to your PC.
Step 4
Run the installer to install the ASDM Launcher.
Starting ASDM from the ASDM Launcher
The ASDM Launcher is for Windows only.
To start ASDM from the ASDM Launcher, perform the following steps:
Step 1
Double-click the Cisco ASDM Launcher shortcut on your desktop, or start it from the Start menu.
Step 2
Enter the security appliance IP address or hostname, your username, and your password, and then click OK.
If there is a new version of ASDM on the security appliance, the ASDM Launcher automatically downloads it before starting ASDM.
Using ASDM in Demo Mode
ASDM Demo Mode is available as a separately installed application running under Windows. It makes use of the ASDM Launcher and pre-packaged configuration files to let you run ASDM without having a live device available. ASDM Demo Mode lets you:
•
Demonstrate ASDM or security appliance features using the ASDM interface.
•
Perform configuration and select monitoring tasks via ASDM as though you were interacting with a real device.
ASDM Demo Mode provides simulated monitoring data, including real-time system log messages. The data shown is randomly generated, but the experience is identical to what you would see when connecting to a real device.
ASDM Demo Mode has the following limitations:
•
Changes made to the configuration will appear in the GUI but are not applied to the configuration file. That is, when you click the Refresh button, it will revert back to the original configuration. The changes are never saved to the configuration file.
•
File/Disk operations are not supported.
•
Monitoring and logging data are simulated. Historical monitoring data is not available.
•
You can only log in as an admin user; you cannot log in as a monitor-only or read-only user.
•
Demo Mode does not support the following features:
–
File menu:
Reset Device to the Factory Default Configuration
Save Running Configuration to Flash
Save Running Configuration to TFTP Server
Save Running Configuration to Standby Unit
Save Internal Log Buffer to Flash
Clear Internal Log Buffer
–
Tools menu:
Command Line Interface
Ping
Traceroute
File Management
Upgrade Software from Local Computer
Upgrade Software from Cisco.com
Backup Configurations
Restore Configurations
System Reload
Administrator's Alert to Clientless SSL VPN Users
–
Toolbar/Status bar > Save
–
Configuration > Interface > Edit Interface > Renew DHCP Lease
–
Failover—Configuring a standby device
•
These operations cause a reread of the configuration and therefore will revert the configuration back to the original settings.
–
Switching contexts
–
Making changes in the Interface panel
–
NAT panel changes
–
Clock panel changes
To run ASDM in Demo Mode, perform the following steps:
Step 1
If you have not yet installed the Demo Mode application, perform the following steps:
a.
Download the ASDM Demo Mode installer from the following website:
http://www.cisco.com/cisco/software/navigator.html
or
http://www.cisco.com/pcgi-bin/tablebuild.pl/pix
The filename is asdm-demo-611.msi.
b.
Double-click the installer to install the software.
Step 2
Double-click the Cisco ASDM Launcher shortcut on your desktop, or start it from the Start menu.
Step 3
Check Run in Demo Mode.
Step 4
To set the platform, context and firewall modes, and ASDM Version, click Demo and make your selections from the Demo Mode area.
Step 5
To use new ASDM images as they come out, you can either download the latest installer, or you can download the normal ASDM images and install them for Demo Mode:
a.
Download the image from the download page (see Step 1).
The filename is asdm-version.bin.
b.
In the Demo Mode area, click Install ASDM Image.
A file browser appears. Find the ASDM image file in the browser.
Step 6
Click OK to launch ASDM Demo Mode.
You see a Demo Mode label in the title bar of the window.
Starting ASDM from a Web Browser
To start ASDM from a web browser, perform the following steps:
Step 1
From a supported web browser on the security appliance network, enter the following URL:
https://interface_ip_address/adminIn transparent firewall mode, enter the management IP address.
Note
Be sure to enter https, not http.
Step 2
Click OK or Yes to all browser prompts, including the name and password prompt. By default, leave the name and password blank.
A page displays with the following buttons:
•
Install ASDM Launcher and Run ASDM
Step 3
Click Run ASDM.
Step 4
Click OK or Yes to all Java prompts, including the name and password prompt. By default, leave the name and password blank.
Using the Startup Wizard
The Startup Wizard helps you easily configure a single mode security appliance or a context in multiple context mode.
To use the Startup Wizard to configure the basic setup of the security appliance, perform the following steps:
Step 1
Launch the wizard according to the steps for the correct security context mode.
•
In single context mode, click Wizards > Startup Wizard.
•
In multiple context mode, for each new context, perform the following steps:
a.
Create a new context using the System > Configuration > Security Context pane.
b.
Be sure to allocate interfaces to the context.
c.
When you apply the changes, ASDM prompts you to use the Startup Wizard.
d.
Click the System/Contexts icon on the toolbar, and choose the context name.
e.
Click Wizards > Startup Wizard.
Step 2
Click Next as you proceed through the Startup Wizard screens, filling in the appropriate information in each screen, such as device name, domain name, passwords, interface names, IP addresses, basic server configuration, and access permissions.
Step 3
Click Finish on the last pane to transmit the configuration to the security appliance. Reconnect to ASDM using the new IP address, if the IP address of the connection changes.
Step 4
Enter other configuration details on the Configuration panes.
Using the IPsec VPN Wizard
The IPsec VPN Wizard configures basic VPN access for LAN-to-LAN or remote client access. The VPN Wizard is available only for security appliances running in single context mode and routed (not transparent) firewall mode.
To use the VPN Wizard to configure VPN, perform the following steps:
Step 1
Click Wizards > VPN Wizard.
Step 2
Supply information on each wizard pane. Click Next to move through the VPN Wizard panes. You may use the default IPSec and IKE policies. Click Help for more information about each field.
Step 3
After you complete the VPN Wizard information, click Finish on the last pane to transmit the configuration to the security appliance.
Printing from ASDM
Note
Printing is supported only for Microsoft Windows 2000 or XP in this release.
ASDM supports printing for the following features:
•
The Configuration > Interfaces table
•
All Configuration > Security Policy tables
•
All Configuration > NAT tables
•
The Configuration > VPN > IPSec > IPSec Rules table
•
Monitoring > Connection Graphs and its related table
ASDM Limitations
This section describes ASDM limitations, and includes the following topics:
•
Interactive User Commands Not Supported in ASDM CLI Tool
Unsupported Commands
ASDM does not support the complete command set of the CLI. For any CLI configuration that ASDM does not support, the commands remain unchanged in the configuration.
Effects of Unsupported Commands
•
If ASDM loads an existing running configuration and finds IPv6-related commands, ASDM displays a dialog box informing you that it does not support IPv6. You cannot configure any IPv6 commands in ASDM, but all other configuration is available.
•
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 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.
Ignored and View-Only Commands
The following table lists commands that ASDM supports in the configuration when you add them through the CLI, but that you cannot add or edit 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.
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 in 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 command: crypto key generate rsa
ASDM generates the default 1024-bit RSA key.
3.
Enter the command again: crypto key generate rsa
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 noconfirm
Miscellaneous Limitations
•
Configuration > Remote Access VPN > Secure Desktop Manager is not supported.
•
Dynamic Access Policies, located in Configuration > Remote Access VPN > Network (Client) Access and Configuration > Remote Access VPN > Clientless SSL VPN Access, have limited support because it depends on Secure Desktop Manager which is not supported.
Caveats
The following sections describes the open and resolved caveats for Version 6.1(3).
•
Open Caveats - Version 6.1(3)
•
Resolved Caveats - Version 6.1(3)
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 6.1(3)
The following list shows caveats that are opened for Version 6.1(3):
Resolved Caveats - Version 6.1(3)
The following list shows caveats that are resolved for Version 6.1(3):
End-User License Agreement
For information on the end-user license agreement, go to:
http://www.cisco.com/en/US/docs/general/warranty/English/EU1KEN_.html
Related Documentation
For additional information on ASDM or its platforms, see the ASDM online Help or the following documentation found on Cisco.com:
•
Cisco ASA 5500 Series Hardware Installation Guide
•
Cisco ASA 5500 Series Getting Started Guide
•
Cisco ASA 5500 Series Release Notes
•
Migrating to ASA for VPN 3000 Series Concentrator Administrators
•
Cisco Security Appliance Command Line Configuration Guide
•
Cisco Security Appliance Command Reference
•
Release Notes for Cisco Intrusion Prevention System 5.0
•
Installing and Using Cisco Intrusion Prevention System Device Manager 5.0
•
Release Notes for Cisco Intrusion Prevention System 5.1
•
Installing and Using Cisco Intrusion Prevention System Device Manager 5.1
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.
CCDE, CCENT, Cisco Eos, Cisco Lumin, Cisco Nexus, Cisco StadiumVision, Cisco TelePresence, the Cisco logo, DCE, and Welcome to the Human Network are trademarks; Changing the Way We Work, Live, Play, and Learn and Cisco Store are service marks; and Access Registrar, Aironet, AsyncOS, Bringing the Meeting To You, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, CCVP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Collaboration Without Limitation, EtherFast, EtherSwitch, Event Center, Fast Step, Follow Me Browsing, FormShare, GigaDrive, HomeLink, Internet Quotient, IOS, iPhone, iQ Expertise, the iQ logo, iQ Net Readiness Scorecard, iQuick Study, IronPort, the IronPort logo, LightStream, Linksys, MediaTone, MeetingPlace, MeetingPlace Chime Sound, MGX, Networkers, Networking Academy, Network Registrar, PCNow, PIX, PowerPanels, ProConnect, ScriptShare, SenderBase, SMARTnet, Spectrum Expert, StackWise, The Fastest Way to Increase Your Internet Quotient, TransPath, WebEx, and the WebEx logo are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries.
All other trademarks mentioned in this document or Website 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. (0807R)
© 2008 Cisco Systems, Inc.
All rights reserved.