402 Fabric OS Administrator’s Guide
53-1001763-02
Ingress Rate Limiting
18
•Traffic Isolation Zoning
Traffic Isolation Zoning (TI zoning) allows you to control the flow of interswitch traffic by creating
a dedicated path for traffic flowing from a specific set of source ports (F_Ports). Traffic
Isolation Zoning does not require a license. See “Traffic Isolation Zoning” on page 267 for
more information about this feature.
•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 “Ingress Rate Limiting” on
page 402 for more information about this feature.
•QoS SID/DID Traffic Prioritization
SID/DID traffic prioritization allows you to categorize the traffic flow between a host and target
has having a high or low priority. QoS SID/DID traffic prioritization requires an Adaptive
Networking license for 8 Gbps platforms, but does not require a license for 4 Gbps platforms.
See “QoS: SID/DID traffic prioritization” on page 403 for more information about this feature.
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.

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 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.
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.
Note the following considerations about ingress rate limiting:
•Ingress rate limiting is applicable only to F_Ports and FL_Ports.