To delete the meter, use the following command:
delete meter <metername>
Configuring the ACL Meter
After the ACL meter is created, you will configure it. Configuring the ACL meter sets allowable traffic
limits, and the actions to take with out of limit traffic. Use the following command to configure an ACL
meter:
configure meter <metername> {max-burst-size <burst-size> [Gb | Kb | Mb]} {committed-
rate <cir-rate> [Gbps | Mbps | Kbps]} {out-actions [drop | set-drop-precedence {dscp
[none | <dscp-value>]}}
Associating the Meter with an ACL
To associate a meter with an ACL, you will add the
modifier of the ACL rule entry, similar to the
associate the meter maxbw with an ACL, use syntax similar to the following:
entry
meter_bw {
if
{
} then {
meter maximum_bandwidth;
}
}
This example will take the actions specified for the meter maxbw for all the traffic that this ACL is
applied to.
Example ACL Rule Entries
The following entry accepts all the UDP packets from the 10.203.134.0/24 subnet that are destined for
the host 140.158.18.16, with source port 190 and a destination port in the range of 1200 to 1400:
entry
udpacl {
if
{
source-address 10.203.134.0/24;
destination-address 140.158.18.16/32;
protocol
udp;
source-port 190;
destination-port
} then {
permit;
}
}
The following rule entry accepts TCP packets from the 10.203.134.0/24 subnet with a source port larger
than 190 and ACK & SYN bits set and also increments the counter tcpcnt. The packets will be forwarded
using QoS profile QP3:
entry
tcpacl {
if
{
ExtremeWare XOS 11.1 Concepts Guide
meter <metername>
count <countername>
1200 - 1400;
ACL Policies
statement to the condition
statement. For example, to
189