HP Fabric OS v7.0.1, Administrator'S Manual

Page: 317 / 584

Fabric OS Administrator’s Guide 279
53-1002446-01
General rules for TI zones
12
Using D,I and port WWN notation, the members of the TI zone in Figure 40 are:
1,1 (EX_Port for FC router 1)
1,4 (VE_Port for FC router 1)
2,7 (VE_Port for FC router 2)
2,1 (EX_Port for FC router 2)
10:00:00:00:00:01:00:00 (Port WWN for the host)
10:00:00:00:00:02:00:00 (Port WWN for target 1)
10:00:00:00:00:03:00:00 (Port WWN for target 2)
Limitations of TI zones over FC routers
Be aware of the following when configuring TI zones over FC routers:
•
A TI zone defined within the backbone fabric does not guarantee that edge fabric traffic will
arrive at a particular EX_Port. You must set up a TI zone in the edge fabric to guarantee this.
•
TI zones within the backbone fabric cannot contain more than one destination router port
(DRP) per each fabric. This means you cannot define more than one EX_Port to any one edge
fabric unless they are part of a trunk.
•
Only one egress E_Port or VE_Port connected to the next hop can be defined within TI zones.
Only one ISL or trunk can be defined between two backbone switches.
•
TI over FCR is supported only from edge fabric to edge fabric. Traffic isolation from backbone to
edge is not supported.
•
Non-TI data traffic is not restricted from going through the TI path in the backbone fabric.
•
For TI over FCR, failover must be enabled in the TI zones in the edge fabrics and in the
backbone fabric.
•
TI over FCR is not supported with FC Fast Write.
•
For the FC8-16, FC8-32, FC8-48, FC8-64, and FX8-24 blades only: If Virtual Fabrics is disabled,
two or more shared area EX_Ports connected to the same edge fabric should not be configured
in different TI zones. This configuration is not supported.
General rules for TI zones
Note the following general rules for TI zones:
•
A TI zone must include E_Ports and N_Ports that form a complete, end-to-end route from
initiator to target.
•
When an E_Port is a member of a TI zone that E_Port cannot have its indexed swapped with
another port.
•
A given E_Port used in a TI zone should not be a member of more than one TI zone.
If multiple E_Ports are configured that are on the lowest cost route to a domain, the various
source ports for that zone are load-balanced across the specified E_Ports.
•
TI zones reside only in the defined configuration and not in the effective configuration. When
you make any changes to TI zones, including creating or modifying them, you must enable the
effective configuration for the changes to take effect, even if the effective configuration is
unchanged.
•
A TI zone only provides traffic isolation and is not a “regular” zone.