HP StorageWorks 8/80 HP StorageWorks Fabric OS 6.1.x administrator guide (5697 - Page 291

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. Ingress rate limiting is applicable only to F_Ports and FL_Ports and is available only on the DC Director model. The ingress rate limiting configuration is persistent across reboots. To limit traffic from a particular device: 1. Connect to the switch and log in as admin. 2. Enter the portcfgqos --setratelimit command. portcfgqos --setratelimit [slot/]port ratelimit where: slot/port The slot and port number of the F_Port or FL_Port on which you want to limit traffic. The slot number is required for a 4/256 SAN Director or DC Director. ratelimit The maximum speed, in megabits per second (Mbps), for traffic coming from the device. The valid values are: 200, 400, 600, 800, 1000, 1500, 2000, 2500, 3000, 3500, 4000, 5000, 6000, 7000, and 8000. For example, to set the rate limit on slot 3, port 9 to 4000 Mbps, enter the following command: portcfgqos --setratelimit 3/9 4000 To disable ingress rate limiting 1. Connect to the switch and log in as admin. 2. Enter the portcfgqos --resetratelimit command. portcfgqos --resetratelimit [slot/]port where: slot/port The slot and port number of the F_Port or FL_Port for which you want to disable ingress rate limiting. The slot number is required for a 4/256 SAN Director or DC Director. For example, to disable ingress rate limiting on slot 3, port 9, enter the following command: portcfgqos --resetratelimit 3/9 QoS: SID/DID traffic prioritization SID/DID traffic prioritization is a licensed feature that allows you to categorize the traffic flow between a given host and target as having a high or low priority. For example, you could assign online transaction processing (OLTP) to high priority and backup traffic to low priority. All flows without QoS prioritization are considered medium priority. High, medium, and low priority flows are allocated to different virtual channels (VCs). High priority flows receive more VCs than medium priority flows, which receive more VCs than low priority flows. NOTE: If there is a single low priority flow to a destination ID (DID) and several medium priority flows to that same DID, then it is possible that the medium priority flows would have less bandwidth because they have to share the medium priority VCs, whereas the low priority flow would have a separate VC. SID/DID traffic prioritization is a licensed feature. An Adaptive Networking license must be installed on every switch that is in the path between a given configured device pair. Fabric OS 6.1.x administrator guide 291