HP ProCurve W.14.03 Figure 9-19.Example of Inserting an ACE in an Existing ACL, Figure 9-20.Example of Inserting an ACE into an Existing Sequence

Enters the “Named-ACL context for “My-List”.

Inserts the new ACE.

IPv4 Access Control Lists (ACLs)

Editing an Existing ACL

2.Begin the ACE command with a sequence number that identifies the position you want the ACE to occupy. (The sequence number range is 1­ 2147483647.)

3.Complete the ACE with the command syntax appropriate for the type of ACL you are editing.

For example, inserting a new ACE between the ACEs numbered 10 and 20 in figure 9-18 requires a sequence number in the range of 11-19 for the new ACE.

ProCurve(config)# ip access-list standard My-List ProCurve(config-std-nacl)# 15 deny 10.10.10.1/24 ProCurve(config-std-nacl)# show run

.

.

.

ip access-list standard "My-List" 10 permit 10.10.10.25 0.0.0.0 15 deny 10.10.10.1 0.0.0.255

20 permit 10.20.10.117 0.0.0.0

30 deny 10.20.10.1 0.0.0.255

40 permit 0.0.0.0 255.255.255.255 exit

Figure 9-19. Example of Inserting an ACE in an Existing ACL

In the following example, the first two ACEs entered become lines 10 and 20 in the list. The third ACE entered is configured with a sequence number of 15 and is inserted between lines 10 and 20.

ProCurve(config)# ip access-list standard List-01 ProCurve(config-std-nacl)# permit 10.10.10.1/24 ProCurve(config-std-nacl)# deny 10.10.1.1/16 ProCurve(config-std-nacl)# 15 permit 10.10.20.1/24 ProCurve(config-std-nacl)# show run

Becomes Line 10

Becomes Line 20

Running configuration:

. . .

ip access-list standard "List-01" 10 permit 10.10.10.1 0.0.0.255

15 permit 10.10.20.1 0.0.0.255

20 deny 10.10.1.1 0.0.255.255 exit

Lines 10 and 20 were automatically numbered according to their order of entry in the list. Line 15 was explicitly numbered by the 15 permit command and was inserted in its proper place in the list.

Figure 9-20. Example of Inserting an ACE into an Existing Sequence

9-78