Filter
Top Products
Port Traffic Controls
Rate-Limiting
• Kbps rate-limiting is done in segments of 1% of the lowest
corresponding media speed. For example, if the media
speed is 100 Kbps, the value would be 1 Mbps. A 1-100 Kbps
rate-limit is implemented as a limit of 100 Kbps; a limit of
100-199 Kbps is also implemented as a limit of 100 Kbps,
a limit of 200-299 Kbps is implemented as a limit of 200
Kbps, and so on.
• Percentage limits are based on link speed. For example, if
a 100 Mbps port negotiates a link at 100 Mbps and the
inbound rate-limit is configured at 50%, then the traffic
flow through that port is limited to no more than 50 Mbps.
Similarly, if the same port negotiates a 10 Mbps link, then
it allows no more than 5 Mbps of inbound traffic.
Configuring a rate limit of 0 (zero) on a port blocks all traffic
on that port. However, if this is the desired behavior on the
port, ProCurve recommends using the < port-list > disable
command instead of configuring a rate limit of 0.
You can configure a rate limit from either the global configuration level or
from the port context level. For example, either of the following commands
configures an inbound rate limit of 60% on ports A3 - A5:
ProCurve (config)# int a3-a5 rate-limit all in percent 60
ProCurve (eth-A3-A5)# rate-limit all in percent 60
Displaying the Current Rate-Limit Configuration
The show rate-limit all command displays the per-port rate-limit configuration
in the running-config file.
Syntax: show rate-limit all [ port-list ]
Without [ port-list ], this command lists the rate-limit
configuration for all ports on the switch. With [ port-list ], this
command lists the rate-limit configuration for the specified
port(s). This command operates the same way in any CLI
context.
For example, if you wanted to view the rate-limiting configuration on the first
six ports in the module in slot “A”:
13-6