Acl statistics and rate limit counting, Enabling acl statistics, Acl statistics and rate limit – Brocade FastIron Ethernet Switch Traffic Management Guide User Manual

Page 72: Counting

Advertising
background image

The command configures an adaptive rate limiting policy that enforces a guaranteed committed rate of
10000 kbps (10000 pkts/s in ICX 6650) and allows bursts of up to 1600 bytes (1600 packets in ICX
6650). It also enforces a peak rate of 20000 kbps (20000 pkts/s in ICX 6650) and allows bursts of
4000 bytes (4000 packets in ICX 6650) above the PIR limit. If the port receives additional bits during a
given one-second interval, the port permits all packets on the port and forwards the packets at the
lowest priority level.

Syntax: [no] traffic-policy TPDname rate-limit adaptive cir cirvalue cbs cbsvalue pir pirvalue pbs
pbsvalue exceed-action permit-at-low-pri

ACL statistics and rate limit counting

ACL statistics , also called ACL counting , enables the Brocade device to count the number of packets
and the number of bytes per packet to which ACL filters are applied.

Rate limit counting counts the number of bytes and the conformance level per packet to which rate
limiting traffic policies are applied. The device uses the counting method similar to the two-rate three-
color marker (trTCM) mechanism described in RFC 2698 for adaptive rate limiting, and the single-rate
three-color marker (srTCM) mechanism described in RFC 2697 for fixed rate limiting. Rate limit
counting is automatically enabled when a traffic policy is enforced (active). You can view these
counters using the show commands listed in

Viewing traffic policies

on page 73.

Enabling ACL statistics

NOTE
ACL statistics and ACL counting are used interchangeably throughout this chapter and mean the
same thing.

Use the procedures in this section to configure ACL statistics. Before configuring ACL statistics, see
what to consider in

Configuration notes and feature limitations for traffic policies

on page 62.

To enable ACL statistics on a device, first create a traffic policy , and then reference the traffic policy in
an extended ACL entry. Lastly, bind the ACL to an interface. The ACL counting policy becomes
effective on ports to which the ACLs are bound.

You also can enable ACL statistics when you create a traffic policy for rate limiting. Refer to

Enabling

ACL statistics with rate limiting traffic policies

on page 71.

Complete the following steps to implement the ACL statistics feature.

1.

Create a traffic policy. Enter a command such as the following.

device(config)#traffic-policy TPD5 count

2.

Create an extended ACL entry or modify an existing extended ACL entry that references the
traffic policy definition. Enter a command such as the following.

device(config)#access-list 101 permit ip host 10.10.12.2 any traffic-policy TPD5

3.

Bind the ACL to an interface. Enter commands such as the following.

device(config)#interface ethernet 4

device(config-if-e4)#ip access-group 101 in

device(config-if-e4)#exit

The previous commands configure an ACL counting policy and apply it to port e4. Port e4 counts
the number of packets and the number of bytes on the port that were permitted or denied by ACL
filters.

ACL statistics and rate limit counting

70

FastIron Ethernet Switch Traffic Management Guide

53-1003093-03

Advertising