Brocade FICON Administrator's Guide v7.1.0 (53-1002753-01, March 2013)

52 FICON Administrator’s Guide
53-1002753-01
FCIP configuration requirements for FICON extension
4
• Intermediate ending status as appropriate to prevent FlCON channel protocol timeout (PTOV)
expirations.
• Acceptance of device status as required to prevent FICON control unit PTOV expirations.
• Prevention of “clutching” during print jobs.
For information on configuring printer emulation, refer to “Configuring FICON emulation” on
page 54. For information on displaying printer emulation status and statistics, refer to “Displaying
FICON emulation performance statistics” on page 55.
Teradata emulation
Teradata emulation reduces latency on links to Teradata warehouse systems caused by WAN
propagation delays and bandwidth restrictions. It accomplishes this by processing selected FICON
commands for associated control, data, and status responses. FICON Teradata emulation is only
supported between FICON channels and FICON Teradata controllers.
For write commands, control and status frames are generated for the host side of the WAN in order
to pipeline write commands over the same or multiple exchanges. Such pipelined write commands
and their data are queued at the device side of the WAN for asynchronous transfer to the device.
For read operations received by the device side of the WAN, a number of anticipatory read
commands are autonomously generated and transferred to the device. The data and status
associated with such commands are sent to the host side of the WAN and queued in anticipation of
host generated read commands.
FICON emulation for Teradata sequences over an FCIP tunnel is controlled by using FICON
emulation feature flags in the portcfg fciptunnel command associated with the FCIP tunnel.
For information on configuring Teradata emulation or tape emulation, refer to “Configuring FICON
emulation” on page 54. For information on displaying Teradata emulation status and statistics,
refer to “Displaying FICON emulation performance statistics” on page 55.
FCIP configuration requirements for FICON extension
FICON extension uses FCIP for transport. FCIP interfaces and tunnels used for FICON extension
must be defined prior to configuring FICON emulation. Ports should remain persistently disabled
until after FICON emulation is configured. Refer to the FCIP Administrator’s Guide for information
about configuring FCIP interfaces, tunnels, and circuits.
Configuration requirements for switches and Backbones
Consider these configuration issues when an extension switch or blade is connected to a switch in
a FICON configuration:
• If you are creating a cascaded configuration (connecting two switches or Backbones with
different domain IDs), be aware of IBM requirements for high integrity fabrics.
• In configurations with ISLs, ensure that ISL paths are properly configured to meet FICON
emulation requirements for a determinate path for FICON commands and responses.
• FICON networks with FCIP emulating and nonemulating tunnels do not support Dynamic Path
Selection (aptpolicy 3) configurations.