Brocade Communications Systems StoreFabric SN6500B Administrator's Manual
  1. Manuals
  2. Brands
  3. Brocade Communications Systems Manuals
  4. Storage
  5. StoreFabric SN6500B
  6. Administrator's manual

Brocade Communications Systems StoreFabric SN6500B Administrator's Manual

Brocade ficon administrator's guide v7.1.0 (53-1002753-01, march 2013)
Hide thumbs Also See for StoreFabric SN6500B:
Table of Contents

Advertisement

Quick Links

Download this manual See also: Troubleshooting Manual, Administrator's Manual
53-1002753-01
53-1002753-01
®
14 December 2012
FICON
Administrator's Guide
Supporting Fabric OS v7.1.0

Advertisement

Table of Contents
loading

Related Manuals for Brocade Communications Systems StoreFabric SN6500B

Summary of Contents for Brocade Communications Systems StoreFabric SN6500B

  • Page 1 53-1002753-01 53-1002753-01 ® 14 December 2012 FICON Administrator’s Guide Supporting Fabric OS v7.1.0...
  • Page 2 Copyright © 2009-2012 Brocade Communications Systems, Inc. All Rights Reserved. Brocade, the B-wing symbol, BigIron, DCX, Fabric OS, FastIron, NetIron, SAN Health, ServerIron, and TurboIron are registered trademarks, and Brocade Assurance, Brocade NET Health, Brocade One, CloudPlex, MLX, VCS, VDX, and When the Mission Is Critical, the Network Is Brocade are trademarks of Brocade Communications Systems, Inc., in the United States and/or in other countries.

  • Page 3: Table Of Contents

    Contents About This Document How this document is organized ......vii Supported hardware and software ......viii What’s new in this document .
  • Page 4 Chapter 2 Administering FICON Fabrics User security considerations ....... 17 Meeting Query Security Attribute requirements .
  • Page 5 Chapter 4 Administering FICON Extension Services Platforms supporting FICON extension over IP ....47 FICON emulation overview ....... . . 47 IBM z/OS Global Mirror emulation .
  • Page 6 Troubleshooting FICON ........76 General information to gather for all cases ....76 Switched point-to-point topology checklist.

  • Page 7: About This Document

    About This Document • How this document is organized ........vii •...

  • Page 8: Supported Hardware And Software

    • Appendix D, “Configuration Information Record” provides a form to record your FICON configuration information. • Appendix E, “EBCDIC Code Page” provides a table of the EBCDIC Code Page 37. Supported hardware and software Although many different software and hardware configurations are tested and supported by Brocade Communications Systems, Inc.

  • Page 9: Document Conventions

    • Removed restriction that XISLs cannot be configured. • Added instructions and restrictions on enabling XISL use and referenced Fabric OS Command Reference for details. Added section on FICON Best Practices. Added section on FICON link address and FC address. •...

  • Page 10: Command Syntax Conventions

    For readability, command names in the narrative portions of this guide are presented in mixed lettercase: for example, switchShow. In actual examples, command lettercase is often all lowercase. Otherwise, this manual specifically notes those cases in which a command is case sensitive.

  • Page 11: Key Terms

    CAUTION A Caution statement alerts you to situations that can be potentially hazardous to you. DANGER A Danger statement indicates conditions or situations that can be potentially lethal or extremely hazardous to you. Safety labels are also attached directly to products to warn of these conditions or situations.

  • Page 12: Other Industry Resources

    For additional Brocade documentation, visit the Brocade SAN Info Center and click the Resource Library location: http://www.brocade.com Release notes are available on the MyBrocade website and are also bundled with the Fabric OS firmware. Other industry resources White papers, online demonstrations, and data sheets are available through the Brocade website at http://www.brocade.com/products-solutions/products/index.page •...

  • Page 13: Document Feedback

    The serial number label on FICON-qualified devices is located as follows: • Brocade 5100, 5300, 7800, and 6510 — On the switch ID pull-out tab located inside the chassis on the port side on the left. • Brocade DCX 8510-8 and DCX - On the port side of the chassis, on the lower right side and directly above the cable management comb.
  • Page 14 FICON Administrator’s Guide 53-1002753-01...

  • Page 15: Chapter 1 Introducing Ficon

    Chapter Introducing FICON • FICON overview ..........1 •...
  • Page 16 FICON overview • Insistent (IDID) Disables the dynamic domain ID feature and only allows the switch to use a pre-set domain ID. All switches in a fabric must have a unique domain ID. An insistent domain ID is required with 2-byte addressing.

  • Page 17: Latency Guideline

    FICON concepts Latency guideline The maximum supported distance for a FICON channel is 300 Km (1.5 msec of delay). Synchronous mirroring applications are generally limited to 100 Km (0.5 msec of delay). Greater distances require that the FICON Acceleration feature be used with FCIP. The FICON Acceleration feature emulates control unit response to the channel to make the devices appear closer to the channel than they actually are.
  • Page 18 FICON concepts • FICON Control Unit Port (CUP) The internal port in a switch that assumes an FC address such that it is the FC DID used to direct FICON traffic to the FICON Management Server. • FICON Manager Host communication includes control functions such as blocking and unblocking ports, as well as monitoring and error-reporting functions.

  • Page 19: Ficon Configurations

    FICON configurations • Sysplex In IBM mainframe computers, a Systems Complex, commonly called a sysplex, allows multiple processors to be joined into a single unit, sharing the same sysplex name and Couple Data Sets. FICON configurations There are two types of FICON configurations that are supported using Brocade Fabric OS: switched point-to-point and cascaded topologies.

  • Page 20: Cascaded Ficon

    FICON configurations Cascaded FICON Cascaded FICON refers to an implementation of FICON that uses one or more FICON channel paths whereby the domain ID of the entry switch is different than the domain of the switch where the control unit is attached. Therefore, cascading requires a 2-byte link address. Any time a 2-byte link address is defined on a channel, all link addresses must be 2-byte link addresses.
  • Page 21 FICON configurations • The mainframes must be zSeries machines or System z processors: z196, z114, z800, 890, 900, 990, z9 BC, z9 EC, z10 BC, EC, and zEC12. Cascaded FICON requires 64-bit architecture to support the 2-byte addressing scheme. Cascaded FICON is not supported on 9672 G5/G6 mainframes.

  • Page 22: Access Control In Ficon

    Access control in FICON Access control in FICON Zoning is used to control access in a FICON environment. A zone consists of a group of ports or WWNs. Connectivity is permitted only between connections to the switch that are in the same zone. There are three types of zoning: WWN, port, and domain index zoning.
  • Page 23 Access control in FICON FIGURE 7 Complex cascaded zoning Blue Zone A: Any CHPID connected to Director 1, except CHPID 79, can get to any control unit connected to Director 1. The zone includes all ports in Director 1 except ports 4, 5, and 6. Orange Zone B: Any CHPID connected to Director 2, except CHPID 7A, can get to any control unit connected to Director 2.

  • Page 24: Error Reporting

    Access control in FICON Error reporting Non-implicit (such as Fabric OS recognized or bit error rate threshold exceeded) and implicit (FRU failure) link incidents are reported to registered listeners on the local switch. The RMF 74-7 record (FICON Director Activity Report, which is the same RMF Record containing the average frame pacing delay information) reports port errors, which in turn are also reported back to the mainframe host management consoles.
  • Page 25 Access control in FICON FIGURE 8 Three types of binding FICON Administrator’s Guide 53-1002753-01...

  • Page 26: Ficon Commands

    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).
  • Page 27 FICON commands TABLE 1 Fabric OS commands related to FICON (Continued) Command Description ficonclear rnid Removes all outdated RNID records from the local RNID database. ficoncfg set LIRR <portnumber> Sets the current LIRR device port number persistently. ficoncfg reset LIRR <portnumber> Clears the currently configured LIRR port number.

  • Page 28: Link And Fc Addressing

    Link and FC addressing Link and FC addressing To understand the addressing mode requirements and restrictions for FICON it is important to understand the relationship between the link address and the FC address. Understanding this relationship is also valuable for troubleshooting paths. Figure 9 represents components of link and FC addresses that are explained in this section.
  • Page 29 Link and FC addressing FICON protocol does not use the ALPA byte. However, the ALPA is a required byte in the FC address. The channel completes the FC address for a control unit link address by acquiring the ALPA that the switch returned to the channel when the channel logged in.
  • Page 30 Link and FC addressing FICON Administrator’s Guide 53-1002753-01...

  • Page 31: User Security Considerations

    Chapter Administering FICON Fabrics • User security considerations ........17 •...
  • Page 32 User security considerations Enabling insistent domain ID To enable Insistent Domain ID, follow these steps for each switch in the fabric: 1. Connect to the switch and log in using an account assigned to the admin role. 2. Enter the configure command and step through the interactive prompts. a.

  • Page 33: Preparing A Switch For Ficon

    Preparing a switch for FICON Deleting SCC_POLICY Enter the following command if you get messages that the E_Port in a security violation state. secpolicydelete "SCC_POLICY" Recovering the E_Port Enter the following commands for each switch if the E_Port is down. secpolicyactivate portenable n NOTE...

  • Page 34: Configuring Switched Point-To-Point Ficon

    Configuring switched point-to-point FICON Configuring switched point-to-point FICON This section provides detailed steps and commands to configure a switch for point-to-point FICON operation. The following steps assume that you have used your hardware reference manual to perform the initial setup of the switch and have performed all the steps from “Preparing a switch for FICON”...
  • Page 35 Configuring switched point-to-point FICON Configure the switch parameters using the configure command and enter the responses shown in Table 2 when prompted. (Items in italics are top-level parameters.) TABLE 2 FICON switch parameters Parameter Response Comment Fabric parameter Prompts for the fabric parameters. Domain The domain ID is the switch address.
  • Page 36 Configuring switched point-to-point FICON TABLE 2 FICON switch parameters (Continued) Parameter Response Comment Sequence level switching 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.
  • Page 37 Configuring switched point-to-point FICON TABLE 2 FICON switch parameters (Continued) Parameter Response Comment RSCN transmission mode 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 Parameters include Send FAN frames, Enable CLOSE on OPEN received, and Always send RSCN.
  • Page 38 Configuring switched point-to-point FICON 12. Enter the portCfgLongDistance command for ports with fiber connections exceeding 10 km. For ports with fiber connections exceeding 10 km, configuring the port for long distance mode increases the number of buffer-to-buffer (BB) credits available on that port. If you have any Extended Fabrics links, enable VC translation link initialization to stabilize them.

  • Page 39: Configuring Cascaded Ficon

    Configuring cascaded FICON Configuring cascaded FICON In addition to performing the steps listed in “Configuring switched point-to-point FICON” page 20, you also need to perform the following steps to configure cascaded FICON. CAUTION Configuring the switch for FICON is a disruptive process. The switch must be disabled to configure switch parameters.

  • Page 40: Ficon And Ficon Cup In Virtual Fabrics

    FICON and FICON CUP in Virtual Fabrics FICON and FICON CUP in Virtual Fabrics For FICON CUP, FICON Management Server (FMS) mode is enabled on the logical switch and not the chassis. For example, in a Virtual Fabrics environment on the Brocade 6510 switch and the Brocade DCX Backbones, enable CUP on each logical switch.

  • Page 41: Addressing Modes

    Addressing modes • If addresses 0xFE or 0XFF have been assigned to physical ports, those ports must be disabled before FMS can be enabled. • For FICON CUP, FMS mode is enabled on the logical switch and not the chassis. For example, in a Virtual Fabrics environment on the Brocade 6510 switch and the Brocade DCX 8510-4 and DCX 8510-8 Backbones, you must set FMS mode independently on each logical switch.

  • Page 42: Mode 2 (Port-Based Addressing)

    Addressing modes NOTE Although port addresses are assigned when moved to a logical switch, the address is not bound to the port. To ensure that the link address for a control unit attached to a port does not change, the portAddress command must be used to bind the address to the port even if you are not changing the port address assignments.

  • Page 43: Ficon And Blade Support For Addressing Modes

    Clearing the FICON management database 5. Enable FMS mode using the ficonCupSet fmsmode enable command. For more information on these Fabric OS commands, refer to the Fabric OS Administrator’s Guide. FICON and blade support for addressing modes Note the following considerations about FICON and blade support on logical switches in DCX systems: •...

  • Page 44: Automating Cs_Ctl Mapping

    Automating CS_CTL Mapping 3. Enter ficonClear rnid to remove all the RNID records marked “not current” from the local RNID database. Automating CS_CTL Mapping The CS_CTL-based frame prioritization feature allows you to prioritize the frames between a host and target as having high, medium, or low priority, depending on the value of the CS_CTL field in the FC frame header.

  • Page 45: Ficon Best Practices

    FICON best practices 5. Reboot the switch or chassis. 6. To verify if auto mode or default mode is set for the chassis, enter the configShow --all command as in the following example: root> configshow -all | grep fos.csctlMode fos.csctlMode:1 •...
  • Page 46 FICON best practices • Default switch Leave the default switch FID at 128. • Logical switches Always use a logical switch other than the default switch for FICON and do not disable virtual fabrics. • Cascading When cascading switches, connect ISLs so that a fabric forms before configuring switches for FICON.

  • Page 47: Configuring Ficon Cup

    Chapter Configuring FICON CUP • Control Unit Port overview........33 •...

  • Page 48: Ficon Cup Restrictions

    Control Unit Port overview FICON director CHPIDs FICON director Embedded port System Automation Embedded OS390 application port I/0-CPs FICON Switch Embedded port Management Application Server FIGURE 10 FICON CUP Figure 10 is a simplified representation of a FICON environment and how CUP fits into that environment.

  • Page 49: Cup Configuration Recommendations

    Control Unit Port overview ATTENTION Once FMS mode is enabled, you cannot bind FE/FF to any ports using either the portAddress or wwnAddress commands. • The switch is advertised to the mainframe by the CUP as having a specific number of ports, which is based on the hardware platform.

  • Page 50: Ficon Cup Zoning And Pdcm Considerations

    Port and switch naming standards for FMS mode NOTE Although 180 seconds should be the default value set on the switch when FMS is enabled, this value may not be set when older versions of Fabric OS are upgraded. This value must be set on the host system as well.

  • Page 51: Configuring Ficon Cup

    Configuring FICON CUP TABLE 4 Fabric OS commands related to FICON CUP Command Description ficonCupShow fmsmode Displays the FICON Management Server enabled or disabled state for the switch. ficonCupShow modereg Displays the mode register bit settings for the switch. Configuring FICON CUP To set up FICON CUP, use the following procedure and be sure to perform the steps in the order indicated.

  • Page 52: Disabling Ports 0Xfe And 0Xff

    Determining physical port assignment Disabling ports 0xFE and 0xFF Addresses 0xFE and 0xFF are not available for external connections, so they must be disabled to configure FICON CUP. Note that in logical switches or in cases where port address binding or port swapping has occurred, addresses 0xFE and 0xFF are not necessarily tied to specific physical ports, such as 254 and 255.

  • Page 53: Fms Mode And Ficon Cup

    FMS mode and FICON CUP For more information and example output from this command, refer to the Fabric OS Command Reference Manual. FMS mode and FICON CUP Enabling FICON Management Server (FMS) mode in a Fabric OS environment allows the switch to behave within the context of the FICON architecture and effectively creates a FICON director.

  • Page 54: Fabric Os Command Limitations And Considerations

    FMS mode and FICON CUP Fabric OS command limitations and considerations This section describes limitations and considerations for using Fabric OS commands with FMS mode enabled. For a list of Fabric OS commands related to FICON, refer to FICON commands •...

  • Page 55: Fms Mode And Ficon Oxfe Or Oxff Ports

    FMS mode and FICON CUP FMS mode and FICON OxFE or OxFF ports OxFE and OxFF are assigned to the CUP and cannot be associated with any physical port with FMS mode enabled. Therefore, note the following when using FMS mode: •...

  • Page 56: Port Swap Limitations

    Mode register bit settings After a nondisruptive upgrade from Fabric OS v6.4.0 to v7.0.0 or later, the following events occurs: NOTE These only occur on platforms released prior to Fabric OS v7.0.0. You can manage port connectivity using the Allow/Prohibit Matrix in Brocade Network Advisor and Web Tools.

  • Page 57: Ficon File Access Facility

    Mode register bit settings TABLE 5 FICON CUP mode register bits (Continued) Host control prohibited. When this bit is set on, the host is not allowed to set CUP parameters. The default setting is 0 (off). POSC Programmed offline state control. If the bit is set (=1), the command from the host will set the switch offline.
  • Page 58 Mode register bit settings Configuration files downloaded with Active=Saved mode disabled The contents of existing files saved on the switch, which are also present in the [FICU SAVED FILES] section, are overwritten. The files in the [FICU SAVED FILES] section of the configuration file, which are not currently on the switch, are saved on the switch.

  • Page 59: Setting The Mode Register Bits

    Setting the MIHPTO value PATH=(5A,5B), LINK=(25FE,25FE) IODEVICE ADDRESS=(0DB,1),CUNUMBR=0DB,UNIT=2032,STADET=Y,UNITADD=00 *------------------------------------------------------------------ Setting the mode register bits Consider the following when changing mode register bits: • The UAM bit can only be set by host programming. • All mode register bits except UAM are saved across power on/off cycles; the UAM bit is reset to 0 following a power-on.

  • Page 60: Persistently Enabling And Disabling Ports For Cup

    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.

  • Page 61: Platforms Supporting Ficon Extension Over Ip

    Chapter Administering FICON Extension Services • Platforms supporting FICON extension over IP ..... . . 47 • FICON emulation overview ........47 •...

  • Page 62: Ibm Z/Os Global Mirror Emulation

    FICON emulation overview The Advanced FICON Acceleration license contains the following options: Capacity 1 Consumed 1 Configured Blade Slots 1 This is a slot-based license for the Brocade FX8-24 and 7800. • Advanced Extension (FTR_AE) Required for multiple-circuit tunnels, FCIP Trunking, Adaptive Rate Limiting, and other FCIP features.

  • Page 63: Tape Emulation

    FICON emulation overview System z hosts IBM Z/OS global mirror system data mover Brocade extension switch with emulation for FICON Brocade Brocade IP network FICON FICON Directors Directors IP network Brocade extension switch with emulation for FICON Secondary disk Primary disk volumes volumes FIGURE 11...

  • Page 64: Tape Write Pipelining

    FICON emulation overview For information on configuring tape emulation, refer to “Configuring FICON emulation” on page 54. For information on displaying tape emulation status and statistics, refer to “Displaying FICON emulation performance statistics” on page 55. Tape Write Pipelining FICON Tape Write Pipelining (refer to Figure 12)improves performance for a variety of applications when writing to tape over extended distances.

  • Page 65: Printer Emulation

    FICON emulation overview System z Virtual Tape hosts Brocade Brocade Controller extension switch Tape FICON extension blade Library Director(s) with emulation with emulation for FICON for FICON IP network Read command Read emulation indication Local host held off with command retry awaiting read data to be delivered sent to remote Read command...

  • Page 66: Teradata Emulation

    FCIP configuration requirements for FICON extension • Intermediate ending status as appropriate to prevent FlCON channel protocol timeout (PTOV) expirations. • Acceptance of device status as required to prevent FICON control unit PTOV expirations. • Prevention of “clutching” during print jobs. For information on configuring printer emulation, refer to “Configuring FICON emulation”...

  • Page 67: High Integrity Fabric Requirements For Cascaded

    Configuration requirements for switches and Backbones • When running FICON emulation features over an FCIP tunnel, it is highly recommended that both switches providing the FCIP tunnel are using the same Fabric OS release level. High integrity fabric requirements for cascaded configurations You can use extended FICON connections between or through Brocade 7800 Extension Switches or FX8-24 blade to create a cascaded FICON switched configuration.

  • Page 68: Configuring Ficon Emulation

    Configuring FICON emulation Configuring FICON emulation Before you configure FICON emulation, you need to understand the available options, and whether those options are to be implemented in your installation. If FICON emulation is new to you, refer to “FICON emulation overview” on page 47.

  • Page 69: Displaying Ficon Emulation Configuration Values

    Modifying FICON emulation portcfg fciptunnel 23 modify --ficon-tape-write 1 --ficon-tape-read 1 portcfg fciptunnel 23 modify --ficon-print 1 Note that the preceding commands assume that an FCIP tunnel was a enabled for FICON operation by using the --ficon option. Following are two examples: •...

  • Page 70: Ficon Emulation Monitoring

    Displaying FICON emulation performance statistics Refer to “FICON emulation monitoring” on page 56, “+------------+----------------+-+-----+----+----+----+----+-----------+---+------+------+------+” on page 58, and the Fabric OS Command Reference Manual for information on command formats that you can use to display various FICON statistics. FICON emulation monitoring Use examples in this section to display emulation monitoring for extension blades and switches.
  • Page 71 Displaying FICON emulation performance statistics Emulation statistics example Following is a tape and XRC statistics output example for the 7800 switch and FX8-24 blade. root> portshow xtun 17 -ficon -emultape TAPE EMULATION STATS +------------+----------------+-+-----+----+----+----+-----------+----------+------+----------+--+ FDCB Ptr Path |H|State|Emul|Emul|Rtry| Emulated |Emulated |RdAvg |Emulated |WtAvg (0x)

  • Page 72: Options For Displaying Statistics On 7800 Switches And Fx8-24 Blades

    Displaying FICON emulation performance statistics |0x04100ED980|116300640006003B|H| 0x00|0000|0003|0000|0001| 1| 58864| |0x04100DD100|1163006400060043|H| 0x00|0000|0003|0000|0001| 1| 58864| |0x04100E2000|1163006400060047|H| 0x00|0000|0003|0000|0001| 1| 58864| |0x04100E7100|1163006400060057|H| 0x00|0000|0003|0000|0001| 1| 58864| |0x04100ECC80|116300640006005F|H| 0x00|0000|0003|0000|0001| 1| 58864| +------------+----------------+-+-----+----+----+----+----+-----------+---+------+------+------+ Options for displaying statistics on 7800 switches and FX8-24 blades Use options for the portshow xtun <slot/>ve_port -ficon -stats command to view statistics and monitor the behavior of FICON emulation on 7800 switches and FX8-24 blades.

  • Page 73: Maintaining And Troubleshooting Ficon

    Chapter Maintaining and Troubleshooting FICON • Firmware management in a FICON environment ..... 59 • Configuration restoration in a FICON environment ....61 •...

  • Page 74: Firmware Upgrade Disruption

    Firmware management in a FICON environment Firmware upgrade disruption Loading new firmware is a non-disruptive process except for the following cases: • During the firmware download process a failover to the backup processor occurs. Any outstanding CUP commands are lost and result in a timeout. To avoid this, CUP should be varied offline before starting a firmware download.

  • Page 75: Configuration Restoration In A Ficon Environment

    Configuration restoration in a FICON environment Configuration restoration in a FICON environment If the switch is operating in a FICON CUP environment, and the ASM (Active=Saved) bit is set on, then the switch ignores the IPL file downloaded when you restore a configuration. Table 7 describes this behavior in more detail.

  • Page 76: Determining Ports For The Ti Zone

    Traffic Isolation Zoning Determining ports for the TI Zone To find the device ports, use the MVS display command. The following example will display the paths to device 1002 and where it is connected: D M=DEV(1002) Response is: DEVICE 1002 STATUS=OFFLINE ENTRY LINK ADDRESS 6715 6808 6679...
  • Page 77 Traffic Isolation Zoning Channel Flow A Flow B ISL 1 ISL 2 ISL 3 Flow C CU A CU B FIGURE 15 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.
  • Page 78 Traffic Isolation Zoning Channel Flow A Flow B ISL 1 ISL 2 ISL 3 Flow C CU A CU B FIGURE 16 Triangular topology with Enhanced TI Zones Figure 16 shows the following TI Zone definitions for the triangular topology: •...
  • Page 79 Traffic Isolation Zoning System Data Mover topology Figure 17 shows a cascaded topology which can be used to support an operations recovery site. In this environment, host and storage systems exist at both sites, which are connected by two switches cascaded together using the System Data Mover (SDM) application. The storage differs between the sites.
  • Page 80 Traffic Isolation Zoning FIGURE 18 System Data Mover topology using Enhanced TI Zones Figure 18 on page 66 shows the following Enhanced TI Zones definitions for the System Data Mover topology: • Green Zone includes Host A, ISL 1, and CU B. •...
  • Page 81 Traffic Isolation Zoning Emulation topology FICON device emulation topologies have unique requirements due to the characteristics of the emulation devices. Each device must track the emulated sessions and maintain the state of the emulated devices in order to satisfy both ends of the connection. Since this is done over very long distances, care must be taken when configuring the ISL connections to insure that the sessions remain along exclusive paths.
  • Page 82 Traffic Isolation Zoning CPU1 Grid 1 Grid 4 TI Zone 1 TI Zone 2 FIGURE 19 Emulation topology using Enhanced TI Zones Figure 19 on page 68 shows the following Enhanced TI Zoning definitions for the emulation topology: • Green TI Zone includes channel 0, ISL 80, ISL 81, Grid 1, and Grid 4. •...

  • Page 83: Port Fencing

    Port fencing Port fencing Occasionally, bad optics and cables can cause errors to occur at a rapid rate that error processing and sending and processing RSCNs can cause fabric performance problems. Port fencing allows the user to limit the number of errors a port can receive by forcing a port offline when certain error thresholds are met.

  • Page 84: Registered Listeners

    FICON information To display link incidents, connect to the switch, log in as user, and enter one of the following commands: • For the local switch: ficonShow rlir • For all switches defined in the fabric: ficonShow rlir fabric Identifying ports The ficonShow rlir command displays, among other information, a tag field for the switch port.

  • Page 85: Fru Error Reporting

    FICON information • For all switches defined in the fabric: ficonShow switchrnid fabric • For all devices registered with the local switch: ficonShow rnid • For all devices registered with all switches defined in the fabric: ficonShow rnid fabric FRU error reporting FRU failure information is no longer stored on the switch.

  • Page 86: Swapping Port Area Ids

    Swapping port area IDs FRU numbers Following are the Brocade FRU numbers provided for error reports and associated FRU names that display in error reports. Note that the FRU number does not actually display in the error reports, but its associated FRU name does display. •...

  • Page 87: Important Notes

    Blade swapping Important notes Consider the following when swapping port area IDs: • Ports that have been swapped cannot be moved to another logical switch. • Ports with area OxFE or OxFF addresses cannot be swapped when FMS mode is enabled. •...

  • Page 88: Common Ficon Issues

    Common FICON issues Common FICON issues Any information you need to verify that FICON has been set up correctly can be found in the Chapter 2, “Administering FICON Fabrics” Chapter 3, “Configuring FICON CUP”. Symptom Cascading: No path – Entry Link is “..” Probable cause and recommended action This typically occurs when one or more of the required high integrity features for cascading have not been met.
  • Page 89 Common FICON issues Symptom Channel path with 2-byte addressing does not come online Probable cause and recommended action Ask the operator what CHPID he is attempting to bring online. In FICON environments, only the egress ports are defined in the IOCDS. The CHPID number of the channel appears in the node list, but only if the channel path has logged in.

  • Page 90: Troubleshooting Ficon

    Troubleshooting FICON + ONLINE @ PATH NOT VALIDATED - OFFLINE . DOES NOT EXIST * PHYSICALLY ONLINE $ PATH NOT OPERATIONAL The responses “NOT ALL PATHS BROUGHT ONLINE” after attempting to configure the CHPID online and “FICON INCOMPLETE” after the display command indicate that the channel did not come online.

  • Page 91: Switched Point-To-Point Topology Checklist

    Troubleshooting FICON 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, the following will be collected and appear in the output for the supportShow command: ficonCupShow fmsmode ficonCupShow modereg...

  • Page 92: Cascaded Topology Checklist

    Troubleshooting FICON • Have you verified that your switch does not have a special mode setting turned on for FICON? NOTE There is no requirement to have a secure fabric in a switched point-to-point topology. Brocade Advanced features software package (Trunking, Fabric Watch, Extended Fabric) license activation is required.

  • Page 93: Troubleshooting Ficon Cup

    Troubleshooting FICON CUP Also refer to the most recent version of the Fabric OS Release Notes for notes on FICON setup and configuration. • Is this a switched point-to-point or cascaded environment? • Is the FICON group enabled for supportshow? Check at the top of the supportshow.
  • Page 94 Troubleshooting NPIV FICON Administrator’s Guide 53-1002753-01...

  • Page 95: Appendix A Platforms Supporting Ficon

    Appendix Platforms supporting FICON This appendix provides the following support details on the following: • Brocade products with end of support announcements supported for FICON for different IBM systems and drivers (Table • Brocade products currently supported for FICON for different IBM systems and drivers (Table 9 on page 82).

  • Page 96: Currently Supported Platforms

    Currently supported platforms Currently supported platforms Table 9 lists Brocade products currently supported for Fabric OS v7.1.0 for various IBM systems and drivers. TABLE 9 Currently supported platforms Brocade 7800 Brocade 5300 Brocade DCX-4S Brocade DCX Brocade DCX 8510-4 Brocade DCX 8510-8 Brocade 6510 Fabric OS Fabric OS...

  • Page 97: Unsupported Blades

    Supported Brocade blades The IP ports of an FX8-24 extension blade can operate with another FX8-24 or 7800. The maximum number of FX8-24 blades supported in a chassis it four. An FX8-24 can operate with an FX8-24E; however, IPSEC and compression is only supported on one 10G IP port on the FX8-24.
  • Page 98 Supported Brocade blades FICON Administrator’s Guide 53-1002753-01...

  • Page 99: Appendix B Basic Switch Configuration

    Appendix 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 switch point-to-point and cascaded FICON operation, refer to Chapter 2, “Administering FICON Fabrics”.
  • Page 100 Basic Switch Configuration TABLE 11 Switch configuration example and commands Feature Relevant Commands Upgrade code (if necessary) firmwaredownload firmwareshow Feature keys (add licenses) licenseadd licenseshow Create all logical switches and add all intended ports to each logical switch. lscfg Set switch offline switchdisable Repeat the following procedure to configure switch parameters for each configure...
  • Page 101 Basic Switch Configuration TABLE 11 Switch configuration example and commands Feature Relevant Commands If you are enabling FMS (CUP), disable all ports assigned address 0xFE and portdisable 0xFF. Enable FMS if FICON CUP will be used. ficoncupset fmsmode enable ficoncupshow fmsmode Set the default zone for no access.
  • Page 102 Basic Switch Configuration Parameters in Table 12 are only required when 2-byte link addressing is used in the IOCP. Normally, these parameters are not set when single-byte addressing is used. TABLE 12 Cascading (2-byte addressing) example and commands Feature Parameter Add members to the SCC Policy.

  • Page 103: Appendix C Address Binding Examples

    Appendix Address Binding Examples This appendix provides examples for the following: • “Sequential address binding” • “Zero-Based to Port-Based Address Binding” • “Unbinding Multiple Ports” Example scripts containing the portaddress --bind and portaddress --unbind commands are included for binding or unbinding ports on all blades installed in a chassis. Sequential address binding This section provides an example of ensuring that all ports on blades installed in a Brocade DCX Backbone that are set with zero-based addressing are bound to sequential addresses as illustrated...

  • Page 104: Example Scripts For Binding Ports

    Sequential address binding Example scripts for binding ports Following are example scripts that bind all ports on the DCX Backbone to sequential addresses. You can copy these scripts and paste directly into a Telnet Fabric OS command line session. If a port does not exist, an error message will be reported, but this has no effect.
  • Page 105 Sequential address binding portaddress --bind 2/18 3200 portaddress --bind 2/19 3300 portaddress --bind 2/20 3400 portaddress --bind 2/21 3500 portaddress --bind 2/22 3600 portaddress --bind 2/23 3700 portaddress --bind 2/24 3800 portaddress --bind 2/25 3900 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...
  • Page 106 Sequential address binding portaddress --bind 4/12 6C00 portaddress --bind 4/13 6D00 portaddress --bind 4/14 6E00 portaddress --bind 4/15 6F00 portaddress --bind 4/16 7000 portaddress --bind 4/17 7100 portaddress --bind 4/18 7200 portaddress --bind 4/19 7300 portaddress --bind 4/20 7400 portaddress --bind 4/21 7500 portaddress --bind 4/22 7600 portaddress --bind 4/23 7700 portaddress --bind 4/24 7800...
  • Page 107 Sequential address binding 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...
  • Page 108 Sequential address binding # 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...

  • Page 109: Zero-Based To Port-Based Address Binding

    Zero-Based to Port-Based Address Binding Zero-Based to Port-Based Address Binding This section provides an example for binding all ports set with zero-based addressing to port-based addresses on all blades installed in a Brocade DCX Backbone. Figure 20 illustrates all ports with port-based addressing.
  • Page 110 Zero-Based to Port-Based Address Binding portaddress --bind 1/13 0D00 portaddress --bind 1/14 0E00 portaddress --bind 1/15 0F00 portaddress --bind 1/16 8000 portaddress --bind 1/17 8100 portaddress --bind 1/18 8200 portaddress --bind 1/19 8300 portaddress --bind 1/20 8400 portaddress --bind 1/21 8500 portaddress --bind 1/22 8600 portaddress --bind 1/23 8700 portaddress --bind 1/24 8800...
  • Page 111 Zero-Based to Port-Based Address Binding portaddress --bind 3/7 2700 portaddress --bind 3/8 2800 portaddress --bind 3/9 2900 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...
  • Page 112 Zero-Based to Port-Based Address Binding portaddress --bind 9/1 4100 portaddress --bind 9/2 4200 portaddress --bind 9/3 4300 portaddress --bind 9/4 4400 portaddress --bind 9/5 4500 portaddress --bind 9/6 4600 portaddress --bind 9/7 4700 portaddress --bind 9/8 4800 portaddress --bind 9/9 4900 portaddress --bind 9/10 4A00 portaddress --bind 9/11 4B00 portaddress --bind 9/12 4C00...
  • Page 113 Zero-Based to Port-Based Address Binding 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/0 6000 portaddress --bind 11/1 6100 portaddress --bind 11/2 6200 portaddress --bind 11/3 6300 portaddress --bind 11/4 6400 portaddress --bind 11/5 6500 portaddress --bind 11/6 6600...

  • Page 114: Unbinding Multiple Ports

    Unbinding Multiple Ports 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 Unbinding Multiple Ports This section provides example scripts for unbinding all addresses on an 8-slot chassis that is fully populated with 32 port cards.

  • Page 115: Appendix D Configuration Information Record

    Appendix Configuration Information Record You can use the following worksheet (Table 13) for recording FICON configuration information. TABLE 13 FICON configuration worksheet ® FICON Switch Configuration Worksheet ® FICON Switch Manufacturer:___________________Type: _________ Model: ______ S/N: ________ HCD Defined Switch ID_________(Switch ID) Cascaded Directors No _____Yes _____ FICON ®...
  • Page 116 Configuration Information Record FICON Administrator’s Guide 53-1002753-01...
  • Page 117 Appendix 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-charset. FICON Administrator’s Guide 53-1002753-01...
  • Page 118 EBCDIC Code Page FICON Administrator’s Guide 53-1002753-01...
  • Page 119 Index Numerics 256-area addressing mode disabling IDID mode disabling the management server mode displaying information domain ID, insistent address mode Dynamic Load Sharing changing FICON and blade support addressing link and FC modes enabling IDID mode automating CS_CTL mapping extended interswitch link (XISL) extension configuration requirements DASD application...
  • Page 120 FICON emulation configuring on 7800 and FX8-24 displaying configuration values meeting QSA requirements IBM z/OS Global Mirror modifying overview printer statistics node identification data tape node identification, display Teradata FICON extension platform support FICON support blades blades not supported platforms Optica Prizm support firmware upload and download OxFE and OxFF addresses for FMS mode...
  • Page 121 SCC policy security policy, create security-related commands session-based zoning enforcement single-switch configuration swapping port area IDs important notes switch preparation switched point-to-point configuration tag field, interpreting tape emulation Tape Pipelining Teradata emulation Teradata statistics troubleshooting NPIV unable to ’vary online’ XISL zoning and PDCM considerations FICON Administrator’s Guide...
  • Page 122 FICON Administrator’s Guide 553-1002753-01...

This manual is also suitable for:

Ficon

Table of Contents