IPv4 Access Control Lists (ACLs)
General ACL Operating Notes
Monitoring Shared Resources. Applied ACLs share internal switch
resources with several other features. The switch provides ample resources
for all features. However, if the internal resources become fully subscribed,
additional ACLs cannot be applied until the necessary resources are released
from other applications. For information on determining current resource
availability and usage, refer to appendix E, “Monitoring Resources” in the
Management and Configuration Guide for your switch.
Protocol Support . ACL criteria does not include use of MAC information
or QoS.
Replacing or Adding To an Active ACL Policy. If you assign an ACL to
an interface and subsequently add or replace ACEs in that ACL, each new ACE
becomes active when you enter it. If the ACL is configured on multiple
interfaces when the change occurs, then the switch resources must accom-
modate all applications of the ACL. If there are insufficient resources to
accommodate one of several ACL applications affected by the change, then
the change is not applied to any of the interfaces and the previous version of
the ACL remains in effect. Refer to “Monitoring Shared Resources”, above.
“Strict” TCP and UDP. When the ACL configuration includes TCP or UDP
options, the switch operates in “strict” TCP and UDP mode for increased
control. In this case, the switch compares all TCP and UDP packets against
the ACLs. (In the ProCurve 9300m and 9404sl Routing Switches, the Strict TCP
and Strict UDP modes are optional and must be specifically invoked.)
9-100
To Next Page
Loading...
Need help?
General
