HP ProCurve W.14.03 Sequence Numbering in ACLs, no, access-list, access-list, access-list, Figure 9-16.Example of the Default Sequential Numbering for ACEs

IPv4 Access Control Lists (ACLs)

Editing an Existing ACL

■You can delete any ACE from any ACL (named or numbered) by using the ip access-listcommand to enter the ACL’s context, and then using the no < seq-#> command (page 9-79).

■Deleting the last ACE from an 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 does not apply unless the ACL includes at least one explicit ACE.)

Sequence Numbering in ACLs

The ACEs in any ACL are sequentially numbered. In the default state, the sequence number of the first ACE in a list is “10” and subsequent ACEs are numbered in increments of 10. For example, the following show run output lists three ACEs with default numbering in a list named “My-List”:

ip access-list standard "My-List" 10 permit 10.10.10.25 0.0.0.0 20 permit 10.20.10.117 0.0.0.0 30 deny 10.20.10.1 0.0.0.255 exit

Figure 9-16. Example of the Default Sequential Numbering for ACEs

You can add an ACE to the end of a named or numbered ACL by using either access-listfor numbered ACLs or ip access-listfor named ACLs:

ProCurve(config)# access-list 2 permit any	Appends an ACE to
	the end of a standard,
	numbered ACL.

ProCurve(Config)# ip access-list standard My-list

ProCurve(Config-ext-nacl)# permit ip any host 10.10.10.125

Enters the context of an extended ACL and appends an ACE to the end of the list.

Figure 9-17. Examples of Adding an ACE to the end of Numbered or Named ACLs

9-76