7Step Command Remarks5. Create or edit arule.rule [ rule-id ] { deny | permit }protocol [ { { ack ack-value | finfin-value | psh psh-value | rstrst-value | syn syn-value | urgurg-value } * | established } |counting | destination{ dest-addr dest-wildcard | any }| destination-port operatorport1 [ port2 ] | dscp dscp |fragment | icmp-type{ icmp-type [ icmp-code ] |icmp-message } | logging |precedence precedence |source { sour-addr sour-wildcard| any } | source-port operatorport1 [ port2 ] | time-rangetime-range-name | tos tos ] *By default, an IPv4 advanced ACL does notcontain any rule.If an IPv4 advanced ACL is for QoS trafficclassification or packet filtering:• Do not specify the fragment keyword.• Do not specify neq for the operator argument.• The logging and counting keywords (even ifspecified) do not take effect for QoS trafficclassification.6. Add or edit arule comment. rule rule-id comment text Optional.By default, no rule comments are configured.7. Add or edit arule rangeremark.rule [ rule-id ] remark text Optional.By default, no rule range remarks are configured.8. Enable countingACL rulematchesperformed inhardware.hardware-count enableOptional.Disabled by default.When the ACL is referenced by a QoS policy, thiscommand does not take effect.Configuring an IPv6 advanced ACLIPv6 advanced ACLs match packets based on the source IPv6 addresses, destination IPv6 addresses,packet priorities, protocols carried over IPv6, and other protocol header fields such as the TCP/UDPsource port number, TCP/UDP destination port number, ICMPv6 message type, and ICMPv6 messagecode.Compared to IPv6 basic ACLs, IPv6 advanced ACLs allow more flexible and accurate filtering.Configuration restrictions and guidelinesWhen the protocol argument takes 43, 44, 51, or 60, the ACL cannot function on for the outbound QoSapplication.Configuration procedureTo configure an IPv6 advanced ACL:Step Command Remarks1. Enter systemview. system-view N/A