53-1003144-01 27 June 2014 FICON Administrator's Guide Supporting Fabric OS v7.3.
© 2014, Brocade Communications Systems, Inc. All Rights Reserved. Brocade, the B-wing symbol, Brocade Assurance, ADX, AnyIO, DCX, Fabric OS, FastIron, HyperEdge, ICX, MLX, MyBrocade, NetIron, OpenScript, VCS, VDX, and Vyatta are registered trademarks, and The Effortless Network and the On-Demand Data Center are trademarks of Brocade Communications Systems, Inc., in the United States and in other countries. Other brands and product names mentioned may be trademarks of others.
Contents Preface..................................................................................................................................... 5 Document conventions......................................................................................5 Text formatting conventions.................................................................. 5 Command syntax conventions.............................................................. 5 Notes, cautions, and warnings....................................
Mode 0 (10-bit addressing)............................................................... 44 Mode 1 (zero-based addressing)...................................................... 45 Mode 2 (port-based addressing)....................................................... 45 Changing the addressing mode........................................................ 45 FICON and blade support for addressing modes............................. 46 Port swap limitations........................................................
Options for displaying statistics...........................................................75 Maintaining and Troubleshooting FICON..................................................................................77 Firmware management in a FICON environment........................................... 77 Upgrade and downgrade considerations............................................ 77 Firmware download disruption............................................................
EBCDIC Code Page............................................................................................................. 119 Index..................................................................................................................................
Preface ● Document conventions......................................................................................................5 ● Brocade resources............................................................................................................ 7 ● Contacting Brocade Technical Support.............................................................................7 ● Document feedback..........................................................................................................
Notes, cautions, and warnings Convention Description value In Fibre Channel products, a fixed value provided as input to a command option is printed in plain text, for example, --show WWN. [] 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.
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 www.brocade.com. 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.
Document feedback • • • • 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. 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.
About This Document ● Supported hardware and software.................................................................................... 9 ● Additional FICON resources............................................................................................. 9 ● What’s new in this document............................................................................................
About This Document • • • • • • • • • • 10 Added notes wherever configupload command mentioned that it backs up Fabric OS feature and switch configuration, but not FMS and FICON-specific configuration. Added notes wherever enabling FMS mode is described that all high-integrity fabric attributes must be configured and HIF mode enabled to enable FMS mode.
Introducing FICON ● FICON overview..............................................................................................................11 ● FICON concepts..............................................................................................................13 ● FICON configurations......................................................................................................14 ● Access control in FICON....................................................................................
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.
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.
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 disk array or tape drive.
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.
Qualified FICON cascaded configurations switches and backbones is also supported. An example of this would be a Brocade DCX 8510-8 Backbone connected to a Brocade 6510. 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.
Extended fabric configurations 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.
Introducing FICON The following figure illustrates a multi-hop ICL triangle configuration that uses ICLs. Note that three switches are connected through ICLs only.
Introducing FICON 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. 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.
Introducing FICON 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.
Introducing FICON The following figure illustrates a configuration that uses FCIP between 7800 switches that are used as routers only, for ISL extension. Channel or control unit connections are not permitted. The 7800 switches may be replaced with FX8-24 blades installed in directors. 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.
Introducing FICON 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. 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.
Access control in FICON the 7800 switches. The 7800 switches at either site may be replaced with the FX8-24 blades installed in directors. 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.
Cascaded zoning devices to changes in the fabric. Using multiple smaller zones instead of one large zone helps alleviate the need for channels and device interfaces to process RSCNs that are not relevant. 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.
Introducing FICON 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. 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.
Error reporting 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 average frame pacing delay information) reports port errors, which in turn are also reported back to the mainframe host management consoles.
Introducing FICON The figure below demonstrates the three types of binding you can use depending on the security requirements of your fabric.
FICON commands FICON commands NOTE The Fabric OS CLI supports only a subset of the Brocade management features for FICON fabrics. The full set of FICON CUP administrative procedures is available using the Brocade Network Advisor and Web Tools software features. You can also use an SNMP agent and the FICON Management Information Base (MIB). The table below summarizes the Fabric OS CLI commands that can be used for managing FICON fabrics.
Introducing FICON TABLE 1 Fabric OS commands related to FICON (Continued) Command Description portSwap Swaps ports. Note that the portswap --restore command restores swapped ports to an unswapped state. portSwapDisable 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.
Link and FC addressing TABLE 1 Fabric OS commands related to FICON (Continued) Command Description ficonCupShow diag_info Displays the diagnostic interval setting and related statistic sampling information for diagnostic information collected by the CUP. ficonCupShow fmsmode Displays the current FMS mode setting. ficonCupShow hlthchk_log Displays health check logs for the logical switch. ficonCupShow modereg bitname Displays FICON-CUP mode register bits.
Domain ID The following figure represents components of link and FC addresses that are explained in this section. 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.
ALPA 32 FICON Administrator's Guide 53-1003144-01
Administering FICON Fabrics ● User security considerations........................................................................................... 33 ● Meeting high-integrity fabric requirements...................................................................... 33 ● Preparing a switch for FICON......................................................................................... 36 ● Configuring switched point-to-point FICON.....................................................................
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 to v7.3.0, IDID, SCC_Policy, and SCC:S will be validated and the firmware attempt failed if either are incorrect. If 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.
Enabling the fabric-wide consistency policy • Enter the secpolicycreate command to add all switches in the fabric, if they are connected. • 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. secpolicycreate "SCC_POLICY","*" secpolicyadd "SCC_POLICY","wwn1;wwn2" 3. Enter the secpolicyactivate command to activate the currently defined SCC policy.
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.
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 backbone may require scheduled downtime. • • • All fabric operating parameters, such as timeout values, must be the same.
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 Domain R_A_TOV Prompts for the fabric parameters.
Administering FICON Fabrics TABLE 2 FICON switch parameters (Continued) Parameter Response Comment Suppress Class F traffic 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. Per-frame route priority 0 Do not change.
Administering FICON Fabrics TABLE 2 FICON switch parameters (Continued) Parameter Response Comment RSCN transmission mode No 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.
Configuring cascaded FICON 13. Configure the fill word for all 8 Gbps ports using the portCfgFillWord command. The following example shows the command with recommended mode 3 and passive operands set: portcfgfillword slot/port, 3 passive NOTE This command is only supported on 8 Gbps FC ports. For more information, refer to the portCfgFillWord command in the Fabric OS Command Reference. 14. Enter the defZone --noaccess command to disable the default zone. 15. Configure zoning for your fabric.
FCR and FICON cascading CAUTION Configuring the switch for FICON is a disruptive process. The switch must be disabled to configure switch parameters. This procedure must be followed prior to channels joining the fabric. 1. Perform the following actions for each switch: a) b) 2. 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 34. Set the domain ID.
FICON and FICON CUP in Virtual Fabrics 3. Add the front domain WWN to the SCC Policy lists in the edge switches to be merged. 4. Connect the switches. FICON and FICON CUP in Virtual Fabrics For FICON CUP, FICON Management Server (FMS) mode is enabled on the logical switch and not the chassis. For example, in a Virtual Fabrics environment on the Brocade 6510 switch and the Brocade DCX Backbones, enable CUP on each logical switch.
Addressing modes 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.
Mode 1 (zero-based addressing) • • 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.
FICON and blade support for addressing modes 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.
Clearing the FICON management database 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.
Administering FICON Fabrics 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. NOTE Check with your host and storage manufacturer to determine if they support Fibre Channel CS_CTL prioritization on their devices.
FICON best practices 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.
Latency guideline • ‐ 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. Latency guideline The maximum supported distance for a FICON channel is 300 Km (1.5 msec of delay). Synchronous mirroring applications are generally limited to 100 Km (0.5 msec of delay).
Configuring FICON CUP ● Control Unit Port overview.............................................................................................. 51 ● Port and switch naming standards for FMS mode.......................................................... 54 ● Configuring FICON CUP................................................................................................. 55 ● Determining physical port assignment ...........................................................................
FICON CUP restrictions 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 56. 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.
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.
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.
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 backbone has been set up according to the instructions in Configuring switched point-to-point FICON on page 37 and, if in a cascaded topology, Configuring cascaded FICON on page 41. 3. For switches with at least 256 ports installed, use the portDisable command to disable ports 0xFE and 0xFF.
Configuring FICON CUP in Virtual Fabrics On a Brocade DCX and DCX-4S Backbones, 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.
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 in force.
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 33. 1. Connect to the switch and log in using an account assigned to the admin role. 2. Enter ficonCupSet fmsmode enable. 3.
Upgrade considerations • • • • • 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 55 for more information. Enabling FMS mode disables all ports with OxFE and OxFF addresses.
Port swap limitations ‐ ‐ • 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.
FICON file access facility TABLE 7 FICON CUP mode register bits (Continued) DCAM 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). HCP Host control prohibited. When this bit is set on, the host is not allowed to set CUP parameters. The default setting is 0 (off). POSC Programmed offline state control.
Configuration files downloaded with Active=Saved mode disabled The IPL 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.
Considerations for setting mode register bits * *------------------------------------------------------------------ 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.
Persistently enabling and disabling ports for CUP Persistently enabling and disabling ports for CUP When FMS mode is enabled, you cannot use the portCfgPersistentEnable and portCfgPersistentDisable commands to persistently enable and disable ports. Instead, use the following procedure. 1. Connect to the switch and log in using an account assigned to the admin role. 2. Enter the ficonCupShow modereg command to display the mode register bit settings. 3. Verify that the ASM bit is set on (1). 4.
Administering FICON Extension Services ● Platforms supporting FICON extension over IP.............................................................. 65 ● FICON emulation overview............................................................................................. 65 ● FCIP configuration requirements for FICON extension...................................................70 ● Configuration requirements for switches and backbones...............................................
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.
Tape emulation primary volume to be located at a distance from its mirrored secondary without encountering performance degradation associated with IU pacing. 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.
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.
FICON and ESCON conversion support 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. 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.
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 72.
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.
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 65. ATTENTION Make sure both ends of the tunnel match before bringing it up or the tunnel will not form. 1.
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.
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.
Options for displaying statistics |0x041011C500|116301640106040A|H| 0x00| N/A|0000|0000| 34516| 0| 0| 262878|32760| |0x04100A9700|116301640106040B|H| 0x3C|0x12|006C|0000| 33834| 19329| 32760| 240347|32760| |0x04100F0000|116301640106040C|H| 0x3C|0x12|006C|0000| 34537| 12385| 32760| 253620|32760| |0x0410049980|116301640106040D|H| 0x00| N/A|0000|0000| 34764| 0| 0| 266346|32760| |0x04100FA500|116301640106040E|H| 0x3C|0x12|006C|0000| 23636| 16742| 32760| 183126|32760| |0x041008F280|116301640106040F|H| 0x00| N/A
Administering FICON Extension Services TABLE 8 FICON emulation statistics commands (Continued) Command Output display portshow xtun ve_port -ficon -tapeperf FICON tape pipelining performance statistics. portshow xtun ve_port -ficon -xrcperf IBM z/OS Global Mirror performance statistics. portshow xtun ve_port -ficon -printperf Printer emulation processing statistics. Refer to the portShow command section of the Fabric OS Command Reference for more information on these commands.
Maintaining and Troubleshooting FICON ● Firmware management in a FICON environment........................................................... 77 ● Configuration restoration in a FICON environment......................................................... 78 ● Traffic Isolation Zoning....................................................................................................79 ● Monitoring and Alerting Policy Suite...............................................................................
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.
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.
Determining ports for the TI Zone 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. 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.
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.
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.
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.
Maintaining and Troubleshooting FICON 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. 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.
Emulation topology Emulation topology FICON device emulation topologies have unique requirements due to the characteristics of the emulation devices. Each device must track the emulated sessions and maintain the state of the emulated devices in order to satisfy both ends of the connection. Because this is done over very long distances, care must be taken when configuring the ISL connections to insure that the sessions remain along exclusive paths.
Maintaining and Troubleshooting FICON connections that make emulation isolation difficult. By using Enhanced TI Zoning to support device membership in multiple zones, these types of emulation configurations are addressed. FIGURE 25 Emulation topology using Enhanced TI Zones The preceding figure shows the following Enhanced TI Zoning definitions for the emulation topology: • • Green TI Zone includes channel 0, ISL 80, ISL 81, Grid 1, and Grid 4. Blue TI Zone includes channel 1, ISL 82, ISL 83, and Grid 4.
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 7.2.0. 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.
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.
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.
FRU numbers *IRD000E 1065,002032-001 LEVEL=1 FRU(S)=SLOT8 IOS000I 1065,AB,EQC,**,8200,,,*MASTER*, 286 1000A00000000046700000000000000000000000000000000000000000088000 *IRD000E 1065,002032-001 LEVEL=0 FRU(S)=FAN1 IOS000I 1065,AB,EQC,**,8200,,,*MASTER*, 461 1000A00000000046700000000000000000000000000000000000000000084000 *IRD000E 1065,002032-001 LEVEL=0 FRU(S)=PWR4 IOS000I 1065,AB,EQC,**,8200,,,*MASTER*, 496 1000A00000000046700000000000000000000000000000000000000000089000 *IRD000E 1065,002032-001 LEVEL=0 FRU
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.
Common FICON issues • • • • Undetermined board types cannot be swapped. For example, a blade swap will fail if the blade type cannot be identified. 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.
Maintaining and Troubleshooting FICON Symptom Probable cause and recommended action Packets are being dropped between two FICON units. 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 .
Maintaining and Troubleshooting FICON Symptom Probable cause and recommended action Channel path with two-byte addressing does not come online. 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.
Troubleshooting FICON Symptom Probable cause and recommended action SWITCH DEVICE NUMBER = NONE ATTACHED ND = NOT KNOWN PHYSICAL CHANNEL ID = 01F0 ************************ SYMBOL EXPLANATIONS ************************ + ONLINE @ PATH NOT VALIDATED OFFLINE . DOES NOT EXIST * PHYSICALLY ONLINE $ PATH NOT OPERATIONAL The responses "NOT ALL PATHS BROUGHT ONLINE" after attempting to configure the CHPID online and "FICON INCOMPLETE" in the display example indicate that the channel did not come online.
Switched point-to-point topology checklist you get confirmation that the configuration has been updated, ouput from the following will be collected and display for the supportShow command: • • • ‐ 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.
Cascaded topology checklist Cascaded topology checklist Verify the following in your FICON environment to ensure proper functionality of the feature: • • • • • • • • • • • • 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.
Troubleshooting NPIV • • • • • • 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. Ensure no device is plugged into port 254 on the Brocade DCX Backbone.
Platforms Supporting FICON ● Introduction..................................................................................................................... 99 ● Supported platforms with end-of-support announcements............................................. 99 ● Currently supported platforms.......................................................................................100 ● Supported Brocade blades............................................................................................
Currently supported platforms TABLE 10 Supported platforms with end-of-support announcements (Continued) Brocade 4900 Brocade 5000 Brocade 6140 Brocade i10K Brocade 7500 Brocade 48000 Brocade 5100 Fabric OS Fabric OS Fabric OS Fabric OS Fabric OS Fabric OS Fabric OS z10 EC & z10 BC Driver 76D & 79F v6.2.0e v6.2.0e v9.9.9 v9.9.8 v6.4.2a v6.4.2a v7.0.0d z10 BC Driver 76D v6.2.0e v6.2.0e v9.9.9 v9.9.8 v6.4.2a v6.4.2a v7.0.
Supported Brocade blades TABLE 11 Currently supported platforms (Continued) Brocade 7800, 7840 Brocade 5300 Brocade DCX-4S Brocade DCX Brocade Brocade Brocade DCX 8510-4 DCX 8510-8 6510 Fabric OS Fabric OS Fabric OS Fabric OS Fabric OS Fabric OS Fabric OS z196 Driver 86E or 93G v7.3.0 v7.3.0 v7.3.0 v7.3.0 v7.3.0 v7.3.0 v7.3.0 z114 Driver 93G v7.3.0 v7.3.0 v7.3.0 v7.3.0 v7.3.0 v7.3.0 v7.3.0 EC12 at driver 12K v7.3.0 v7.3.0 v7.3.0 v7.3.0 v7.3.0 v7.3.0 v7.3.
Unsupported blades Unsupported blades The following port blades are not supported in a FICON environment: • • • • • 102 FCOE10-24 FS8-18 FC4-48 FC8-32E FC8-48E FICON Administrator's Guide 53-1003144-01
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.
Basic Switch Configuration TABLE 13 Switch configuration example and commands (Continued) Feature Relevant Commands Repeat the following procedure to configure switch parameters for each logical switch. configure 1. 2. 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.
Basic Switch Configuration TABLE 13 Switch configuration example and commands (Continued) Feature Relevant Commands If you are enabling FMS (CUP), disable all ports assigned address 0xFE and 0xFF. portdisable Enable FMS if FICON CUP will be used. ficoncupset fmsmode enable ficoncupshow fmsmode NOTE High-integrity fabric requirements must be met and HIF mode enabled to enable FMS mode. Set the default zone for no access. defZone --noaccess cfgsave defZone --show Configure zones.
Basic Switch Configuration TABLE 13 Switch configuration example and commands (Continued) Feature Relevant Commands Set port fencing. Setting port fencing parameters is much easier with Brocade Network Advisor. 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.
Address Binding Examples ● Sequential address binding...........................................................................................107 ● Port-based address binding.......................................................................................... 112 ● Unbinding multiple ports................................................................................................
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.
Address Binding Examples # Slot 3 portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress # Slot 4 portaddress portaddress portaddress portaddress portaddress portaddress portaddress
Address Binding Examples portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress # Slot 10 portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddr
Address Binding Examples portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress # Slot 12 portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddr
Port-based address binding Port-based address binding This section provides an example that will allow all ports on all blades installed in a Brocade DCX Backbone to use port-based (Mode 2) addresses. The following figure illustrates ports with port-based addressing. FIGURE 27 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.
Address Binding Examples portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress # Slot 2 portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddre
Address Binding Examples portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress # Slot 4 portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddre
Address Binding Examples portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress # Slot 11 portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddr
Unbinding multiple ports portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress portaddress --bind --bind --bind --bind --bind --bind --bind --bind --bind --bind --bind --bind --bind --bind --bind --bind --bind --bind 12/14 12/15 12/16 12/17 12/18 12/19 12/20 12/21 12/22 12/23 12/24 12/25 12/26 12/27 12/28 12/29 12/30 12/31 7E00 7F00 F000 F100 F200 F300 F40
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).
Configuration Information Record 118 FICON Administrator's Guide 53-1003144-01
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.
EBCDIC Code Page 120 FICON Administrator's Guide 53-1003144-01
Index 256-area addressing mode 44 A addressing link and FC 30 modes 44 address mode changing 45 FICON and blade support 46 automating CS_CTL mapping 47 B best practices for configuring FICON 49 binding 26 blades not supported for FICON 102 blades supported for FICON 101 D disabling and enabling ports 46 disabling IDID modeenabling IDID mode 28 disabling the management server mode 28 displaying information 88 DLS 95 domain ID, insistent 11 downgrade considerations 77 Dynamic Load Sharing 95 E emulation
FICON support blades 101 blades not supported 102 platforms 100 firmware management 77 firmware upload and download 78 FMS mode disabling 58 displaying 58 enabling 58 Fabric OS command limitations 57 OxFE and OxFF addresses 58 resetting 58 upgrade considerations 59 FRU failures 89 G gathering additional information 95, 97 Global Mirror emulation 66 M MAPS 87 meeting QSA requirements 33 mode register bit considerations 63 mode register bits 60 Monitoring and Alerting Policy Suite 87 N node identificatio
S SCC policy creating and activating 34 deleting 36 security policy, create 41 security-related commands 36 session-based zoning enforcement 23, 79 single-switch configuration 36 swapping port area IDs important notes 91 switched point-to-point configuration 15 switch preparation 36 system data mover topology 83 T tape emulation 67 Tape Pipelining 72 Teradata emulation 70 Teradata statistics 75 triangular topology 81 troubleshooting NPIV 98 U unable to ’vary online’ 92 upgrade considerations 77 X XISL
124 FICON Administrator's Guide 53-1003144-01
