IPv4 Access Control Lists (ACLs)
Editing ACLs and Creating an ACL Offline
Note
Before editing an assigned ACL, you must use the no interface < interface > ip
access-group < acl-# > in command to remove the ACL from all interfaces to
which it is assigned.
Using the CLI To Edit a Short ACL. To insert a new ACE between exist
ing ACEs in a short ACL, you may want to delete the ACL and then re-configure
it by entering your updated list of ACEs in the correct order.
Using the CLI to Edit a Longer ACL. To insert a new ACE between exist
ing ACEs in a longer ACL:
General Editing Rules
■
■
■
Deleting Any ACE from an ACL
You can delete an ACE from an ACL by repeating the ACE's entry command,
preceded by the "no" statement.
Syntax: no access-list < name-str |1-99> < permit | deny > < any | host | ip-addr/mask
9-62
a. Delete the first ACE that is out of sequence and all following ACEs
through the end of the ACL.
b. Re-Enter the desired ACEs in the correct sequence.
You can delete any ACE from an ACL by repeating the ACE's entry
command, preceded by the "no" statement. When you enter a new
ACE, the switch inserts it as the last entry of the specified ACL.
Deleting the last ACE from a numeric ACL, removes the ACL from
the configuration. Deleting the last ACE from a named ACL leaves the
ACL in memory. In this case, the ACL is "empty" and cannot perform
any filtering tasks. (In any ACL the implicit "deny any" does not apply
unless the ACL includes at least one explicit ACE.)
When you create a new ACL, the switch inserts it as the last ACL in
the startup-config file. (Executing write memory saves the running
config file to the startup-config file.)
length >
Deletes an ACE from a standard ACL. All variable parame
ters in the command must be an exact match with their
counterparts in the ACE you want to delete.