ProCurve 6200yl User's Guide Page 335

  • Download
  • Add to my manuals
  • Print
  • Page
    / 596
  • Table of contents
  • BOOKMARKS
  • Rated. / 5. Based on customer reviews
Page view 334
10-49
Access Control Lists (ACLs)
Configuring and Assigning an ACL
Using the CLI To Create an ACL
You can use either the switch CLI or an offline text editor to create an ACL.
This section describes the CLI method, which is recommended for creating
short ACLs. (To use the offline method, refer to “Creating or Editing ACLs
Offline” on page 10-104.)
General ACE Rules
These rules apply to all ACEs you create or edit using the CLI:
Inserting or adding an ACE to an ACL:
Named ACLs: Add an ACE to the end of a named ACE by using the
ip access-list command to enter the Named ACL (nacl) context and
entering the ACE without the sequence number. For example, if you
wanted to add a “permit” ACL at the end of a list named “List-1” to
allow IP traffic from the device at 10.10.10.100:
ProCurve(config)# ip access-list standard List-1
ProCurve(config-std-nacl)# permit host
10.10.10.100
Insert an ACE anywhere in a named ACL by specifying a sequence
number. For example, if you wanted to insert a new ACE as line 15
between lines 10 and 20 in an existing ACL named “List-2” to deny IP
traffic from the device at 10.10.10.77:
ProCurve(config)# ip access-list standard List-2
ProCurve(config-std-nacl)# 15 deny host 10.10.10.77
Numbered ACLs: Add an ACE to the end of a numbered ACL by using
the access-list < 1 - 99 | 100 - 199 > command. For example, if you wanted
to add a “permit” ACE at the end of a list identified with the number
“11” to allow IP traffic from the device at 10.10.10.100:
ProCurve(config)# access-list 11 permit host
10.10.10.100
Command Page
access-list (standard ACLs) 10-51
access-list (extended ACLs) 10-60
Page view 334
1 2 ... 330 331 332 333 334 335 336 337 338 339 340 ... 595 596

Comments to this Manuals

No comments