May 2015 FICON. Administrator's Guide. Supporting Fabric OS v7.4.0

Transcription

1 29 May 2015 FICON Administrator's Guide Supporting Fabric OS v7.4.0

2 2015, Brocade Communications Systems, Inc. All Rights Reserved. ADX, Brocade, Brocade Assurance, the B-wing symbol, DCX, Fabric OS, HyperEdge, ICX, MLX, MyBrocade, OpenScript, The Effortless Network, VCS, VDX, Vplane, and Vyatta are registered trademarks, and Fabric Vision and vadx are trademarks of Brocade Communications Systems, Inc., in the United States and/or in other countries. Other brands, products, or service names mentioned may be trademarks of others. Notice: This document is for informational purposes only and does not set forth any warranty, expressed or implied, concerning any equipment, equipment feature, or service offered or to be offered by Brocade. Brocade reserves the right to make changes to this document at any time, without notice, and assumes no responsibility for its use. This informational document describes features that may not be currently available. Contact a Brocade sales office for information on feature and product availability. Export of technical data contained in this document may require an export license from the United States government. The authors and Brocade Communications Systems, Inc. assume no liability or responsibility to any person or entity with respect to the accuracy of this document or any loss, cost, liability, or damages arising from the information contained herein or the computer programs that accompany it. The product described by this document may contain open source software covered by the GNU General Public License or other open source license agreements. To find out which open source software is included in Brocade products, view the licensing terms applicable to the open source software, and obtain a copy of the programming source code, please visit

3 Contents Preface... 7 Document conventions...7 Text formatting conventions... 7 Command syntax conventions... 7 Notes, cautions, and warnings... 8 Brocade resources... 9 Contacting Brocade Technical Support...9 Document feedback About This Document Supported hardware and software Additional FICON resources What's new in this document...11 Introducing FICON...13 FICON overview...13 Fabric OS support for FICON...13 Latency guideline FICON concepts...15 FICON configurations...16 Switched point-to-point...17 Cascaded FICON...17 Access control in FICON...25 Cascaded zoning Error reporting Secure access control...28 FICON commands Link and FC addressing Domain ID Port area ALPA Administering FICON Fabrics...35 User security considerations Meeting high-integrity fabric requirements Enabling the insistent domain ID...36 Creating and activating the SCC policy...36 Enabling the fabric-wide consistency policy...37 Enabling High-Integrity Fabric mode...37 Using other security commands...38 Preparing a switch for FICON Cascaded FICON and two-byte addressing considerations Configuring switched point-to-point FICON...39 Configuring cascaded FICON FICON and FICON CUP in Virtual Fabrics Addressing modes Mode 0 (10-bit addressing) FICON Administrator's Guide 3

4 Mode 1 (zero-based addressing) Mode 2 (port-based addressing)...47 Changing the addressing mode FICON and blade support for addressing modes Port swap limitations Disabling and enabling ports - persistent states Clearing the FICON management database...49 Automating CS_CTL mapping FICON best practices...50 Latency guideline Configuring FICON CUP Control Unit Port overview FICON CUP restrictions...54 CUP configuration recommendations FICON CUP zoning and PDCM considerations...56 Port and switch naming standards for FMS mode FICON CUP Fabric OS commands...56 Configuring FICON CUP...57 Disabling ports 0xFE and 0xFF...57 Configuring FICON CUP in Virtual Fabrics Determining physical port assignment FMS mode and FICON CUP...58 Fabric OS command limitations and considerations...59 Displaying FMS mode...60 Enabling FMS mode...60 Disabling FMS mode...60 FMS mode and FICON 0xFE or 0xFF ports...60 Upgrade considerations Port swap limitations Mode register bit settings...62 FICON file access facility Considerations for setting mode register bits...64 Setting the mode register bits Setting the MIHPTO value Persistently enabling and disabling ports for CUP...65 Administering FICON Extension Services...67 Platforms supporting FICON extension over IP FICON emulation overview IBM z/os Global Mirror emulation Tape emulation Printer emulation...71 Teradata emulation FCIP configuration requirements for FICON extension Configuration requirements for switches and directors...72 High-integrity fabric requirements for cascaded configurations FICON emulation requirement for a determinate path...73 Configuring FICON emulation...74 Configuration examples Displaying FICON emulation configuration values...75 Modifying FICON emulation...75 Displaying FICON emulation performance statistics...75 FICON emulation monitoring...76 Options for displaying statistics FICON Administrator's Guide

5 Maintaining and Troubleshooting FICON...79 Firmware management in a FICON environment Upgrade and downgrade considerations Firmware download disruption Non-disruptive firmware upload and download Configuration restoration in a FICON environment Traffic Isolation Zoning...81 Determining ports for the TI Zone Enhanced TI Zoning...82 Monitoring and Alerting Policy Suite Port fencing Defining port fencing Settings for FICON environments FICON information Link incidents Registered listeners Node identification data...89 FRU error reporting Swapping port area IDs...91 Important notes Blade swapping...91 Common FICON issues Troubleshooting FICON General information to gather for all cases Switched point-to-point topology checklist Cascaded topology checklist...96 Gathering additional information CUP diagnostics...97 Troubleshooting FICON CUP...97 Troubleshooting NPIV Platforms Supporting FICON...99 Introduction Supported platforms with end-of-support announcements Currently supported platforms Supported Brocade blades Unsupported blades Basic Switch Configuration Address Binding Examples Sequential address binding Example scripts for binding ports Port-based address binding Example scripts for binding ports Unbinding multiple ports Configuration Information Record EBCDIC Code Page FICON Administrator's Guide 5

6 6 FICON Administrator's Guide

7 Preface Document conventions...7 Brocade resources... 9 Contacting Brocade Technical Support...9 Document feedback Document conventions The document conventions describe text formatting conventions, command syntax conventions, and important notice formats used in Brocade technical documentation. Text formatting conventions Text formatting conventions such as boldface, italic, or Courier font may be used in the flow of the text to highlight specific words or phrases. Format bold text italic text Courier font Description Identifies command names Identifies keywords and operands Identifies the names of user-manipulated GUI elements Identifies text to enter at the GUI Identifies emphasis Identifies variables Identifies document titles Identifies CLI output Identifies command syntax examples Command syntax conventions Bold and italic text identify command syntax components. Delimiters and operators define groupings of parameters and their logical relationships. Convention bold text italic text value Description Identifies command names, keywords, and command options. Identifies a variable. In Fibre Channel products, a fixed value provided as input to a command option is printed in plain text, for example, --show WWN. FICON Administrator's Guide 7

8 Notes, cautions, and warnings Convention Description [ ] Syntax components displayed within square brackets are optional. Default responses to system prompts are enclosed in square brackets. { x y z } A choice of required parameters is enclosed in curly brackets separated by vertical bars. You must select one of the options. In Fibre Channel products, square brackets may be used instead for this purpose. x y A vertical bar separates mutually exclusive elements. < > Nonprinting characters, for example, passwords, are enclosed in angle brackets.... Repeat the previous element, for example, member[member...]. \ Indicates a soft line break in command examples. If a backslash separates two lines of a command input, enter the entire command at the prompt without the backslash. Notes, cautions, and warnings Notes, cautions, and warning statements may be used in this document. They are listed in the order of increasing severity of potential hazards. NOTE A Note provides a tip, guidance, or advice, emphasizes important information, or provides a reference to related information. ATTENTION An Attention statement indicates a stronger note, for example, to alert you when traffic might be interrupted or the device might reboot. CAUTION A Caution statement alerts you to situations that can be potentially hazardous to you or cause damage to hardware, firmware, software, or data. 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. 8 FICON Administrator's Guide

9 Brocade resources Brocade resources Visit the Brocade website to locate related documentation for your product and additional Brocade resources. You can download additional publications supporting your product at Select the Brocade Products tab to locate your product, then click the Brocade product name or image to open the individual product page. The user manuals are available in the resources module at the bottom of the page under the Documentation category. To get up-to-the-minute information on Brocade products and resources, go to MyBrocade. You can register at no cost to obtain a user ID and password. Release notes are available on MyBrocade under Product Downloads. White papers, online demonstrations, and data sheets are available through the Brocade website. Contacting Brocade Technical Support As a Brocade customer, you can contact Brocade Technical Support 24x7 online, by telephone, or by e- mail. Brocade OEM customers contact their OEM/Solutions provider. Brocade customers For product support information and the latest information on contacting the Technical Assistance Center, go to If you have purchased Brocade product support directly from Brocade, use one of the following methods to contact the Brocade Technical Assistance Center 24x7. Online Telephone Preferred method of contact for nonurgent issues: My Cases through MyBrocade Software downloads and licensing tools Knowledge Base Required for Sev 1-Critical and Sev 2-High issues: Continental US: Europe, Middle East, Africa, and Asia Pacific: +800-AT FIBREE ( ) For areas unable to access toll free number: Toll-free numbers are available in many countries. support@brocade.com Please include: Problem summary Serial number Installation details Environment description Brocade OEM customers If you have purchased Brocade product support from a Brocade OEM/Solution Provider, contact your OEM/Solution Provider for all of your product support needs. OEM/Solution Providers are trained and certified by Brocade to support Brocade products. Brocade provides backline support for issues that cannot be resolved by the OEM/Solution Provider. FICON Administrator's Guide 9

10 Document feedback Brocade Supplemental Support augments your existing OEM support contract, providing direct access to Brocade expertise. For more information, contact Brocade or your OEM. For questions regarding service levels and response times, contact your OEM/Solution Provider. Document feedback To send feedback and report errors in the documentation you can use the feedback form posted with the document or you can the documentation team. Quality is our first concern at Brocade and we have made every effort to ensure the accuracy and completeness of this document. However, if you find an error or an omission, or you think that a topic needs further development, we want to hear from you. You can provide feedback in two ways: Through the online feedback form in the HTML documents posted on By sending your feedback to documentation@brocade.com. Provide the publication title, part number, and as much detail as possible, including the topic heading and page number if applicable, as well as your suggestions for improvement. 10 FICON Administrator's Guide

11 About This Document Supported hardware and software Additional FICON resources What's new in this document...11 Supported hardware and software Although many different software and hardware configurations are tested and supported by Brocade Communications Systems, Inc. for Fabric OS v7.4.0 documenting all possible configurations and scenarios is beyond the scope of this document. For a complete list of platforms supported by FICON and Fabric OS v7.4.0, refer to Platforms supporting FICON on page 99 Platforms supporting FICON. In cases where procedures or parts of procedures do not apply to all Brocade hardware platforms, this guide identifies which platforms are supported. Additional FICON resources In addition to Brocade product resources listed under "Brocade Resources" in this Preface, a dedicated page for mainframe resources is located at Mainframe and FICON Solutions. What's new in this document This document includes new and modified information for the Fabric OS release. Changes made for this release The following information was added or changed in this document, in addition to other changes made for accuracy and clarity: Throughout the document, updated reference to third-party products. Updated the information in FICON Overview to current IBM versions. Updated the information in Configuring switched point-to-point FICON on page 39 to allow both PBR and DBR when FICON Emulation features are enabled. Updated the information and added a note about HIF requirements in Meeting high-integrity fabric requirements on page 35. Updated the information in Configuration restoration in a FICON environment on page 80 for changes to configuration upload and configuration download. In the chapter Administering FICON Fabrics on page 35, removed the section FCR and FICON cascading that exists in prior releases of the document FICON Administrator's Guide 11

12 About This Document Added information in IBM z/os Global Mirror emulation on page 68 recommending use of DBR rather than PBR in cascaded FICON configurations. Updated the supported platform list in Enhanced TI Zoning on page 82. Updated the information in Port fencing on page 87 to recommend alternatives to port fencing. Updated the list of supported platforms and releases in Currently supported platforms on page 100. Changes made for this release () Minor changes have been made to the document to enhance presentation of the graphics and illustrations. 12 FICON Administrator's Guide

13 Introducing FICON FICON overview...13 FICON concepts...15 FICON configurations...16 Access control in FICON...25 FICON commands Link and FC addressing FICON overview IBM Fibre Connection (FICON ) is an industry-standard, high-speed input/output (I/O) interface for mainframe connections to storage devices. This guide discusses support offered by Fabric OS in intermix mode operations, in which FICON and Fibre Channel technology work together. For specific information about intermix mode and other aspects of FICON, refer to the IBM Redbook, FICON Implementation Guide (SG ), and IBM z System Connectivity Handbook (G ). NOTE In this guide, the term switch is used to refer to a Brocade switch, Backbone, backbone platform, or director unless otherwise noted. Fabric OS support for FICON The following Fabric OS standard features support FICON fabrics: Blade swapping Allows you to swap a blade of the same type so that you can replace a field-replaceable unit (FRU) with minimal traffic disruption. This feature is available for both FICON and open system environments. Blade swapping resolves situations in which the hardware has failed and the channel configurations cannot be changed quickly. In addition, a blade swap minimizes and eliminates the need to make changes to the I/O sysgen in the hardware configuration definition (HCD). Blade swapping has minimal or no impact on other switch features. Routing policies IBM z Systems FICON did not support exchange-based routing as of the publication date of this document, but does support port-based and device- based routing. For details on these policies, refer to the "Routing Traffic" chapter in the Fabric OS Administrator's Guide. FICON MIB module Addresses link incident data for FICON hosts and devices connected to a switch. The FICON MIB module supplements other Management Information Bases (MIBs) used to manage switches and should be used in conjunction with those other MIBs. Insistent Domain ID (IDID) FICON Administrator's Guide 13

14 Latency guideline 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 the recommended best practice for single byte addressing. Link incident detection, registration, and reporting Provides administrative and diagnostic information. Swap port area IDs (PIDs) of physical ports Redirects resources from a failed port to a healthy port without changing the mainframe hardware configuration definition (HCD) settings. This feature, also called "port swapping," is available for both FICON and open system environments. Swapping PIDs on ports resolves situations in which the hardware has failed and the channel configurations cannot be changed quickly. Port swapping has minimal or no impact on other switch features. Switch connection control (SCC) policy Includes fabric security methods that prevent unauthorized switches from joining a fabric. SCC policy configured in strict mode is required for cascaded FICON configurations and whenever 2-byte addressing is used. Traffic Isolation (TI) Zones and Enhanced TI Zones TI Zones are used to direct traffic across links through a specified path. Enhanced TI Zones allow you to have ports in more than one TI Zone and to program domain controller routes to destination domains for F-class traffic, ensuring fabric stability. NOTE For more detail on these features and configuration procedures, refer to the Fabric OS Administrator's Guide. Brocade management tools provide further support: Brocade Network Advisor Brocade Network Advisor is an optional software program that can be used to manage a fabric that supports FICON and Fibre Channel Protocol (FCP) devices and traffic. This is the recommended GUI management tool for FICON environments on B-series enterprise-class switches. For more information on Brocade Network Advisor, refer to the manual appropriate for your version requirements: Brocade Network Advisor SAN + IP User Manual Brocade Network Advisor SAN User Manual Web Tools Web Tools is an embedded GUI-management tool that can be used to manage a Brocade switch or director that supports FICON and Fibre Channel Protocol (FCP) devices and traffic. For more information on Web Tools, refer to the Web Tools Administrator's Guide. Latency guideline The maximum supported distance for a FICON channel is 300 Km (1.5 msec of delay). Synchronous remote data replication for DASD is generally limited to 100 Km (0.5 msec of delay). Asynchronous remote data replication for DASD, and remote tape reads/writes require that the Brocade Advanced Accelerator for FICON feature be used with FCIP. The Advanced Accelerator for FICON feature emulates control unit response to the channel to improve the performance over distances greater than locally attached distances. 14 FICON Administrator's Guide

15 FICON concepts FICON concepts The following figure shows how the traffic in a switched point-to-point configuration flows in a FICON environment. The logical path of the traffic is defined as frames moving from the channel to the switch to the control unit. FICON traffic moves from a logical partition (LPAR) and through the channel, through a Fibre Channel link to the switch through the control unit, and ends at the device. This is also called a channel path, which is a single interface between a central processor and one or more control units along which signals and data can be sent to perform I/O requests. The channel path uses the logical path to traverse the Fibre Channel fabric. The channel path is defined using an ID, called the channel path ID (CHPID). This information is stored in the Input/Output Definition File (IODF) and may be dynamically configured. The IODF is typically built using the hardware configuration definition (HCD). FIGURE 1 FICON traffic The traffic on the channel path communicates using channel command words (CCW) for Command Mode FICON, and transport control words (TCW) for z High Performance FICON (zhpf) channel programs. In a FICON environment, buffer credits are used at the Fibre Channel Protocol (FCP) level for flow control between optically adjacent ports, while information unit (IU) pacing is the flow control mechanism used by the channel. There are times when there are no more buffer credits to pass back to the other end of the link and a frame pacing delay occurs. Frame pacing delay is the number of intervals of 2.5 microseconds that a frame had to wait to be transmitted due to a lack of available buffer credits. Frame pacing delay information is reported via the z/os Resource Measurement Facility (RMF), specifically in the FICON Director Activity Report (RMF 74-7). FICON introduces the following concepts: FICON Control Unit Port (CUP) The internal port in a switch that assumes an Fibre Channel (FC) address such that it is the FC domain ID (DID) used to direct FICON traffic to the FICON Management Server (FMS). FICON Manager Host communication includes control functions such as blocking and unblocking ports, as well as monitoring and error-reporting functions. Hardware configuration definition (HCD) HCD is an IBM interactive interface application that allows you to define the hardware configuration for both the processor channel subsystem and the operating system running on the processor. Information unit FICON Administrator's Guide 15

16 FICON configurations A unit of FICON data consisting of from one to four Fibre Channel frames. Link Incident Record Registration (LIRR) The LIRR Extended Link Service (ELS) requests that the recipient add the requesting port to its list of ports that are to receive a Registered Link Incident Report (RLIR). Node A node is an endpoint that contains information. It can be a computer (host), a device controller, or a peripheral device, such as a DASD array or tape drive. A node has a unique 64-bit identifier known as the Node_Name. The Node_Name is typically used for management purposes. Prohibit Dynamic Connectivity Mask (PDCM) and connectivity attributes PDCM controls whether communication between a pair of ports in the switch is prohibited. Connectivity attributes control whether all the communication is blocked for a port. Read Record Set (RRS) RRS is an IBM Channel-initiated CCW command. The Brocade Advanced Accelerator for FICON License allows the emulation of command chains that include this CCW command. The command is used in IBM z/os Global Mirror configurations to read updates from a volume in an active mirroring session. Registered Link Incident Report (RLIR) RLIR ELS provides a way for a node port to send an incident record to another node port. Request Node Identification Data (RNID) RNID ELS acquires the associated node s identification data, which provides configuration discovery and management purpose information. Resource Measurement Facility (RMF) Performance monitoring component of z/os that gathers transaction data from the environment and generates performance reports. All Level II reports, which include port statistics, require the FICON Control Unit Port (CUP) and FICON Management Server (FMS), the FICON director included in the IOSysGen as a 2032 Control Unit, and the appropriate parmlib settings configured to enable the RMF 74-7 record generation and statistics collected. Systems Operations (SysOps) SysOps provides the ability to monitor and control all subsystems in a sysplex from any system in the sysplex. This includes controlled startup, controlled shutdown, and automated recovery of software resources. 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. IPL file The initial program load (IPL) File, located in nonvolatile storage, contains the current, active configuration settings for the FICON director. If functions to initialize data on the Director during a POR event. When the "Active=Saved" FICON CUP mode register bit setting is on, any active configuration in switch memory is automatically saved to the IPL file. FICON configurations There are two types of FICON configurations that are supported using Brocade Fabric OS: switched point-to-point and cascaded topologies. 16 FICON Administrator's Guide

17 Switched point-to-point Switched point-to-point A single-switch configuration is called switched point-to-point allows the channel to use single-byte addressing. FIGURE 2 Switched point-to-point FICON Cascaded FICON Cascaded FICON refers to an implementation of FICON that uses one or more FICON channel paths in which the domain ID of the entry switch is different than the domain ID of the switch where the control unit is attached. Therefore, cascading requires a two-byte link address. Anytime a two-byte link address is defined on a channel, all link addresses associated with that channel must be two-byte link addresses. Switches may be interconnected using the following links: Traditional Inter-Switch Links (ISLs) Inter-Chassis Links (ICLs) Fibre Channel over Internet Protocol (FCIP) The processor interface is connected to one switch (known as the entry switch), while the storage interface is connected to the other. This configuration is supported for both DASD and tape, with multiple processors, DASD subsystems, and tape subsystems sharing the ISLs or ICLs between the switches and directors. Multiple ISLs between the switches and directors are also supported. Cascading FICON Administrator's Guide 17

18 Introducing FICON between switches and directors is also supported. An example of this would be a Brocade DCX director connected to a Brocade A cascaded configuration (refer to the following figure) requires two-byte addressing. Two byteaddressing requires a list of authorized switches. This authorization feature, called fabric binding, is available through the Secure Access Control List feature. The fabric binding policy allows a predefined list of switches (domains) to exist in the fabric and prevents other switches from joining the fabric. This type of configuration is described in User security considerations on page 35. The Switch Connection control Policy must also be configured in strict mode. FIGURE 3 Cascaded FICON There are hardware and software requirements specific to two-byte addressing: Both the FICON switches must be Brocade switches. The mainframes must be zarchitecture machines: z196, z114, z800, 890, 900, 990, z9 BC, z9 EC, z10 BC, z10 EC, zec12, zbc12, and z13. Cascaded FICON requires 64-bit architecture to support the two-byte addressing scheme. Cascaded FICON is not supported on 9672 G5/G6 or earlier mainframes. z/os version 1.4 or later, or z/os version 1.3 with required Program Temporary Fixes (PTFs) and Microcode Loads (MCLs) to support two-byte link addressing (DRV3g and MCL (J11206) or later) is required. Switch configuration requirements: Make sure that E_D_TOV is the same on all switches in the fabric (typically, this is not changed from the default) Make sure that R_A_TOV is the same on all switches in the fabric (typically, this is not changed from the default) Configure insistent Domain ID (IDID) Configure fabric binding (strict SCC policy) 18 FICON Administrator's Guide

19 Qualified FICON cascaded configurations Qualified FICON cascaded configurations Not all fibre channel fabrics are qualified for FICON. Cascaded FICON configurations are limited to wellcontrolled paths. Only the channel paths illustrated in this section are supported for FICON. The resulting fabric scenario after ISL failures must not result in an unsupported configuration. When physical cabling is not practical to enforce these configurations, zoning or Traffic Isolation zoning (TI zoning) with failover disabled may be used to ensure unsupported fabrics cannot be formed. Note that these restrictions apply to logical switches and not the chassis. The following figures show two cascaded configurations. These configurations require Channel A to be configured for two-byte addressing and require IDID and fabric binding. It is recommended that there be only two domains in a path from a FICON Channel interface to a FICON Control Unit interface. There are exceptions to the two-domain rule in extended fabric configurations. Refer to Extended fabric configurations on page 19 for examples. FIGURE 4 Cascaded configuration, two switches The following figure illustrates multiple switches cascaded off of switch 21. As long as there is only one hop from channel to control unit, the configuration is supported. FIGURE 5 Cascaded configuration, core-edge architecture Extended fabric configurations Switches in cascaded configurations may be connected through interchassis links (ICLs), interswitch links (ICLs), and FCIP. Connection using FCIP is through Fibre Channel extension devices, such as 7800 switches, 7840 switches, and FX8-24 blades. Following are example configurations. For more information on long distance and extended fabrics, refer to the Fabric OS Administrator's Guide. For more information on extension products, including FCIP and IP Extension, refer to the Fabric OS Extension Administrator's Guide. The following figure illustrates a multi-hop ICL triangle configuration that uses ICLs. Note that three switches are connected through ICLs only. FICON Administrator's Guide 19

20 Introducing FICON FIGURE 6 Multi-hop ICL triangle The following figure illustrates a multi-hop configuration that uses ICLs and ISLs. This configuration is supported with or without switches 4 or 1. All switches must be all generation (Gen) 4 or all Gen 5. You cannot mix Gen 4 and Gen 4 on ICL connections. 20 FICON Administrator's Guide

21 Introducing FICON FIGURE 7 Multi-hop configuration with ICLs The following figure illustrates a multi-hop configuration that uses ICLs and FCIP. The two 7800 switches are for ISL extension only using FCIP. Channel or control unit connections are not permitted. These switches may be replaced with an FX8-24 blade installed in directors. This configuration can be supported with or without switches 4 or 1. All switches must be Gen 4 or Gen 5. You cannot mix Gen 4 and Gen 5 switches with ICLs. FICON Administrator's Guide 21

22 Introducing FICON FIGURE 8 Multi-hop with ICLS and FCIP The following figure illustrates a configuration that uses FCIP between 7800 switches that are used as routers only, for ISL extension. In this configuration topology, direct FICON channel or control unit connections into the 7800 FC Ports are not supported. The 7800 switches may be replaced with FX8-24 blades installed in directors. 22 FICON Administrator's Guide

23 Introducing FICON FIGURE 9 FCIP with 7800 switches as routers only The following figure illustrates a configuration that uses cascaded FCIP with four 7800 switches. The 7800 switches at site 1 are used for ISL extension only. Channel or control unit connections are not permitted. The 7800 switches at site 2 are only for network, channel, and control unit connections. The 7800 switches on either site may be replaced with the FX8-24 blades installed in directors. FICON Administrator's Guide 23

24 Introducing FICON FIGURE 10 Cascaded configuration using FCIP and 7800 switches The following figure illustrates a cascaded configuration that uses FCIP and 7800 switches as edge switches. At site 1, the 7800 switches are used for ISL extension only. Channel or control unit connections are not permitted. At site 2, only channel, and control unit connections are permitted on the 7800 switches. The 7800 switches at either site may be replaced with the FX8-24 blades installed in directors. 24 FICON Administrator's Guide

25 Access control in FICON FIGURE 11 Cascaded configuration using FCIP and 7800 edge switches 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. Although domain index zoning is supported, WWN zoning for Quality of Service (QoS) is recommended in environments where N_Port ID Virtualization (NPIV) is deployed. For more information on how to implement QoS domain index zoning in your fabric, refer to the "QoS zones" section of the Fabric OS Administrator's Guide for details. When zoning changes occur, Registered State Change Notification (RSCN) messages are sent out throughout the zone. RSCNs are part of the low-level Fibre Channel Protocol that alerts channels and devices to changes in the fabric. As a best practice, Brocade recommends use of one zone for all FICON connectivity. FICON Administrator's Guide 25

26 Cascaded zoning NOTE Session-based zoning enforcement is not recommended on a FICON switch. For more information on session-based zoning enforcement, refer to the Fabric OS Administrator's Guide. Cascaded zoning The figure below illustrates multiple sites sharing the same disaster-recovery site. Each switch or Director at a remote site, labeled Director 1 and Director 31, can pass traffic to Director 2, but no traffic is permitted between Zone A and Zone B. FIGURE 12 Simple cascaded zoning The figure below illustrates the multiple zoning concepts that can be used to restrict traffic. Any host channel at the Backup Site (connected to Director 11 or Director 12) can connect to the backup tape contained within the same zone. Notice that no more than a single hop is ever allowed and only Channel Path Identifiers (CHPIDs) 79 and 7A on the Primary Site can connect to the backup tape. Furthermore, CHPIDs 79 and 7A can only connect to the backup tape at the Backup Site. NOTE Zoning does not replace the need to set up the connectivity from the host to storage control units in the HCD or Input/Output Configuration Program (IOCP). For more information on zoning, refer to the Fabric OS Administrator's Guide. 26 FICON Administrator's Guide

27 Error reporting FIGURE 13 Complex cascaded zoning Zone A (Blue): 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. Zone B (Orange): 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. Zone C (Green): Any CHPID connected to Director 11 can get to any control unit connected to Director 11. The zone includes all ports in Director 11 except ports 5 and 6. Adding ports 5 and 6 to the zone, so that all ports in the switch or Director are in the same zone, would not affect permitted connectivity and may be a more practical alternative. Zone D (Yellow): Any CHPID connected to Director 12 can get to any control unit connected to Director 12. The zone includes all ports in Director 12 except ports 5 and 6, which are used for ISLs. Red Zone E: CHPID 79 can talk only to the remote tape connected to ports 7 and 8 on Director 11. The zone includes port 4 of Director 1 and ports 7 and 8 of Director 11. Either ISL can be used. Purple Zone F: CHPID 7A can talk only to the remote tape connected to ports 7 and 8 on Director 12. The zone includes port 4 of Director 2 and ports 7 and 8 of Director 12. Either ISL can be used. Error reporting Non-implicit link incidents (such as Fabric OS recognized or bit error rate threshold exceeded) and implicit link incidents (such as FRU failure) 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 FICON Administrator's Guide 27

28 Secure access control average frame pacing delay information) reports port errors, which in turn are also reported back to the mainframe host management consoles. Secure access control Binding is a method used to prevent devices from attaching to the switch or director. Secure Access Control Lists (ACLs) provides the following fabric, switch, and port binding features: Fabric binding is a security method for restricting switches within a multiple-switch fabric. Brocade recommends using fabric binding for cascaded FICON. SCC ACLs with strict fabric-wide consistency are required for FICON fabric binding. Switch binding is a security method for restricting devices that connect to a particular switch or director. If the device is another switch, this is handled by the SCC policy. If the device is a host or storage device, the device connection control (DCC) policy binds those devices to a particular switch. Policies range from completely restrictive to reasonably flexible, based upon customer needs. SCC ACLs with strict fabric-wide consistency are necessary for FICON switch binding. Port binding is a security method for restricting host or storage devices that connect to particular switch ports. The DCC policy also binds device ports to switch ports. Policies range from completely restrictive to reasonably flexible, based on customer needs. The figure below demonstrates the three types of binding you can use depending on the security requirements of your fabric. 28 FICON Administrator's Guide

29 FICON commands FIGURE 14 Types of binding for access control 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). The table below summarizes the Fabric OS CLI commands that can be used for managing FICON fabrics. For detailed information on these commands, refer to the Fabric OS Command Reference. FICON Administrator's Guide 29

30 Introducing FICON TABLE 1 Fabric OS commands related to FICON Command Description Standard Fabric OS commands bladeswap configure configupload firmwareshow licenseadd licenseremove licenseshow licenseslotcfg portaddress portswap portswapdisable portswapenable portswapshow Swaps the area numbers for matching port pairs of two blades. Changes a variety of switch configuration settings, including setting the domain ID and the insistent mode. Backs up the current FOS feature and switch configuration, including FMS or FICON-specific configuration such as IPL file, active configuration, mode register, and host data. Displays the current version of the firmware. Adds a license to the switch. The license key is casesensitive and must be entered exactly. Removes a license from the switch. Note that FMS mode must be disabled before removing the FICON license. Displays current license keys, along with a list of licensed products enabled by these keys. Enables and displays slot-based licenses for a switch chassis. Note that for a switch without blades, such as the 7840 Extension Switch, slot 0 is used as the slotbased license target. For blades, slot numbers are based on the switch chassis numbering scheme. A license key with the specified capacity must be installed with the licenseadd command before you can enable a feature on a specified slot with this command. Binds the 16-bit address to the lower two bytes of a port 24-bit Fibre Channel address. Also unbinds the currently bound address for the specified port. Swaps ports. Note that the portswap --restore command restores swapped ports to an unswapped state. Disables the portswap feature. The portswap command cannot be used after this feature is disabled. The disabled state is persistent across reboots and power cycles. Enabling or disabling the portswap feature does not affect previously performed portswap operations. Enables the portswap feature. Displays information about swapped ports. 30 FICON Administrator's Guide

31 Introducing FICON TABLE 1 Command Fabric OS commands related to FICON (Continued) Description supportshowcfgenable ficon Turns on logging of FICON information on the switch. Commands specific to FICON ficonclear rlir ficonclear rnid ficoncfg --set LIRR portnumber ficoncfg --reset LIRR portnumber ficonhelp ficoncupset fmsmode enable disable reset Removes all RLIR records from the local RLIR database. Removes all outdated RNID records from the local RNID database. Sets the current LIRR device port number persistently. Clears the currently configured LIRR port number. Displays a list of FICON support commands. Enables, disables, or resets FICON Management Server (FMS) mode. CAUTION Use the ficoncupset fmsmode reset option only under direction from technical support personnel. Indiscriminate use can disrupt CCW processing and create errors at the host. ficoncupset modereg bitname 0 1 ficoncupset MIHPTO seconds ficoncupset CRP PID CHID ficoncupshow DD_LOG ficoncupshow diag_info ficoncupshow fmsmode ficoncupshow hlthchk_log ficoncupshow modereg bitname ficoncupshow MIHPTO ficoncupshow LP ficonshow lirr fabric Sets FICON-CUP mode register bits. Sets missing interrupt handler primary timeout (MIHPTO) values. Sets the current reporting path (CRP). Displays the log information associated with the last diagnostic command processed by the CUP. Displays the diagnostic interval setting and related statistic sampling information for diagnostic information collected by the CUP. Displays the current FMS mode setting. Displays health check logs for the logical switch. Displays FICON-CUP mode register bits. Displays MIHPTO values. Displays the CUP logical path and error-reporting path information. Displays registered listeners for link incidents for the local switch or for the fabric, if specified. FICON Administrator's Guide 31

32 Link and FC addressing TABLE 1 Command Fabric OS commands related to FICON (Continued) Description ficonshow rlir fabric ficonshow rnid fabric ficonshow rnid port ficonshow rnid table ficonshow switchrnid fabric While all FICON channels register as "conditional" recipients of registered link incident reports (RLIRs) and are added to the switch LIRR database, only one channel per switch is selected to forward reports to the host. The command output displays all channels which have registered and indicates which node on each switch is selected to generate reports to the host. Displays node identification data for all devices registered with the local switch or all devices registered with all switches defined in the fabric, if specified. Displays node identification data for a specified port. Displays the local node identification database in tabular format. Displays node identification data for the local switch or for the fabric, if specified. For limitations and considerations for using Fabric OS commands with FMS mode enabled, refer to Fabric OS command limitations and considerations on page 59. 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. The following figure represents components of link and FC addresses that are explained in this section. 32 FICON Administrator's Guide

33 Domain ID FIGURE 15 Link and FC address components Domain ID Although you enter the domain ID in decimal format when configuring a switch, it is represented in hexadecimal formal in the FC address. For single-byte addressing, the domain area returned from the switch where the channel logs in is used for the FC address. Therefore, the channel and control unit must be in the same logical switch. With two-byte link addressing, the most significant byte of the link address is used for the domain area of the FC address. Once two-byte link addressing is defined for a channel, all link addressing for that channel must use two-byte link addressing. Port area The port area address is the single-byte link address or the least significant byte of a two-byte link address. The link address is entered in the HCD in hexadecimal format and is represented in hexadecimal in the FC address. ALPA The Arbitrated Loop Physical Address (ALPA) was originally used in fibre channel for loop devices. Currently, the ALPA is used for N_Port ID Virtualization (NPIV), which allows multiple WWNs to log in to the same switch port. The ALPA determines the logical entity to which frames belong. This is how virtual servers using Linux on IBM z Systems or z/vm can share the same channel. Because the DCX and DCX directors can have up to 512 ports, the upper two bits of the ALPA are used in certain addressing modes. FICON 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 FICON Administrator's Guide 33

34 Introducing FICON 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 46). 34 FICON Administrator's Guide

35 Administering FICON Fabrics User security considerations Meeting high-integrity fabric requirements Preparing a switch for FICON Configuring switched point-to-point FICON...39 Configuring cascaded FICON FICON and FICON CUP in Virtual Fabrics Addressing modes Disabling and enabling ports - persistent states Clearing the FICON management database...49 Automating CS_CTL mapping FICON best practices...50 Latency guideline User security considerations To administer FICON, you must have one of the following roles associated with your login name on the switch: Admin Operator SwitchAdmin FabricAdmin The User and BasicSwitchAdmin roles are view-only. The ZoneAdmin and SecurityAdmin roles have no access. In an Admin Domain-aware fabric, if you use the FICON commands (ficonshow, ficonclear, ficoncupshow, and ficoncupset) for any Admin Domain other than AD0 and AD255, the current switch must be a member of that Admin Domain. The output is not filtered based on the Admin Domain. In Virtual Fabrics, these commands apply to the current logical or specified switch only. Meeting high-integrity fabric requirements In a cascaded switch configuration, FICON channels use an Extended Link Service Query Security Attributes (ELS QSA) function to determine whether they are connected to a high-integrity fabric. Each switch in a high integrity fabric must have the following attributes configured: An insistent domain ID (IDID) A valid SCC policy, configured and activated A fabric-wide consistency policy greater than or equal to switch connection control - strict mode (SCC:S) FICON Administrator's Guide 35

36 Enabling the insistent domain ID NOTE You enable the fabric-wide consistency policy on the fabric once the switch joins the fabric. NOTE If FMS mode is enabled before upgrading from any earlier release to v7.3.0 or later, including v7.4.0, the IDID, SCC_Policy, and SCC:S are validated. If any of the validations fail, the firmware upgrade will fail. When validation is successful, HIF mode will automatically enable when the firmware installs. If a FICON channel tries to connect to a fabric switch without these features configured, the channel segments from the fabric. With HIF mode not configured, new channel bring-up is not possible in v7.3.0 or later firmware. The absence of HIF mode configuration will fail all the security attributes in QSA even though they are actually present. Therefore, you must perform HIF mode configuration when upgrading from v7.3.0 or later firmware. Once these features are configured, you must enable the switch in High-Integrity Fabric (HIF) mode using the Fabric OS configure command. This verifies the required features are set and locks the configuration to ensure connection with the FICON channel. Once the HIF mode is set, you cannot change the IDID, fabric-wide consistency policy, and SCC policy without disabling HIF mode. Following are considerations for using HIF mode: Once at or later firmware you must enable HIF mode to enable FMS mode. Before a Fabric OS downgrade, you must disable HIF mode. Note that this operation is not recommended for FICON and should only be used when downgrading firmware. You will receive a warning to this effect if FMS mode is enabled. If HIF is disabled, any new channel initialization would fail as the Query Security Attribute (QSA) reply from the switch to the channel will fail. The existing channel will continue to operate. Before a Fabric OS firmware upgrade, be sure the switch has appropriate IDID, fabric-wide consistency policy, SCC policy settings enabled. FICON users should verify that HIF is enabled following the upgrade to v7.3.0 or later. The following instructions are provided in this section to configure a switch as part of a high-integrity fabric: Enabling insistent domain ID on page 36 Creating and activating the SCC policy on page 36 Enabling the fabric-wide consistency policy on page 37 Enabling High-Integrity Fabric mode on page 37 Enabling the insistent domain ID To enable the insistent domain ID, complete the following 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. Creating and activating the SCC policy Creating a switch connection control (SCC) policy defines switches allowed in the fabric. 36 FICON Administrator's Guide

37 Enabling the fabric-wide consistency policy To configure and activate an SCC policy, use the following steps. 1. Connect to the switch and log in. 2. Perform one of the following steps: Enter the secpolicycreate command to add all switches in the fabric, if they are connected. secpolicycreate "SCC_POLICY","*" Enter the secpolicyadd command to add one or more members to an existing policy. The following command is an example of adding a member using device WWNs. secpolicyadd "SCC_POLICY","wwn1;wwn2" 3. Enter the secpolicyactivate command to activate the currently defined SCC policy. This activates the policy set on the local switch or all switches in the fabric, depending on the configured fabric-wide consistency policy. Enabling the fabric-wide consistency policy Enable the fabric-wide consistency policy after all the switches have joined the merged fabric. If there are fabric-wide data distribution (FDD) conflicts on any of the ISLs, disable the fabric-wide consistency policy on each switch in the fabric. Once the fabric has merged successfully (use fabricshow to verify), enter the following command. fddcfg --fabwideset "SCC:S" Following are considerations for enabling the fabric-wide security policy: SCC:S enforces strict mode, which is required for FICON. Enabling High-Integrity Fabric mode Setting High-Integrity Fabric (HIF) mode on a switch verifies that the switch meets high-integrity fabric requirements through the channel's Extended Link Services Exchange Query Security Attributes (ELS QSA) function. For a list of high-integrity fabric requirements for switches, refer to Meeting high-integrity fabric requirements on page 35. Setting HIF mode locks the IDID, fabric-wide consistency policy, and SCC policy settings to ensure that the fabric is of high integrity so that it can connect with the FICON channel. You cannot change these settings without disabling HIF mode. NOTE HIF mode must be enabled to enable FMS mode. To enable HIF mode, use the following steps. 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 "High Integrity Fabric Mode" prompt, type y. If HIF configuration requirements have not been met, an error message describes what you must configure for the command to succeed. For example, the following message states that an IDID, SCC policy or fabric-wide consistency policy have not been configured for the switch. Perform additional configuration if required, then enable HIF mode. Error: Unable to set HIF Mode. No valid IDID settings, SCC policy and/or Fabric wide(scc:s) configuration FICON Administrator's Guide 37

38 Using other security commands Using other security commands The following commands are some other security-related commands that you might find useful. Disabling the fabric-wide consistency policy To disable the fabric-wide consistency policy, enter the fddcfg --fabwideset command. Displaying the fabric-wide consistency policy To display fabric-wide consistency policy information, enter the fddcfg --showall command. Displaying the current security policy To display the current security policy, enter the secpolicyshow command. Deleting the SCC_POLICY Enter the secpolicydelete "SCC_POLICY" command if you get messages that the E_Port is in a security violation state. 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 Fabric OS Command Reference. Preparing a switch for FICON Use the following steps to verify and prepare a switch for use in a switched point-to-point FICON environment. A single-switch configuration does not require insistent domain IDs (IDIDs) or fabric binding, provided that connected channels are configured for single-byte addressing. However, you should configure an IDID to ensure that domain IDs are maintained. 1. Connect to the switch and log in using an account assigned to the admin role. 2. Verify the management IP addresses have been set up. 3. Verify the switches can be seen by your management tool. 4. Verify the switches have the correct version of Fabric OS. 5. Add feature keys, if applicable. 6. Enter the configupload command to save a baseline of the switch configuration. 38 FICON Administrator's Guide

39 Cascaded FICON and two-byte addressing considerations Cascaded FICON and two-byte addressing considerations The following are considerations when installing a switch in a FICON environment where two-byte addressing is used. Two-byte addressing is always used in cascaded environments but may be used in single-switch fabrics as well. Making changes to your switch or director may require scheduled downtime. All fabric operating parameters, such as timeout values, must be the same. If you have not made any changes outside the scope of this document, there is nothing additional to consider regarding these parameters. The domain IDs of all switches must be unique and insistent. Although not required, it will be easier to configure the security policies if the zoning matches. Ensuring proper zoning configuration, ISL connections, and that switches and directors have merged into a fabric will also make the process of setting the security attributes much easier. 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 38. For basic steps and commands in a checklist format to quickly configure a switch for fabric and possible FICON operation, refer to the Basic Switch Configuration chapter, then return to this chapter for detailed FICON configuration procedures. Use the worksheet in the Configuration Information Record appendix to record your configuration information. Refer to FICON commands on page 29 for a list of FICON-related Fabric OS commands. CAUTION Configuring the switch for FICON is a disruptive process. The switch must be disabled to configure switch parameters. 1. Connect to the switch and log in using an account assigned to the admin role. 2. Enter the switchdisable command. You will need to disable the switch to access all the switch parameters. 3. Configure the switch and chassis name, if applicable. 4. Set the routing policy by entering the aptpolicy command. Port-based routing (PBR) and device-based routing (DBR) are qualified for IBM z Systems; however, reference your system qualification letter for current support information. The recommended policy is DBR (aptpolicy 2). If FICON Emulation features (IBM z/os Global Mirror or Tape Pipelining) are enabled on an FCIP Tunnel in the switch, either PBR (aptpolicy 1) or DBR (aptpolicy 2) should be set in the switch. 5. Configure Dynamic Load Sharing. The recommended best practice is to enable Dynamic Load Sharing (DLS); however, DLS is only supported when Lossless is enabled. To enable Lossless with DLS, use the dlsset --enable -lossless command. If Lossless will not be used, use the dlsreset command. FICON Administrator's Guide 39

40 Administering FICON Fabrics NOTE If Lossless DLS is not enabled, the routing policy must be port-based routing (aptpolicy 1). 6. Set In-Order Delivery using the iodset command. 7. Configure the switch parameters using the configure command and enter the responses shown in the table below 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 The domain ID is the switch address. The recommended best practice is to set the switch address and domain ID to be the same. The domain ID is entered in decimal, so a switch address of hexadecimal 0x22 would have a domain ID of decimal 34. R_A_TOV Do not change. The Resource Allocation TimeOut Value (R_A_TOV) is entered in milliseconds. This works with the variable E_D_TOV to determine switch actions when presented with an error condition. Allocated circuit resources with detected errors are not released until the time value has expired. If the condition is resolved prior to the timeout, the internal timeout clock resets and waits for the next error condition. E_D_TOV 2000 The Error Detect TimeOut Value (E_D_TOV) is a timeout value entered in milliseconds. This timer is used to flag a potential error condition when an expected response is not received within the set time limit. If the time for an expected response exceeds the set value, then an error condition occurs. Leave this value at 2 seconds (2000) unless connected to extension equipment. In some cases, when connecting to extension equipment, such as the Brocade 7800, it must be set to 5 seconds (5000). This field should only be changed after consulting a Brocade Certified Fabric Professional. WAN_TOV 0 Wide-Area Network TimeOut Value (WAN_TOV) is set in milliseconds. This is the maximum frame timeout value for a WAN, if any, interconnecting the Fibre Channel islands. MAX HOPS 7 This parameter should not be confused with the one- hop FICON cascading limitation. There are configurations that are more than one hop because more than two domain IDs are used in the path that fit within the IBM support limitation of "one hop." Also, Linux on IBM z Systems using FCP channels is not restricted to "one hop". Data field size 2112 Do not change. Specifies the largest possible value, in bytes, for the size of a type 1 (data) frame. The switch advertises this value to other switches in the fabric during construction of the fabric and to other devices when they connect to the fabric. Setting this value smaller than 2112 may result in decreased performance. Sequence level switching Disable device probing 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. 1 The recommended best practice is to disable device probing. When disable device probing is set to 1, devices that do not register with the Name Server will not be present in the Name Server database. 40 FICON Administrator's Guide

41 Administering FICON Fabrics TABLE 2 FICON switch parameters (Continued) Parameter Response Comment Suppress Class F traffic Per-frame route priority Long-distance fabric 0 Do not change. By default, the switch can send Class F frames. When this option is turned on (set to 1), Class F traffic is converted to Class 2 traffic before being transmitted to support remote fabrics that involve ATM gateways. 0 Do not change. In addition to the virtual channels used in frame routing priority, when this value is set to 1, support is also available for per-framebased prioritization. 0 Do not change. The recommended best practice is to configure individual ports for long distance when cascading at extended distances. Insistent Domain ID Mode Yes The recommended best practice is to set the domain ID to be insistent. Setting the insistent domain ID is required for two-byte addressing. High Integrity Fabric Mode No Before setting HIF mode, the following attributes must be configured: An insistent domain ID (IDID A Fabric Wide Consistency Policy => SCC:S (Strict mode) A valid SCC_Policy (configured and activated) Setting HIF mode locks the IDID, fabric wide consistency policy, and SCC policy settings to ensure that the fabric is of high integrity so that it can connect with the FICON channel. You cannot change these settings without disabling HIF mode. Virtual Channel parameters No Do not change. The switch allows fine-tuning of a specific application through virtual channel parameters. The default virtual channel settings have already been optimized for switch performance. Changing these values can improve switch performance, but can also degrade performance. F_Port login parameters No With Fabric OS v6.1.0 and later, it is not necessary to make any changes to F_Port login parameters. The only other reason to answer yes (y) to this prompt is if NPIV is being used and there is a need to change the default number of NPIV logins. Maximum logins per switch Change this only if NPIV is being used and the number of fabric logins will exceed the default or there is a need to limit the number of logins. Maximum logins per port Change this only if NPIV is being used and the number of port logins will exceed the default or there is a need to limit the number of logins. Maximum logins per second For Fabric OS v6.1.0b and later - Do not change. Leave at default. Login stage interval Do not change. Specifies the stage interval in the staged F_Port login, in milliseconds. Zoning operation parameters No Do not change. Disables and enables NodeName Zone Checking. FICON Administrator's Guide 41

42 Administering FICON Fabrics TABLE 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. Refer to the configure command in the Fabric OS Command Reference for more information. System services No Enables or disables the read link status (RLS) probing performed by the FCP daemon. Portlog events enable No Determines whether various types of port events are logged. SSL attributes No Enables or disables Secure Socket Layer attributes. RPCD attributes No Enables or disables Remote Procedure Call Daemon (RPCD) attributes. cfgload attributes No Configures configuration upload and download parameters. Refer to the configurechassis command in the Fabric OS Command Reference for more information. Web Tools attributes No Modifies Webtools attributes such as enabling the Basic User Enabled Perform License, Checking and Warning, Allow Fabric Event Collection, and Login Session Timeout. 8. Enter the switchenable command to set the switch online. 9. Enter the trackchangesset command to enable or disable the track-changes feature and to configure the SNMP-TRAP mode. 10.Enter the fabricprincipal command on the switch you want to be the principal switch. In cascaded fabrics, only one switch should be the principal. In core-edge designs, the director class switch should be the principal. 11.Enter the portcfgspeed command to configure port speeds. By default, all ports are configured to auto-negotiate. Normally, the only time the port configuration is changed is when connecting to 1 Gbps ports. Some Dense Wavelength Division Multiplexing (DWDM) ports are known not to auto-negotiate well. NOTE 8 Gbps ports will not auto-negotiate to 1 Gbps and cannot be configured for 1 Gbps. 16 Gbps ports will not auto-negotiate to 2 Gbps or 1 Gbps. 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. Refer to the Fabric OS Administrator's Guide for details on this option of the portcfglongdistance command. 13.Configure the fill word on Gen4 (8 Gbps capable) switches using the portcfgfillword command. The following example shows the command with mode 3 and passive operands set: portcfgfillword slot/port, 3 passive 42 FICON Administrator's Guide

43 Configuring cascaded FICON NOTE This command is only supported on Gen4 (8 Gbps capable) switch products. It is not supported on Gen2 (4 Gbps capable) switches and is automatic in Gen5 (16 Gbps capable) switches. Refer to your switch vendor for appropriate fill word settings, such as mode. For more information on the portcfgfillword command, refer to the Fabric OS Command Reference. 14.Enter the defzone --noaccess command to disable the default zone. 15.Configure zoning for your fabric. Follow standard FICON zoning practices published by IBM. For more information on zoning, refer to the administrator s guide for your management tool. 16.Enter the statsclear command to clear port statistics. 17.Enter the switchshow command to verify that the switch and devices are online. 18.Enter the ficonshow rnid command to verify that the FICON devices are registered with the switch. Enter this command only if fabric binding is enabled; otherwise, channels will be attached as invalid. The ficonshow rnid port command displays RNID information for a port. 19.Enter the ficonshow lirr command to verify that the FICON host channels are registered to listen for link incidents. Enter this command only if fabric binding is enabled; otherwise, channels will be attached as invalid. 20.Enter the configupload command to save your configuration. NOTE This command backs up the current FOS feature and switch configuration, including FMS or FICONspecific configuration such as IPL file, active configuration, mode register, and host data. 21.Enter the command appropriate for your environment: If you do not have access to an FTP server, use a Telnet session that can log console output and enter the supportshow command to save a FICON baseline. If you have access to an FTP server, enter the supportsave command to save the FICON baseline of your switch. 22.Take the appropriate action based on your configuration: If you have a cascaded configuration, continue configuring your switches using the instructions in Configuring cascaded FICON on page 43. If you have and plan to use a CUP license, continue configuring your switches using the instructions in Configuring FICON CUP on page 57. If you have a switched point-to-point configuration, you have completed the switch configuration. Configuring cascaded FICON In addition to performing the steps listed in Configuring switched point-to-point FICON on page 39, you also must 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: FICON Administrator's Guide 43

44 FICON and FICON CUP in Virtual Fabrics a) Enable the IDID mode using the Fabric OS configure command. For details on enabling the IDID mode, refer to Enabling the insistent domain ID on page 36. b) Set the domain ID. It is highly recommended that the switch ID used in hardware configuration definition (HCD) and Input/Output Configuration Program (IOCP) be the same as the switch address in hexadecimal. All switches ship from the factory with a default domain ID of 1. The best practice is to use something other than 1 so that a new switch can be added to the fabric without changing the domain ID. 2. Use the secpolicycreate command to configure the SCC policies on all switches to limit connectivity to only the switches in the selected fabric. switch:admin> secpolicycreate SCC_POLICY, member;...;member In the command syntax, member indicates a switch that is permitted to join the fabric. Specify switches by WWN, domain ID, or switch name. Enter an asterisk (*) to indicate all the switches in the fabric. To create a policy that includes all the switches in the fabric, enter the following command: switch:admin> secpolicycreate SCC_POLICY "*" 3. Save or activate the new policy by entering either the secpolicysave or the secpolicyactivate command. If neither of these commands is entered, the changes are lost when the session is logged out. 4. Enter the fddcfg command to enable the ACL fabric-wide consistency policy and enforce a strict SCC policy. switch:admin> fddcfg --fabwideset "SCC:S" 5. Enable High-Integrity Fabric mode using the Fabric OS configure command. For details on enabling HIF mode, refer to Enabling High-Integrity Fabric mode on page 37. Setting HIF mode locks the IDID, fabric-wide consistency policy, and SCC policy settings to ensure that the fabric is of high integrity to connect with the FICON channel. You cannot change these settings without disabling HIF mode. 6. Connect and enable channel and control unit (CU) devices. The Query Security Attributes (QSA) response to the channel indicates that the fabric binding and IDID are enabled. 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 Directors, enable CUP on each logical switch. You can configure up to four CUP switches as logical switches in a Virtual Fabrics-enabled platform in FMS mode. Complete instructions for creating a logical switch using Fabric OS commands are in the Fabric OS Administrator's Guide. Instructions for for creating a logical switch using Brocade Network Advisor are in the Brocade Network Advisor User Manual. Once a logical switch is configured, CUP must be installed on the switch per the instructions under Configuring FICON CUP on page 57. The table below specifies the maximum number of logical switches and maximum number of logical switches with FMS mode enabled for supported Brocade FICON switches and directors. 44 FICON Administrator's Guide

45 Administering FICON Fabrics TABLE 3 Maximum logical switches for FICON switches and directors Switch or director Maximum number of logical switches Maximum number of logical switches with FMS (CUP) enabled DCX DCX 8 4 DCX-4S (does not support base switch) (does not support base switch) (3 if using a base switch) When creating a logical switch, consider the following for FICON: Set the addressing mode to 1 (zero-based) or 2 (port-based) for FICON CUP. Setting these modes may be required for specific hardware configurations; refer to the following examples: For 48-port blades in an 8-slot chassis, FICON is supported only on a logical switch with mode 1 addressing configured. This must be in a logical switch other than the default switch. For 48-port blades in a DCX or DCS 8510 FICON Director, FICON is supported on a logical switch defined for mode 1 or mode 2 addressing. This must be in a logical switch other than the default switch. For more information on addressing modes, refer to Addressing modes on page 46. You can use the Fabric OS configure command to allow XISL use. An extended interswitch link (XISL) is an interswitch link (ISL) that connects the logical switch to a base switch and carries traffic for multiple logical fabrics. The XISL is a logical switch feature, not a link feature. It is shared by multiple logical switches and can be used for multiple Fabric IDs (FIDs). Creating an XISL is disruptive because it provides a core routing function for the switch. For more information on creating XISLs and restrictions, refer to the configure command in the Fabric OS Command Reference. When using XISLs, the effective routing policy for all logical switches configured to allow XISL use is that of the base switch regardless of how the routing policy is defined. The best practice is to set the routing policy in all logical switches that allow XISL use to have the same routing policy as the base switch to avoid confusion about the routing policy used. A base switch can only be used for XISLs. Therefore, the switch cannot be managed through a CUP port and cannot report statistics for RMF. Port-based routing (PBR) and device-based routing (DBR) are qualified for IBM z Systems; however, refer to your system qualification letter for current support information. The recommended policy is DBR or aptpolicy 2. If addresses 0xFE or 0xFF have been assigned to physical ports, those ports must be disabled before FMS can be enabled. Each logical switch has its own configuration data, such as the following: 1 Refer to your system qualification letter to determine your specific limits. FICON Administrator's Guide 45

46 Addressing modes Initial Program Load (IPL) file. Configuration data elements, such as Prohibit Dynamic Connectivty Mask (PDCM), Port Information Block (PIB), port address names, mode register, and key counter. CUP configuration files. Ports moved into a logical switch will have persistent states based on the Active=Saved (ASM) bit setting and other factors. Refer to Disabling and enabling ports - persistent states on page 48 for more information. Addressing modes The following 256-area addressing modes provide extended functionality in dynamically created partitions: Mode 0-10-bit addressing Mode 1 - zero-based addressing Mode 2 - port-based addressing Mode 0 (10-bit addressing) Mode 0 is called Disabled in the Brocade Network Advisor. It is not supported for FICON, but can be used for mainframe FCP channels associated with Linux on IBM z Systems or z/vm partitions. That is, on a chassis in a FICON environment, you can utilize a logical switch or default switch only in Mode 1 (zero-based addressing) for FICON, even if Mode 0 is enabled on a different non-ficon logical switch. Mode 0 uses the two upper bits in the ALPA to address up to 1024 ports in a single logical switch. Because a 64-port blade is the highest port count blade available and eight slots is the highest slot count available in a Brocade chassis, the practical address limit is 512 ports. Because NPIV also uses ALPA bits, this address mode leaves just 6 bits for NPIV. Therefore, the maximum NPIV logins is limited to 64 (63 practical), not 256. Mode 0 is supported on chassis switch models only when one of the following is true (typically for customers upgrading from FOS v6.x): The default switch is being used for FICON and no 48 or 64 port blades are installed in the chassis. The default switch address mode 0 will be 8-bit area mode with zero based addressing (which supports FICON) instead of 10-bit addressing. The chassis is not enabled for virtual fabrics and 48 or 64 port blades are not installed in the chassis. Mode 1 (zero-based addressing) Mode 1 is the recommended mode for FICON. In this addressing mode, port numbers are assigned starting with 00 as the ports are moved into the logical switch. Typically, several ports are moved at once. The bottom port in the left-most port column on the blade has the lowest slot number and is assigned 00. Addresses increment by one as ports progress up the blade from 00 and to the next column on the right. Addresses continue to increment by one as they move to the next blade. This is different than how port addresses are assigned in a chassis that is not enabled for Virtual Fabrics. The ALPA is always 0x00. Therefore, Mode 1 addressing limits the maximum switch size to 256 ports. Mode 1 does not use any of the ALPA bits and may be preferred for native FCP with zvm to allow up to 256 (255 practical) NPIV logins. 46 FICON Administrator's Guide

47 Mode 2 (port-based addressing) 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 107 for a list of commands that will bind ports on DCX or DCX Directors fully populated with 32-port blades. Mode 2 (port-based addressing) Port-based addressing follows a default port numbering scheme that starts with 00 for the port on the bottom leftmost column of the blade in slot 1 and increments for each port going up the blade. For a DCX and DCX director, the rightmost port column on the blade starts with 0x80, and port numbering increments going up the blade. Subsequent blade slots follow the same port numbering scheme with an offset of 0x80. The ALPA is always 0x00 except on the 48-port blades. The 48-port blades use bits in the ALPA for the upper 16 ports on bladed switches that support more than 256 ports. This is why the 48-port blade in the DCX and DCX directors is only supported with zero-based addressing. The DCX-4S and DCX directors do not use the ALPA bits with the 48-port blades. Port-based addressing is used in a Brocade switch or director not enabled for Virtual Fabrics. Refer to Port-Based Address Binding on page 111 for a list of commands that will allow DCX or DCX directors fully populated with 32-port blades that are configured for zero-based addressing to use port-based addresses. Changing the addressing mode Changing the addressing mode can have serious implications. After changing the addressing mode, the following actions occur: Physical ports can receive new area assignments. Port addresses that are referenced in an Input/Output Configuration Data Set (IOCDS) generation can be associated with entirely new physical ports. To change the addressing mode, use the following procedure. NOTE To access all parameters controlled by the configure command, you must disable the switch. Any configuration change to a logical switch that requires disabling the switch also requires disabling FMS mode. 1. Disable FMS mode using the ficoncupset fmsmode disable command. 2. Disable the switch using the switchdisable command. 3. Change the address mode using the configure command. The configure command runs in interactive mode and presents you with a series of hierarchical menus. To change the address mode, select the Fabric parameters menu, then select the Enable a 256 Area Limit field and enter appropriate option values. For more information on this command and an example of command output, refer to the Fabric OS Command Reference. 4. Enable the switch using the switchenable command. 5. Enable FMS mode using the ficoncupset fmsmode enable command. FICON Administrator's Guide 47

48 FICON and blade support for addressing modes FICON and blade support for addressing modes Note the following considerations about FICON and blade support on logical switches in DCX and DCX 8510 systems: On default logical switches (and non-virtual Fabrics switches), FICON is not supported if addressing Mode 1 is enabled. Addressing Mode 1 is not supported if FICON CUP is enabled on the default logical switch. On default logical switches with an addressing mode other than Mode 1, any 48-port and 64-port blades are disabled. Port swap limitations For limitations for port swapping on logical switches and when FMS mode is enabled, refer to Port swap limitations on page 61. Disabling and enabling ports - persistent states You cannot issue the portcfgpersistentdisable command if FMS mode is enabled. When FMS mode is enabled, persistently enabled or disabled configuration states are saved in the CUP's IPL file. When FMS mode is enabled and Active=Saved Mode (ASM) is ON, the user can achieve persistent port configuration states by using the portdisable and portenable command. IBM CUP documentation refers to these persistent configuration states as blocked and unblocked. The persistent configuration state depends on the following factors: If ASM is set to one (1) and you change the port's enabled state to block, unblock, enable, or disable in the CUP Active Configuration, then that setting will update the IPL file and will be in a persistent configuration state. If ASM is set to zero (0) and you change the port's enabled state to block, unblock, enable, or disable in the CUP Active Configuration, then that setting will not update the IPL file and will not be in a persistent configuration state. The following tables compare the achievement of port persistent enable and disable states with interactions between the ASM Mode setting, IPL state. and use of the portdisable or portenable command. TABLE 4 ASM 1 ON Initial IPL state Blocked Blocked Unblocked Unblocked User action portenable command pordisable command portenable command pordisable command Physical state of port Enabled Disabled Enabled Disabled Port state in IPL file Unblocked Blocked Unblocked Blocked PortCfgShow command display for persistent state OFF ON OFF ON TABLE 5 ASM 0 OFF Initial IPL state Blocked Blocked Unblocked Unblocked 48 FICON Administrator's Guide

49 Clearing the FICON management database TABLE 5 ASM 0 OFF (Continued) User action portenable command pordisable command portenable command pordisable command Physical state of port Enabled Disabled Enabled Disabled Port state in IPL file Blocked Blocked Unblocked Unblocked PortCfgShow command display for persistent state OFF OFF OFF OFF Following are summaries of important points in the tables: The only time "Persistent Disable ON" should display with the PortCfgShow command is when you disable a port and ASM is set to ON. The only time the IPL file changes is when ASM is set to ON. When FMS mode is enabled, persistence is controlled by the interaction of ASM mode and the IPL file. Clearing the FICON management database Perform the following steps to clear RLIR and RNID records from the FICON management database. 1. Connect to the switch and log in as admin. 2. Enter ficonclear rlir to remove all the RLIR records from the local RLIR database. 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 Control Unit (CU) 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). High priority frames receive more VCs than medium priority frames, which receive more VCs than low priority frames. The virtual channels are allocated according to the CS_CTL value. IBM introduced a new feature, SAN Fabric I/O Priority with the IBM z13. SAN Fabric I/O Priority integrates the IBM z/os Workload Manager (WLM) I/O prioritization with the FICON SAN fabric QoS functionality. The Brocade CS_CTL based frame prioritization functionality should be run in auto mode for use with the SAN Fabric I/O priority feature. QoS zoning is not supported in FICON environments. NOTE Check with your host and storage manufacturer to determine if they support Fibre Channel CS_CTL prioritization on their devices. The Fabric OS Administrator's Guide provides additional information on this feature and steps to enable CS_CTL-based frame prioritization on your switch using the portcfgqos command. The configurechassis command allows you to set chassis-level configuration parameters, such as cfgload, custom, system, and Fabric OS attributes, to be used by ASIC drivers. The following procedure uses the Fabric OS attribute, CS_CTL QoS Mode, to change CS_CTL values mapped to VCs for FICON Administrator's Guide 49

50 FICON best practices priority levels from default to auto mode. While default mode maps CS_CTL values 1-8 (low), 9-16 (medium), and (high) to specific VCs, auto mode maps CS_CTL values 1 (low), 2 (medium), and 3 (high) to VCs based on the ASIC supported by your platform. For DCX , DCX , and 6510 models, a single CS_CTL value is mapped to multiple VCs. To enable auto mode for CS_CTL to VC mapping on a FICON switch, use the following steps. NOTE This process is disruptive as you must reboot the chassis to reset the configuration in the ASIC. You cannot enable CS_CTL mapping on individual ports until this is done. If auto mode is selected, you must select auto mode for each chassis in the fabric. Not doing so will mean different virtual channels (VCs) will be used across the fabric with undesirable results. 1. Connect to the switch and log in to an account that has admin permissions. 2. Launch the configurechassis command. 3. Select no when prompted to modify cfgload attributes, custom attributes, and system attributes, then select yes to modify Fabric OS attributes. root> configurechassis Configure... cfgload attributes (yes, y, no, n): [no] Custom attributes (yes, y, no, n): [no] system attributes (yes, y, no, n): [no] fos attributes (yes, y, no, n): [no] y 4. Select 1 (auto mode) when prompted to configure CS_CTL QoS mode. CSCTL QoS Mode (0 = default; 1 = auto mode): (0..1) [0] 1 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. 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.csctlmode:0 To return to default mode, follow the preceding steps, but select 0 (default mode) for CS_CTL QoS mode when modifying fos attributes through the configurechassis command. NOTE The configurechassis command does not provide options to enable the CS_CTL QoS mode on individual ports in the chassis. Once you set the mode on the chassis, you must enable individual ports to use this mode with the portcfgqos command. For details on the configurechassis and portcfgqos commands, refer to the Fabric OS Command Reference for details. FICON best practices Use the following best practices for configuring FICON on Brocade switches and directors: Configuring Domain ID 50 FICON Administrator's Guide

51 Administering FICON Fabrics Give all switches a unique domain ID and always set the IDs to "insistent." Switch ID Make the Switch ID in the IOCP or HCD the same as the hexadecimal equivalent of the domain ID. Although not required, this will make it easier to correlate switches to the IOCP. For example, if the domain ID is 32 (0x20), the Switch ID should be 20. Firmware Use only qualified firmware for FICON. All versions of firmware for switches that Brocade Network Advisor will be managing should be in the Brocade Network Advisor repository. All switches in a fabric should be at the same code level. When upgrading code more than two levels, plan the upgrades so that no switch in the fabric is more than one release apart. Always check the version of firmware on a switch before putting the switch into production. If a firmware upgrade is required on a new switch installation, upgrade the firmware before making any configuration changes. CHPID and control unit placement Place CHPID and control unit connections on the same port card when possible to minimize the impact of a card failure. This also allows for maximum use of Brocade local switching to minimize latency and optimize performance. Consult your Brocade SE for more specifics on maximizing the benefits of local switching with your specific configuration. This should be done in conjunction with your IOCDS planning. 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 or directors into the fabric after configuring FICON is possible, but allowing the fabrics to form before applying the FICON settings simplifies the configuration process. Addressing mode Always use Mode 1 addressing. You can bind ports to specific addresses and ensure Mode 1 or Mode 2 addressing using the portaddress --bind command. Use the Fabric OS scripts in Sequential address binding on page 107 and Port-Based Address Binding on page 111 to help simplify configuration. Port fencing Set the port fencing parameters with the following values: C3 Discard Frames - 2 per minute Invalid Words - 25 per minute Invalid CRCs - 3 per minute Link Reset - 2 per minute Protocol Error - 2 per minute State Change - 7 per minute WWN-based persistent port area IDs (PIDs) Do not enable WWN-based persistent PIDs for FICON environments. FICON Administrator's Guide 51

52 Latency guideline Latency guideline The maximum supported distance for a FICON channel is 300 Km (1.5 msec of delay). Synchronous remote data replication for DASD is generally limited to 100 Km (0.5 msec of delay). Asynchronous remote data replication for DASD, and remote tape reads/writes require that the Brocade Advanced Accelerator for FICON feature be used with FCIP. The Advanced Accelerator for FICON feature emulates control unit response to the channel to improve the performance over distances greater than locally attached distances. 52 FICON Administrator's Guide

53 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...58 Mode register bit settings Setting the MIHPTO value Persistently enabling and disabling ports for CUP Control Unit Port overview The Control Unit Port (CUP) provides an in-band management interface defined by IBM that defines the channel command words (CCWs) that the FICON host can use for managing the switch. The protocol used is the IBM version of the ANSI FC-SB4 single-byte command code specification, which defines the protocol used for transporting CCWs to the switch, and for the switch to direct data and status back. The CUP is an optional licensed feature. The CUP provides an interface for host in-band management and collection of FICON switch performance metrics using the Resource Measurement Facility (RMF) 74-7 record, more commonly known as the FICON Director Activity Report. Host-based management programs manage the FICON switches by sending commands to the switch control unit defined in the I/O Configuration Data Set (IOCDS) and hardware configuration definition (HCD). A FICON switch that supports CUP can be controlled by one or more host-based management programs or switch consoles. Control of the FICON switches can be shared between these options. CUP commands, or CCWs, monitor and control FICON switch functions. CUP commands are oriented towards management of a single switch, even though the use of CUP in a cascaded FICON environment is fully supported. NOTE The CUP port address will always be xxfexx. Port addresses xxfe and xxff are unavailable to assign to physical ports when FMS is enabled. For more information, refer to Disabling ports 0xFE and 0xFF on page 57. FICON Management Server mode (FMS mode) must be enabled on the switch to enable CUP management features. For more information, refer to FMS mode and FICON CUP on page 58. FICON Administrator's Guide 53

54 FICON CUP restrictions FIGURE 16 FICON CUP The figure above 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. Therefore, addresses "FE" and "FF" cannot be used for assignment to physical ports when FMS is enabled. For more information, refer to Disabling ports 0xFE and 0xFF on page 57. In a FICON environment, only one RMF logical partition (LPAR) should be configured to poll the CUP for port statistical counter data to minimize contention for the CUP device. Host contention for access to the CUP can lead to missing interrupts, potentially causing the host to box the device. It is a best practice to have more than one CHPID defined as a path to the CUP to ensure redundancy for host-to- CUP connectivity. FICON CUP restrictions The following restrictions apply to Brocade FICON switches having at least 256 ports when FMS mode is enabled and when host applications are used for in-band monitoring and management of the switch: FICON Management Server mode (FMS mode) must be enabled on the switch to enable CUP management features. When this mode is enabled, Fabric OS prevents configuration requests from out-of-band management interfaces from interfering with host in-band configuration requests by serializing access to switch parameters. 54 FICON Administrator's Guide

55 CUP configuration recommendations ATTENTION Once FMS mode is enabled, you cannot bind addresses 0xFE or 0xFF 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. The FE and FF addresses are not components of the Allow/Prohibit Matrixes (as they are called in Brocade Network Advisor and Web Tools), because the Prohibit Dynamic Connectivity Masks (PDCMs) for the ports associated with FE and FF are defined architecturally and cannot be modified by the user. The port address name for the internal FE port can be read by the host, and corresponds to the switch name that is set for the switch. The switch name can be modified by the host, with the limitation that the host can write Extended Binary Coded Decimal Interchange Code (EBCDIC) characters that cannot be converted directly to ASCII for display in the GUI or CLI management interfaces. Such characters will be converted to dots (...) for these displays. Addresses FE and FF are not available for external connections. Before enabling FMS mode, you must manually disable physical ports associated with FE and FF if there is an active device connected to these ports. If there is an active device connected to either of these ports, Fabric OS will not enable FMS mode until either the port is disabled or the device is taken offline (logs out of the switch). If there is no active device connected, these ports will automatically disable when FMS enables. Because the ports associated with FE and FF are not available after enabling FMS mode, you should first move any fiber connected to either of them to another free port. For more information, refer to Disabling ports 0xFE and 0xFF on page 57. CUP configuration recommendations The following are recommendations for setting up FICON CUP: Device Type: 2032 Use device type 2032 as the CUP "UNIT" type for the CNTLUNIT and IODEVICE statements in the IOCDS or HCD. Although IBM has developed new machine types for switches, all Brocade FICON directors and switches regardless of model or manufacture should be configured as Paths Define at least two CHPIDs as paths to the CUP in the IOCDS Control Unit statement for the switch to ensure redundancy for host connectivity. RMF 74-7 statistics gathering So as not to overwhelm the CUP, the recommended best practice in a sysplex environment is to disable FICON switch statistics (RMF polling) on all but one host system that has in-band access to the CUP. If no FICON statement is specified, the system will gather switch statistics by default so FICON switch statistics should be disabled on all but the system intended to gather statistics. Missing Interrupt Handler (MIH) Set the MIHPTO to three minutes (180 seconds). NOTE Although 180 seconds should be the default value set on the switch when FMS mode 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 Administrator's Guide 55

56 FICON CUP zoning and PDCM considerations 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. Each port on the switch has its own PDCM that defines whether communication is allowed between that particular port and each of the other ports in the switch, including itself. The Allow/Prohibit Matrix presents a matrix that allows you to set and clear the PDCMs for all external ports. If there are any differences between restrictions set up with Brocade Advanced Zoning and PDCMs, the most restrictive rules are automatically applied. FMS mode must be enabled for the Allow/Prohibit Matrix to be operational, and there must be an active zoning configuration. Domain,Index (D,I) zoning is recommended for FICON, but is not specifically required. Hard-port or hard WWN zoning enforcement is required however. PDCMs will not be enforced on ports with session-based enforcement. If Brocade Advanced Zoning is in use, refer to the Fabric OS Administrator's Guide for more information on configuration. Port and switch naming standards for FMS mode The FICON management server and the FICON programming interface employ 8-bit EBCDIC characters in port address names and switch names. Fabric OS employs 7-bit characters. Therefore, when FMS mode is enabled, all characters greater than 0x40 and not equal to 0xFF; refer to the EBCDIC Code Page section) are allowed in port address names, and it is possible for a channel to set a name with nonprintable characters. If a name contains nonprintable characters, those characters are displayed as dots (...). The following characters are also displayed as dots: semicolon (;), comma (,), equal sign (=), and at sign (@). The port name for the CUP must be unique within the chassis. FICON CUP Fabric OS commands The table below summarizes the Fabric OS CLI commands that can be used for managing FICON fabrics. For detailed information on these commands, refer to the Fabric OS Command Reference. TABLE 6 Command Fabric OS commands related to FICON CUP Description ficoncupset fmsmode ficoncupset crp ficoncupset MIHPTO ficoncupset modereg ficoncupshow lp ficoncupshow fmsmode ficoncupshow modereg Sets FICON Management Server mode on or off for the switch. Sets the current reporting path (CRP). Sets the Missing Interrupt Handler Primary Timeout value. Sets the mode register bits for the switch. Displays the host logical path information for the CUP. Displays the FICON Management Server enabled or disabled state for the switch. Displays the mode register bit settings for the switch. 56 FICON Administrator's Guide

57 Configuring FICON CUP Configuring FICON CUP To set up FICON CUP, use the following procedure. 1. Connect to the switch and log in using an account assigned to the admin role. 2. Verify that the switch or director has been set up according to the instructions in Configuring switched point-to-point FICON on page 39 and, if in a cascaded topology, Configuring cascaded FICON on page For switches with at least 256 ports installed, use the portdisable command to disable ports 0xFE and 0xFF. Refer to Disabling ports 0xFE and 0xFF on page 57 for more information. 4. Enter the ficoncupshow fmsmodefmsmode command to verify if FMS mode is disabled. 5. Take the appropriate action based on whether FMS mode is enabled or disabled: If FMS mode is disabled, proceed to step 6. If FMS mode is enabled, disable it using the ficoncupset fmsmode disable command. ATTENTION If FMS mode is already enabled, disabling it may be disruptive to operations because ports that were previously prohibited from communicating will be allowed to do so because prohibits are no longer enforced.you must disable FMS mode to continue setting up CUP. 6. Install a CUP license on the switch. For more information on installing a license, refer to the Fabric OS Administrator's Guide. 7. Be sure that the switch meets requirements for a high-integrity fabric, and then enable High-Integrity Fabric (HIF) mode using the configure command. For details, refer to Meeting high-integrity fabric requirements on page 35. NOTE You must enable HIF mode to enable FMS mode. 8. Enter the ficoncupset modereg command to set the mode register bits. Refer to Mode register bit settings on page 62 for more information. 9. Verify with the systems programmer that the CUP ports, and the switches and directors, are defined properly in their IOCDS. FICON ports are defined as part of the sysgen process. The z/os systems programmer can verify if the CUP ports are defined properly. 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. After FMS mode has been successfully enabled, these two ports remain disabled and cannot be used either as an F_Port or an E_Port. Because these ports are not available after enabling FMS mode, you should first move any cable connected to either of them to another free port. You must manually disable ports associated with 0xFE and 0xFF to enable FMS mode only if there is an active device connected to these ports. Otherwise, if physical ports have been assigned these addresses by default prior to enabling FMS mode, they will be automatically disabled when FMS mode is enabled. FICON Administrator's Guide 57

58 Configuring FICON CUP in Virtual Fabrics On a Brocade DCX and DCX-4S Directors, when Virtual Fabrics is not enabled or addressing Mode 1 is not used, you must disable physical ports associated with addresses 0xFE and 0xFF (if ports were assigned by default) before enabling FMS mode. Note that physical ports associated with 0xFE and 0xFF may be different in logical switches using Mode 1 addressing. Disable these addresses manually if there is an active device attached. If an active device is not attached to the ports, they will be disabled automatically when you enable FMS mode. You can only disable ports if there is a card present in the slot. If FMS mode is enabled in a logical switch with Mode 2 addressing, the physical ports with addresses 0xFE and 0xFF are essentially wasted and may be used better elsewhere. This is the same for a switch with Mode 1 addressing where all available addresses are used, and thus no addresses are available for binding to these ports. On logical switches with Mode 1 addressing, such ports may be reclaimed for external connections by binding a new address to the port, if unused addresses are available. Ports that are disabled for having addresses "FE or "FF" when FMS mode is enabled are not eligible for port swapping. Configuring FICON CUP in Virtual Fabrics For details on FICON and FICON CUP in Virtual Fabrics, refer to FICON and FICON CUP in Virtual Fabrics on page 44. Determining physical port assignment The following steps help you locate the physical port from CUP_PortAddress. 1. Connect to the switch and log in using an account assigned to the admin role. 2. Set the context to the appropriate logical switch. 3. Enter the switchshow command. 4. Look for the PID in the Address column. 5. Read across to the Slot and Port columns to find the physical port number. For more information and example output from the switchshow command, refer to the Fabric OS Command Reference. 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 creates a FICON director. The FMS mode setting can be changed whether the switch is disabled or enabled. If FMS mode is changed while the switch is enabled, a device reset is performed for the control device and an RSCN is generated with PID 0xDDFE00, where 0xDD is the domain ID of the switch. The following are required on the switch to enable FMS mode: For Fabric OS 7.0 and later, a FICON CUP license. For Fabric OS 7.3 and later, High-Integrity Fabric (HIF) mode must also be enabled. Changing FMS mode from disabled to enabled triggers the following events: 58 FICON Administrator's Guide

59 Fabric OS command limitations and considerations Access to switch configuration parameters is serialized. The active CUP configuration data, including the following, is initialized according to the IPL file: Port and switch names Port "Block" and "Unblock" values PDCM values Brocade Advanced Zoning, if used, continues to be enforced. If there are any differences between the port-to-port connectivity restrictions defined by Brocade Advanced Zoning and those defined by PDCMs, the most restrictive rules are automatically applied. RSCNs are sent to devices if PDCM changes result in changes to connectivity between a set of ports that are zoned together. An RSCN for the CUP is generated to all mainframe FICON and FCP channels in the fabric. Changing FMS mode from enabled to disabled triggers the following events: A device reset is performed on the control device. Prohibits are no longer enforced. RSCNs may be generated to some devices if PDCM removal results in changes to connectivity between a set of ports that are zoned together. If a given port was set to "Block" or "Unblock," that port remains disabled or enabled. The switch interface for host in-band management is no longer enabled. An RSCN for the CUP is generated to all mainframe FICON and FCP channels in the fabric. NOTE FMS mode cannot be enabled in a Virtual Fabrics environment when a logical switch is using Mode 0 addressing. 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 on page 29. The following Fabric OS commands return a "switch busy" response if they are issued when the hostbased management application is performing a write operation. This prevents interference from outof-band management applications when a host-based management program is being used to administer the switch. bladeenable portname portshow portswap switchcfgpersistentdisable switchdisable switchenable switchname switchshow portdisable portenable You cannot use the portcfgpersistentenable and portcfgpersistentdisable commands to persistently enable and disable ports. Refer to Persistently enabling and disabling ports for CUP on page 65 for instructions. Specifying a range of ports for the portname command will fail except for the first port in the range. FMS mode does not permit multiple ports with the same name. FICON Administrator's Guide 59

60 Displaying FMS mode Displaying FMS mode Use the ficoncupshow fmsmode command to display the enabled or disabled state of FMS mode for the switch. Enabling FMS mode Before enabling FMS mode, you must enable attributes for high-integrity fabrics and HIF mode. For more information, refer to Meeting high-integrity fabric requirements on page Connect to the switch and log in using an account assigned to the admin role. 2. Enter ficoncupset fmsmode enable. 3. Enter the ficoncupshow fmsmode command to verify that FMS mode is enabled. Disabling FMS mode 1. Connect to the switch and log in using an account assigned to the admin role. 2. Enter ficoncupset fmsmode disable. 3. Enter the ficoncupshow fmsmode command to verify that FMS mode is disabled. FMS mode and FICON 0xFE or 0xFF ports 0xFE and 0xFF addresses 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 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. Refer to Disabling ports 0xFE and 0xFF on page 57 for more information. Enabling FMS mode disables all ports with 0xFE and 0xFF addresses. If you enable FMS mode, you will get port-disable messages for physical ports with 0xFE or 0xFF FICON addresses. You cannot enable FMS mode when physical ports have 0xFE or 0xFF FICON addresses with live devices connected. Port swapping and blade swapping cannot be performed on ports where FMS mode is enabled and ports have either 0xFF or 0xFE FICON addresses. Upgrade considerations Take the CUP offline before performing a firmware upgrade or downgrade operation. The upgrade can disrupt host communication with the CUP, especially for active RMF sessions. For Fabric OS 7.0 and later, a FICON CUP license is required to enable FMS mode. Consider the following when using FMS mode and upgrading from Fabric OS v6.4.0 to v7.0 or later: If using Fabric OS v6.4.0 and FMS mode is enabled, but a FICON CUP license was never installed: You can manage the port connectivity configuration through management applications such as Brocade Network Advisor and Web Tools. The In-band Management feature is not enabled. After a nondisruptive upgrade from Fabric OS v6.4.0 to v7.0.0 or later: 60 FICON Administrator's Guide

61 Port swap limitations You can manage the port connectivity configuration using management applications such as Brocade Network Advisor and Web Tools. The FICON CUP mode register is accessible through Web Tools. To enable In-band Management, you must install a FICON CUP license and disable and then re-enable FMS mode. If using Fabric OS v6.4 and FMS mode is enabled, but a FICON CUP license was installed and then removed: You can manage the port connectivity configuration through management applications such as Brocade Network Advisor and Web Tools. The FICON CUP mode register is accessible through Web Tools. Inband Management is enabled, providing you do not disable FMS mode, disable and then reenable the switch, or power-cycle the switch. After a nondisruptive upgrade from Fabric OS v6.4.0 to v7.0.0 or later, the following events occur: NOTE The following only occur on platforms released prior to Fabric OS v 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. In-band Management is enabled, provided you do not disable FMS mode, disable and then enable the switch, or power-cycle the switch. If you disable FMS, a FICON CUP license is required to re-enable the feature. Upgrading with FMS mode enabled from Fabric OS v7.2.1 or prior to v7.3.0 or later requires that the following attributes be configured. If FMS mode is enabled on the switch and these are not configured, the upgrade will fail. Refer to Administering FICON Fabrics on page 35 for configuration information. An insistent domain ID (IDID) A valid SCC_Policy (configured and activated) A Fabric Wide Consistency Policy => SCC:S (Strict mode) NOTE You enable the Fabric Wide Consistency Policy on the fabric once the switch joins the fabric. HIF mode enabled. Port swap limitations The following limitations apply to swapping ports or blades using CLI commands or Brocade Network Advisor options. Note that some of these constraints apply to logical switches in general, and are not necessarily limited to switches enabled for FMS mode. A port can be swapped with only one other port at a time. Ports cannot be swapped if one of the ports has a value of 0xFE or 0xFF in the Fibre Channel Port ID (FC ID) field. The logical switch addressing mode cannot be changed if the logical switch contains swapped ports. Logical switch configuration (LSCFG) operations cannot operate on swapped ports. You cannot swap ports that are in two different logical switches. Swapped ports cannot be moved out of a logical switch. The portaddress - -bind command is not allowed on swapped ports. The wwnaddress - -bind command is not recommended on swapped ports. FICON Administrator's Guide 61

62 Mode register bit settings Mode register bit settings A mode register controls the behavior of the switch with respect to CUP itself, and with respect to the behavior of other management interfaces. The FICON CUP mode register bits are described in the table below. TABLE 7 FICON CUP mode register bits ACP ASM DCAM HCP POSC UAM Alternate control prohibited. Because the Fabric OS CLI, Web Tools, and Brocade Network Advisor are considered to be switch consoles, this bit has no effect on their operations. Attempts to set CUP parameters through SNMP are denied when this bit is set on. The default setting is 1 (on). Active=Saved mode. When this bit is set on, all CUP configuration parameters are persistent, meaning that they will be saved in nonvolatile storage in the IPL file that is applied upon a cold reboot or a power cycle. The default setting is 1 (on). Switch clock alert mode. When this bit is set on, a warning is issued when the date, tsclockserver, or tstimezone commands are entered to set the time and date on the switch. The default setting is 0 (off). Host control prohibited. When this bit is set on, the host is not allowed to set CUP parameters. The default setting is 0 (off). Programmed offline state control. If the bit is set (=1), the command from the host sets the switch offline. If the bit is off (=0), the command from the host is rejected and the switch does not go offline. The default setting is 1 (on). User alert mode. When this bit is set on, a warning is issued when an action is attempted that will write CUP parameters on the switch; for example, changing the block/unblock state of a port, the portname, or a PDCM by means of the out of band interfaces. This bit can only be modified in-band by the host. The default setting is 0 (off). When the POSC bit=1, the FICON host is allowed to set the switch offline. The bit is set to 1 by default. If you do not want to allow the host to have permission to set the switch offline, the bit should be turned off. The state of this bit cannot be changed by the FICON host; it can only be changed through the command line. The ficoncupshow modereg command displays the mode register bit settings for the switch. A display of 0 indicates that the mode register bit is set to off; 1 indicates that the bit is set to on. To display the mode register bit HCP for the switch, enter the command as shown in the following example: switch:admin> ficoncupshow modereg HCP For more information on this command and an example of command output, refer to the Fabric OS Command Reference. FICON file access facility The FICON file access facility (FAF) stores configuration files. This includes the initial program load (IPL) and other configuration files. Fabric OS saves the IPL and all other configuration files on the switch. The FAF supports a maximum of 16 configuration files, including the IPL file. You can upload the configuration files saved on the switch to a management workstation using the configupload command. 62 FICON Administrator's Guide

63 Configuration files uploaded For more information on the configupload process, refer to the configuration file backup section in the Fabric OS Administrator's Guide. Configuration files uploaded When you execute the configupload command, all the files saved in the file access facility are uploaded to a management workstation. There is a section in the uploaded configuration file labeled [FICU SAVED FILES] where the files are stored in an encoded format. Configuration files downloaded with Active=Saved mode enabled When the Active=Saved mode register bit is set to on, the contents of existing files saved on the switch, also present in the FICON_CUP section of the configuration file, 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 file is not replaced because Active=Saved mode is enabled. A warning message is displayed in the event log to warn users that the IPL will not be overwritten. 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. When the Active=Saved mode register bit is set to off, the contents of existing files saved on the switch, also present in the [FICU SAVED FILES] section of the configuration file, are overwritten. The IPL is replaced because Active=Saved mode is disabled. Sample IOCP configuration file The channel subsystem controls communication between a configured channel, the control unit, and the device. The I/O Configuration Data Set (IOCDS) defines the channels, control units, and devices to the designated logical partitions (LPARs) within the server; this is generated using the Input/Output Configuration Program (IOCP). The IOCP statements are typically built using the hardware configuration definition (HCD). The interactive dialog is used to generate the Input/Output Definition File (IODF), invoke the IOCP, and subsequently build the production IOCDS. Each FICON switch in a fabric must have a unique domain ID and a unique switch ID. The switch ID used in the IOCP definitions can be any value between x00 to xff. The domain ID range for switches is hex x01 to xef or decimal 1 to 239. When defining the switch IDs in the IOCP definitions, ensure that you use values within the FICON switch s range. The switch ID must be assigned by the user and must be unique within the scope of the definitions (IOCP and HCD). The domain ID is assigned by the manufacturer and can be customized to a different value. It must be unique within the fabric. Brocade recommends that the switch ID (IOCP or HCD) be set to the same value as the domain ID of the FICON switch, which is defined to the switch at installation time. This simplifies the configuration and reduces confusion by having a common designation across all definitions. For more information on switch numbering, refer to the IBM Redbook FICON Planning and Implementation Guide (SG ). FICON Administrator's Guide 63

64 Considerations for setting mode register bits In the following sample IOCP configuration file, the UNIT value for FICON CUP definitions is 2032 for any FICON switch regardless of vendor or platform. All Brocade switches require UNIT=2032 for the CUP definition. All domain IDs are specified in hex values in the IOCP (and not in decimal values). * * Brocade Domain_ID=0x3c0000 * CNTLUNIT CUNUMBR=0D8,UNITADD=00,UNIT=2032, PATH=(50,51), LINK=(60FE,60FE) IODEVICE ADDRESS=(0D8,1),CUNUMBR=0D8,UNIT=2032,STADET=Y,UNITADD=00 * CNTLUNIT CUNUMBR=0D9,UNITADD=00,UNIT=2032, PATH=(8A,8B), LINK=(22FE,22FE) IODEVICE ADDRESS=(0D9,1),CUNUMBR=0D9,UNIT=2032,STADET=Y,UNITADD=00 * * Brocade Domain_ID=0x * * CNTLUNIT CUNUMBR=0DB,UNITADD=00,UNIT=2032, PATH=(5A,5B), LINK=(25FE,25FE) IODEVICE ADDRESS=(0DB,1),CUNUMBR=0DB,UNIT=2032,STADET=Y,UNITADD=00 * * Considerations for setting 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 cycles; the UAM bit is reset to 0 following a power-on. Mode register bits can be changed when the switch is offline or online. If the ACP or HCP bits are changed when the switch is online, they will take effect any time between the completion of the current command and the end of the CCW command chain (or the next alternate manager operation). Setting the mode register bits Perform the following steps to set mode register bits: 1. Connect to the switch and log in using an account assigned to the admin role. 2. Enter the ficoncupset modereg command to set the FICON CUP mode register bits for the local switch. Example of setting the mode register bit HCP to off switch:admin> ficoncupset modereg HCP 0 Example of setting the mode register bit ACP to on switch:admin> ficoncupset modereg ACP 1 64 FICON Administrator's Guide

65 Setting the MIHPTO value Setting the MIHPTO value The missing interrupt handler primary timeout (MIHPTO) value determines how long the channel will wait before timing out an expected response from the CUP. This value is part of the data returned to the host when it reads the configuration data, but the host is under no obligation to adhere to this value. The actual value that the host will use before detecting a timeout can be set by the system programmer (overriding the value returned by the switch). Use the ficoncupset MIHPTO command to increase, decrease, or display the MIHPTO value that the CUP returns to the host when configuration data is read. Changing the MIHPTO value requires that the CUP control device be varied offline from the host, as the host will not automatically be notified when the value is changed. The host will normally read the new value using the Read Configuration Data command when the CUP is varied back online. The MIHPTO setting will persist across switch reboots, power on reset (POR), and failovers. Setting this value to the upper end of the time range will allow the CUP more time to process requests during intervals of peak usage, without causing the host to detect timeouts. It is recommended that the value be set to 180 seconds (default). Complete the following steps to set the MIHPTO value. 1. Connect to the switch and log in using an account assigned to the admin role. 2. Enter the ficoncupset MIHPTO command and set the value from 15 through 600. 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. If the ASM bit is set off (0), enter the ficoncupset modereg asm 1 command to set the bit to on. For more information on this command and an example of command output, refer to the Fabric OS Command Reference. 5. Use the portenable and portdisable commands to enable and disable ports as necessary. The ports remain enabled or disabled after a switch reboot. switch:admin> portenable 1/1 Refer to Disabling and enabling ports - persistent states on page 48 for more information on enabling and disabling ports and persistent states. FICON Administrator's Guide 65

66 Persistently enabling and disabling ports for CUP 66 FICON Administrator's Guide

67 Administering FICON Extension Services Platforms supporting FICON extension over IP FICON emulation overview FCIP configuration requirements for FICON extension...72 Configuration requirements for switches and directors Configuring FICON emulation Modifying FICON emulation Displaying FICON emulation performance statistics...75 Platforms supporting FICON extension over IP FICON extension over IP is supported between Brocade 7800 Extension Switches and FX8-24 blades. FICON on Brocade 7840 Extension Switches is supported, but these switches can only connect to Brocade 7840 switches. The Brocade 7800 switch has 16 Fibre Channel ports and six physical GbE ports. The FX8-24 blade has 12 Fibre Channel ports, ten 1 GbE ports, and two 10 GbE ports. The Brocade 7840 switch has 24 physical Fibre Channel ports, two 40 GbE ports, and 16 1/10 GbE ports. FICON emulation overview FICON emulation supports FICON traffic over IP WANs using FCIP as the underlying protocol. FICON emulation can be extended to support performance enhancements for specific applications through use of the following licensed features: IBM z/os Global Mirror emulation (formerly extended Remote Copy or XRC) FICON tape emulation (tape read and write pipelining) Brocade extension products use the following licenses: Advanced Accelerator for FICON (FTR_AFA) Allows interoperability for the following features and products: Prizm FICON to ESCON converter and ESBT Bus/Tag Interface Module for Prizm from Optica Technologies, Inc. These products allow emulation and extended distance support for bus and tag tapes and printers, such as 3203, 3211, 3800, 3900, 4248, and intelligent printer data stream (IPDS) models. Write and read tape pipelining Teradata emulation IBM z/os Global Mirror emulation This license contains the following options: FICON Administrator's Guide 67

68 IBM z/os Global Mirror emulation Capacity 1 Consumed 1 Configured Blade Slots 1 This is a slot-based license for extension switches and blades. Advanced Extension (FTR_AE) Required for multiple-circuit tunnels, FCIP Trunking, Adaptive Rate Limiting, and other FCIP features. Advanced Extension is not required for FICON Acceleration features, but multiple circuits could be used in a FICON emulation environment. This is a slot-based license for extension switches and blades. This license contains the following options: Capacity 1 Consumed 1 Configured Blade Slots 1 ATTENTION Use the licenseshow command to verify the licenses are installed on the hardware at both ends of the FCIP tunnel. For slot-based licenses, use the licenseslotcfg --show command to display all slotbased licenses in a chassis. For more information on licensing, such as licensing required per product, refer to the Fabric OS Software Licensing Guide. IBM z/os Global Mirror emulation The IBM z/os Global Mirror emulation (formerly extended Remote Copy or XRC) application is a direct-attached storage device (DASD) application that implements asynchronous disk mirroring, as supported by the disk hardware architecture and a host software component called the System Data Mover (SDM). Within this application, a specific application channel program invokes a wellconstrained type of channel program called a Read Record Set (RRS) channel program. This channel program is used to read only updates to disk volumes (record sets) after they have been brought into synchronization with the aim of writing only record updates to a mirrored volume. The RRS channel program accesses primary volumes from a remote host for the purpose of reading these record sets (updates) supported by IBM z/os Global Mirror emulation. The emulation feature thus allows the primary volume to be located at a distance from its mirrored secondary without encountering performance degradation associated with IU pacing. 68 FICON Administrator's Guide

69 Tape emulation FIGURE 17 IBM z/os Global Mirror emulation The figure above shows how the primary volume and the secondary mirrored volume may be geographically distant across an IP WAN. Updates to the primary disk volumes are completed by the production applications and then staged in a control unit cache to be read by SDM. SDM then writes the updates to the secondary volumes. The latency introduced by greater distance creates delays in anticipated responses to certain commands. The FICON IU pacing mechanism may interpret delays as an indication of a large data transfer that could monopolize a shared resource and react by throttling the I/O. IBM z/os Global Mirror emulation provides local responses to remote hosts, eliminating distancerelated delays. You can use the Brocade 7800 switch, Brocade 7840 switch, or an FX8-24 blade with FICON emulation. For information on configuring IBM z/os Global Mirror emulation, refer to Configuring FICON emulation on page 74. For information on displaying IBM z/os Global Mirror emulation status and statistics, refer to Displaying FICON emulation performance statistics on page 75. For z/os Global Mirror implementations with cascaded FICON, it is recommended that device based routing (DBR) be used for the routing policy on the ISLs instead of PBR. Tape emulation Tape emulation (also called tape pipelining) refers to the concept of maintaining a series of I/O operations across a host-wan-device environment and should not be confused with the normal FICON streaming of CCWs and data in a single command chain. Normally, tape access methods can be expected to read data sequentially until they reach the end-of-file delimiters (tape marks) or to write data sequentially until either the data set is closed or an end-of-tape condition occurs (multi-volume file). The emulation design strategy attempts to optimize performance for sequential reads and writes, while accommodating any other nonconforming conditions in a lower performance non-emulating frame shuttle. Because write operations can be expected to comprise the larger percentage of I/O operations for tape devices (for archival purposes), they are addressed first. For information on configuring tape emulation, refer to Configuring FICON emulation on page 74. For information on displaying tape emulation status and statistics, refer to Displaying FICON emulation performance statistics on page 75. FICON Administrator's Guide 69

70 Tape Write Pipelining Tape Write Pipelining FICON Tape Write Pipelining improves performance for a variety of applications when writing to tape over extended distances. FICON Tape Write Pipelining locally acknowledges write data records, enabling the host to generate more records while previous records are in transit across the IP WAN. If an exception status is received from the device, the writing of data and emulation is terminated. FIGURE 18 Tape Write Pipelining Tape Read Pipelining FICON Tape Read Pipelining improves performance for certain applications when reading from FICON tape over extended distances. FICON Tape Read Pipelining reads data on the tape directly from the tape device. Reading of the tape continues until a threshold is reached. The buffered data is forwarded to the host in response to requests from the host. When the host sends the status accept frame indicating that the data was delivered, the read processing on the device side credits the pipeline and requests more data from the tape. If an exception status is received from the device, the reading of data and emulation is terminated. 70 FICON Administrator's Guide

71 FICON and ESCON conversion support FIGURE 19 Tape Read Pipelining FICON and ESCON conversion support Brocade extension switches and blades can operate with the Prizm FICON to ESCON converter and ESBT Bus/Tag Interface Module for Prizm from Optica Technologies, Inc. This allows FICON tape emulation when connecting to ESCON and to bus and tag devices including 3480, 3490, and 3590 controllers. Discovery of these devices is automatic when FICON emulation is enabled on an FCIP tunnel. Printer emulation Brocade extension switches and blades can operate with a Prizm FICON to ESCON converter and an ESBT Bus/Tag Interface Module for Prizm from Optica Technologies, Inc. This allows FICON printer emulation when connecting to printers such as the 1043, 3203, 3211, 3800, 4245, 4248, 6262, Xerox Printer Access Facility (XPAF), and Intelligent Printer Data Stream (IPDS) models. Discovery of these devices is automatic when FICON emulation is enabled on an FCIP tunnel. For printer emulation, basic write streams are emulated to help resolve link latency resulting from channel programming and associated FICON protocols. Because most supported printers will be connected through the Prizm FICON to ESCON converter or ESBT Bus/Tag Interface Module, resolving latency on the WAN is not required. The bottleneck will be the remote channel connection where it is more important to have outstanding commands queued. Basic read commands known to be part of the write command chain, typically those that read printer page counters, will be handled locally without waiting for the actual read data from the device. This emulation provides the following benefits: FICON Administrator's Guide 71

72 Teradata emulation Optimized performance for FICON printers over distance when printers are extended through an FCIP tunnel with FICON emulation. 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 74. For information on displaying printer emulation status and statistics, refer to Displaying FICON emulation performance statistics on page 75. 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 74. For information on displaying Teradata emulation status and statistics, refer to Displaying FICON emulation performance statistics on page 75. 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 Fabric OS Extension Administrator's Guide for information about configuring FCIP interfaces, tunnels, and circuits. Configuration requirements for switches and directors Consider these configuration issues when an extension switch or blade is connected to a switch or director in a FICON configuration: If you are creating a cascaded configuration (connecting two switches or directors 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. 72 FICON Administrator's Guide

73 High-integrity fabric requirements for cascaded configurations FICON networks with FCIP emulating and non-emulating tunnels do not support Dynamic Path Selection (aptpolicy 3) configurations. When running FICON emulation features over an FCIP tunnel, it is highly recommended that both switches providing the FCIP tunnel use the same Fabric OS release level. High-integrity fabric requirements for cascaded configurations You can use extended FICON connections between or through Brocade extension switches or blades to create a cascaded FICON switched configuration. The fabric must be set up to provide a secure, or high integrity, fabric to enable this configuration to operate in an IBM environment. Refer to Meeting high-integrity fabric requirements on page 35 for an explanation of these requirements. FICON emulation requirement for a determinate path FICON emulation processing creates FICON commands and responses on extended CHPIDs, and intercepts all exchanges between a channel and a CU. For FICON emulation processing to function correctly, all the exchanges between a channel and a CU must take a single tunnel path. There are two ways to ensure a determinate path for FICON commands and responses: Define only one FCIP tunnel between sites. When multiple FICON emulation FCIP tunnels are required between a pair of chassis, define a new logical switch pair (one logical switch in each chassis) for each tunnel. The logical switches and the FCIP tunnel in those logical switches will provide a determinant path for all FICON sequences between the host and device ports in that logical switch pair. When it is not possible to create logical switches, use Traffic Isolation Zones (TI Zones) to define the host and device ports that traverse each required FCIP tunnel. FCIP tunnel between sites Brocade extension switches and blades use FCIP trunking features to overcome the limitation of one Ethernet interface, one IP address, and one FCIP tunnel. In Fabric OS v6.3 and later, an FCIP tunnel is created with multiple FCIP circuits over different IP interfaces to provide WAN load balancing and failover recovery in the event of a limited WAN outage. This provides a highly redundant WAN configuration for all FICON or FCP emulation technologies with Fabric OS. The figure below shows that a tunnel can have up to four circuits per GbE port. FIGURE 20 FCIP tunnel and circuits FICON Administrator's Guide 73

74 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 67. ATTENTION Make sure both ends of the tunnel match before bringing it up or the tunnel will not form. 1. Verify that the following ports are opened in the IP network for FCIP: TCP FC Class F frames TCP FC Class 2 and 3 frames TCP Brocade proprietary IP path performance utility (ipperf) IP protocol 6--Transmission Control Protocol IP protocol 108--IP Payload Compression Protocol (IPComp) 2. Verify that the firmware is Fabric OS v6.1.0e or later using the firmwareshow command. 3. Verify the correct licenses are installed using the licenseshow command. You can verify all slotbased licenses in a chassis using the licenseslotcfg --show command. 4. Verify the switches have been set up according to the instructions in Configuring switched point-topoint FICON on page 39 and Configuring cascaded FICON on page Configure the FCIP tunnel according to the Fabric OS Extension Administrator's Guide. 6. Enable compression on the FCIP tunnel. 7. Configure FICON emulation on the tunnel that is solution-specific. Refer to Configuration examples on page If you have more than one tunnel being configured, take the following actions: If there is more then one tunnel to the same destination and their tunnel commit rates are different, configure the link cost values the same. Configure TI Zones ensuring that if there are multiple E_Ports of different link costs, from one switch to another switch within TI Zones, configure the link cost values to be the same. Configuration examples You can configure FICON emulation with such features as Teradata read, Teradata write, printer emulation, tape write pipelining, tape read pipelining, TIN/TIR, device level ACK, and IBM z/os Global Mirror (formerly XRC) emulation enabled. Following are examples for enabling IBM z/os Global Mirror, Teradata emulation, tape read and write pipelining, and printer emulation. portcfg fciptunnel 23 modify --ficon-xrc 1 portcfg fciptunnel 23 modify --ficon-tera-read ficon-tera-write 1 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 -F or --ficon option. Following are two examples: 74 FICON Administrator's Guide

75 Displaying FICON emulation configuration values To create a empty tunnel as a FICON FCIP tunnel, use the following command: portcfg fciptunnel 1/17 create -F -c 1 To modify a tunnel to be FICON enabled and with hardware compression enabled, use the following command: portcfg fciptunnel 1/17 modify -c 1 -F 1 Displaying FICON emulation configuration values For Brocade extension switches or blades, use the portshow fciptunnel command to display FICON configuration values. Command output shows which emulation features are enabled or disabled and displays related emulation parameters for each tunnel. For more information, refer to Displaying FICON emulation performance statistics on page 75. Modifying FICON emulation FICON emulation can be enabled on a per-fcip tunnel basis. For Brocade extension switches and blades, use the portcfg fciptunnel command to make modifications to the FICON emulation feature. For details on command usage, refer to the Fabric OS Command Reference. ATTENTION You must bring the FCIP tunnel down in order to make changes. The following process is disruptive to all traffic on the tunnel. 1. Connect to the switches at both ends of the FCIP tunnel and log in using an account assigned to the admin role. 2. Disable the FCIP tunnel at both ends where FICON emulation is enabled. 3. Use the portcfg fciptunnel modify command for the Brocade extension switches and blades. 4. Make matching FICON emulation changes to both ends of the tunnel. 5. Enable the FCIP tunnel. Displaying FICON emulation performance statistics You can use the portshow command to view performance statistics and monitor the behavior of FICON emulation. You do not need to disable any FICON emulation feature to display statistics. 1. Connect to the switch and log in using an account assigned to the admin role. 2. Use the portshow xtun command to display the statistics for the Brocade extension switches and blades. Refer to FICON emulation monitoring on page 76, Options for displaying statistics on page 77, and the Fabric OS Command Reference for information on command formats that you can use to display various FICON statistics. FICON Administrator's Guide 75

76 FICON emulation monitoring FICON emulation monitoring Use the -emul option for the portshow xtun command to display FICON emulation statistics. The syntax for this command is portshow xtun [slot/]ve_port -ficon -emul. The -emul option displays statistics and status for printer, Teradata, tape, and IBM z/os Global Mirror emulation. IBM z/os Global Mirror emulation (formerly extended Remote Copy or XRC) and tape statistics are presented differently in output formats for the -emul option. The following elements are common to both tape and IBM z/os Global Mirror emulation outputs (refer to Emulation statistics examples on page 76 for an illustration of actual tape and XRC emulation statistics output). FDCB Ptr Path A pointer to the FICON Device Control Block. Support personnel may use this pointer. The device path, in the format VE-HD-HP-DD-DP-LP-CU-DV: where VE is the internal VE_Port number. HD is the hex value for the Host Domain (the entry domain for this host port into the fabric). HP is the hex value for the Host Port (the entry port of this host connection into the fabric). DD is the hex value for the Device Domain (the entry domain for this device into the fabric). DP is the hex value for the Device Port (the entry port for this device connection into the fabric). LP is the Logical Partition (LPAR) value for the host accessing the specific device. CU is the Control Unit number (CUADDR) for the specific FICON connection. DV is the Device Number of this FICON connected device. For example, the value breaks down as follows. VE HD HP DD DP LP CU DV State A value of zero indicates emulation is idle. Any non-zero value indicates emulation is active. Emulation statistics examples The following is a tape statistics output example for the Brocade 7800 switch and 7840 extension switch. root> portshow xtun 17 -ficon -emultape TAPE EMULATION STATS FDCB Ptr Path H State Emul Emul Rtry Emulated Emulated RdAvg Emulated WtAvg (0x) (0x) D Pipe Q'd Qd Tape Ops Read CCWs Size Write CCWs Size x04100F H 0x3C 0x x04100F H 0x3C 0x12 006C x041013BC H 0x00 N/A x C H 0x3C 0x12 006C x04100F H 0x3C 0x x H 0x3C 0x x041012DC H 0x3C 0x12 006C x04100D H 0x3C 0x12 006C x H 0x00 N/A FICON Administrator's Guide

77 Options for displaying statistics 0x041010B H 0x00 N/A x041011C A H 0x00 N/A x04100A B H 0x3C 0x12 006C x04100F C H 0x3C 0x12 006C x D H 0x00 N/A x04100FA E H 0x3C 0x12 006C x041008F F H 0x00 N/A x04100FA H 0x00 N/A x H 0x00 N/A x04100ED B H 0x00 N/A The following is an IBM z/os Global Mirror output example. root> portshow xtun 17 -ficon -emulxrc XRC EMULATION STATS FDCB Ptr Path H State Cmds Cmd Data Data Emulated Avg RRS RRS Large (0x) (0x) D Qd Max Qd Max RRS Ops RRS TLF Read Chains x04100D H 0x F x04100DA B H 0x F x041008FB H 0x x04100ED B H 0x x04100DD H 0x x04100E H 0x x04100E H 0x x04100ECC F H 0x Options for displaying statistics Use the portshow xtun [slot/]ve_port -ficon -stats command to display status, performance statistics, and other statistics for tape, Teradata, IBM z/os Global Mirror, and printer emulation on Brocade extension switches and blades. Refer to the table below for a description of command formats to achieve various outputs. TABLE 8 FICON emulation statistics commands Command portshow xtun slot/ve_port ve_port -ficon -emul portshow xtun slot/ve_port -ficon -emulxrc portshow xtun slot/ve_port -ficon -emultape portshow xtun slot/ve_port -ficon -emulprint portshow xtun slot/ve_port -ficon -emultera portshow xtun slot/ve_port -ficon -stats portshow xtun slot/ve_port -ficon -fdcb control block portshow xtun ve_port ficon -teraperf Output display Statistics and status for printer, Teradata, tape, and IBM z/os Global Mirror (XRC) emulation. FICON IBM z/os Global Mirror emulation statistics and status. FICON tape emulation statistics and status. FICON printer emulation statistics and status. FICON Teradata emulation statistics and status. General statistics, including those for Teradata, XRC, tape emulation, and FICON idle status acceptance. Teradata, tape, IBM z/os Global Mirror, or printer emulation statistics, including the device extension of the FDCB for a specified Device Control Block. Teradata performance statistics. FICON Administrator's Guide 77

78 Administering FICON Extension Services TABLE 8 Command FICON emulation statistics commands (Continued) Output display portshow xtun ve_port -ficon -tapeperf portshow xtun ve_port -ficon -xrcperf portshow xtun ve_port -ficon -printperf FICON tape pipelining performance statistics. IBM z/os Global Mirror performance statistics. Printer emulation processing statistics. Refer to the portshow command section of the Fabric OS Command Reference for more information on these commands. 78 FICON Administrator's Guide

79 Maintaining and Troubleshooting FICON Firmware management in a FICON environment Configuration restoration in a FICON environment Traffic Isolation Zoning...81 Monitoring and Alerting Policy Suite Port fencing FICON information Swapping port area IDs...91 Blade swapping...91 Common FICON issues Troubleshooting FICON Troubleshooting FICON CUP...97 Troubleshooting NPIV Firmware management in a FICON environment You can use either the CLI or Brocade Network Advisor to upgrade or downgrade your Fabric OS. Registered users can log in on the Brocade website at and follow the links for downloads to access firmware. Firmware is downloaded in a.gz or.zip file. Brocade Network Advisor contains built-in intelligence that unbundles the necessary files, making it unnecessary to unbundle a package. With Web Tools or the CLI, it is necessary to decompress or extract the files from the package first. For more information, refer to the firmware download process overview in the Fabric OS Administrator's Guide. Upgrade and downgrade considerations Consider the following when upgrading and downgrading firmware: Concurrent upgrades are generally supported from one major release level to the next, for example, Fabric OS v7.0.0 to v As a precaution, always read the appropriate section in the Brocade Fabric OS Release Notes before upgrading or downgrading firmware. Firmware may need to be upgraded in multiple steps. Consult the Release Notes for details. When downgrading firmware, turn off and disable all features not supported in the final release. For more information on the firmware download process and considerations for FICON CUP environments, refer to the firmware download process overview section of the Fabric OS Administrator's Guide. Firmware download disruption Downloading new firmware is not a disruptive process except for the following cases: FICON Administrator's Guide 79

80 Non-disruptive firmware upload and download During the firmware download process, a failover to the backup processor occurs. Any outstanding CUP commands are lost which results 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. All firmware downloads cause an I/O disruption when the new code is activated on the Brocade 7800 switch and FX8-24 blade. However, the Brocade 7840 switch supports the FCIP Hot Code Load (HCL) feature which allows firmware downloads without I/O disruption. Non-disruptive firmware upload and download All systems maintain a primary and a secondary partition of nonvolatile storage areas. The following overview of the firmware download process illustrates the use of the two partitions: 1. The firmware is downloaded to the secondary partition. 2. The current secondary and primary partitions are swapped. 3. The CP then reboots. In dual-cp systems (Brocade DCX and DCX 8510 FICON directors), the backup CP is rebooted with the new firmware and the HA failover is automatically invoked. 4. Once rebooted, the primary code image is copied to the secondary. Considerations for fixed-port switches Unlike director-class products, fixed-port switches have only one control processor (CP) so they behave differently during Fabric OS hot code upgrades. This can impact FICON operations if best practices are not followed. During the code upload process, there is a period of time when the CP is busy rebooting the operating system and re-initializing Fabric OS, and CP is not available to respond to CPU-targeted queries or frames. For dual-cp products, this "busy" time is a couple of seconds (the time it takes for mastership to change), and is non-disruptive. For single-cp fixed-port switches, however, the "busy" period can last a minute or two. During this time, data traffic continues to flow uninterrupted, unless a response from the CP is required. If a response from the CP is required, for path and device validation for instance, Interface Control Checks (IFCCs) are possible. Any IFCCs should be recovered automatically by the IBM z Systems host, with no required user action. This does not mean that switches are not appropriate for FICON. Fully certified FICON switch deployments will continue to be sold and supported. It is important to follow the best practices of performing the firmware upgrade during scheduled maintenance windows when traffic is minimized, IFCCs can be tolerated, and the CUP is turned off. Configuration restoration in a FICON environment The following table describes the behavior of the configupload and configdownload commands and IPL file function when the ASM bit is set on or off. In general, 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. 80 FICON Administrator's Guide

81 Traffic Isolation Zoning TABLE 9 Backup and restore in a FICON CUP environment ASM bit Command Description on or off configupload All the files saved in the file access facility are uploaded to the management workstation. A section in the uploaded configuration file labeled FICON_CUP is in an encoded format. on configdownload Files saved on the switch that are also present in the FICON_CUP section of the configuration file are overwritten. Files in the FICON section of the configuration file that are not currently present on the switch are saved. off configdownload Files saved on the switch that are also present in the FICON_CUP section of the configuration file are overwritten. Files in the FICON section of the configuration file that are not currently present on the switch are saved. The IPL file is replaced. The Active Configuration is reestablished with values that may be different from what is in IPL file. Traffic Isolation Zoning Traffic Isolation (TI) Zoning allows you to specify dedicated data paths to control traffic flowing from a specific set of source ports (N_Ports). TI Zoning has the following benefits: Separates direct attached storage device (DASD) and tape traffic. Selects traffic for diverse ISL routes (typical of dual fiber networks). In conjunction with long-distance channel extension equipment (FICON Acceleration), guarantees bandwidth for certain mission-critical data. Creating logical switches is preferred over creating TI Zones for FICON emulation configurations. Logical switches can be created easily and they naturally separate disk and tape traffic to different tunnels and network bandwidth. Fabric OS v6.2.0 or later is required for TI Zoning in a FICON fabric. For more information on TI Zoning, refer to the Fabric OS Administrator's Guide. FICON Administrator's Guide 81

82 Determining ports for the TI Zone NOTE Session-based zoning enforcement is not recommended on a FICON switch. For more information on session-based zoning enforcement, refer to the Fabric OS Administrator s Guide. Determining ports for the TI Zone To determine source ports and paths for specific devices, use the MVS display command. The following example displays paths to device 1002 and where the device is connected: D M=DEV(1002) Response is: DEVICE 1002 STATUS=OFFLINE CHP AC AD AE AF ENTRY LINK ADDRESS DEST LINK ADDRESS 66FE 66FE 66FE 66FE \ //CUP has link address = DDFE, where DD= domain ID of switch// PATH ONLINE Y Y Y Y CHP PHYSICALLY ONLINE Y Y Y Y PATH OPERATIONAL Y Y Y Y MANAGED N N N N CU NUMBER MAXIMUM MANAGED CHPID(S) ALLOWED: 0 DESTINATION CU LOGICAL ADDRESS = 00 SCP CU ND = SLKWRM.DCX.BRD.CA.4FT00X39C19A.0001 SCP TOKEN NED = SLKWRM.DCX.BRD.CA.4FT00X39C19A.0000 SCP DEVICE NED = SLKWRM.DCX.BRD.CA.4FT00X39C19A.0000 Enhanced TI Zoning Enhanced Traffic Isolation Zones allow you to specify a preferred and exclusive path through a cascaded fabric for a particular flow by defining a set of devices or ports to appear in more than one Enhanced TI Zone. A preferred path is one that has failover enabled and an exclusive path has failover disabled. An exclusive path in the following topologies is beneficial as it limits the number of hops between switches: Triangular System Data Mover Emulation Enhanced TI Zoning for the three previously listed topologies is available only on the following platforms running Fabric OS v6.4.0 or later: Brocade 5100 Brocade 5300 Brocade 7800 Brocade 7840 Brocade 6510 Brocade DCX Brocade DCX Brocade DCX Brocade DCX-4S 82 FICON Administrator's Guide

83 Triangular topology Triangular topology The triangular topology shown in the figure below is a common FICON deployment for managing data center recovery functions. In this topology, a switch is located in each of three sites and connected to the other two forming a triangle. In most environments, the purpose of this configuration is to give the host application the ability to connect to storage media at the other two sites, which allows it to recover from an outage at either site. Meanwhile, the storage systems constantly synchronize between the two storage sites. FIGURE 21 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. To get around the multiple-hop issue, use Enhanced TI Zoning to prohibit the connection between E_Ports on the switches. For this setup you must define a device in two zones with failover disabled. FICON Administrator's Guide 83

84 Maintaining and Troubleshooting FICON The figure below shows that the setup allows a source device to reach two separate destinations over exclusive, one-hop paths, while preventing the source device from taking the two-hop path in the event of a failure. FIGURE 22 Triangular topology with Enhanced TI Zones The preceding figure 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. The channel can reach CU A only over ISL 1 and CU B only over ISL 2. If either ISL should fail, connectivity to the destination with the failed ISL is prevented because the exclusive path has failed. 84 FICON Administrator's Guide

85 System Data Mover topology System Data Mover topology The figure below 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, DASD storage is used to support fast access for production applications. In the backup site, tape storage is used to support archival operations for system restoration. FIGURE 23 Typical System Data Mover topology The host in the production site operates the SDM application that reads data from the DASD and writes it to the remote tape. The path to the remote site is required to be isolated to support the bandwidth requirements needed to write the data to the remote tape. The host in the backup site needs access to the DASD in the production site to support a hot recovery scenario in the event the production host goes down. Supporting these two functions requires the ability to define overlapping zones that isolate the tape traffic from the DASD traffic and allow local access to the DASD ports. FICON Administrator's Guide 85

86 Maintaining and Troubleshooting FICON FIGURE 24 System Data Mover topology using Enhanced TI Zones The figure above shows the following Enhanced TI Zone 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. The production channels can access the local DASD and use an exclusive path to write data to the remote tape. The remote channels can access the remote tape and use an exclusive path to write data to the production DASD. In both cases, the production tape traffic is excluded from intruding on the backup DASD traffic and vice versa. 86 FICON Administrator's Guide

87 Monitoring and Alerting Policy Suite Monitoring and Alerting Policy Suite The Monitoring and Alerting Policy Suite (MAPS) is an optional storage area network (SAN) health monitor supported on all switches running Fabric OS MAPS allows you to enable each switch to constantly monitor itself for potential faults and automatically alerts you to problems before they become costly failures. MAPS tracks a variety of SAN fabric metrics and events. Monitoring fabric-wide events, ports, and environmental parameters enables early fault detection and isolation as well as performance measurements. MAPS provides the following set of predefined monitoring policies that allow you to immediately use MAPS on activation: dflt_conservative_policy dflt_moderate_policy dflt_aggressive_policy It is recommended that all IBM z Systems customers enable MAPS after upgrading to Fabric OS version supporting MAPS and use the default aggressive policy (dflt_aggressive_policy). This policy contains rules with very strict thresholds. For details on enabling MAPS and monitoring policies, refer to the Monitoring and Alerting Policy Suite Administrator's Guide. Port fencing Occasionally, bad optics and cables can cause errors to occur at such a rapid rate that error processing and RSCN transmission and processing results in fabric performance problems. Port fencing allows you 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. It is recommended that the port decommissioning/recommissioning feature be used to the maximum extent possible in place of port fencing. Defining port fencing The following overview defines port fencing. 1. (Optional) Clear all alarms. 2. Define threshold levels. 3. Define alarm action. 4. Activate alarming. NOTE Establish a Telnet session with a tool such as PuTTy that allows the columns to be increased. This is because some of the displays use more than the standard 80 columns that programs such as HyperTerminal support. The recommended number of columns is 120. FICON Administrator's Guide 87

88 Settings for FICON environments Settings for FICON environments For typical FICON environments, port fencing is usually only set for CRC errors and Invalid Words. The default of 1,000 errors per minute is a little high for CRC errors and Invalid Words. A more common setting is 50 errors per minute. This is high enough to ignore occasional errors and transient errors due to recabling but low enough to stop problematic optics from causing fabric issues. By default, the alarms are set to fence the port, log an alert, send an message, and set an SNMP trap. In most FICON environments, only fencing the port and logging the alert are desired. The following are the default thresholds: Low - 0 High - 1,000 errors per minute FICON information You can display link incidents, registered listeners, node identification data, and FRU failures, as described in the following sections. Link incidents The Registered Link Incident Report (RLIR) ELS contains the link incident information sent to a listener N_Port. 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 rlirrlir 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. The tag field is a concatenation of the switch domain ID and port number, in hexadecimal format. The following example shows the top portion of command output which shows a link incident for the switch port at domain ID 120, port 93 (785d in hex): switch:admin> ficonshow rlir { {Fmt Type PID Port Incident Count TS Format Time Stamp 0x18 F 785d Time server Thu Apr 22 09:13: Port Status: Link not operational Link Failure Type: Loss of signal or synchronization Registered Port WWN Registered Node WWN Flag Node Parameters 50:05:07:64:01:40:16:03 50:05:07:64:00:c1:69:ca 0x10 0x (output truncated) For complete examples of output from this command, refer to the ficonshow command section of the Fabric OS Command Reference. 88 FICON Administrator's Guide

89 Registered listeners Registered listeners To display registered listeners for link incidents, connect to the switch, log in as user, and enter one of the following commands: For the local switch: ficonshow lirr For all switches defined in the fabric: ficonshow lirr fabric For an example of local Link Incident Record Registration (LIRR) database output, refer to the ficonshow command section of the Fabric OS Command Reference. When you configure an LIRR entry and it is current, it is marked with -C. If the Management Server marks an entry as current based on order, it is marked with -C. If the Management Server marks an entry as secondary, it is marked with -S. Following is an example of output with the -C and -S flags. Switch Port WWN Listener Type 20:2d:00:60:69:80:1e:4e Conditional-C 20:0d:00:60:69:80:1e:4f Conditional-S If the LIRR is configured, then the a valid port number displays as shown in the following example. Current LIRR device port number: 27 (0x1b) If the LIRR is not configured, the following displays: Current LIRR device port number is not configured. Node identification data To display node identification data, connect to the switch, log in as user, and enter one of the following commands: For the local switch: ficonshow switchrnid 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 FRU error reporting Field Replaceable Unit (FRU) error information, such as FRU failures and fan and power supply removals and insertions, are stored in error reports as sense data. All FRUs in a chassis have an assigned number that is included in this data. Each CUP instance retains a database of ten FRU error reports. All error reports are sent to host LPARs that have appropriate Current Reporting Paths established with the CUP. Error reports are added to the database as they occur, and then they are removed when sent. If the database fills up, new reports are discarded and not delivered. Error data The following examples show error data available from the host. The number identifying the failed Brocade FRU (refer to FRU numbers on page 90) is derived from a single bit from byte 29 as the high order bit and four bits from byte 30 or 31 as the low order bits (refer to the data in bold in the second lines of the following examples). The FRU numbers are decoded for display as the FRU names, which display in the third lines of the following examples. IOS000I 1065,AB,EQC,**,8200,,,*MASTER*, A FICON Administrator's Guide 89

90 FRU numbers *IRD000E 1065, LEVEL=1 FRU(S)=SLOT8 IOS000I 1065,AB,EQC,**,8200,,,*MASTER*, A *IRD000E 1065, LEVEL=0 FRU(S)=FAN1 IOS000I 1065,AB,EQC,**,8200,,,*MASTER*, A *IRD000E 1065, LEVEL=0 FRU(S)=PWR4 IOS000I 1065,AB,EQC,**,8200,,,*MASTER*, A *IRD000E 1065, LEVEL=0 FRU(S)=FAN2 IOS000I 1065,AB,EQC,**,8200,,,*MASTER*, A *IRD000E 1065, LEVEL=0 FRU(S)=PWR1 IOS000I 1065,AB,EQC,**,8200,,,*MASTER*, A F000 *IRD000E 1065, LEVEL=0 FRU(S)=WWN-CRD IOS000I 1065,AB,EQC,**,8200,,,*MASTER*, A A000 *IRD000E 1065, LEVEL=1 FRU(S)=SLOT10 IOS000I 1061,A8,EQC,**,8200,,,*MASTER*, A *IRD000E 1061, LEVEL=1 FRU(S)=SLOT7 FRU numbers The following Brocade FRU numbers are provided for error reports and associated FRU names that display in error reports. Note that the FRU number does not display in the error reports, but its associated FRU name does display. 1 = SLOT1 2 = SLOT2 3 = SLOT3 4 = SLOT4 5 = SLOT5 6 = SLOT6 7 = SLOT7 8 = SLOT8 9 = SLOT9 10 = SLOT10 11 = SLOT11 12 = SLOT12 17 = PWR1 18 = PWR2 19 = PWR3 20 = PWR4 24 = FAN1 25 = FAN2 26 = FAN3 30 = CHASSIS 31 = WWN-CRD 90 FICON Administrator's Guide

91 Swapping port area IDs Swapping port area IDs If a port malfunctions, or if you want to connect to different devices without having to rewire your infrastructure, you can move a port s traffic to another port (swap port area ID ) without changing the I/O Configuration Data Set (IOCDS) on the mainframe computer. To swap port area IDs, refer to the "Swapping port area IDs" procedure in the Fabric OS Administrator's Guide. For more detail on the following commands that you will use to swap port area IDs, refer to the Fabric OS Command Reference Manual: portswapenable portdisable portswap portswapshow PortSwapDisable 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 0xFE or 0xFF 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. The enabled state of the port swapping feature is persistent across reboots and power cycles. Enabling and disabling the port swapping feature does not affect previously executed port swapping operations. Blade swapping Blade swapping allows you to swap one blade with another of the same type; in this way, you can perform a FRU replacement with minimal traffic disruption. The entire operation is accomplished when the bladeswap command runs on Fabric OS. Fabric OS then validates each command before actually implementing the command on the platform. If an error is encountered, the blade swap quits without disrupting traffic flowing through the blades. If an unforeseen error does occur during the running of the bladeswap command, an entry will be made into the RASlog and all ports that have been swapped as part of the blade swap operation will be swapped back. On successful completion of the command, the source and destination blades are left in a disabled state, allowing you to complete the cable move. Blade swapping is based on port swapping and has the same restrictions: Shared area ports cannot be swapped. Faulty blades cannot be swapped. Ports or blades with area OxFE or OxFF addresses cannot be swapped when FMS mode is enabled. Ports that are part of a trunk group cannot be swapped. GbE ports cannot be swapped. Swapping ports between different logical switches is not supported. The ports on the source and destination blades must be in the same logical switch. Undetermined board types cannot be swapped. For example, a blade swap will fail if the blade type cannot be identified. FICON Administrator's Guide 91

92 Common FICON issues Blade swapping is not supported when swapping to a different model of blade or a different port count. For example, you cannot swap an FC8-32 blade with an FC8-48 port blade. Blade swapping is not supported on application blades. Blade swapping is supported on the FX8-24 blade, but only the 12 Fibre Channel ports will swap. The GbE and VE_ Ports will not be swapped. For procedures and more information on blade swapping, refer to the Fabric OS Administrator's Guide. Common FICON issues Any information you need to verify that FICON has been set up correctly can be found in the Administering FICON Fabrics or the Configuring FICON CUP chapters. Symptom Cascading: No path - Entry Link is ".." message Path to a device does not come online. Probable cause and recommended action This typically occurs when one or more of the required high integrity features for cascading have not been met. Check the following: Review each step in Configuring switched point-topoint FICON on page 39 and Configuring cascaded FICON on page 43 and validate that all features are configured properly. Validate that CUP is online for each FICON director or switch in the fabric with the data center s system programmer. No connection to device. Make sure binding or zoning does not prevent the connection. Validate the following with the data center's system programmer: Correct switch addresses (not switch IDs) are used in link statements. Remember that the switch address is the domain ID converted to hex and may have an offset. The switch ID, used in the CHPID statements, was defined with the correct switch address. All addressing (link statements) uses two-byte addressing on the channel if two-byte addressing has been previously used on that channel. This is necessary even when the specified path is not cascaded. 92 FICON Administrator's Guide

93 Maintaining and Troubleshooting FICON Symptom Packets are being dropped between two FICON units. Probable cause and recommended action Distance between devices is impacting data. When planning cable needs, the following criteria must be considered: Distance considerations Fiber Optic Sub Assembly (FOSA) type (SW or LW) Cable specifications (SM or MM) Patch Panel Connections between FOSA ports (link loss.3-5 db per) Maximum allowable link budget (db) loss For cabling, the most important factor of a Fibre Channel link is the selection of the Fibre Optic Sub Assembly (FOSA) and matching cable type, to support the required distance. Both ends of the optical link must have the matching FOSA (SFP) types. FICON Administrator's Guide 93

94 Maintaining and Troubleshooting FICON Symptom Channel path with two-byte addressing does not come online. Probable cause and recommended action The fabric may not be configured properly, cable connections are not correct, or cable is wrong type. Find out what CHPID the operator 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. If this is the case, you will have to rely on customer documentation to determine the switch port to which the channel is connected. Next, find out what type of error message the operator is getting. An IOS error message is reported when there is an error external to the host; an IEE error message indicates something is wrong internal to the host. Fabric Not Configured Properly Make sure that the insistent domain ID is set and the domain IDs are unique for all switches in the fabric. Make sure that the same binding method is used on all switches in the fabric. Scroll through the node list and make sure there are no invalid attachments. Make sure that the re-routing delay is turned off. Cabling Validate that cables are connected where intended. When using multimode fiber, make sure that all fiber is either all 50u or all 62.5u. A common mistake is to mix 50u and 62.5u fiber cables, which causes errors at patch panels. Example of a Boxed Channel In the following example, the CHPIDs with two-byte addressing did not come online. In response, the CHPID was configured offline and then reconfigured back online. MVS console commands and responses (lines beginning with "IEE" are responses and all other lines are entries). CF CHP(60),OFFLINE IEE503I CHP(60),OFFLINE IEE712I CONFIG PROCESSING COMPLETE CF CHP(60),ONLINE IEE754I NOT ALL PATHS BROUGHT ONLINE WITH CHP(60) IEE502I CHP(60),ONLINE IEE712I CONFIG PROCESSING COMPLETE The following line displays the status of the CHPID with the "D M =" command. All other lines are responses. D M=CHP(60) IEE174I DISPLAY M 021 CHPID 60: TYPE=1D, DESC=FICON INCOMPLETE, ONLINE DEVICE STATUS FOR CHANNEL PATH A B C D E F 006. $@ SWITCH DEVICE NUMBER = NONE 94 FICON Administrator's Guide

95 Troubleshooting FICON Symptom The Control Unit Port cannot access the switch. Probable cause and recommended action ATTACHED ND = NOT KNOWN PHYSICAL CHANNEL ID = 01F0 ************************ SYMBOL EXPLANATIONS ************************ + 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" in the display example indicate that the channel did not come online. You can determine this because the IEE error types are shown and combined with the validation that there was no attempt to do a basic FLOGI (no light displayed on the port view (LED) and no Fibre Channel frames were received). Domain or port ID has changed on CHPID link. A two-byte CHPID link is defined using a domain and port ID that must remain consistent. Any change in the physical link, such as a change in a domain or port ID, will prevent storage control unit access. Use the configure command to verify and set the insistent domain ID (IDID) parameter. FICON:admin> configure For more information and examples of using this command to set the IDID parameter, refer to the Configure command in the Fabric OS Command Reference. Unable to "vary online" FICON CUP port on the switch. FICON CUP port cannot go online. Use the hafailover command on the FICON director. This the only known fix as there is no known firmware solution. Troubleshooting FICON This section provides information-gathering and troubleshooting techniques necessary to fix your problem. General information to gather for all cases The following information must be gathered for all FICON environments: The output from the standard support commands (portlogdump, supportsave, and supportshow) the Fabric Manager Event Log or Brocade Network Advisor logs. 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. After you get confirmation that the configuration has been updated, ouput from the following will be collected and display for the supportshow command: FICON Administrator's Guide 95

96 Switched point-to-point topology checklist ficoncupshow fmsmode ficoncupshow modereg ficondbg dump rnid ficondbg log ficonshow lirr ficonshow rlir ficonshow rnid ficonshow switchrnid ficucmd dump -A The type of mainframe involved including the make, model, and driver levels in use. The type of storage array installed. Many arrays emulate a certain type of IBM array and the make, model, and firmware of the array in use must be provided. Other detailed information for protocol-specific problems: Port data structures, displayed using the ptdatashow command. Port registers, displayed using the ptregshow command. The following actions must be performed to troubleshoot all FICON environments: Use the configupload command to gather configuration files. Provide the IOCDS mainframe file. This will define how all mainframe ports are configured. Verify that Dynamic Load Sharing (DLS) has been disabled with the dlsreset command. If DLS is enabled, traffic on existing ISL ports may be affected when one or more new ISLs is added between the same two switches. Specifically, adding the new ISL may result in dropped frames as routes are adjusted to take advantage of the bandwidth provided. By disabling DLS, you ensure that there will be no dropped frames. In thesupportshow output, search for route.stickyroutes and check for a value of 1 or enter the dlsshow command. Verify that IOD is enabled using the iodset command to ensure in-order delivery. In the output from the supportshow or supportsave, search for route.delayreroute and check for a value of 1 as this indicates that the feature is turned on. Alternately, you can enter the iodshow command. Switched point-to-point topology checklist Verify the following in your FICON environment to ensure proper functionality of the feature: Fabric OS v6.1.0 or later release is installed on Brocade switch or director. Appropriate management tool is being used, such as EFCM v9.6x, DCFM, or Brocade Network Advisor. All required licenses are enabled for your FICON configuration. Switch or director does not have a special mode setting turned on for FICON. Brocade Advanced features software package (Trunking, Fabric Watch, Extended Fabric) license is activated. NOTE There is no requirement to have a secure fabric in a switched point-to-point topology. Cascaded topology checklist Verify the following in your FICON environment to ensure proper functionality of the feature: 96 FICON Administrator's Guide

97 Gathering additional information Fabric OS v6.1.0 or later is installed Brocade switch or director. Appropriate management tool is used, such as EFCM v9.6x, DCFM, or Brocade Network Advisor. All required licenses are activated to enable your FICON configuration? The switch or director does not have a special mode setting enabled for FICON. In addition to device-based routing, lossless, and in-order frame delivery (IOD), the dynamic loadsharing feature is enabled. If you have a fabric for intermix mode of operations, separate zones for FICON and FCP devices are configured. A maximum of one hop exists for both FCP and FICON devices (mainframe channel device connectivity rule). The insistent domain ID flag is set to keep the domain ID of a fabric switch persistent. The CHPID link path is defined using the two-byte address format. The FICON channel connectivity to the storage CU port does not exceed one hop. Proper security policies are enabled. Refer to Configuring cascaded FICON on page 43. The Switch Connection Control (SCC) security policy is active. Brocade Advanced features software package (Trunking, Fabric Watch, Extended fabric) license is activated. Gathering additional information Collect information for your support provider as mentioned in the Fabric OS Troubleshooting and Diagnostics Guide. In addtion, gather the following FICON-specific information. Did the problem occur during an initial install or has was everything functioning prior to the problem? What was changed immediately before the problem occurred. Is the switch properly configured for a FICON environment. 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. Enter the supportshow command and verify that FICON is enabled under "supportshow groups enabled". If it is not enabled, use supportshowcfgenable ficon command. CUP diagnostics FICON CUP supports the IBM Health Checker for zos to diagnose problems. Refer to the IBM Redbooks website at for details on using the IBM Health Checker for z/os. Troubleshooting FICON CUP In addition to the information you collect for your support provider mentioned in Troubleshooting FICON on page 95, also gather the following information which is specific to FICON CUP: Verify the FICON CUP license is installed. Check the state of the CUP by running the ficoncupshow fmsmode command. If it is disabled, enter the ficoncupset fmsmode enable command to enable it. If the CUP is on a director, enter the hafailover command to ensure both CPs are set correctly. Verify that the switch is using Fabric OS v6.1.0 or later. FICON Administrator's Guide 97

98 Troubleshooting NPIV Ensure no device is plugged into port 254 on the Brocade FICON director. Verify with the systems programmer that the CUP ports are defined properly. FICON ports are defined as part of the sysgen process. The z/os systems programmer can verify if the CUP ports are defined properly. Verify that ports 254 and 255 display Disabled (FMS Mode) by entering the switchshow command. If not, enter the portdisable command on the appropriate models for the related ports: On a Brocade 48000, disable 10/30 and 10/31. On a Brocade DCX Backbone, disable 12/30 and 12/31. Troubleshooting NPIV Gather all information as listed in General information to gather for all cases on page 95 and Gathering additional information on page 97. Be sure that NPIV licenses are installed if using Fabric OS v5.0.x. There is no license requirement for Fabric OS v5.1.0 and later. 98 FICON Administrator's Guide

99 Platforms Supporting FICON Introduction Supported platforms with end-of-support announcements Currently supported platforms Supported Brocade blades Introduction This appendix provides the following support details: Brocade products with end-of-support announcements supported for FICON for different IBM systems and drivers (Supported platforms with end-of-support announcements on page 99). Brocade products currently supported for FICON for different IBM systems and drivers (Currently supported platforms on page 100). Brocade blades supported for FICON in various Brocade Switch and Data Center Backbone products (Supported Brocade blades on page 101). Due to the nature of environments in which the mainframes are used, product qualification for FICON is more rigorous than with other products. As a result, not all product combinations and versions of Fabric OS are qualified for FICON. Supported platforms with end-of-support announcements All Brocade products in the table below have end-of-support announcements. However, end-of-support dates vary for each product, and your service provider may have end-of-support dates that differ from Brocade dates. Contact your service provider for details. Firmware listed in the following table is the final version supported and the recommended target path. TABLE 10 Supported platforms with end-of-support announcements Brocade 4900 Brocade 5000 Brocade 6140 Brocade i10k Brocade 7500 Brocade Brocade 5100 Fabric OS Fabric OS Fabric OS Fabric OS Fabric OS Fabric OS Fabric OS z900 & z800 Driver 3GF z990 & z890 Driver 55K z9 EC & z9 BC Driver 67L v6.2.0e v6.2.0e v9.9.9 v9.9.8 v6.4.2a v6.4.2a v7.0.0d v6.2.0e v6.2.0e v9.9.9 v9.9.8 v6.4.2a v6.4.2a v7.0.0d v6.2.0e v6.2.0e v9.9.9 v9.9.8 v6.4.2a v6.4.2a v7.0.0d FICON Administrator's Guide 99

100 Currently supported platforms TABLE 10 Supported platforms with end-of-support announcements (Continued) Brocade 4900 Brocade 5000 Brocade 6140 Brocade i10k Brocade 7500 Brocade Brocade 5100 Fabric OS Fabric OS Fabric OS Fabric OS Fabric OS Fabric OS Fabric OS z10 EC & z10 BC Driver 76D & 79F z10 BC Driver 76D v6.2.0e v6.2.0e v9.9.9 v9.9.8 v6.4.2a v6.4.2a v7.0.0d v6.2.0e v6.2.0e v9.9.9 v9.9.8 v6.4.2a v6.4.2a v7.0.0d z196 Driver 86E or 93G Not supported Not supported v9.9.9 v9.9.8 v6.4.2a v6.4.2a v7.0.0d z114 Driver 93G Not supported Not supported v9.9.9 v9.9.8 v6.4.2a v6.4.2a v7.0.0d EC12 at driver 12K Not supported Not supported Not supported Not supported v6.4.2a v6.4.2a v7.0.0d Currently supported platforms The table below lists Brocade products currently supported for Fabric OS v7.3.0 for various IBM systems and drivers. NOTE When qualifications are available, this table will be updated with Fabric OS v7.4.0 support. TABLE 11 Currently supported platforms Brocade 7800, 7840 Brocade 5300 Brocade DCX-4S Brocade DCX Brocade DCX Brocade DCX Brocade 6510 Fabric OS Fabric OS Fabric OS Fabric OS Fabric OS Fabric OS Fabric OS z900 & z800 Driver 3GF z990 & z890 Driver 55K z9 EC & z9 BC Driver 67L z10 EC & z10 BC Driver 76D & 79F v7.3.0 v7.3.0 v7.3.0 v7.3.0 v7.3.0 v7.3.0 v7.3.0 v7.3.0 v7.3.0 v7.3.0 v7.3.0 v7.3.0 v7.3.0 v7.3.0 v7.3.0 v7.3.0 v7.3.0 v7.3.0 v7.3.0 v7.3.0 v7.3.0 v7.3.0 v7.3.0 v7.3.0 v7.3.0 v7.3.0 v7.3.0 v FICON Administrator's Guide

101 Supported Brocade blades TABLE 11 Currently supported platforms (Continued) Brocade 7800, 7840 Brocade 5300 Brocade DCX-4S Brocade DCX Brocade DCX Brocade DCX Brocade 6510 Fabric OS Fabric OS Fabric OS Fabric OS Fabric OS Fabric OS Fabric OS z10 BC Driver 76D z196 Driver 86E or 93G z114 Driver 93G EC12 at driver 12K v7.3.0 v7.3.0 v7.3.0 v7.3.0 v7.3.0 v7.3.0 v7.3.0 v7.3.0 v7.3.0 v7.3.0 v7.3.0 v7.3.0 v7.3.0 v7.3.0 v7.3.0 v7.3.0 v7.3.0 v7.3.0 v7.3.0 v7.3.0 v7.3.0 v7.3.0 v7.3.0 v7.3.0 v7.3.0 v7.3.0 v7.3.0 v7.3.0 z13 v7.3.0b v7.2.1d v7.3.0b v7.3.0b v7.3.0b v7.3.0b v7.3.0b Supported Brocade blades The table below lists Brocade blades supported for FICON in various Brocade Switch and Data Center Backbone products. TABLE 12 Currently supported blades in Brocade Switch and Data Center Backbone products FC4-16 FC4-32 FX FC8-16 FC8-32 FC8-48 FC8-64 FC FC FC CR16-8 CR16-4 FC10-6 DCX DCX No No Yes No No No Yes 2 Yes Yes Yes 2 Yes No No No No Yes No No No Yes 2 Yes Yes 3 Yes 2 No Yes No DCX No No Yes Yes Yes Yes 3 Yes 2 No No No No No Yes 4 DCX-4 S No No Yes Yes Yes Yes Yes 2 No No No No No Yes Yes Yes Yes No No No No No No No No No No 1. The Ethernet ports of an FX8-24 extension blade can operate with another FX8-24 or Brocade 7800 switch. The maximum number of FX8-24 blades supported in a chassis is four. An FX8-24 can operate with an FX8-24E; however, IPsec and compression is only supported on one 10GbE port on the FX 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. FICON Administrator's Guide 101

102 Unsupported blades 3. For the 48-port card in an 8-slot chassis, FICON is supported in a logical switch configured for zerobased addressing mode. For this card in a DCX-4S Backbone, FICON is supported only on a logical switch defined for port-based addressing (mode 2). 4. FC Gbps port blade for ISL connections. Unsupported blades The following port blades are not supported in a FICON environment: FCOE10-24 FS8-18 FC4-48 FC8-32E FC8-48E 102 FICON Administrator's Guide

103 Basic Switch Configuration 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 for point-to-point and cascaded FICON operation, refer to Administering FICON Fabrics. The following tables are included in this appendix: The Switch configuration example and commands table provides the basic steps and commands in a checklist format to quickly configure a switch for fabric and possible FICON operation. The Cascading (2-byte addressing) example and commands table provides additional steps and commands for FICON cascading (two-byte addressing). TABLE 13 Switch configuration example and commands Feature Upgrade code (if necessary). Feature keys (add licenses). Create all logical switches and add all intended ports to each logical switch. Set switch offline. Relevant Commands firmwaredownload firmwareshow licenseadd licenseshow lscfg switchdisable FICON Administrator's Guide 103

104 Basic Switch Configuration TABLE 13 Feature Switch configuration example and commands (Continued) Relevant Commands Repeat the following procedure to configure switch parameters for each logical switch. 1. Enter the configure command. You will be asked several questions. Only answer questions listed in the Relevant Commands column. Use defaults for other settings unless instructed by a Brocade Certified Architect for FICON. Note that the BB_Credit setting here should not be changed. BB_Credits will be set elsewhere in this checklist. 2. Change fabric parameter settings by answering Yes. After answering Yes, you will be asked several questions. Change only the following parameters. Leave all other parameters at the default unless instructed by a Brocade Certified Architect for FICON. After completing all of the Fabric Parameter settings, answer No for all other parameters. Domain Allow XISL Use When applicable. Enable a 256 Area Limit 0 - Not supported for FICON. 1 - Zero-based addressing. Recommended for FICON. 2 - Port-based addressing. Not supported for 48-port cards in 8-port slot chassis. Disable Device Probing Set to 1. Insistent Domain ID Mode Answer Yes. Set Interop mode configure To set the routing policy to 1: aptpolicy 1 interopmode No other interop mode is supported for FICON. Device Based Routing. Set to 2. Set in-order delivery with lossless DLS enabled. Enable dynamic load sharing only if lossless DLS is set. Set switch name. Set chassis name. Set switch online. Set the principal switch. This can only be one switch in the fabric. In mixed M-Type and B-Type fabrics, the M-Type must be the principal switch. If you are enabling FMS (CUP), disable all ports assigned address 0xFE and 0xFF. To set the routing policy to 2: aptpolicy 2 To display the routing policy: aptpolicy iodset --enable -losslessdls dlsset switchname chassisname switchenable fabricprincipal 1 portdisable 104 FICON Administrator's Guide

105 Basic Switch Configuration TABLE 13 Feature Switch configuration example and commands (Continued) Relevant Commands Enable FMS if FICON CUP will be used. ficoncupset fmsmode enable ficoncupshow fmsmode NOTE High-integrity fabric requirements must be met and HIF mode enabled to enable FMS mode. Set the default zone for no access. Configure zones. This is much easier with Brocade Network Advisor or Web Tools. Typically, scripts are used when using Fabric OS commands. defzone --noaccess cfgsave defzone --show cfgclear cfgcreate cfgdelete cfgdisable cfgenable cfgremove cfgsave cfgshow Clear all port statistics and trace information. supportsave -R errclear statsclear portlogclear diagclearerror -all tracedump -c slotstatsclear errclear ficonclear rlir Turn on FICON logging. Set port fencing. Setting port fencing parameters is much easier with Brocade Network Advisor. supportshowcfgenable ficon To clear alarms: fwalarmsfilterset 0 To define alarms: fwconfigure Respond to menu driven prompts accordingly. To enable the defined alarms: fwalarmsfilterset 1 Parameters in the table below are only required when two-byte link addressing is used in the IOCP. Normally, these parameters are not set when single-byte addressing is used. FICON Administrator's Guide 105

106 Basic Switch Configuration TABLE 14 Feature Cascading (two-byte addressing) example and commands Parameter Add members to the SCC Policy. secpolicycreate "SCC_POLICY", "wwn;wwn;..." Or, to add all switches already in the fabric, use an "*" for each WWN: secpolicycreate "SCC_POLICY", "*" Save the policy. Activate the policy. Enable the ACL Fabric-Wide Consistency Policy and enforce a strict SCC policy. secpolicysave secpolicyactivate fddcfg --fabwideset "SCC:S;" 106 FICON Administrator's Guide

107 Address Binding Examples Sequential address binding Port-based address binding Unbinding multiple ports Sequential address binding This section provides an example that will allow all ports on all blades installed in a Brocade DCX or DCX 8510 FICON director to use sequential, zero-based, Mode 1 addresses. The following figure illustrates ports with sequential addresses. FIGURE 25 Sequential addresses Before binding an address with the portaddress --bind command, disable the port with the portdisable command. To change the bound address, you must first unbind the addresses. Refer to Unbinding multiple ports on page 116 for an easy method to unbind multiple ports at once. For more information on port addressing modes, refer to Addressing modes on page 46. FICON Administrator's Guide 107

108 Example scripts for binding ports Example scripts for binding ports The following example scripts containing the portaddress --bind command bind all ports on the DCX Backbone to sequential, zero based (Mode 1) addresses. You can copy and paste these scripts 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. date # Slot 1 portaddress --bind 1/ portaddress --bind 1/ portaddress --bind 1/ portaddress --bind 1/ portaddress --bind 1/ portaddress --bind 1/ portaddress --bind 1/ portaddress --bind 1/ portaddress --bind 1/ portaddress --bind 1/ portaddress --bind 1/10 0A00 portaddress --bind 1/11 0B00 portaddress --bind 1/12 0C00 portaddress --bind 1/13 0D00 portaddress --bind 1/14 0E00 portaddress --bind 1/15 0F00 portaddress --bind 1/ portaddress --bind 1/ portaddress --bind 1/ portaddress --bind 1/ portaddress --bind 1/ portaddress --bind 1/ portaddress --bind 1/ portaddress --bind 1/ portaddress --bind 1/ portaddress --bind 1/ portaddress --bind 1/26 1A00 portaddress --bind 1/27 1B00 portaddress --bind 1/28 1C00 portaddress --bind 1/29 1D00 portaddress --bind 1/30 1E00 portaddress --bind 1/31 1F00 # Slot 2 portaddress --bind 2/ portaddress --bind 2/ portaddress --bind 2/ portaddress --bind 2/ portaddress --bind 2/ portaddress --bind 2/ portaddress --bind 2/ portaddress --bind 2/ portaddress --bind 2/ portaddress --bind 2/ portaddress --bind 2/10 2A00 portaddress --bind 2/11 2B00 portaddress --bind 2/12 2C00 portaddress --bind 2/13 2D00 portaddress --bind 2/14 2E00 portaddress --bind 2/15 2F00 portaddress --bind 2/ portaddress --bind 2/ portaddress --bind 2/ portaddress --bind 2/ portaddress --bind 2/ portaddress --bind 2/ portaddress --bind 2/ portaddress --bind 2/ portaddress --bind 2/ portaddress --bind 2/ portaddress --bind 2/26 3A00 portaddress --bind 2/27 3B00 portaddress --bind 2/28 3C00 portaddress --bind 2/29 3D00 portaddress --bind 2/30 3E00 portaddress --bind 2/31 3F FICON Administrator's Guide

109 Address Binding Examples # Slot 3 portaddress --bind 3/ portaddress --bind 3/ portaddress --bind 3/ portaddress --bind 3/ portaddress --bind 3/ portaddress --bind 3/ portaddress --bind 3/ portaddress --bind 3/ portaddress --bind 3/ portaddress --bind 3/ portaddress --bind 3/10 4A00 portaddress --bind 3/11 4B00 portaddress --bind 3/12 4C00 portaddress --bind 3/13 4D00 portaddress --bind 3/14 4E00 portaddress --bind 3/15 4F00 portaddress --bind 3/ portaddress --bind 3/ portaddress --bind 3/ portaddress --bind 3/ portaddress --bind 3/ portaddress --bind 3/ portaddress --bind 3/ portaddress --bind 3/ portaddress --bind 3/ portaddress --bind 3/ portaddress --bind 3/26 5A00 portaddress --bind 3/27 5B00 portaddress --bind 3/28 5C00 portaddress --bind 3/29 5D00 portaddress --bind 3/30 5E00 portaddress --bind 3/31 5F00 # Slot 4 portaddress --bind 4/ portaddress --bind 4/ portaddress --bind 4/ portaddress --bind 4/ portaddress --bind 4/ portaddress --bind 4/ portaddress --bind 4/ portaddress --bind 4/ portaddress --bind 4/ portaddress --bind 4/ portaddress --bind 4/10 6A00 portaddress --bind 4/11 6B00 portaddress --bind 4/12 6C00 portaddress --bind 4/13 6D00 portaddress --bind 4/14 6E00 portaddress --bind 4/15 6F00 portaddress --bind 4/ portaddress --bind 4/ portaddress --bind 4/ portaddress --bind 4/ portaddress --bind 4/ portaddress --bind 4/ portaddress --bind 4/ portaddress --bind 4/ portaddress --bind 4/ portaddress --bind 4/ portaddress --bind 4/26 7A00 portaddress --bind 4/27 7B00 portaddress --bind 4/28 7C00 portaddress --bind 4/29 7D00 portaddress --bind 4/30 7E00 portaddress --bind 4/31 7F00 # Slot 9 portaddress --bind 9/ portaddress --bind 9/ portaddress --bind 9/ portaddress --bind 9/ portaddress --bind 9/ portaddress --bind 9/ portaddress --bind 9/ portaddress --bind 9/ portaddress --bind 9/ portaddress --bind 9/ portaddress --bind 9/10 8A00 FICON Administrator's Guide 109

110 Address Binding Examples portaddress --bind 9/11 8B00 portaddress --bind 9/12 8C00 portaddress --bind 9/13 8D00 portaddress --bind 9/14 8E00 portaddress --bind 9/15 8F00 portaddress --bind 9/ portaddress --bind 9/ portaddress --bind 9/ portaddress --bind 9/ portaddress --bind 9/ portaddress --bind 9/ portaddress --bind 9/ portaddress --bind 9/ portaddress --bind 9/ portaddress --bind 9/ portaddress --bind 9/26 9A00 portaddress --bind 9/27 9B00 portaddress --bind 9/28 9C00 portaddress --bind 9/29 9D00 portaddress --bind 9/30 9E00 portaddress --bind 9/31 9F00 # Slot 10 portaddress --bind 10/0 A000 portaddress --bind 10/1 A100 portaddress --bind 10/2 A200 portaddress --bind 10/3 A300 portaddress --bind 10/4 A400 portaddress --bind 10/5 A500 portaddress --bind 10/6 A600 portaddress --bind 10/7 A700 portaddress --bind 10/8 A800 portaddress --bind 10/9 A900 portaddress --bind 10/10 AA00 portaddress --bind 10/11 AB00 portaddress --bind 10/12 AC00 portaddress --bind 10/13 AD00 portaddress --bind 10/14 AE00 portaddress --bind 10/15 AF00 portaddress --bind 10/16 B000 portaddress --bind 10/17 B100 portaddress --bind 10/18 B200 portaddress --bind 10/19 B300 portaddress --bind 10/20 B400 portaddress --bind 10/21 B500 portaddress --bind 10/22 B600 portaddress --bind 10/23 B700 portaddress --bind 10/24 B800 portaddress --bind 10/25 B900 portaddress --bind 10/26 BA00 portaddress --bind 10/27 BB00 portaddress --bind 10/28 BC00 portaddress --bind 10/29 BD00 portaddress --bind 10/30 BE00 portaddress --bind 10/31 BF00 # Slot 11 portaddress --bind 11/0 C000 portaddress --bind 11/1 C100 portaddress --bind 11/2 C200 portaddress --bind 11/3 C300 portaddress --bind 11/4 C400 portaddress --bind 11/5 C500 portaddress --bind 11/6 C600 portaddress --bind 11/7 C700 portaddress --bind 11/8 C800 portaddress --bind 11/9 C900 portaddress --bind 11/10 CA00 portaddress --bind 11/11 CB00 portaddress --bind 11/12 CC00 portaddress --bind 11/13 CD00 portaddress --bind 11/14 CE00 portaddress --bind 11/15 CF00 portaddress --bind 11/16 D000 portaddress --bind 11/17 D100 portaddress --bind 11/18 D200 portaddress --bind 11/19 D300 portaddress --bind 11/20 D400 portaddress --bind 11/21 D500 portaddress --bind 11/22 D FICON Administrator's Guide

111 Port-based address binding portaddress --bind 11/23 D700 portaddress --bind 11/24 D800 portaddress --bind 11/25 D900 portaddress --bind 11/26 DA00 portaddress --bind 11/27 DB00 portaddress --bind 11/28 DC00 portaddress --bind 11/29 DD00 portaddress --bind 11/30 DE00 portaddress --bind 11/31 DF00 # Slot 12 portaddress --bind 12/0 E000 portaddress --bind 12/1 E100 portaddress --bind 12/2 E200 portaddress --bind 12/3 E300 portaddress --bind 12/4 E400 portaddress --bind 12/5 E500 portaddress --bind 12/6 E600 portaddress --bind 12/7 E700 portaddress --bind 12/8 E800 portaddress --bind 12/9 E900 portaddress --bind 12/10 EA00 portaddress --bind 12/11 EB00 portaddress --bind 12/12 EC00 portaddress --bind 12/13 ED00 portaddress --bind 12/14 EE00 portaddress --bind 12/15 EF00 portaddress --bind 12/16 F000 portaddress --bind 12/17 F100 portaddress --bind 12/18 F200 portaddress --bind 12/19 F300 portaddress --bind 12/20 F400 portaddress --bind 12/21 F500 portaddress --bind 12/22 F600 portaddress --bind 12/23 F700 portaddress --bind 12/24 F800 portaddress --bind 12/25 F900 portaddress --bind 12/26 FA00 portaddress --bind 12/27 FB00 portaddress --bind 12/28 FC00 portaddress --bind 12/29 FD00 portaddress --bind 12/30 FE00 portaddress --bind 12/31 FF00 Port-based address binding This section provides an example that will allow all ports on all blades installed in a Brocade DCX or DCX 8510 FICON director to use port-based (Mode 2) addresses. The following figure illustrates ports with port-based addressing. FICON Administrator's Guide 111

112 Example scripts for binding ports FIGURE 26 Port-based addresses Before binding an address with the portaddress --bind command, disable the port with the portdisable command. To change the bound address, you must first unbind the addresses. Refer to Unbinding multiple ports on page 116 for an easy method to unbind multiple ports at once. For more information on port addressing modes, refer to Addressing modes on page 46. Example scripts for binding ports The following example scripts bind all ports on the DCX Backbone to port-based (Mode 2) addresses. You can copy and paste these scripts 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. date # Slot 1 portaddress --bind 1/ portaddress --bind 1/ portaddress --bind 1/ portaddress --bind 1/ portaddress --bind 1/ portaddress --bind 1/ portaddress --bind 1/ portaddress --bind 1/ portaddress --bind 1/ portaddress --bind 1/ portaddress --bind 1/10 0A00 portaddress --bind 1/11 0B00 portaddress --bind 1/12 0C00 portaddress --bind 1/13 0D00 portaddress --bind 1/14 0E00 portaddress --bind 1/15 0F00 portaddress --bind 1/ portaddress --bind 1/ portaddress --bind 1/ portaddress --bind 1/ portaddress --bind 1/ portaddress --bind 1/ FICON Administrator's Guide

113 Address Binding Examples portaddress --bind 1/ portaddress --bind 1/ portaddress --bind 1/ portaddress --bind 1/ portaddress --bind 1/26 8A00 portaddress --bind 1/27 8B00 portaddress --bind 1/28 8C00 portaddress --bind 1/29 8D00 portaddress --bind 1/30 8E00 portaddress --bind 1/31 8F00 # Slot 2 portaddress --bind 2/ portaddress --bind 2/ portaddress --bind 2/ portaddress --bind 2/ portaddress --bind 2/ portaddress --bind 2/ portaddress --bind 2/ portaddress --bind 2/ portaddress --bind 2/ portaddress --bind 2/ portaddress --bind 2/10 1A00 portaddress --bind 2/11 1B00 portaddress --bind 2/12 1C00 portaddress --bind 2/13 1D00 portaddress --bind 2/14 1E00 portaddress --bind 2/15 1F00 portaddress --bind 2/ portaddress --bind 2/ portaddress --bind 2/ portaddress --bind 2/ portaddress --bind 2/ portaddress --bind 2/ portaddress --bind 2/ portaddress --bind 2/ portaddress --bind 2/ portaddress --bind 2/ portaddress --bind 2/26 9A00 portaddress --bind 2/27 9B00 portaddress --bind 2/28 9C00 portaddress --bind 2/29 9D00 portaddress --bind 2/30 9E00 portaddress --bind 2/31 9F00 # Slot 3 portaddress --bind 3/ portaddress --bind 3/ portaddress --bind 3/ portaddress --bind 3/ portaddress --bind 3/ portaddress --bind 3/ portaddress --bind 3/ portaddress --bind 3/ portaddress --bind 3/ portaddress --bind 3/ portaddress --bind 3/10 2A00 portaddress --bind 3/11 2B00 portaddress --bind 3/12 2C00 portaddress --bind 3/13 2D00 portaddress --bind 3/14 2E00 portaddress --bind 3/15 2F00 portaddress --bind 3/16 A000 portaddress --bind 3/17 A100 portaddress --bind 3/18 A200 portaddress --bind 3/19 A300 portaddress --bind 3/20 A400 portaddress --bind 3/21 A500 portaddress --bind 3/22 A600 portaddress --bind 3/23 A700 portaddress --bind 3/24 A800 portaddress --bind 3/25 A900 portaddress --bind 3/26 AA00 portaddress --bind 3/27 AB00 portaddress --bind 3/28 AC00 portaddress --bind 3/29 AD00 portaddress --bind 3/30 AE00 portaddress --bind 3/31 AF00 # Slot 4 portaddress --bind 4/ FICON Administrator's Guide 113

114 Address Binding Examples portaddress --bind 4/ portaddress --bind 4/ portaddress --bind 4/ portaddress --bind 4/ portaddress --bind 4/ portaddress --bind 4/ portaddress --bind 4/ portaddress --bind 4/ portaddress --bind 4/ portaddress --bind 4/10 3A00 portaddress --bind 4/11 3B00 portaddress --bind 4/12 3C00 portaddress --bind 4/13 3D00 portaddress --bind 4/14 3E00 portaddress --bind 4/15 3F00 portaddress --bind 4/16 B000 portaddress --bind 4/17 B100 portaddress --bind 4/18 B200 portaddress --bind 4/19 B300 portaddress --bind 4/20 B400 portaddress --bind 4/21 B500 portaddress --bind 4/22 B600 portaddress --bind 4/23 B700 portaddress --bind 4/24 B800 portaddress --bind 4/25 B900 portaddress --bind 4/26 BA00 portaddress --bind 4/27 BB00 portaddress --bind 4/28 BC00 portaddress --bind 4/29 BD00 portaddress --bind 4/30 BE00 portaddress --bind 4/31 BF00 # Slot 9 portaddress --bind 9/ portaddress --bind 9/ portaddress --bind 9/ portaddress --bind 9/ portaddress --bind 9/ portaddress --bind 9/ portaddress --bind 9/ portaddress --bind 9/ portaddress --bind 9/ portaddress --bind 9/ portaddress --bind 9/10 4A00 portaddress --bind 9/11 4B00 portaddress --bind 9/12 4C00 portaddress --bind 9/13 4D00 portaddress --bind 9/14 4E00 portaddress --bind 9/15 4F00 portaddress --bind 9/16 C000 portaddress --bind 9/17 C100 portaddress --bind 9/18 C200 portaddress --bind 9/19 C300 portaddress --bind 9/20 C400 portaddress --bind 9/21 C500 portaddress --bind 9/22 C600 portaddress --bind 9/23 C700 portaddress --bind 9/24 C800 portaddress --bind 9/25 C900 portaddress --bind 9/26 CA00 portaddress --bind 9/27 CB00 portaddress --bind 9/28 CC00 portaddress --bind 9/29 CD00 portaddress --bind 9/30 CE00 portaddress --bind 9/31 CF00 # Slot 10 portaddress --bind 10/ portaddress --bind 10/ portaddress --bind 10/ portaddress --bind 10/ portaddress --bind 10/ portaddress --bind 10/ portaddress --bind 10/ portaddress --bind 10/ portaddress --bind 10/ portaddress --bind 10/ portaddress --bind 10/10 5A00 portaddress --bind 10/11 5B00 portaddress --bind 10/12 5C FICON Administrator's Guide

115 Address Binding Examples portaddress --bind 10/13 5D00 portaddress --bind 10/14 5E00 portaddress --bind 10/15 5F00 portaddress --bind 10/16 D000 portaddress --bind 10/17 D100 portaddress --bind 10/18 D200 portaddress --bind 10/19 D300 portaddress --bind 10/20 D400 portaddress --bind 10/21 D500 portaddress --bind 10/22 D600 portaddress --bind 10/23 D700 portaddress --bind 10/24 D800 portaddress --bind 10/25 D900 portaddress --bind 10/26 DA00 portaddress --bind 10/27 DB00 portaddress --bind 10/28 DC00 portaddress --bind 10/29 DD00 portaddress --bind 10/30 DE00 portaddress --bind 10/31 DF00 # Slot 11 portaddress --bind 11/ portaddress --bind 11/ portaddress --bind 11/ portaddress --bind 11/ portaddress --bind 11/ portaddress --bind 11/ portaddress --bind 11/ portaddress --bind 11/ portaddress --bind 11/ portaddress --bind 11/ portaddress --bind 11/10 6A00 portaddress --bind 11/11 6B00 portaddress --bind 11/12 6C00 portaddress --bind 11/13 6D00 portaddress --bind 11/14 6E00 portaddress --bind 11/15 6F00 portaddress --bind 11/16 E000 portaddress --bind 11/17 E100 portaddress --bind 11/18 E200 portaddress --bind 11/19 E300 portaddress --bind 11/20 E400 portaddress --bind 11/21 E500 portaddress --bind 11/22 E600 portaddress --bind 11/23 E700 portaddress --bind 11/24 E800 portaddress --bind 11/25 E900 portaddress --bind 11/26 EA00 portaddress --bind 11/27 EB00 portaddress --bind 11/28 EC00 portaddress --bind 11/29 ED00 portaddress --bind 11/30 EE00 portaddress --bind 11/31 EF00 # Slot 12 portaddress --bind 12/ portaddress --bind 12/ portaddress --bind 12/ portaddress --bind 12/ portaddress --bind 12/ portaddress --bind 12/ portaddress --bind 12/ portaddress --bind 12/ portaddress --bind 12/ portaddress --bind 12/ portaddress --bind 12/10 7A00 portaddress --bind 12/11 7B00 portaddress --bind 12/12 7C00 portaddress --bind 12/13 7D00 portaddress --bind 12/14 7E00 portaddress --bind 12/15 7F00 portaddress --bind 12/16 F000 portaddress --bind 12/17 F100 portaddress --bind 12/18 F200 portaddress --bind 12/19 F300 portaddress --bind 12/20 F400 portaddress --bind 12/21 F500 portaddress --bind 12/22 F600 portaddress --bind 12/23 F700 portaddress --bind 12/24 F800 FICON Administrator's Guide 115

116 Unbinding multiple ports portaddress --bind 12/25 F900 portaddress --bind 12/26 FA00 portaddress --bind 12/27 FB00 portaddress --bind 12/28 FC00 portaddress --bind 12/29 FD00 portaddress --bind 12/30 FE00 portaddress --bind 12/31 FF00 Unbinding multiple ports The following example scripts containing the portaddress --unbind command unbind all addresses on an 8-slot chassis that is fully populated with 32-port cards. You can copy and paste these scripts 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. for ((i=0;i<32;i++)); do (echo 1/$i;portaddress --unbind 1/$i); done for ((i=0;i<32;i++)); do (echo 2/$i;portaddress --unbind 2/$i); done for ((i=0;i<32;i++)); do (echo 3/$i;portaddress --unbind 3/$i); done for ((i=0;i<32;i++)); do (echo 4/$i;portaddress --unbind 4/$i); done for ((i=0;i<32;i++)); do (echo 9/$i;portaddress --unbind 9/$i); done for ((i=0;i<32;i++)); do (echo 10/$i;portaddress -unbind102/$i); done for ((i=0;i<32;i++)); do (echo 11/$i;portaddress --unbind 11/$i); done for ((i=0;i<32;i++)); do (echo 12/$i;portaddress --unbind 12/$i); done 116 FICON Administrator's Guide

117 Configuration Information Record You can use the following worksheet for recording FICON configuration information. NOTE Attached E_Ports can be for an ISL, control unit (CU) interface, or central processor complex (CPC) channel path identifier (CHPID). FICON Switch Configuration Worksheet FICON Switch Manufacturer: Type: Model: S/N: HCD Defined Switch ID (Switch ID) FICON Switch Domain ID Cascaded Directors No Yes Corresponding Cascaded Switch Domain ID Fabric Name FICON Switch F_Ports and Attached N_Ports/E_Ports Slot Number Port Number Port Address Laser Type: LX / SX Port Name Node Type CU / CHNL Machine Type Model Serial Number ISL, CU I/F, CPC CHPID FICON Administrator's Guide 117

118 Configuration Information Record 118 FICON Administrator's Guide

119 EBCDIC Code Page 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 character set. FICON Administrator's Guide 119