Table of Contents
Advertisement
246
C
11: C
HAPTER
ONFIGURING AND
Modifying a
Security ACL
M
S
ANAGING
ECURITY
To stop the packet filtering of a user-based security ACL, you must
modify the user's configuration in the local database on the WX switch or
on the RADIUS servers where packet filters are authorized. For
information about deleting a security ACL from a user's configuration in
the local WX database, see "Clearing a Security ACL from a User or
Group" on page 320. To delete a security ACL from a user's
configuration on a RADIUS server, see the documentation for your
RADIUS server.
If you no longer need the security ACL, delete it from the configuration
with the clear security acl and commit security acl commands. (See
"Clearing Security ACLs" on page 242.)
You can modify a security ACL in the following ways:
Add another ACE to a security ACL, at the end of the ACE list. (See
"Adding Another ACE to a Security ACL" on page 247.)
Place an ACE before another ACE, so it is processed before
subsequent ACEs, using the before editbuffer-index portion of the
set security acl commands. (See "Placing One ACE before Another"
on page 247.)
Modify an existing ACE using the modify editbuffer-index portion of
the set security acl commands. (See "Modifying an Existing Security
ACL" on page 248.)
Use the rollback command set to clear changes made to the security
ACL edit buffer since the last time it was saved. The ACL is rolled back
to its state at the last commit command. (See "Clearing Security ACLs
from the Edit Buffer" on page 249.)
Use the clear security acl map command to stop the filtering action
of an ACL on a port, VLAN, or virtual port. (See "Clearing a Security
ACL Map" on page 245.)
Use clear security acl plus commit security acl to completely delete
the ACL from the WX switch's configuration. (See "Clearing Security
ACLs" on page 242.)
ACL
S
Advertisement
Table of Contents
