HP 6200YL - Manual (Page 216)

IPv6 Access Control Lists (ACLs)
Configuring and Assigning an IPv6 ACL
A Configured ACL Has No Effect Until You Apply It
to an Interface
The switch stores ACLs in the configuration file. Until you actually assign an
ACL to an interface, it is present in the configuration, but not used (and does
not use any of the monitored resources described in the appendix titled
“Monitored Resources” in the latest version of the Management and Config­
uration Guide
for your switch.)
You Can Assign an ACL Name to an Interface
Even if the ACL Has Not Been Configured
In this case, if you subsequently create an ACL with that name, the switch
automatically applies each ACE as soon as you enter it in the running-config
file. Similarly, if you modify an existing ACE in an ACL you already applied to
an interface, the switch automatically implements the new ACE as soon as
you enter it. (See “General ACL Operating Notes” on page 8-103.) The switch
allows up to 2048 ACLs each for IPv4 and IPv6. For example, if you configure
two ACLs, but assign only one of them to a VLAN, the ACL total is two, for the
two unique ACL names. If you then assign the name of an empty ACL to a
VLAN, the new ACL total is three, because the switch now has three unique
ACL names in its configuration. (RADIUS-based ACL resources are drawn
from the IPv4 allocation).
(For information on switch resource use, refer to “Monitoring Shared
Resources” on page 8-103.)
Using the CLI To Create an ACL
Command Page
access-list 8-41
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 8-84.)
8-40