Table Of Contents
Cisco ASDM Release Notes Version 5.0(2)
Contents
Introduction
New Features
System Requirements
Hardware Requirements
Client PC Operating System and Browser Requirements
Important Notes
Upgrading to a New Software Release
Deleting Your Old Cache
Getting Started with ASDM
Before You Begin
Starting ASDM
Using the Startup Wizard
VPN Wizard
Bootstrapping LAN Failover
ASA Interface Supports Either WebVPN or ASDM Admin Session
Unsupported Characters
ASDM CLI Does Not Support Interactive User Commands
Printing from ASDM
Unsupported Commands
Effects of Unsupported Commands
Ignored and View-Only Commands
ASDM Limitations
Other CLI Limitations
Securing the Failover Key
Caveats
Open Caveats - Release 5.0(2)
Resolved Caveats - Release 5.0(2)
Related Documentation
Obtaining Documentation and Submitting a Service Request
Cisco ASDM Release Notes Version 5.0(2)
July 2005
Contents
This document contains release information for Cisco ASDM Version 5.0(2) on Cisco PIX 500 series and Cisco ASA 5500 series security appliances 7.0(2). It includes the following sections:
•
Introduction
•New Features
•System Requirements
•Important Notes
•Caveats
•Related Documentation
•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 ASA 5500 series 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 by Cisco PIX 500 and ASA 5500 series security appliance software Version 7.0(2). Its secure, web-based design enables anytime, anywhere access to security appliances.
New Features
There were no new features in ASA 7.0(2)/ASDM 5.0(2)
System Requirements
This section includes the following topics:
•Hardware Requirements
•Client PC Operating System and Browser Requirements
Hardware Requirements
ASDM software runs on the following platforms:
•Cisco ASA 5510 security appliance
•Cisco ASA 5520 security appliance
•Cisco ASA 5540 security appliance
•SSM-10
•SSM-20
•PIX 515/515E
•PIX 525
•PIX 535
Note ASDM is not currently supported on PIX 501, PIX 506/506E, or PIX 520 hardware.
For more information on minimum hardware requirements, see:
http://www.cisco.com/en/US/docs/security/asa/asa70/asdm50/webhelp/sysreq.html
Certain features, such as load balancing and QoS, require particular hardware platforms. Other features require licensing.
For more information on feature support for each platform license, see:
http://www.cisco.com/en/US/docs/security/asa/asa70/asdm50/webhelp/gen_info_licenses.html
Client PC Operating System and Browser Requirements
Table 1 lists the supported and recommended PC operating systems and browsers for Version 5.0(2).
Table 1 Operating System and Browser Requirements
| |
Operating System
|
Browser
|
Other Requirements
|
Windows1
|
Windows 2000 (Service Pack 4) or Windows XP operating systems
|
Internet Explorer 6.0 with Java Plug-in 1.4.2 or 1.5.0
Note HTTP 1.1—Settings for Internet Options > Advanced > HTTP 1.1 should use HTTP 1.1 for both proxy and non-proxy connections.
Netscape 7.1/7.2 with Java Plug-in 1.4.2 or 1.5.0
|
SSL Encryption Settings—All available encryption options are enabled for SSL in the browser preferences.
|
Sun Solaris
|
Sun Solaris 8 or 9 running CDE window manager
|
Mozilla 1.7.3 with Java Plug-in 1.4.2 or 1.5.0
|
Linux
|
Red Hat Linux 9.0 or Red Hat Linux WS, Version 3 running GNOME or KDE
|
Mozilla 1.7.3 with Java Plug-in 1.4.2
|
Important Notes
This section includes the following topics:
•Upgrading to a New Software Release
•Getting Started with ASDM
•Unsupported Characters
•ASDM CLI Does Not Support Interactive User Commands
•Printing from ASDM
•Unsupported Commands
•Securing the Failover Key
Upgrading to a New Software Release
If you have a Cisco Connection Online (CCO) login, you can obtain software from the following website:
http://www.cisco.com/cisco/software/navigator.html?mdfid=268438162&i=rp
Refer to the Guide for Cisco PIX 6.2 and 6.3 Users Upgrading to Cisco PIX Software Version 7.0 for more information.
Note Before you upgrade your device manager, upgrade your platform software to Cisco PIX software Version 7.0.
To upgrade from PIX Device Manager to ASDM, perform the following steps:
Step 1 Copy the ASDM binary file (asdm-501.bin) to a TFTP or FTP server on your network.
Step 2 Log in to your security appliance using the console (or other appropriate method that you have configured).
Step 3 Ensure that you have connectivity from your security appliance to your TFTP/FTP server.
Step 4 If you have an existing copy of the PIX Device Manager, delete it:
Step 5 Copy the ASDM binary onto your security appliance using the appropriate command:
•For TFTP: copy tftp://your-server-IP/pathtofile flash:/asdm-501.bin
•For FTP: copy ftp://your-server-IP/pathtofile flash:/asdm-501.bin
Note For more information on the copy command and its options, see the Cisco Security Appliance Command Reference.
Step 6 If you have more than one ASDM image, enter the following command to configure the location of the ASDM image:
asdm image flash:/asdm501.bin
Step 7 Enter the following command to enable the HTTPS server on the device:
Step 8 Identify the systems or networks that are allowed to access ASDM by specifying one or more hosts/networks, using the following command:
http 10.1.1.1 255.255.255.255 inside
where IP address 10.1.1.1 is a host that can access ASDM and which is connected via the inside interface. Refer to Cisco Security Appliance Command Reference for more information on the options to the http command.
Step 9 Verify that ASDM is installed correctly by connecting from the client system (10.1.1.1 in the preceding example) to the security appliance, using a supported browser. For example:
https://10.1.1.254/admin/
where 10.1.1.254 is the IP address of the inside interface of the device in Step 8.
Note ASDM requires Java Plug-in software. After you install ASDM, download the latest Java Plug-in from the following site:http://www.cisco.com/cisco/software/navigator.html?a=a&i=rch.
Deleting Your Old Cache
In early beta releases of ASDM and in previous releases of PDM (Versions 4.1 and earlier), the device manager stored its cache in: <userdir>\pdmcache. For example, D:\Documents and Settings\jones\pdmcache.
Now, the cache directory for ASDM is in: <user dir>\.asdm\cache.
The File > Clear ASDM Cache option in ASDM clears this new cache directory. It does not clear the old one. To free up space on your system, if you are no longer using your older versions of PDM or ASDM, delete your pdmcache directory manually.
Getting Started with ASDM
If you are using ASDM for the first time on a new security appliance, follow the instructions in this section to get started using ASDM. If you are upgrading an existing device, see Upgrading to a New Software Release.
Because ASDM uses a GUI interface, it requires that you access it from a PC using a supported web browser. For the supported browsers, see the "Client PC Operating System and Browser Requirements" section.
Before You Begin
Before using ASDM for the first time, do the following:
Step 1 Set up your security appliance.
Step 2 Connect your PC directly to the security appliance via the port Ethernet 1.
Step 3 Do one of the following:
–Either configure your PC for DHCP, or
–Make sure your PC is on the same subnet as the security appliance. (The default IP address for the security appliance is: 192.168.1.1. The default subnet mask is 255.255.255.0.)
•If you want to configure transparent firewall mode on your security appliance, enter the CLI setup command. Refer to the Cisco Security Appliance Command Line Configuration Guide for more information.
Starting ASDM
To start ASDM for the first time, perform the following steps:
Step 1 Start ASDM from a supported web browser connected to the security appliance by entering the URL:
https://192.168.1.1/admin/
where 192.168.1.1 is the IP address of the security appliance.
Note Be sure to enter https, not http.
Step 2 Click OK or Yes to all prompts, including the name and password prompt. No name or password is required for a new device.
If ASDM does not start, check the device configuration. Your security appliance should be configured to accept ASDM configuration on its inside interface. (A new security appliance is configured this way by default.) If you need to modify the configuration to reestablish this default setting, use the CLI. Include configuration information similar to the following.
Note This example is of a PIX security appliance in single mode. If you are using an ASA security appliance, use the Management0/0 interface in place of Ethernet1.
interface Ethernet1
nameif inside
security-level 100
ip address 192.168.1.1 255.255.255.0
http server enable
http 0.0.0.0 0.0.0.0 inside
where the IP address 192.168.1.1 is on the same subnet as your security appliance and inside is the default name of the interface. (You might give your interface a different name, such as "management.")
The http server enable command with the inside argument enables the HTTP(S) server on the security appliance interface named inside. The http command with the 0.0.0.0 0.0.0.0 arguments allows HTTP traffic from any and all IP addresses and subnet masks to the HTTP server through the interface named inside. For more information, see the http and http server enable commands in the Cisco Security Appliance Command Reference.
Note Refer to the configure factory defaults or setup command in the Cisco Security Appliance Command Line Configuration Guide for more information on using the CLI to reestablish factory default settings.
Using the Startup Wizard
The Startup Wizard helps you easily configure a single mode device or a context of a multiple mode device.
Use the Startup Wizard to configure the basic set-up of your security appliance:
Step 1 If your security appliance is in multi mode, for each new context, do the following:
a. Create a new context using the System > Configuration > Features > Security Context panel.
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 Context icon on the upper header bar and select the context name from the Context menu on the lower header bar.
e. Click Context > Configuration > Wizards > Startup.
f. Click Launch Startup Wizard.
If your security appliance is in single mode:
a. Click Configuration > Wizards > Startup.
b. Click Launch Startup Wizard.
Step 2 Click Next as you proceed through the Startup Wizard panels, filling in the appropriate information in each panel, such as device name, domain name, passwords, interface names, IP addresses, basic server configuration, and access permissions.
Step 3 Click Finish on the last panel to transmit your configuration to the security appliance. Reconnect to ASDM using the new IP address, if the IP address of your connection changes.
(Optional.) You can now enter other configuration details on the Configuration > Features panels.
VPN Wizard
The VPN Wizard configures basic VPN access for site-to-site or remote-client access. The VPN Wizard is available only for security appliances running in single context mode with routed (not transparent) firewall mode.
Step 1 Start ASDM.
Step 2 Click Configuration > Wizards > VPN. Click Launch VPN Wizard.
Step 3 Supply information on each wizard panel. Click Next to move through the VPN Wizard panels. You may use the default IPSec and IKE policies. Click the Help button for more information on each field.
Step 4 After you complete entering the VPN Wizard information, click Finish on the last panel to transmit your configuration to the security appliance.
You can now test the configuration.
Bootstrapping LAN Failover
This section describes how to implement failover on security appliances connected via a LAN.
If you are connecting two ASA security appliances for failover, you must connect them via a LAN. If you are connecting two PIX security appliances, you can connect them using either a LAN or a serial cable.
Tip If your PIX security appliances are located near each other, you might prefer connecting them with a serial cable to connecting them via the LAN. Although the serial cable is slower than a LAN connection, using a cable prevents having to use an interface or having LAN and state failover share an interface, which could affect performance. Also, using a cable enables the detection of power failure on the peer device.
As specified in the Cisco Security Appliance Command Line Configuration Guide, both devices must have appropriate licenses and have the same hardware configuration.
Before you begin, decide on active and standby IP addresses for the interfaces ASDM connects through on the primary and secondary devices. These IP addresses must be assigned to device interfaces with HTTPS access.
To configure LAN failover on your security appliance, perform the following steps:
Step 1 Configure the secondary device for HTTPS IP connectivity. Use the configure factory defaults or the setup CLI command to assign the standby IP address to the ASDM interface on the secondary device.
Step 2 After configuration, the secondary device, has a configuration such as the following. (If you are using an ASA security device, replace the interface Ethernet1 with Management0/0.)
security-level 100
ip address 192.168.1.2 255.255.255.0
http 0.0.0.0 0.0.0.0 inside
where in this example IP address 192.168.1.2 is the standby IP address of the ASDM interface on the secondary device.
Step 3 Configure the primary device for HTTPS IP connectivity using the active IP address for the ASDM interface.
Step 4 Connect the pair of devices together and to their networks in their failover LAN cable configuration.
Step 5 Start ASDM from the primary device through a supported web browser. (See the section Starting ASDM.)
Step 6 Perform one of the following steps, depending on your security context mode:
a. If your device is in multiple security context mode, click Context. Choose the admin context from the Context drop-down menu, and click Configuration > Features > Properties > Failover.
b. If your device is in single mode, click Configuration > Features > Properties > Failover. Click the Interfaces tab.
Step 7 Perform one of the following steps, depending on your firewall mode:
a. If your device is in routed mode: configure standby addresses for all routed mode interfaces.
b. If your device is in transparent mode: configure a standby management IP address.
Note Interfaces used for failover connectivity should not have names (in single mode) or be allocated to security contexts (in multiple security context mode). In multiple context mode, other security contexts may also have standby IP addresses configured.
Step 8 Perform one of the following steps, depending on your security context mode:
a. If your device is in multiple security context mode: click System > Configuration > Features > Failover.
b. If your device is in single mode: click Configuration > Features > Properties > Failover.
Step 9 On the Setup tab of the Failover panel under LAN Failover, select the interface that is cabled for LAN failover.
Step 10 Configure the remaining LAN Failover fields.
Step 11 (Optional) Provide information for other fields in all of the failover tabs. If you are configuring Active/Active failover, you must configure failover groups in multiple security context mode. If more than one failover pair of devices coexist on a LAN in Active/Active failover, provide failover-group MAC addresses for any interfaces on shared LAN networks.
Step 12 On the Setup tab, select the Enable Failover check box. If you are using the PIX 500 series security appliance, select the Enable LAN rather than serial cable failover check box.
Step 13 Click Apply, read the warning dialog that appears, and click OK. A dialog box about configuring the peer appears.
Step 14 Enter the IP address of the secondary device, which you configured as the standby IP address of the ASDM interface. Wait about 60 seconds. The standby peer still could become temporarily inaccessible.
Step 15 Click OK. Wait for configuration to be synchronized to the standby device over the failover LAN connection.
The secondary device should now enter standby failover state using the standby IP addresses. Any further configuration of the active device or an active context is replicated to the standby device or the corresponding standby context.
ASA Interface Supports Either WebVPN or ASDM Admin Session
The security appliance supports either WebVPN or an ASDM administrative session on an interface, but not both simultaneously. To use ASDM and WebVPN at the same time, configure them on different interfaces.
Unsupported Characters
ASDM does not support any non-English characters or any other special characters. If you enter non-English characters in any text entry field, they become unrecognizable when you submit the entry, and you cannot delete or edit them.
If you are using a non-English keyboard or usually type in language other than English, be careful not to enter non-English characters accidentally.
Workaround:
For work around, see CSCeh39437 under Caveats.
ASDM CLI Does Not Support Interactive User Commands
ASDM provides a CLI tool (click Tools > Command Line Interface...) that allows you to enter certain CLI commands from ASDM. For a list of specific commands that are not support, see Unsupported Commands.
The ASDM CLI feature also 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. On 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 key
Input 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 panels.
•For CLI commands that have a noconfirm option, use the noconfirm option when entering the CLI command. For example:
crypto key generate rsa noconfirm
Printing from ASDM
Note Printing is supported only for Microsoft Windows 2000 or XP in this release.
If you want to print from within ASDM, start ASDM in application mode. Printing is not supported in applet mode in this release.
ASDM supports printing for the following features:
•The Configuration > Features > Interfaces table
•All Configuration > Features > Security Policy tables
•All Configuration > NAT tables
•The Configuration > Features > VPN > IPSec > IPSec Rules table
•Monitoring > Features > Connection Graphs and its related table
Unsupported Commands
ASDM does not support the complete command set of the CLI. In most cases, ASDM ignores unsupported commands, and they can remain in your configuration. In the case of the alias command, ASDM enters into Monitor-only mode until you remove the command from your 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, see Options > 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 3 by your system administrator, which allows Monitor-only mode. For more information, see Configuration > Device Administration > User Accounts and Configuration > Device Administration > AAA Access.
Ignored and View-Only Commands
The following table lists commands that ASDM supports in the configuration when added by 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 it is view-only, then the command appears in the GUI, but you cannot edit it.
Unsupported Commands
|
ASDM Behavior
|
access-list
|
Ignored if not used, except for use in VPN group policy screens
|
asr-group
|
Ignored
|
capture
|
Ignored
|
established
|
Ignored
|
failover timeout
|
Ignored
|
ipv6, any IPv6 addresses
|
Ignored
|
object-group icmp-type
|
View-only
|
object-group network
|
Nested group is view-only
|
object-group protocol
|
View-only
|
object-group service
|
Nested group cannot be added
|
pager
|
Ignored
|
pim accept-register route-map
|
Ignored. Only the list option can be configured using ASDM
|
prefix-list
|
Ignored if not used in an OSPF area
|
route-map
|
Ignored
|
service-policy global
|
Ignored if it uses a match access-list class. For example:
access-list myacl line 1 extended permit ip
any any
service-policy mypm global
|
sysopt nodnsalias
|
Ignored
|
sysopt uauth allow-http-cache
|
Ignored
|
terminal
|
Ignored
|
virtual
|
Ignored
|
ASDM Limitations
ASDM does not support the one-time password (OTP) authentication mechanism.
Other CLI Limitations
•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.255
Securing the Failover Key
To prevent the failover key from being replicated to the peer unit in clear text for an existing failover configuration, disable failover on the active unit (or in the system execution space on the unit that has failover group 1 in the active state), enter the failover key on both units, and then reenable failover. When failover is reenabled, the failover communication is encrypted with the key.
Follow this procedure on the active device:
Step 1 Perform one of the following steps, depending on your security context mode:
a. If your device is in single mode, navigate to Configuration > Features > Properties > Failover > Setup.
b. If you device is in multiple mode, navigate to System > Configuration > Features > Failover > Setup.
Step 2 Turn off failover. (The standby should switch to pseudo-standby mode.)
a. Clear the Enable failover check box.
b. Click Apply. (Click OK if CLI preview is enabled.)
Step 3 Enter the failover key in the Shared Key box.
Step 4 Reenable failover.
a. Select the Enable failover check box.
b. Click Apply. (Click OK if CLI preview is enabled.) A dialog box about configuring the peer appears.
Step 5 Enter the IP address of the peer. Wait about 60 seconds. Even though the standby peer does not have the shared failover key, the standby peer still could become inaccessible.
Step 6 Click OK. (Click OK if CLI preview is enabled.) Wait for configuration to be synchronized to the standby device over the encrypted failover LAN connection.
Caveats
The following sections describe caveats for the 5.0 release.
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/l
To become a registered cisco.com user, go to the following website:
http://tools.cisco.com/RPF/register/register.do
Open Caveats - Release 5.0(2)
Table 2 Open Caveats
ID Number
|
Software Release 5.0(2)
|
Corrected
|
Caveat Title
|
CSCeg14905
|
No
|
Applying service group change causes no ACL CLI to be generated
|
CSCeg67083
|
No
|
failover panel lock after apply config will need reset to input data
|
CSCeg69476
|
No
|
ASDM can not take any input from keyboard from SunOS 5.8 / Mozilla
|
CSCeh06459
|
No
|
ASDM can not create appropriate ACL for QoS on outbound interface
|
CSCeh20409
|
No
|
Startup Wizard allows not naming any interface
|
CSCeh24529
|
No
|
ASDM sometimes allows more than 2 traffic match criteria
|
CSCeh24609
|
No
|
Live Log: live log on Monitoring/Home don't work after disconn/conn
|
CSCeh33941
|
No
|
ASDM: Webtype ACL port checking does not match supported values
|
CSCeh39437
|
No
|
Non-English characters do not display properly in some screens
|
CSCeh39531
|
No
|
ASDM allows user to configure same static for different networks
|
CSCeh41391
|
No
|
Priority Queue screen - range limits for Add are not correct
|
CSCeh42043
|
No
|
ASDM-IP AUDIT Policy-to-interface pull-down don't track mouse motion
|
CSCeh43422
|
No
|
edit nssa for default-info, metric and metric-type ignored
|
CSCeh43569
|
No
|
ASDM: Logging fails-> Exception occurred during event dispatching
|
CSCeh52524
|
No
|
Check logging permit when syslog server is down doesn't enable apply
|
CSCeh53158
|
No
|
Wrong cmds sent when objgp w/ PNAT is edited to add net-obj with NAT
|
CSCeh66856
|
No
|
ASDM crashes IE and launcher after socket timeout
|
CSCei56371
|
No
|
MTU minimum size can not be set below 300
|
CSCei58507
|
No
|
ASDM: missing enhanced split tunnel functionality - extended ACLs
|
Resolved Caveats - Release 5.0(2)
Table 3 Resolved Caveats
ID Number
|
Software Release 5.0(2)
|
Corrected
|
Caveat Title
|
CSCei16647
|
Yes
|
Cannot read iplog file downloaded from ASDM
|
CSCeh53516
|
Yes
|
ASDM displays in-complete rule in error in some configurations
|
CSCeh78270
|
Yes
|
IKE policy configuration should include infinite lifetime option
|
CSCeh91338
|
Yes
|
ASDM Home Page is blank if authenticated username is 3 chars or less
|
CSCeh93183
|
Yes
|
Destination IP is not correctly set in the CLI
|
CSCeh95237
|
Yes
|
Dynamic Crypto Maps unattached to static crypto maps crash ASDM
|
CSCei23118
|
Yes
|
Show past events with large number of hours gives blank screen
|
CSCei25996
|
Yes
|
Operator having trouble changing Global Variable
|
CSCei27394
|
Yes
|
ASDM is not displaying VPN IKE tunnel summary on home page
|
CSCei38991
|
Yes
|
Blocking property panel delete button not visible in multi-mode
|
CSCei10049
|
Yes
|
Error displayed when trying to edit inline interface pair
|
CSCei08437
|
Yes
|
Stopping IP Logging giving java.lang.Exception
|
CSCei34740
|
Yes
|
Need to disable Use Additional Data option for Add Rate Limit
|
CSCei37660
|
Yes
|
Help page didn't popup in Add Rate Limit panel
|
CSCei38088
|
Yes
|
Add support for IPS 5.1 sensor
|
CSCeh22246
|
Yes
|
asdm_handler: After Tearing down overnight testing ASDM rep 114 tun
|
CSCeg85016
|
Yes
|
Can't login to ASDM when authentication required (Linux, JRE 1.5.0)
|
CSCeh01635
|
Yes
|
Printing from ASDM invoked as an applet is not supported
|
CSCeh43624
|
Yes
|
NTP:unable to edit key value and number
|
CSCeh49697
|
Yes
|
ASDM IPSec/IKE graphs reporting tunnel count incorrectly.
|
CSCeh50535
|
Yes
|
Can't edit a route summarization entry in second ospf process
|
CSCeh39560
|
Yes
|
ASDM cannot switch from serial to LAN failover
|
Related Documentation
For additional information on ASDM or its platforms, refer to the ASDM online Help or the following documentation found on Cisco.com:
•Cisco ASA 5500 Series Hardware Installation Guide
•Cisco ASA 5500 Series Quick Start 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
•Cisco PIX Security Appliance Release Notes
•Guide for Cisco PIX 6.2 and 6.3 Users Upgrading to Cisco PIX Software Version 7.0
•Release Notes for Cisco Intrusion Prevention System 5.0
•Installing and Using Cisco Intrusion Prevention System Device Manager 5.0
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.
Feedback
