3-31
Cisco ASA 5500 Series Configuration Guide using ASDM
Chapter3 Using the ASDM User Interface
Unsupported Commands
Unsupported Commands
ASDM supports almost all commands available for the adaptive ASA, 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, page3-31
•Effects of Unsupported Commands, page 3-32
•Discontinuous Subnet Masks Not Supported, page3-32
•Interactive User Commands Not Supported by the ASDM CLI Tool, page3-32

Ignored and View-Only Commands

Table 3 -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.
Table3-5 List of Unsupported Commands
Unsupported Commands ASDM Behavior
capture Ignored.
coredump Ignored. This can be configured only using the CLI.
crypto engine large-mod-accel Ignored.
dhcp-server (tunnel-group name
general-attributes)
ASDM only allows one setting for all DHCP servers.
eject Unsupported.
established Ignored.
failover timeout Ignored.
fips Ignored.
nat-assigned-to-public-ip Ignored.
pager Ignored.
pim accept-register route-map Ignored. You can configure only the list option using
ASDM.
prefix-list (supported in 6.4(7) and later) Ignored if not used in an OSPF area.
service-policy global Ignore d if it u ses a match access-list class. For example:
access-list myacl extended permit ip any any
class-map mycm
match access-list myacl
policy-map mypm
class mycm
inspect ftp
service-policy mypm global
set metric Ignored.
sysopt nodnsalias Ignored.