Access Control Lists (ACLs) for the Series 3400cl and Series 6400cl Switches
Editing ACLs and Creating an ACL Offline
■ 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.)
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 < interface > < permit | deny > < any | host | ip-addr/mask-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.
no access-list < interface > < permit | deny > < ip | tcp | udp >
< src-addr: any | host | ip-addr/mask-length > [operator < src-port-num >]
< dest-addr: any | host | ip-addr-mask-length > [operator < dest-port-num >
[log]
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.
For example, the first of the following two commands creates an ACE in ACL
22 and the second deletes the same ACE:
Creates an ACE in ACL 22.
Removes the same ACE
from ACL 22, regardless of
the ACE’s position in the
ACL.
Figure 10-26. Example of Deleting an ACE from a Standard ACL
Figure 10-27 shows an example of deleting an ACE from an extended ACL.
10-66
To Next Page
Loading...
