Deployment Guide

Trunk members in TI zone: 16 18
Trunk members not in TI zone: 17
F-Port Trunks
Trunk members in TI zone: 4 5
Trunk members not in TI zone: 6
TI Zone Name: loop
E-Port Trunks
Trunk members in TI zone: 0
Trunk members not in TI zone: 1
TI Zone Name: operand
E-Port Trunks
Trunk members in TI zone: 8
Trunk members not in TI zone: 9 10
E-Port Trunks
Trunk members in TI zone: 16
Trunk members not in TI zone: 17 18
Limitations and restrictions of Traffic Isolation Zoning
The following limitations and restrictions apply to 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 348 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.
• If two N_Ports are online and have the same shared area, and one of them is configured in a TI
zone, then they both must be configured in that same TI zone. One of the online shared area
N_Ports should not remain outside the TI zone unless it is offline, then it may remain outside the TI
zone. This limitation does not apply to E_Ports that use the same shared area on FC4-48 and
FC8-48 port blades.
• Port swapping is not permitted in TI zones.
• 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.
• TI zones that have members with port index greater than 511 are not supported with Fabric OS
versions earlier than v6.4.0. If such a TI zone and Fabric OS version combination is detected, a
warning is issued. These configurations are not prevented, but their behavior is unpredictable.
• When you merge two switches, if there is an effective configuration on the switches and TI zones are
present on either switch, the TI zones are not automatically activated after the merge. Check the TI
zone enabled status using the zone --show command, and if the TI Zone Enabled status does not
match across switches, issue the cfgEnable command.
• Use care when creating TI zones on ICL ports in topologies that span more than two switches
connected with ICLs. If a user-defined TI zone breaks the ICL connectivity requirements, a a
FSPF-1009 RASLOG entry and message is generated to notify you of this error condition.
ATTENTION
Removing a core blade when both ICL connections and lossless dynamic load sharing are enabled may
cause frame loss on a number of F_Ports.
Limitations and restrictions of Traffic Isolation Zoning
Fabric OS Administrators Guide 359
53-1003130-01