Fabric OS Administrator’s Guide 281
53-1002446-01
Limitations and restrictions of Traffic Isolation Zoning
12
Additional configuration rules for enhanced TI zones
Enhanced TI zones (ETIZ) have the following additional configuration rules:
• Enhanced TI zones are supported only if every switch in the fabric is ETIZ capable. A switch is
ETIZ capable if it meets the following qualifications:
- The switch must be one of the supported platforms, as listed in “Supported hardware and
software” on page xxxiv.
- The switch must be running Fabric OS v6.4.0 or later.
• If the fabric contains a switch running an earlier version of Fabric OS, you cannot create an
enhanced TI zone. You cannot merge a downlevel switch into a fabric containing enhanced TI
zones, and you cannot merge a switch with enhanced TI zones defined into a fabric containing
switches that do not support ETIZ.
• Overlapping TI zones must have the same failover type. That is, both must be either failover
enabled or failover disabled.
FC router domains are excluded from the ETIZ platform restrictions. You can create enhanced TI
zones with these switches in the fabric.
Trunking with TI zones
Note the following if you implement trunking and TI zones:
• To include a trunk group in a TI zone, you must include all ports of the trunk in the TI zone.
• Trunked ISL ports cannot be members of more than one TI zone.
Limitations and restrictions of Traffic Isolation Zoning
• For switches running Fabric OS 6.1.0 or later, a maximum of 255 TI zones can be created in
one fabric. For switches running Fabric OS 6.0.x, no more than 239 TI zones should be
created.
A fabric merge resulting in greater than the maximum allowed TI zones results in merge failure
and the fabrics are segmented.
• A TI zone can be created using D,I (Domain, Index) notation only, except for TI zones in a
backbone fabric, which use port WWNs. See “Traffic Isolation Zoning over FC routers” on
page 276 for information about TI zones in a backbone fabric.
• To include a trunk group in a TI zone, you must include all ports of the trunk in the TI zone.
• Two N_Ports that have the same shared area should not be configured in different TI zones.
This limitation does not apply to E_Ports that use the same shared area on the FC4-48 and
FC8-48 port blades.
• Ports that are in different TI zones cannot communicate with each other if failover is disabled.
• TI zone members that overlap must have the same TI failover policy across all TI zones to which
they belong. That is, if an overlapping member is part of a failover-disabled zone, then it can
belong only to other TI zones where the policy is also failover-disabled; the member cannot
overlap with failover-enabled TI zones.
To Next Page
Loading...
Need help?
General