53-1002753-01 14 December 2012 FICON Administrator’s Guide Supporting Fabric OS v7.1.
Copyright © 2009-2012 Brocade Communications Systems, Inc. All Rights Reserved. Brocade, the B-wing symbol, BigIron, DCX, Fabric OS, FastIron, NetIron, SAN Health, ServerIron, and TurboIron are registered trademarks, and Brocade Assurance, Brocade NET Health, Brocade One, CloudPlex, MLX, VCS, VDX, and When the Mission Is Critical, the Network Is Brocade are trademarks of Brocade Communications Systems, Inc., in the United States and/or in other countries.
Contents About This Document How this document is organized . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii Supported hardware and software . . . . . . . . . . . . . . . . . . . . . . . . . . viii What’s new in this document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii Document conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix Text formatting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Chapter 2 Administering FICON Fabrics User security considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 Meeting Query Security Attribute requirements . . . . . . . . . . . . 17 Preparing a switch for FICON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 Cascaded FICON and 2-byte addressing considerations . . . . . 19 Configuring switched point-to-point FICON . . . . . . . . . . . . . . . . . . . . 20 Configuring cascaded FICON . . . . . . . . . . . . . . . . . .
Chapter 4 Administering FICON Extension Services Platforms supporting FICON extension over IP . . . . . . . . . . . . . . . . . 47 FICON emulation overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 IBM z/OS Global Mirror emulation . . . . . . . . . . . . . . . . . . . . . . . 48 Tape emulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 Printer emulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Troubleshooting FICON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76 General information to gather for all cases . . . . . . . . . . . . . . . . 76 Switched point-to-point topology checklist. . . . . . . . . . . . . . . . . 77 Cascaded topology checklist. . . . . . . . . . . . . . . . . . . . . . . . . . . . 78 Gathering additional information . . . . . . . . . . . . . . . . . . . . . . . . 78 Troubleshooting FICON CUP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
About This Document • How this document is organized . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii • Supported hardware and software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii • What’s new in this document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii • Document conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix • Notice to the reader . . . . . . . . . . . . . . . . . . .
• Appendix D, “Configuration Information Record” provides a form to record your FICON configuration information. • Appendix E, “EBCDIC Code Page” provides a table of the EBCDIC Code Page 37. Supported hardware and software Although many different software and hardware configurations are tested and supported by Brocade Communications Systems, Inc. for Fabric OS v7.1,0 documenting all possible configurations and scenarios is beyond the scope of this document.
• Removed restriction that XISLs cannot be configured. • Added instructions and restrictions on enabling XISL use and referenced Fabric OS Command Reference for details. - Added section on FICON Best Practices. Added section on FICON link address and FC address. • Chapter 3, “Configuring FICON CUP.
For readability, command names in the narrative portions of this guide are presented in mixed lettercase: for example, switchShow. In actual examples, command lettercase is often all lowercase. Otherwise, this manual specifically notes those cases in which a command is case sensitive. Command syntax conventions Command syntax in this manual follows these conventions: command Commands are printed in boldface. --option, option Command options are printed in bold. -argument, arg Arguments.
CAUTION A Caution statement alerts you to situations that can be potentially hazardous to you. DANGER A Danger statement indicates conditions or situations that can be potentially lethal or extremely hazardous to you. Safety labels are also attached directly to products to warn of these conditions or situations. Key terms For definitions specific to Brocade and Fibre Channel, see the technical glossaries on MyBrocade. See “Brocade resources,” for instructions on accessing MyBrocade.
For additional Brocade documentation, visit the Brocade SAN Info Center and click the Resource Library location: http://www.brocade.com Release notes are available on the MyBrocade website and are also bundled with the Fabric OS firmware. Other industry resources White papers, online demonstrations, and data sheets are available through the Brocade website at http://www.brocade.com/products-solutions/products/index.
The serial number label on FICON-qualified devices is located as follows: • Brocade 5100, 5300, 7800, and 6510 — On the switch ID pull-out tab located inside the chassis on the port side on the left. • Brocade DCX 8510-8 and DCX - On the port side of the chassis, on the lower right side and directly above the cable management comb. • Brocade DCX 8510-4 and DCX-4S - On the nonport side of the chassis, on the lower left side. 3. World Wide Name (WWN) Use the licenseIDShow command to display the switch WWN.
xiv FICON Administrator’s Guide 53-1002753-01
Chapter Introducing FICON 1 • FICON overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 • FICON concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 • FICON configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 • Access control in FICON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 • FICON commands . . .
1 FICON overview • Insistent (IDID) Disables the dynamic domain ID feature and only allows the switch to use a pre-set domain ID. All switches in a fabric must have a unique domain ID. An insistent domain ID is required with 2-byte addressing. IDID is required for cascaded FICON configurations. • Link incident detection, registration, and reporting Provides administrative and diagnostic information.
FICON concepts 1 Latency guideline The maximum supported distance for a FICON channel is 300 Km (1.5 msec of delay). Synchronous mirroring applications are generally limited to 100 Km (0.5 msec of delay). Greater distances require that the FICON Acceleration feature be used with FCIP. The FICON Acceleration feature emulates control unit response to the channel to make the devices appear closer to the channel than they actually are.
1 FICON concepts • FICON Control Unit Port (CUP) The internal port in a switch that assumes an FC address such that it is the FC DID used to direct FICON traffic to the FICON Management Server. • FICON Manager Host communication includes control functions such as blocking and unblocking ports, as well as monitoring and error-reporting functions.
FICON configurations 1 • Sysplex In IBM mainframe computers, a Systems Complex, commonly called a sysplex, allows multiple processors to be joined into a single unit, sharing the same sysplex name and Couple Data Sets. FICON configurations There are two types of FICON configurations that are supported using Brocade Fabric OS: switched point-to-point and cascaded topologies.
1 FICON configurations Cascaded FICON Cascaded FICON refers to an implementation of FICON that uses one or more FICON channel paths whereby the domain ID of the entry switch is different than the domain of the switch where the control unit is attached. Therefore, cascading requires a 2-byte link address. Any time a 2-byte link address is defined on a channel, all link addresses must be 2-byte link addresses.
FICON configurations 1 • The mainframes must be zSeries machines or System z processors: z196, z114, z800, 890, 900, 990, z9 BC, z9 EC, z10 BC, EC, and zEC12. Cascaded FICON requires 64-bit architecture to support the 2-byte addressing scheme. Cascaded FICON is not supported on 9672 G5/G6 mainframes. • z/OS version 1.4 or later, or z/OS version 1.3 with required PTFs/MCLs to support 2-byte link addressing (DRV3g and MCL (J11206) or later) is required.
1 Access control in FICON Access control in FICON Zoning is used to control access in a FICON environment. A zone consists of a group of ports or WWNs. Connectivity is permitted only between connections to the switch that are in the same zone. There are three types of zoning: WWN, port, and domain index zoning. A zone configuration includes at least one zone. In open systems environments and in more complex FICON deployments, the zone configuration contains multiple zones.
Access control in FICON FIGURE 7 1 Complex cascaded zoning Blue Zone A: Any CHPID connected to Director 1, except CHPID 79, can get to any control unit connected to Director 1. The zone includes all ports in Director 1 except ports 4, 5, and 6. Orange Zone B: Any CHPID connected to Director 2, except CHPID 7A, can get to any control unit connected to Director 2. The zone includes all ports in Director 2 except ports 4, 5, and 6.
1 Access control in FICON Error reporting Non-implicit (such as Fabric OS recognized or bit error rate threshold exceeded) and implicit (FRU failure) link incidents are reported to registered listeners on the local switch. The RMF 74-7 record (FICON Director Activity Report, which is the same RMF Record containing the average frame pacing delay information) reports port errors, which in turn are also reported back to the mainframe host management consoles.
Access control in FICON FIGURE 8 FICON Administrator’s Guide 53-1002753-01 1 Three types of binding 11
1 FICON commands FICON commands NOTE The Fabric OS CLI supports only a subset of the Brocade management features for FICON fabrics. The full set of FICON CUP administrative procedures is available using the Brocade Network Advisor and Web Tools software features. You can also use an SNMP agent and the FICON Management Information Base (MIB). Table 1 summarizes the Fabric OS CLI commands that can be used for managing FICON fabrics.
FICON commands TABLE 1 1 Fabric OS commands related to FICON (Continued) Command Description ficonclear rnid Removes all outdated RNID records from the local RNID database. ficoncfg --set LIRR Sets the current LIRR device port number persistently. ficoncfg --reset LIRR Clears the currently configured LIRR port number. ficonhelp Displays a list of FICON support commands. ficoncupset fmsmode enable|disable Enables or disables FICON Management Server (FMS) mode.
1 Link and FC addressing Link and FC addressing To understand the addressing mode requirements and restrictions for FICON it is important to understand the relationship between the link address and the FC address. Understanding this relationship is also valuable for troubleshooting paths. Figure 9 represents components of link and FC addresses that are explained in this section.
Link and FC addressing 1 FICON protocol does not use the ALPA byte. However, the ALPA is a required byte in the FC address. The channel completes the FC address for a control unit link address by acquiring the ALPA that the switch returned to the channel when the channel logged in. This is why the ALPA must be the same for both the channel port and the control unit port. This is also the reason why 10-bit addressing mode cannot be used for FICON (refer to “Addressing modes” on page 27).
1 16 Link and FC addressing FICON Administrator’s Guide 53-1002753-01
Chapter 2 Administering FICON Fabrics • User security considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Preparing a switch for FICON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Configuring switched point-to-point FICON . . . . . . . . . . . . . . . . . . . . . . . . . . • Configuring cascaded FICON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • FICON and FICON CUP in Virtual Fabrics . . . . . . . . . . .
2 User security considerations Enabling insistent domain ID To enable Insistent Domain ID, follow these steps for each switch in the fabric: 1. Connect to the switch and log in using an account assigned to the admin role. 2. Enter the configure command and step through the interactive prompts. a. At the “Fabric parameters” prompt, type y. b. At the “Insistent Domain ID Mode” prompt, type y.
Preparing a switch for FICON 2 Deleting SCC_POLICY Enter the following command if you get messages that the E_Port in a security violation state. secpolicydelete "SCC_POLICY" Recovering the E_Port Enter the following commands for each switch if the E_Port is down. secpolicyactivate portenable n NOTE For more detailed information on commands and command output referenced in this section, refer to the Brocade Fabric OS Command Reference Manual.
2 Configuring switched point-to-point FICON Configuring switched point-to-point FICON This section provides detailed steps and commands to configure a switch for point-to-point FICON operation. The following steps assume that you have used your hardware reference manual to perform the initial setup of the switch and have performed all the steps from “Preparing a switch for FICON” on page 19.
Configuring switched point-to-point FICON 7. Configure the switch parameters using the configure command and enter the responses shown in Table 2 when prompted. (Items in italics are top-level parameters.) TABLE 2 FICON switch parameters Parameter Response Comment Fabric parameter Yes Prompts for the fabric parameters. Domain FICON Administrator’s Guide 53-1002753-01 2 The domain ID is the switch address. The recommended best practice is to set the switch address and domain ID to be the same.
2 Configuring switched point-to-point FICON TABLE 2 FICON switch parameters (Continued) Parameter Response Comment Sequence level switching 0 Do not change. When set to 1, frames of the same sequence from a particular source are transmitted together as a group. When set to 0, frames are interleaved among multiple sequences when transmitted. Under normal conditions, sequence-level switching should be disabled for better performance.
Configuring switched point-to-point FICON TABLE 2 2 FICON switch parameters (Continued) Parameter Response Comment RSCN transmission mode No Configures end-device RSCN Transmission Mode values such as: • RSCN only contains single PID • RSCN contains multiple PIDs (Default) • Fabric addresses RSCN Arbitrated Loop parameters No Parameters include Send FAN frames, Enable CLOSE on OPEN received, and Always send RSCN.
2 Configuring switched point-to-point FICON 12. Enter the portCfgLongDistance command for ports with fiber connections exceeding 10 km. For ports with fiber connections exceeding 10 km, configuring the port for long distance mode increases the number of buffer-to-buffer (BB) credits available on that port. If you have any Extended Fabrics links, enable VC translation link initialization to stabilize them.
Configuring cascaded FICON 2 Configuring cascaded FICON In addition to performing the steps listed in “Configuring switched point-to-point FICON” on page 20, you also need to perform the following steps to configure cascaded FICON. CAUTION Configuring the switch for FICON is a disruptive process. The switch must be disabled to configure switch parameters. This procedure must be followed prior to channels joining the fabric. 1. Perform the following actions for each switch: a.
2 FICON and FICON CUP in Virtual Fabrics FICON and FICON CUP in Virtual Fabrics For FICON CUP, FICON Management Server (FMS) mode is enabled on the logical switch and not the chassis. For example, in a Virtual Fabrics environment on the Brocade 6510 switch and the Brocade DCX Backbones, enable CUP on each logical switch. You can configure up to four CUP switches as logical switches in a Virtual Fabrics-enabled platform for FMS mode.
Addressing modes 2 • If addresses 0xFE or 0XFF have been assigned to physical ports, those ports must be disabled before FMS can be enabled. • For FICON CUP, FMS mode is enabled on the logical switch and not the chassis. For example, in a Virtual Fabrics environment on the Brocade 6510 switch and the Brocade DCX 8510-4 and DCX 8510-8 Backbones, you must set FMS mode independently on each logical switch. FMS mode is currently limited to four logical switches per chassis.
2 Addressing modes NOTE Although port addresses are assigned when moved to a logical switch, the address is not bound to the port. To ensure that the link address for a control unit attached to a port does not change, the portAddress command must be used to bind the address to the port even if you are not changing the port address assignments. Refer to “Sequential address binding” on page 89 for a list of commands that will bind ports on DCX or DCX 8510-8 Backbones fully populated with 32-port blades.
Clearing the FICON management database 2 5. Enable FMS mode using the ficonCupSet fmsmode enable command. For more information on these Fabric OS commands, refer to the Fabric OS Administrator’s Guide. FICON and blade support for addressing modes Note the following considerations about FICON and blade support on logical switches in DCX systems: • On default logical switches (and non-Virtual-Fabrics switches), FICON is not supported if address mode 1 (dynamic address mode) is enabled.
2 Automating CS_CTL Mapping 3. Enter ficonClear rnid to remove all the RNID records marked “not current” from the local RNID database. Automating CS_CTL Mapping The CS_CTL-based frame prioritization feature allows you to prioritize the frames between a host and target as having high, medium, or low priority, depending on the value of the CS_CTL field in the FC frame header. High, medium, and low priority frames are allocated to different virtual channels (VCs).
FICON best practices 2 5. Reboot the switch or chassis. 6. To verify if auto mode or default mode is set for the chassis, enter the configShow --all command as in the following example: root> configshow -all | grep fos.csctlMode fos.csctlMode:1 • If auto mode is set, the following should display in the command output: fos.csctlMode:1 • If default mode is set, the following should display in the command output: fos.
2 FICON best practices • Default switch Leave the default switch FID at 128. • Logical switches Always use a logical switch other than the default switch for FICON and do not disable virtual fabrics. • Cascading When cascading switches, connect ISLs so that a fabric forms before configuring switches for FICON. Merging switches into the fabric after configuring FICON is possible, but allowing the fabrics to form before applying the FICON settings will simplify the configuration process.
Chapter 3 Configuring FICON CUP • Control Unit Port overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Port and switch naming standards for FMS mode . . . . . . . . . . . . . . . . . . . . • Configuring FICON CUP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Determining physical port assignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • FMS mode and FICON CUP . . . . . . . . . . . . . . . . . . . . . . . . . .
3 Control Unit Port overview FICON director CHPIDs FICON director Embedded port FE FE System Automation OS390 application I/0-CPs Embedded port FE FICON Switch Management Application Server FIGURE 10 Embedded port FICON CUP Figure 10 is a simplified representation of a FICON environment and how CUP fits into that environment. FICON switches with FMS enabled use port address “FE” as the embedded internal port for host connectivity to the CUP, and port address “FF” is reserved.
Control Unit Port overview 3 ATTENTION Once FMS mode is enabled, you cannot bind FE/FF to any ports using either the portAddress or wwnAddress commands. • The switch is advertised to the mainframe by the CUP as having a specific number of ports, which is based on the hardware platform. The maximum supported switch size is 256 ports.
3 Port and switch naming standards for FMS mode NOTE Although 180 seconds should be the default value set on the switch when FMS is enabled, this value may not be set when older versions of Fabric OS are upgraded. This value must be set on the host system as well. FICON CUP zoning and PDCM considerations The FICON PDCMs control whether or not communication between a pair of ports in the switch is prohibited or allowed. PDCMs are a per-port construct.
Configuring FICON CUP TABLE 4 3 Fabric OS commands related to FICON CUP Command Description ficonCupShow fmsmode Displays the FICON Management Server enabled or disabled state for the switch. ficonCupShow modereg Displays the mode register bit settings for the switch. Configuring FICON CUP To set up FICON CUP, use the following procedure and be sure to perform the steps in the order indicated. 1. Connect to the switch and log in using an account assigned to the admin role. 2.
3 Determining physical port assignment Disabling ports 0xFE and 0xFF Addresses 0xFE and 0xFF are not available for external connections, so they must be disabled to configure FICON CUP. Note that in logical switches or in cases where port address binding or port swapping has occurred, addresses 0xFE and 0xFF are not necessarily tied to specific physical ports, such as 254 and 255.
FMS mode and FICON CUP 3 For more information and example output from this command, refer to the Fabric OS Command Reference Manual. FMS mode and FICON CUP Enabling FICON Management Server (FMS) mode in a Fabric OS environment allows the switch to behave within the context of the FICON architecture and effectively creates a FICON director. For Fabric OS 7.0 and later, a FICON CUP license is required to enable FMS mode. The FMS mode setting can be changed whether the switch is disabled or enabled.
3 FMS mode and FICON CUP Fabric OS command limitations and considerations This section describes limitations and considerations for using Fabric OS commands with FMS mode enabled. For a list of Fabric OS commands related to FICON, refer to FICON commands 12. • The following Fabric OS commands return a “switch busy” response if they are issued when the host-based management application is performing a write operation.
FMS mode and FICON CUP 3 FMS mode and FICON OxFE or OxFF ports OxFE and OxFF are assigned to the CUP and cannot be associated with any physical port with FMS mode enabled. Therefore, note the following when using FMS mode: • You must manually disable ports associated with 0xFE and 0xFF using the portDisable command to before you can enable FMS mode, but only if there is an active device connected to these ports. Otherwise, these ports will disable automatically when FMS is enabled.
3 Mode register bit settings After a nondisruptive upgrade from Fabric OS v6.4.0 to v7.0.0 or later, the following events occurs: NOTE These only occur on platforms released prior to Fabric OS v7.0.0. - You can manage port connectivity using the Allow/Prohibit Matrix in Brocade Network Advisor and Web Tools. Note that these applications are not available unless you install a FICON CUP license. The Mode Register is accessible via Web Tools and the Fabric OS commands.
Mode register bit settings TABLE 5 3 FICON CUP mode register bits (Continued) HCP Host control prohibited. When this bit is set on, the host is not allowed to set CUP parameters. The default setting is 0 (off). POSC Programmed offline state control. If the bit is set (=1), the command from the host will set the switch offline. If the bit is off (=0), the command from the host will be rejected and the switch will not go offline. The default setting is 1 (on). UAM User alert mode.
3 Mode register bit settings Configuration files downloaded with Active=Saved mode disabled The contents of existing files saved on the switch, which are also present in the [FICU SAVED FILES] section, are overwritten. The files in the [FICU SAVED FILES] section of the configuration file, which are not currently on the switch, are saved on the switch. The IPL is replaced because Active=Saved mode is disabled.
Setting the MIHPTO value 3 PATH=(5A,5B), LINK=(25FE,25FE) IODEVICE ADDRESS=(0DB,1),CUNUMBR=0DB,UNIT=2032,STADET=Y,UNITADD=00 * *------------------------------------------------------------------ Setting the mode register bits Consider the following when changing mode register bits: • The UAM bit can only be set by host programming. • All mode register bits except UAM are saved across power on/off cycles; the UAM bit is reset to 0 following a power-on.
3 Persistently enabling and disabling ports for CUP Persistently enabling and disabling ports for CUP When FMS mode is enabled, you cannot use the portCfgPersistentEnable and portCfgPersistentDisable commands to persistently enable and disable ports. Instead, use the following procedure. 1. Connect to the switch and log in using an account assigned to the admin role. 2. Enter the ficonCupShow modereg command to display the mode register bit settings. 3. Verify that the ASM bit is set on (1). 4.
Chapter 4 Administering FICON Extension Services • Platforms supporting FICON extension over IP . . . . . . . . . . . . . . . . . . . . . . . • FICON emulation overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • FCIP configuration requirements for FICON extension . . . . . . . . . . . . . . . . . • Configuration requirements for switches and Backbones . . . . . . . . . . . . . . • Configuring FICON emulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4 FICON emulation overview The Advanced FICON Acceleration license contains the following options: - Capacity 1 Consumed 1 Configured Blade Slots 1 This is a slot-based license for the Brocade FX8-24 and 7800. • Advanced Extension (FTR_AE) Required for multiple-circuit tunnels, FCIP Trunking, Adaptive Rate Limiting, and other FCIP features. This is not required for FICON Acceleration features, but multiple circuits would be used in a FICON emulation environment.
FICON emulation overview System z hosts 4 IBM Z/OS global mirror system data mover Brocade extension switch with emulation for FICON Brocade FICON Directors IP network 4 4 Brocade FICON Directors IP network Brocade extension switch with emulation for FICON Secondary disk volumes Primary disk volumes FIGURE 11 IBM z/OS Global Mirror emulation Figure 11 shows how the primary volume and the secondary mirrored volume may be geographically distant across an IP WAN.
4 FICON emulation overview For information on configuring tape emulation, refer to “Configuring FICON emulation” on page 54. For information on displaying tape emulation status and statistics, refer to “Displaying FICON emulation performance statistics” on page 55. Tape Write Pipelining FICON Tape Write Pipelining (refer to Figure 12)improves performance for a variety of applications when writing to tape over extended distances.
FICON emulation overview System z hosts FICON Director(s) Virtual Tape Controller Brocade extension switch with emulation for FICON Brocade extension blade with emulation for FICON 4 Tape Library IP network Read command 1 2 Local host held off with command retry awaiting read data to be delivered Read emulation indication sent to remote 3b 3a Read command 3 Local response FIGURE 13 4b 4a 4 5b 5a 5 6b 6a 6 Read commands are satisfied locally Read data is streamed to host Read cha
4 FCIP configuration requirements for FICON extension • 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.
Configuration requirements for switches and Backbones 4 • When running FICON emulation features over an FCIP tunnel, it is highly recommended that both switches providing the FCIP tunnel are using the same Fabric OS release level. High integrity fabric requirements for cascaded configurations You can use extended FICON connections between or through Brocade 7800 Extension Switches or FX8-24 blade to create a cascaded FICON switched configuration.
4 Configuring FICON emulation Configuring FICON emulation Before you configure FICON emulation, you need to understand the available options, and whether those options are to be implemented in your installation. If FICON emulation is new to you, refer to “FICON emulation overview” on page 47. ATTENTION Make sure both ends of the tunnel match before bringing it up or the tunnel will not form. 1.
Modifying FICON emulation 4 portcfg fciptunnel 23 modify --ficon-tape-write 1 --ficon-tape-read 1 portcfg fciptunnel 23 modify --ficon-print 1 Note that the preceding commands assume that an FCIP tunnel was a enabled for FICON operation by using the --ficon option.
4 Displaying FICON emulation performance statistics Refer to “FICON emulation monitoring” on page 56, “+------------+----------------+-+-----+----+----+----+----+-----------+---+------+------+------+” on page 58, and the Fabric OS Command Reference Manual for information on command formats that you can use to display various FICON statistics. FICON emulation monitoring Use examples in this section to display emulation monitoring for extension blades and switches.
4 Displaying FICON emulation performance statistics Emulation statistics example Following is a tape and XRC statistics output example for the 7800 switch and FX8-24 blade.
4 Displaying FICON emulation performance statistics |0x04100ED980|116300640006003B|H| 0x00|0000|0003|0000|0001| 1| 1| 58864| 40| 0| |0x04100DD100|1163006400060043|H| 0x00|0000|0003|0000|0001| 1| 1| 58864| 40| 0| |0x04100E2000|1163006400060047|H| 0x00|0000|0003|0000|0001| 1| 1| 58864| 40| 0| |0x04100E7100|1163006400060057|H| 0x00|0000|0003|0000|0001| 1| 1| 58864| 40| 0| |0x04100ECC80|116300640006005F|H| 0x00|0000|0003|0000|0001| 1| 1| 58864| 40| 0| +------------+----------------+-+
Chapter 5 Maintaining and Troubleshooting FICON • Firmware management in a FICON environment . . . . . . . . . . . . . . . . . . . . . • Configuration restoration in a FICON environment . . . . . . . . . . . . . . . . . . . . • Traffic Isolation Zoning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Port fencing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • FICON information . . . . . . . . . . . . . . . . . .
5 Firmware management in a FICON environment Firmware upgrade disruption Loading new firmware is a non-disruptive process except for the following cases: • During the firmware download process a failover to the backup processor occurs. Any outstanding CUP commands are lost and result in a timeout. To avoid this, CUP should be varied offline before starting a firmware download. The CUP may be varied back online after a successful firmware download.
Configuration restoration in a FICON environment 5 Configuration restoration in a FICON environment If the switch is operating in a FICON CUP environment, and the ASM (Active=Saved) bit is set on, then the switch ignores the IPL file downloaded when you restore a configuration. Table 7 describes this behavior in more detail.
5 Traffic Isolation Zoning Determining ports for the TI Zone To find the device ports, use the MVS display command. The following example will display the paths to device 1002 and where it is connected: D M=DEV(1002) Response is: DEVICE 1002 STATUS=OFFLINE CHP AC AD AE AF ENTRY LINK ADDRESS ..
Traffic Isolation Zoning 5 Channel Flow A Flow B ISL 1 ISL 2 ISL 3 Flow C CU A FIGURE 15 CU B Typical triangular setup During normal operation, the routes from any device on one switch are a one-hop path to either of the other two switches. However, if the path between any pair of switches fails then a two-hop path is available. Multi-hop paths are not certified for FICON configurations.
5 Traffic Isolation Zoning Channel Flow A Flow B ISL 1 ISL 2 ISL 3 Flow C CU A FIGURE 16 CU B Triangular topology with Enhanced TI Zones Figure 16 shows the following TI Zone definitions for the triangular topology: • Blue Zone includes the channel, ISL 1, and CU A. • Green Zone includes the channel, ISL 2, and CU B. • Red Zone includes the CU A, ISL 3, and CU B. Using these definitions with failover disabled, the topology achieves the desired behavior.
Traffic Isolation Zoning 5 System Data Mover topology Figure 17 shows a cascaded topology which can be used to support an operations recovery site. In this environment, host and storage systems exist at both sites, which are connected by two switches cascaded together using the System Data Mover (SDM) application. The storage differs between the sites. In the production site, the storage is DASD to support fast access for production applications.
5 Traffic Isolation Zoning FIGURE 18 System Data Mover topology using Enhanced TI Zones Figure 18 on page 66 shows the following Enhanced TI Zones definitions for the System Data Mover topology: • • • • Green Zone includes Host A, ISL 1, and CU B. Orange Zone includes CU A, ISL 2, and Host B. Red Zone includes Host A and CU A. Blue Zone includes Host B and CU B. Using these definitions with failover disabled achieves the desired behavior.
Traffic Isolation Zoning 5 Emulation topology FICON device emulation topologies have unique requirements due to the characteristics of the emulation devices. Each device must track the emulated sessions and maintain the state of the emulated devices in order to satisfy both ends of the connection. Since this is done over very long distances, care must be taken when configuring the ISL connections to insure that the sessions remain along exclusive paths.
5 Traffic Isolation Zoning CPU1 0 1 40 41 81 82 80 83 1A 0F TI Zone 1 Grid 1 1B 1E 1E 1E Grid 4 TI Zone 2 FIGURE 19 Emulation topology using Enhanced TI Zones Figure 19 on page 68 shows the following Enhanced TI Zoning definitions for the emulation topology: • Green TI Zone includes channel 0, ISL 80, ISL 81, Grid 1, and Grid 4. • Blue TI Zone includes channel 1, ISL 82, ISL 83, and CU Grid-4.
Port fencing 5 Port fencing Occasionally, bad optics and cables can cause errors to occur at a rapid rate that error processing and sending and processing RSCNs can cause fabric performance problems. Port fencing allows the user to limit the number of errors a port can receive by forcing a port offline when certain error thresholds are met. The port fencing feature is configured through Fabric Watch. For more information on configuring Port Fencing, refer to the Fabric Watch Administrator’s Guide.
5 FICON information To display link incidents, connect to the switch, log in as user, and enter one of the following commands: • For the local switch: ficonShow rlir • For all switches defined in the fabric: ficonShow rlir fabric Identifying ports The ficonShow rlir command displays, among other information, a tag field for the switch port. You can use this tag to identify the port on which a FICON link incident occurred.
FICON information 5 • For all switches defined in the fabric: ficonShow switchrnid fabric • For all devices registered with the local switch: ficonShow rnid • For all devices registered with all switches defined in the fabric: ficonShow rnid fabric FRU error reporting FRU failure information is no longer stored on the switch. FRU error information, such as FRU failures and fan and power supply removals and insertions, are stored in error reports as sense data.
5 Swapping port area IDs FRU numbers Following are the Brocade FRU numbers provided for error reports and associated FRU names that display in error reports. Note that the FRU number does not actually display in the error reports, but its associated FRU name does display.
Blade swapping 5 Important notes Consider the following when swapping port area IDs: • Ports that have been swapped cannot be moved to another logical switch. • Ports with area OxFE or OxFF addresses cannot be swapped when FMS mode is enabled. • You can use the portSwapShow command to display information about swapped ports in a switch. • You can use the portSwap command to disable the port-swapping feature. You cannot use the portSwap command after this feature is disabled.
5 Common FICON issues Common FICON issues Any information you need to verify that FICON has been set up correctly can be found in the Chapter 2, “Administering FICON Fabrics” or Chapter 3, “Configuring FICON CUP”. Symptom Cascading: No path – Entry Link is “..” Probable cause and recommended action This typically occurs when one or more of the required high integrity features for cascading have not been met.
Common FICON issues Symptom 5 Channel path with 2-byte addressing does not come online Probable cause and recommended action Ask the operator what CHPID he is attempting to bring online. In FICON environments, only the egress ports are defined in the IOCDS. The CHPID number of the channel appears in the node list, but only if the channel path has logged in. If the channel path will not come online, it may not have completed a Fibre Channel fabric login.
5 Troubleshooting FICON + ONLINE @ PATH NOT VALIDATED - OFFLINE . DOES NOT EXIST * PHYSICALLY ONLINE $ PATH NOT OPERATIONAL The responses “NOT ALL PATHS BROUGHT ONLINE” after attempting to configure the CHPID online and “FICON INCOMPLETE” after the display command indicate that the channel did not come online.
Troubleshooting FICON 5 By default, the FICON group in the supportShow output is disabled. To enable the capture of FICON data in the supportShow output, enter the supportShowCfgEnable ficon command.
5 Troubleshooting FICON • Have you verified that your switch does not have a special mode setting turned on for FICON? NOTE There is no requirement to have a secure fabric in a switched point-to-point topology. Brocade Advanced features software package (Trunking, Fabric Watch, Extended Fabric) license activation is required.
Troubleshooting FICON CUP 5 Also refer to the most recent version of the Fabric OS Release Notes for notes on FICON setup and configuration. • Is this a switched point-to-point or cascaded environment? • Is the FICON group enabled for supportshow? Check at the top of the supportshow. If not, use supportShowCfgEnable ficon and re-run the test that was failing.
5 80 Troubleshooting NPIV FICON Administrator’s Guide 53-1002753-01
Appendix A Platforms supporting FICON This appendix provides the following support details on the following: • Brocade products with end of support announcements supported for FICON for different IBM systems and drivers (Table 8). • Brocade products currently supported for FICON for different IBM systems and drivers (Table 9 on page 82). • Brocade blades supported for FICON in various Brocade Switch and Data Center Backbone products (Table 10 on page 82).
A Currently supported platforms Currently supported platforms Table 9 lists Brocade products currently supported for Fabric OS v7.1.0 for various IBM systems and drivers. TABLE 9 Currently supported platforms Brocade 7800 Brocade 5300 Fabric OS Fabric OS Brocade DCX-4S Fabric OS Brocade DCX Fabric OS Brocade DCX 8510-4 Fabric OS Brocade DCX 8510-8 Brocade 6510 Fabric OS Fabric OS z900 & z800 Driver 3GF v7.1.0 v7.1.0 v7.1.0 v7.1.0 v7.1.0 v7.1.0 v7.1.0 z990 & z890 Driver 55K v7.1.0 v7.1.
Supported Brocade blades 1. The IP ports of an FX8-24 extension blade can operate with another FX8-24 or 7800. The maximum number of FX8-24 blades supported in a chassis it four. An FX8-24 can operate with an FX8-24E; however, IPSEC and compression is only supported on one 10G IP port on the FX8-24. 2. The 64 port card is not supported for FICON but may be in the same chassis used for FICON. It must be in a logical switch that does not have any FICON traffic. 3.
A 84 Supported Brocade blades FICON Administrator’s Guide 53-1002753-01
Appendix Basic Switch Configuration B This appendix provides basic steps and commands to quickly configure a switch for fabric and possible FICON and cascaded FICON operation. For detailed concepts, procedures, and additional Fabric OS command options to configure a switch switch point-to-point and cascaded FICON operation, refer to Chapter 2, “Administering FICON Fabrics”.
B Basic Switch Configuration TABLE 11 Switch configuration example and commands Feature Relevant Commands Upgrade code (if necessary) firmwaredownload firmwareshow Feature keys (add licenses) licenseadd licenseshow Create all logical switches and add all intended ports to each logical switch. lscfg Set switch offline switchdisable Repeat the following procedure to configure switch parameters for each logical switch. 1 Enter the configure command. You will be asked several questions.
Basic Switch Configuration TABLE 11 B Switch configuration example and commands Feature Relevant Commands If you are enabling FMS (CUP), disable all ports assigned address 0xFE and 0xFF. portdisable Enable FMS if FICON CUP will be used. ficoncupset fmsmode enable ficoncupshow fmsmode Set the default zone for no access. defZone --noaccess cfgsave defZone --show Configure zones. This is much easier with Brocade Network Advisor or Web Tools.
B Basic Switch Configuration Parameters in Table 12 are only required when 2-byte link addressing is used in the IOCP. Normally, these parameters are not set when single-byte addressing is used. TABLE 12 88 Cascading (2-byte addressing) example and commands Feature Parameter Add members to the SCC Policy. secPolicyCreate "SCC_POLICY", "wwn;wwn; …" Or, to add all switches already in the fabric, just use an '*' for each WWN: secPolicyCreate "SCC_POLICY", "*" Save the policy.
Appendix Address Binding Examples C This appendix provides examples for the following: • “Sequential address binding” • “Zero-Based to Port-Based Address Binding” • “Unbinding Multiple Ports” Example scripts containing the portaddress --bind and portaddress --unbind commands are included for binding or unbinding ports on all blades installed in a chassis.
C Sequential address binding Example scripts for binding ports Following are example scripts that bind all ports on the DCX Backbone to sequential addresses. You can copy these scripts and paste directly into a Telnet Fabric OS command line session. If a port does not exist, an error message will be reported, but this has no effect.
Sequential address binding portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress # Slot 3 portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portadd
C Sequential address binding portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress # Slot 9 portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress port
Sequential address binding portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress # Slot 11 portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portad
C Sequential address binding # Slot 12 portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress 94 --bind --bind --bind --bind --bind --bind --bind --bind --bind --bind --bind --bin
Zero-Based to Port-Based Address Binding C Zero-Based to Port-Based Address Binding This section provides an example for binding all ports set with zero-based addressing to port-based addresses on all blades installed in a Brocade DCX Backbone. Figure 20 illustrates all ports with port-based addressing. FIGURE 21 Sequential address binding Before binding addresses to a port with the portaddress --bind command, disable ports with the portdisable command.
C Zero-Based to Port-Based Address Binding portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress # Slot 2 portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress po
Zero-Based to Port-Based Address Binding portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress # Slot 4 portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress porta
C Zero-Based to Port-Based Address Binding portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress # Slot 10 portaddress portaddress portaddress portaddress portaddress portaddress portaddress p
Zero-Based to Port-Based Address Binding portaddress portaddress portaddress portaddress # Slot 11 portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress # Slot 12 portaddress portad
C Unbinding Multiple Ports portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress --bind --bind --bind --bind --bind --bind --bind --bind --bind --bind 12/22 12/23 12/24 12/25 12/26 12/27 12/28 12/29 12/30 12/31 F600 F700 F800 F900 FA00 FB00 FC00 FD00 FE00 FF00 Unbinding Multiple Ports This section provides example scripts for unbinding all addresses on an 8-slot chassis that is fully populated with 32 port cards.
Appendix D Configuration Information Record You can use the following worksheet (Table 13) for recording FICON configuration information.
D 102 Configuration Information Record FICON Administrator’s Guide 53-1002753-01
Appendix EBCDIC Code Page E Extended Binary Coded Decimal Interchange Code (EBCDIC) is an 8-bit character encoding (code page) used on IBM mainframe operating systems such as z/OS and S/390. Code page 37 is an EBCDIC code page with full Latin-1-charset.
E 104 EBCDIC Code Page FICON Administrator’s Guide 53-1002753-01
Index Numerics D 256-area addressing mode, 27 disabling IDID mode, 12 disabling the management server mode, 12 displaying information, 69 DLS, 77 domain ID, insistent, 2 Dynamic Load Sharing, 77 A address mode changing, 28 FICON and blade support, 29 addressing link and FC, 14 modes, 27 automating CS_CTL mapping, 30 B best practices for configuring FICON, 31 binding, 10 blades not supported for FICON, 83 blades supported for FICON, 82 E enabling IDID mode, 12 extended interswitch link (XISL), 26 exte
FICON emulation configuring on 7800 and FX8-24, 54 displaying configuration values, 55 IBM z/OS Global Mirror, 48 modifying, 55 overview, 47 printer, 51 statistics, 55 tape, 49 Teradata, 52 FICON extension platform support, 47 FICON support blades, 82 blades not supported, 83 platforms, 82 firmware upload and download, 60 FMS mode disabling, 40 displaying, 40 enabling, 40 Fabric OS command limitations, 40 OxFE and OxFF addresses, 41 upgrade considerations, 41 FRU failures, 71 G gathering additional informa
S SCC policy, 18 security policy, create, 25 security-related commands, 18 session-based zoning enforcement, 8, 61 single-switch configuration, 19 swapping port area IDs, 72 important notes, 73 switch preparation, 19 switched point-to-point configuration, 5 T tag field, interpreting, 70 tape emulation, 49 Tape Pipelining, 54 Teradata emulation, 52 Teradata statistics, 58 troubleshooting NPIV, 79 U unable to ’vary online’, 76 X XISL, 26 XRC, 48 Z zoning and PDCM considerations, 12 FICON Administrator’s
108 FICON Administrator’s Guide 553-1002753-01
