H3C S7500 Series Ethernet Switches Release 3135 DHCP Configuration Examples

QACL Configuration Examples
H3C S7500 Series Ethernet Switches Release 3135 Chapter 2 QACL Configuration Examples
2-14
6) The ACL rules configured for traffic policing, traffic redirecting, traffic mirroring,
traffic accounting, priority marking, or flow-based selective QinQ must be permit
statements.
7) On a non-type-A LPU, if a traffic policing rule is configured with the kbps keyword
specified, the rate limit granularity is 64 kbps. That is, if the rate value you input is
in the range of N×64 to (N+1)×64 (N is a natural number), the switch sets the value
to (N+1)×64 kbps automatically.
8) In traffic redirecting configuration, the source port and the destination port must
reside on the same LPU.
9) In traffic mirroring configuration, for centralized LPUs, all the involved ports must
reside on the same LPU; for distributed systems, all the involved ports must reside
in the same distributed system.
10) For an S7500 switch, you can configure multiple mirrored ports but only one
monitor port for traffic mirroring. You are recommended to use the monitor port
only for traffic mirroring. If you use it as a service port at the same time, service
traffic may be affected.
11) Non-type-A LPUs of the S7500 series support three queue scheduling algorithms:
round robin (RR), strict priority (SP), and weighted round robin (WRR). When
configuring WRR, you can set some weight values to 0, thus implementing the SP
+ WRR queue scheduling algorithm.
12) With the SP + WRR queue scheduling algorithm enabled, the switch schedules SP
queues preferentially. For example, suppose queues 0 through 3 adopt SP (with
the weight being 0), and queues 4 through 7 adopt WRR. The switch will schedule
queues 0 through 3 with the SP algorithm preferentially, and then schedule
queues 4 through 7 with the WRR algorithm when the SP queues are empty.
13) Flow-based selective QinQ is usually configured on the customer-side port on the
edge device connecting the service provider network to the customer network.
Usually, the customer-side port is configured as a hybrid port.
2.4 Referencing ACLs for Other Purposes
You can reference ACLs to do the following in addition to filtering packets:
z Using ACL 2000 through ACL 3999 for Telnet access control, and ACL 2000
through ACL 2999 for SNMP/Web login control.
z Using ACL 2000 through ACL 3999 as match criteria in routing policies.
z Using ACL 2000 through ACL 3999 for routing information filtering.
z Using ACL 2000 through ACL 2999 for filtering routing entries to be displayed.
z Using ACL 2000 through ACL 2999 for filtering FIB entries to be displayed.
z Using ACL 2000 through ACL 2999 to control access to a TFTP server.