Configuring An Ipv4 Advanced Acl - HP FlexFabric 5700 series Configuration Manual

Configuring an IPv4 advanced ACL

IPv4 advanced ACLs match packets based on the following criteria:
• Source IP addresses.
Destination IP addresses.
•
Packet priorities.
•
Protocol numbers.
•
Other protocol header information, such as TCP/UDP source and destination port numbers, TCP
•
flags, ICMP message types, and ICMP message codes.
Compared to IPv4 basic ACLs, IPv4 advanced ACLs allow more flexible and accurate filtering.
To configure an IPv4 advanced ACL:
Step
1. Enter system view.
2. Create an IPv4 advanced ACL
and enter its view.
3. (Optional.) Configure a
description for the IPv4
advanced ACL.
4. (Optional.) Set the rule
numbering step.
5. Create or edit a rule.
6. (Optional.) Add or edit a rule
comment.
Command
system-view
acl number acl-number [ name
acl-name ] [ match-order { auto |
config } ]
description text
step step-value
rule [ rule-id ] { deny | permit }
protocol [ { { ack ack-value | fin
fin-value | psh psh-value | rst
rst-value | syn syn-value | urg
urg-value } * | established } |
counting | destination
{ dest-address dest-wildcard |
any } | destination-port operator
port1 [ port2 ] | { dscp dscp |
{ precedence precedence | tos tos }
* } | fragment | icmp-type
{ icmp-type [ icmp-code ] |
icmp-message } | logging | source
{ source-address source-wildcard |
any } | source-port operator port1
[ port2 ] | time-range
time-range-name ] *
rule rule-id comment text
6
Remarks
N/A
By default, no ACL exists.
IPv4 advanced ACLs are
numbered in the range of 3000 to
3999.
You can use the acl name acl-name
command to enter the view of a
named ACL.
By default, an IPv4 advanced ACL
has no ACL description.
The default setting is 5.
By default, an IPv4 advanced ACL
does not contain any rule.
The logging keyword takes effect
only when the module (for
example, packet filtering) that uses
the ACL supports logging.
If an ACL is for QoS traffic
classification or packet filtering, do
not specify neq for the operator
argument.
By default, no rule comments are
configured.