Trunking With Ti Zones; Limitations And Restrictions Of Traffic Isolation; Admin Domain Considerations For Traffic Isolation; Ti Zone Creation And Management - HP A7533A - Brocade 4Gb SAN Switch Base Administrator's Manual

• Ports in a TI zone must belong to switches that run Fabric OS 6.0.0 or later. For TI over FCR zones, ports
must belong to switches that run Fabric OS 6.1.0 or later.
• Traffic Isolation has limited support for FICON FCIP in McDATA Fabric Mode (interopmode 2), in the
following configuration only:
• 400 Multi-protocol Router with E_Port connections to an M-switch and VE_Port connections to
another 400 Multi-protocol Router.
• Devices attached to M-switch only.
The following is a sample configuration:
Devices -- M-switch -- 400 MPR -- 400 MPR -- M-switch -- Devices
• Traffic Isolation is not supported in fabrics configured in Open Fabric Mode (interopmode 3).
• Fabric OS 6.1.0 or later supports Traffic Isolation in a mixed fabric (that is, a fabric with Fabric OS and
M-EOS switches) operating in interopmode 2. Traffic Isolation is not supported in fabrics configured in
Open Fabric Mode (interopmode 3). VE_Ports are supported in TI zones.
• Traffic Isolation is not supported in fabrics with switches running firmware versions earlier than Fabric
OS 6.0.0b (earliest 6.0x version HP supported). However, the existence of a TI zone in such a fabric is
backward compatible and does not disrupt fabric operation in switches running earlier firmware
versions.
• TI over FCR is not backward compatible with Fabric OS 6.0.x or earlier. The - 1 in the domain,index
entries cases issues to legacy switches in a zone merge. Firmware downgrade is prevented if TI over
FCR zones exist.

Trunking with TI zones

Consider 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

The following are limitations of TI zones:
• 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 255 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
• 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 cannot 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 blades.
• Ports that are in different TI zones cannot communicate with each other if failover is disabled.

Admin Domain considerations for Traffic Isolation

Consider the following if you implement Admin Domains and TI zones:
• TI zones are applicable only in AD0, and the E_Ports that are members of a TI zone must be in the AD0
device list. Because TI zones must use D,I notation, the AD0 device list must be declared using D,I
notation for ports that are to be used in TI zones.
• A port used in a TI zone cannot be a member of multiple Admin Domains.
• Use care if defining TI zones with ports that are shared across Admin Domains because of the limitation
that a given port can appear in only one TI zone.
Best practice: Do not use ports that are shared across Admin Domains in a TI zone.

TI zone creation and management

Create and modify TI zones using the zone command. Other zoning commands, such as zoneCreate,
aliCreate, and cfgCreate, cannot be used to manage TI zones.
298 Optimizing fabric behavior
"Traffic Isolation over FC routers" on page 294.