Brocade BigIron RX Series Configuration Guide - Manual (Page 706)

628 BigIron RX Series Configuration Guide
53-1002484-04
Modifying ACLs
22
Thus, if a packet matches the first entry in this ACL and is therefore denied, the software does not
compare the packet to the remaining ACL entries. In this example, packets from host
209.157.22.26 will always be dropped, even though packets from this host match the second
entry.
You can use the CLI to reorder entries within an ACL by individually removing the ACL entries and
then re-adding them. To use this method, enter “no” followed by the command for an ACL entry,
and repeat this for each ACL entry in the ACL you want to edit. After removing all the ACL entries
from the ACL, re-add them.
This method works well for small ACLs such as the example above, but can be impractical for ACLs
containing many entries. Therefore, the device provides an alternative method that lets you upload
an ACL list from a TFTP server and replace the ACLs in the device’s running-config file with the
uploaded list. To change an ACL, you can edit the ACL on the file server, then upload the edited ACL
to the device. Then you can save the changed ACL to the device’s startup-config file.
ACL lists contain only the ACL entries themselves, not the assignments of ACLs to interfaces. You
must assign the ACLs on the device itself.
NOTE
The only valid commands that are valid in the ACL list are the access-list and end commands; other
commands are ignored.
To modify an ACL by configuring an ACL list on a file server.
1. Use a text editor to create a new text file. When you name the file, use 8.3 format (up to eight
characters in the name and up to three characters in the extension).
NOTE
Make sure the device has network access to the TFTP server.
2. Optionally, clear the ACL entries from the ACLs you are changing by placing commands such as
the following at the top of the file.
BigIron RX(config)#no access-list 1
BigIron RX(config)#no access-list 101
When you load the ACL list into the device, the software adds the ACL entries in the file after
any entries that already exist in the same ACLs. Thus, if you intend to entirely replace an ACL,
you must use the no access-list <num> command to clear the entries from the ACL before the
new ones are added.
3. Place the commands to create the ACL entries into the file. The order of the separate ACLs
does not matter, but the order of the entries within each ACL is important. The software applies
the entries in an ACL in the order they are listed within the ACL. Here is an example of some
ACL entries.
BigIron RX(config)#access-list 1 deny host 209.157.22.26 log
BigIron RX(config)#access-list 1 deny 209.157.22.0 0.0.0.255 log
BigIron RX(config)#access-list 1 permit any
BigIron RX(config)#access-list 101 deny tcp any any eq http log
The software will apply the entries in ACL 1 in the order shown and stop at the first match.
Thus, if a packet is denied by one of the first three entries, the packet will not be permitted by
the fourth entry, even if the packet matches the comparison values in this entry.