528 Fabric OS Administrator’s Guide
53-1002745-02
QoS zones
21
The following are requirements for establishing QoS over FCRs:
• QoS over FC routers is supported in Brocade native mode only. It is not supported in
interopmode 2 or interopmode 3.
• QoS over FC routers is supported for the following configurations:
- Edge-to-edge fabric configuration: supported on all platforms.
- Backbone-to-edge fabric configuration: supported on 16-Gbps-capable platforms only
(Brocade 6510, 6520, and Brocade DCX 8510 family), and only if no other platforms are
used. For all other platforms, you cannot prioritize the flow between a device in an edge
fabric and a device in the backbone fabric.
• QoS over FC routers is supported only if Virtual Fabrics is disabled in the backbone fabric. QoS
over FC routers cannot be enabled if Virtual Fabrics is also enabled in the backbone fabric.
• The port WWN of the host or target and the port WWN of the proxy device must be in both an
LSAN zone and a QoS zone.
• QoS over FC routers is supported on both EX_Ports and VEX_Ports.
• The EX_Ports (or VEX_Ports) in the path between the QoS devices must be on switches running
Fabric OS v6.3.0 or later.
• QoS zones must use WWN notation only; D,I notation is not supported for QoS over FCRs.
• An Adaptive Networking license must be installed on every switch that is in the path between a
given configured device pair, including the switches in the backbone fabric and both edge
fabrics.
Virtual Fabrics considerations for QoS zone-based traffic prioritization
You can prioritize flows between devices in a logical fabric. The priority is retained for traffic going
across ISLs and through the base fabric XISLs.
For example, Figure 70 shows a logical fabric that includes H1 and S1. To set the traffic between
H1 and S1 to high priority, create a QoS zone in the logical fabric with H1 and S1 as members. Then
enable QoS on all of the E_Ports shown circled in the figure, including all of the E_Ports in the XISLs
(ports 10, 11, 12, 13, 14, 15, 16, and 17).
High-availability considerations for QoS zone-based traffic prioritization
If the standby control processor (CP) is running a Fabric OS version earlier than 6.3.0 and is
synchronized with the active CP, then QoS zones using D,I notation cannot be created. If the
standby CP is not synchronized or if no standby CP exists, then the QoS zone creation succeeds.
If QoS zones using D,I notation exist in either the defined or active configuration and the standby
CP tries to synchronize with the active CP, the synchronization fails if the standby CP is running a
Fabric OS version earlier than 6.3.0. Synchronization can succeed only if the QoS D,I zones are
removed.
To Next Page
Loading...
Need help?
General