Brocade Multi-Service IronWare QoS and Traffic Management Configuration Guide (Supporting R05.6.00) User Manual
Page 20
6
Multi-Service IronWare QoS and Traffic Management Configuration Guide
53-1003037-02
Traffic policing on Brocade NetIron CES and Brocade NetIron CER devices
1
These commands configure a traffic policing policy for outbound traffic on port 1/1. The policy
limits the average rate of all outbound traffic to 500 Mbps with a maximum burst size of 750 bits.
Configuring port-based traffic policing using a policy map
To configure port based traffic policing policy through a policy map, enter commands such as the
following.
Brocade(config)# interface ethernet 1/1
Brocade(config-if-1/1)# rate-limit input policy-map map1
These commands configure a traffic policing policy for inbound traffic on port 1/1. The policy
references policy map1 for rate limiting policy parameters.
The complete syntax for configuring a port-based traffic policing policy is:
Syntax: [no] rate-limit [in | out] [average-rate maximum-burst | policy-map map-name]
The input parameter applies the policy to traffic on inbound ports.
The output parameter applies the policy to traffic on outbound ports.
Only one inbound and one outbound port-based traffic policing policy can be applied to a port.
The average-rate parameter specifies the maximum rate allowed on a port during a one-second
interval. For the Brocade NetIron CER and Brocade NetIron CES devices, the Average Rate can be
entered in as any value from 0 up to the line rate of the port. Refer to
more details. This command is only used when configuring traffic policing directly to a port as
described in
“Applying traffic policing parameters directly to a port”
The maximum-burst parameter specifies the extra bits above the average rate that traffic can have.
Refer to
on page 2 for more details. This command is only used when configuring
traffic policing directly to a port as described in
“Applying traffic policing parameters directly to a
The policy-map parameter specifies the policy map named in the policy-map variable to be used to
provide parameters for rate limiting the port and VLAN specified. This command is only used when
configuring traffic policing to a port using a policy map as described in
parameters using a policy map”
NOTE
Excess-dp is not supported on egress.
Configuring a port-and-ACL-based traffic policing policy
You can use standard or extended IP ACLs for port-and-ACL-based traffic policing:
•
Standard IP ACLs match traffic based on source IP address information.
•
Extended ACLs match traffic based on source and destination IP addresses and IP protocol
information. Extended ACLs for TCP and UDP protocols must also match on source and
destination IP addresses and TCP or UDP protocol information.
•
You can apply an ACL ID to a port-and-ACL-based traffic policing policy before you define the
ACL. The traffic policing policy does not take effect until the ACL is defined.
•
It is not necessary to remove an ACL from a port-and-ACL-based rate limiting policy before
deleting the ACL.
•
Layer-2 ACL rate limiting is supported.
Port-and-ACL-based traffic policing is supported for traffic on inbound and outbound ports. To
configure port-and-ACL-based traffic policing policies, enter commands such as the following.