Ingress Rate Limiting - HP StoreFabric SN6500B Administrator's Manual

21

Ingress Rate Limiting

•
•
•
•
•
Ingress Rate Limiting
Ingress Rate Limiting is a licensed feature that requires the Adaptive Networking license. Ingress
Rate Limiting restricts the speed of traffic from a particular device to the switch port. Use Ingress
Rate Limiting for the following situations:
•
•
•
To limit the traffic, you set the maximum speed at which the traffic can flow through a particular
F_Port or FL_Port. For example, if you set the rate limit at 4 Gbps, then traffic from a particular
device is limited to a maximum of 4 Gbps.
Ingress Rate Limiting enforcement is needed only if the port can run at a speed higher than the
rate limit. For example, if the rate limit is 4 Gbps and the port is only a 2-Gbps port, then Ingress
Rate Limiting is not enforced.
The Ingress Rate Limiting configuration is persistent across reboots.
You should keep in mind the following considerations about Ingress Rate Limiting:
•
•
•
518
Ingress Rate Limiting
Ingress Rate Limiting restricts the speed of traffic from a particular device to the switch port.
Ingress Rate Limiting requires an Adaptive Networking license. See
page 518 for more information about this feature.
Quality of Service (QoS) SID/DID Traffic Prioritization
SID/DID traffic prioritization allows you to categorize the traffic flow between a host and target
as having a high or low priority. QoS SID/DID traffic prioritization requires an Adaptive
Networking license on 8-Gbps platforms. See
for more information about this feature.
NOTE
The Brocade 6520 does not require licenses for the Ingress Rate Limiting and QoS SID/DID
features. They are enabled by default. You can use the Adaptive Networking features together
to optimize the performance of your fabric. For example, you can do the following:
You can use Top Talkers to identify the SID/DID pairs that consume the most bandwidth and
can then configure them with certain QoS attributes so they get proper priority.
If the bottleneck detection feature detects a latency bottleneck, you can use TI zones or QoS
SID/DID traffic prioritization to isolate latency device traffic from high-priority application
traffic.
If the bottleneck detection feature detects ISL congestion, you can use Ingress Rate Limiting to
slow down low-priority application traffic if it is contributing to the congestion.
To reduce existing congestion in the network or proactively avoid congestion.
To enable you to offer flexible bandwidth-limit services based on requirements.
To enable more important devices to use the network bandwidth during specific services, such
as network backup.
Ingress Rate Limiting is applicable only to F_Ports and FL_Ports.
QoS traffic prioritization takes precedence over Ingress Rate Limiting.
Ingress Rate Limiting is not enforced on trunked ports.
"Ingress Rate Limiting"
"QoS: SID/DID traffic prioritization"
Fabric OS Administrator's Guide
on
on page 519
53-1002745-02