6Step Command Remarks5. Create or edit arule.rule [ rule-id ] { deny |permit } [ counting |fragment | logging |routing [ type routing-type ]| source { ipv6-addressprefix-length |ipv6-address/prefix-length| any } | time-rangetime-range-name ] *By default, an IPv6 basic ACL does not contain anyrule.If the ACL is for QoS traffic classification or packetfiltering, do not specify the fragment and routingkeywords. The keywords can cause ACL applicationfailure.The logging and counting keywords (even ifspecified) do not take effect for QoS.6. Add or edit a rulecomment. rule rule-id comment text Optional.By default, no rule comments are configured.7. Add or edit a rulerange remark. rule [ rule-id ] remark text Optional.By default, no rule range remarks are configured.8. Enable countingACL rule matchesperformed inhardware.hardware-count enableOptional.Disabled by default.When the ACL is referenced by a QoS policy, thiscommand does not take effect.Configuring an advanced ACLConfiguring an IPv4 advanced ACLIPv4 advanced ACLs match packets based on source IP addresses, destination IP addresses, packetpriorities, protocols over IP, and other protocol header information, such as TCP/UDP source anddestination 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 Command Remarks1. Enter systemview. system-view N/A2. Create an IPv4advanced ACLand enter itsview.acl number acl-number [ nameacl-name ] [ match-order { auto| config } ]By default, no ACL exists.IPv4 advanced ACLs are numbered in the range of3000 to 3999.You can use the acl name acl-name command toenter the view of a named IPv4 ACL.3. Configure adescription forthe IPv4advanced ACL.description textOptional.By default, an IPv4 advanced ACL has no ACLdescription.4. Set the rulenumbering step. step step-value Optional.The default setting is 5.