Fabric OS Administrator’s Guide 273
53-1001763-02
Traffic Isolation Zoning over FC routers 12
FIGURE 39 Illegal ETIZ configuration
The Fabric OS routing implementation does not support separate routes to separate ports on a
destination domain. Configurations such as this should be avoided.
See Additional configuration rules for enhanced TI zones” on page 278 for more information about
enhanced TI zones.

Traffic Isolation Zoning over FC routers

This section describes how TI zones work with Fibre Channel routing (TI over FCR). See Chapter 21,
“Using the FC-FC Routing Service,” for information about FC routers, phantom switches, and the
FC-FC Routing Service.
Some VE_Port-based features, such as tape pipelining, require the request and corresponding
response traffic to traverse the same VE_Port tunnel across the metaSAN. To ensure that the
request and response traverse the same VE_Port tunnel, you must set up Traffic Isolation zones in
the edge and backbone fabrics.
Set up a TI zone in an edge fabric to guarantee that traffic from a specific device in that edge
fabric is routed through a particular EX_Port or VEX_Port.
Set up a TI zone in the backbone fabric to guarantee that traffic between two devices in
different fabrics is routed through a particular ISL (VE_Ports or E_Ports) in the backbone.
This combination of TI zones in the backbone and edge fabrics ensures that the traffic between
devices in different fabrics traverses the same VE_Port tunnel in a backbone fabric. Figure 40
shows how three TI zones form a dedicated path between devices in different edge fabrics. The
backbone fabric can contain one or more FC routers.
7
3
Domain 1 Domain 3
Domain 2
Host 1
16
4
= ETIZ 1
28
1
2
Host 2
Target
= ETIZ 2