HP Fabric OS v7.0.1, Руководство администратора

Страница: 466 / 584

428 Fabric OS Administrator’s Guide
53-1002446-01
QoS zones
21
High availability considerations for QoS zone-based traffic prioritization
If the standby 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.
Supported configurations for QoS zone-based traffic prioritization
Note the following configuration rules for traffic prioritization:
•
All switches in the fabric must be running Fabric OS v6.0.0 or later.
ATTENTION
If QoS traffic crosses an ISL for a switch running a firmware version earlier than Fabric OS
v6.0.0, the frames are dropped.
•
By default, all devices are assigned medium priority.
-
To be assigned high or low priority, hosts and targets must be connected to a Brocade
8-Gbps or 16-Gbps switch or port blade.
-
To preserve the priority level across ISLs, the switches must be running Fabric OS v6.0.0 or
later and must be one of the following platforms: Brocade 300, 4100, 4900, 5000, 5100,
5300, 5410, 5424, 5450, 5480, 6510, 7500, 7500E, 7600, 7800, 8000, VA-40FC,
48000, Brocade DCX, DCX-4S, or DCX 8510 family.
•
QoS is enabled by default on 8-Gbps and 16-Gbps ports. QoS is disabled by default on all
4-Gbps ports and long-distance ports.
Limitations and restrictions for QoS zone-based traffic prioritization
•
Enabling and disabling QoS is potentially disruptive to the I/O on the affected port.
•
If a host and target are included in two or more QoS zones with different priorities, the zone
with the lowest priority takes precedence. For example, if an effective zone configuration has
QOSH_z1 (H,T) and QOSL_z2 (H,T), the traffic flow between H and T will be of low QoS priority.
Additionally, if QOSH_z1 (H,T) overlaps with a “domain,port” zone at the H port, the traffic flow
between H and T is dropped to medium priority and the H port is marked as a session-based
zoning port.
•
Traffic prioritization is enforced on the egress ports only, not on the ingress ports.
•
Traffic prioritization is not supported on 10 Gbps ISLs.
•
Traffic prioritization is not supported on mirrored ports.
•
Traffic prioritization is not supported over LSAN zones. The traffic is always medium priority in
the ingress edge fabric, the backbone fabric, and the egress edge fabric.
•
Traffic prioritization is not supported on a CryptoTarget container (redirection zone). See the
Fabric OS Encryption Administrator’s Guide for information about redirection zones.