53-1001771-01 30 March 2010 FICON Administrator’s Guide Supporting Fabric OS v6.4.
Copyright © 2009-2010 Brocade Communications Systems, Inc. All Rights Reserved. Brocade, the B-wing symbol, BigIron, DCX, Fabric OS, FastIron, IronPoint, IronShield, IronView, IronWare, JetCore, NetIron, SecureIron, ServerIron, StorageX, and TurboIron are registered trademarks, and DCFM, Extraordinary Networks, and SAN Health are trademarks of Brocade Communications Systems, Inc., in the United States and/or in other countries.
Contents About This Document In this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii How this document is organized . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii Supported hardware and software . . . . . . . . . . . . . . . . . . . . . . . . . . viii What’s new in this document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii Document conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Chapter 2 Administering FICON Fabrics In this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 User security considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 Preparing a switch for FICON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 Cascaded FICON and 2-byte addressing considerations . . . . . 16 Configuring switched point-to-point FICON . . . . . . . . . . . . . . . . . . . . 16 Configuring Cascaded FICON . .
Configuration requirements for switches and directors . . . . . . . . . . 40 Configuration of sufficient buffer credits . . . . . . . . . . . . . . . . . . 41 High integrity fabric requirements for cascaded configurations41 FICON emulation requirement for a determinate path . . . . . . . 41 Cross-coupled configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 Configuring FICON emulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Appendix A Configuration Information Record Appendix B EBCDIC Code Page Index vi FICON Administrator’s Guide 53-1001771-01
About This Document In this chapter • How this document is organized . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii • Supported hardware and software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii • What’s new in this document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii • Document conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii • Notice to the reader . . . . . . . . . . .
Supported hardware and software In those instances in which procedures or parts of procedures documented here apply to some switches but not to others, this guide identifies exactly which switches are supported and which are not. Although many different software and hardware configurations are tested and supported by Brocade Communications Systems, Inc. for v6.4.0, documenting all possible configurations and scenarios is beyond the scope of this document.
italic text Provides emphasis Identifies variables Identifies paths and Internet addresses Identifies document titles code text Identifies CLI output Identifies command syntax examples 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.
CAUTION A Caution statement alerts you to situations that can be potentially hazardous to you. DANGER A Danger statement indicates conditions or situations that can be potentially lethal or extremely hazardous to you. Safety labels are also attached directly to products to warn of these conditions or situations. Key terms For definitions specific to Brocade and Fibre Channel, see the technical glossaries on Brocade Connect. See “Brocade resources,” for instructions on accessing Brocade Connect.
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 Brocade Connect website and are also bundled with the Fabric OS firmware. Other industry resources • White papers, online demos, and data sheets are available through the Brocade website at http://www.brocade.com/products/software.jhtml.
The serial number label is located as follows: • Brocade 300, 4100, 4900, 5100, 5300, 7500, 7800, 8000, VA-40FC, and Brocade Encryption Switch—On the switch ID pull-out tab located inside the chassis on the port side on the left • Brocade 5000—On the switch ID pull-out tab located on the bottom of the port side of the switch • • • • Brocade 7600—On the bottom of the chassis Brocade 48000—Inside the chassis next to the power supply bays Brocade DCX—On the bottom right on the port side of the chassis Broc
Chapter Introducing FICON 1 In this chapter • FICON overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 • FICON concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 • FICON configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 • Access Control in FICON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1 FICON overview • Insistent domain ID (IDID) Allows the switch to insist on a specific domain ID before joining a fabric. This feature guarantees that a switch operates only with its preassigned domain ID. • Link incident detection, registration, and reporting Provides administrative and diagnostic information. • Port swapping Redirects resources from a failed port to a healthy port without changing the mainframe hardware configuration definition (HCD) settings.
FICON overview 1 • Brocade 48000 director (FC4-16, FC4-32 port blades, FR4-18i FCIP blade and FC10-6 10 Gbps port blade for ISL connections). • Brocade 4100, 4900, 5000, 5100, and 5300 switches. • The Brocade 7500 and 7800 Extension Switches and Brocade the FR4-18i (for the Brocade 48000, DCX, and DCX-4S) and FX8-24 blade (for the Brocade DCX and DCX-4S) provide FICON over IP extension.
1 FICON concepts FICON concepts Figure 1 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 an LPAR (logical partition) and through the channel, through a Fibre Channel link to the switch through the control unit, and ending at the device.
FICON concepts 1 • Hardware Configuration Definition (HCD) HCD is an IBM interactive interface application that allows you to define the hardware configuration for both a processor's channel subsystem and the operating system running on the processor. • Information unit A unit of FICON data consisting of from one to four Fibre Channel frames.
1 FICON configurations • Systems Operations (SysOps) This provides the ability to monitor and control all subsystems in a sysplex from any system in the sysplex. This includes controlled startup, controlled shutdown, and automated recovery of software resources. • Sysplex In IBM mainframe computers, a Systems Complex, commonly called a sysplex, allows multiple processors to be joined into a single unit, sharing the same sysplex name and Couple Data Sets.
FICON configurations 1 Cascaded FICON Cascaded FICON refers to an implementation of FICON that involves one or more FICON channel paths defined over two FICON switches connected to each other using an Inter-Switch Link (ISL). The processor interface is connected to one switch, while the storage interface is connected to the other. This configuration is supported for both disk and tape, with multiple processors, disk subsystems, and tape subsystems sharing the ISLs between the directors.
1 Access Control in FICON Figure 4 and Figure 5 on page 8 show two cascaded configurations. These configurations require Channel A to be configured for 2-byte addressing and require IDID and fabric binding. It is recommended that there be only two domains in a path from a FICON Channel interface to a FICON Control Unit interface. There are exceptions to the two domain rule when extended fabric solutions are deployed, for example Brocade 7500 switches between the FICON Directors is allowed.
Access Control in FICON FIGURE 6 1 Simple cascaded zoning Figure 7 illustrates the multiple zoning concepts that can be used to restrict traffic. In Figure 7, any host channel at the Backup Site (connected to Director 11 or Director 12) can connect to the backup tape contained with the same zone. Notice that no more than a single hop is ever allowed and only Channel Path Identifiers (CHPIDs) 79 and 7A on the Primary Site can connect to the backup tape.
1 Access Control in FICON FIGURE 7 Complex cascaded zoning Blue Zone: Any CHPID connected to Director 1, except CHPID 79, can get to any control unit connected to Director 1. The zone includes all ports in Director 1 except ports 4, 5, and 6. Orange Zone B: Any CHPID connected to Director 2, except CHPID 7A, can get to any control unit connected to Director 2. The zone includes all ports in Director 2 except ports 4, 5, and 6.
Access Control in FICON 1 Error reporting Non-implicit (such as NOS 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 info) reports port errors, which in turn are also reported back to the mainframe host management consoles.
1 Access Control in FICON FIGURE 8 12 three types of binding FICON Administrator’s Guide 53-1001771-01
FICON commands 1 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 Data Center Fabric Manager and Web Tools software features. You can also use an SNMP agent and the FICON Management Information Base (MIB). Table 1 summarizes the Fabric OS CLI commands that can be used for managing FICON fabrics.
1 FICON commands TABLE 1 Fabric OS commands related to FICON (Continued) Command 14 Description ficonshow rnid [fabric] Displays node identification data for all devices registered with the local switch or all devices registered with all switches defined in the fabric, if specified. ficonshow switchrnid [fabric] Displays node identification data for the local switch or for the fabric, if specified.
Chapter 2 Administering FICON Fabrics In this chapter • User security considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Preparing a switch for FICON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Configuring switched point-to-point FICON . . . . . . . . . . . . . . . . . . . . . . . . . . • Configuring Cascaded FICON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • FICON and FICON CUP in Virtual Fabrics . . .
2 Configuring switched point-to-point FICON 5. Add feature keys, if applicable. 6. Perform a configUpload to save a baseline of the switch configuration. Cascaded FICON and 2-byte addressing considerations The following are considerations when installing a switch in a FICON environment where 2-byte addressing is used. Two-byte addressing is always used in cascaded environments but may be used in single switch fabrics as well. Making changes to your switch or director may require scheduled downtime.
Configuring switched point-to-point FICON 2 5. Set the routing policy to port-based routing by entering the aptPolicy command. The recommended best practice is to use exchange-based routing (aptPolicy 3); however, exchanged-based routing is only supported for FICON when Lossless DLS is enabled. If Lossless DLS is not enabled then port-based routing (aptPolicy 1) must be used.
2 Configuring switched point-to-point FICON TABLE 2 FICON switch parameters (Continued) Parameter Response Comment Per-frame route priority 0 Do not change. Long-distance fabric 0 Do not change. The recommended best practice is to configure individual ports for long distance when cascading at extended distances. BB credit 16 Do not change. This parameter has been deprecated. BB credit settings should be set on a per port basis.
Configuring switched point-to-point FICON 2 12. Enter the portCfgSpeed command to configure port speeds. By default, all ports are configured to auto-negotiate. Normally, the only time the port configuration is changed is when connecting to 1 Gbps ports. Some DWDM ports are known to not auto-negotiate well. Furthermore, although older 1 Gbps FICON channels log in correctly, they will generate errors, so the speed should be forced to 1 Gbps with 1 Gbps FICON channels.
2 Configuring Cascaded FICON Configuring Cascaded FICON In addition to performing the steps listed in “Configuring switched point-to-point FICON” on page 16, 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. 1. Enter the switchDisable command to disable each switch in the fabric. 2. Perform the following actions for each switch: a. Enable the IDID flag.
FICON and FICON CUP in Virtual Fabrics 2 FICON and FICON CUP in Virtual Fabrics There are three different addressing modes to provide extended functionality in dynamically created partitions. These are: • Fixed addressing mode • Flat addressing mode • Auto addressing mode Because flat addressing mode allocates 10-bit areas by default, auto-addressing mode is used to support FICON in dynamically created partitions. Use the fabric parameters of the configure command to enable this mode.
2 Clearing the FICON management database Clearing the FICON management database Perform the following steps to clear RLIR and RNID records from the FICON management database. 1. Connect to the switch and log in as admin. 2. Enter ficonClear rlir to remove all the RLIR records from the local RLIR database. 3. Enter ficonClear rnid to remove all the RNID records marked “not current” from the local RNID database.
Chapter 3 Configuring FICON CUP In this chapter • Control Unit Port (CUP) overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Port and switch naming standards for CUP . . . . . . . . . . . . . . . . . . . . . . . . . . • Configuring FICON CUP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Configuring FICON CUP in Virtual Fabrics . . . . . . . . . . . . . . . . . . . . . . . . . . . • Determining physical port assignment . . . . . . . . . .
3 Control Unit Port (CUP) overview FIGURE 9 FICON CUP Figure 9 is a simplified representation of a FICON environment and how CUP fits into that environment. FICON directors have the embedded port “FE” for the CUP port. On FICON directors that have 256 or more ports, this has caused a slight dilemma. This logical “FE” overlaps the physical “FE” port, so the physical “FE” and “FF” ports cannot be used on these directors for FICON connectivity.
Control Unit Port (CUP) overview 3 The addresses FE/FF are not components of the Allow/Prohibit Matrixes (as they are called in DCFM) or CUP Configurations (as they are referred to in WebTools), because the PDCMs for these two ports are defined architecturally and cannot be modified, FF being an unimplemented port and FE the internal port, whose PDCM must have no bits set, and cannot be modified.
3 Port and switch naming standards for CUP The configuration is saved to the initial program load (IPL) file. IPL is a more general term that refers to the process of loading an operating system into memory. The switch Active Configuration is replicated to the backup CP. This includes the port PDCM configuration, port block/unblock states, and port address names. If Active=Saved is enabled in the FMS Mode Register, then the Active Configuration is also replicated to the IPL file.
Configuring FICON CUP 3 Configuring FICON CUP To set up FICON CUP, use the following procedure and be sure to perform the steps in the order indicated. 1. Connect to the switch and log in using an account assigned to the admin role. 2. Verify that the switch or director has been set up according to the instructions in “Configuring switched point-to-point FICON” on page 16 and if in a cascaded topology, “Configuring Cascaded FICON” on page 20. 3.
3 Configuring FICON CUP in Virtual Fabrics 7. Take the appropriate action based on whether you have both B- and M-series switches in your fabric: • If you do not have both series, proceed to step 8. • If you have both series, establish a secure E_Port between the supported platforms. For B-series switches you can use SCC policies or EFCM v9.6. For M-Series switches use EFCM or DCFM. 8. Enter the ficonCupSet fmsmode enable command to enable FICON management server mode (FMS mode) on the switch. 9.
Determining physical port assignment 3 1. Connect to the switch and log in using an account assigned to the admin role. 2. Determine current logical switch configuration using the lsCfg --show command. 3. Define the new logical switch using the lsCfg --create command. 4. Enter the setContext command to set the context to the newly created logical switch. 5. Enter the configure command to configure the newly created logical switch. 6. Enter y at the Fabric Parameters prompt. 7.
3 FMS mode and FICON CUP 252 12 28 0x 1fc00 FMS mode and FICON CUP The FMS mode setting can be changed whether the switch is disabled or enabled and whether the switch has a FICON CUP license installed or not. If FMS mode is changed while the switch is enabled, a device reset is performed for the control device and an RSCN is generated with PID 0xDDFE00, where 0xDD is the domain ID of the switch.
FMS mode and FICON CUP 3 • Serialized access to switch parameters ceases. When a CUP license is installed, the transition from FMS mode disabled to FMS mode enabled triggers notification to the host systems that the CUP feature is available. Without this notification, the host systems never know that the CUP feature is available and, consequently, never try to communicate with it.
3 Mode register bit settings 6. Enter the ficonCupSet fmsmode enable command. 7. If you are configuring FICON CUP on a director, enter the haFailover command to ensure that FMS is enabled on both CPs. 8. Enter the ficonCupShow fmsmode command to verify if fmsmode is enabled. Mode register bit settings A mode register controls the behavior of the switch with respect to CUP itself, and with respect to the behavior of other management interfaces. The mode register bits are described in Table 4.
Mode register bit settings 3 FICON file access facility The FICON file access facility (FAF) is used to store configuration files. This includes the initial program load (IPL) and other configuration files. The Fabric OS saves the IPL and all other configuration files on the switch. A maximum of 16 configuration files, including the IPL file, are supported. You can upload the configuration files saved on the switch to a management workstation using the configUpload command.
3 Mode register bit settings Each FICON director in a fabric must have a unique domain ID and a unique switch ID. The switch ID used in the IOCP definitions can be any value between x’00’ to x’FF’. The domain ID range for directors is hex x'01' to x'EF' or decimal 1 to 239. When defining the switch IDs in the IOCP definitions, ensure that you use values within the FICON director’s range. The switch ID has to be assigned by the user and must be unique within the scope of the definitions (IOCP and HCD).
Setting the MIHPTO value 3 1. Connect to the switch and log in using an account assigned to the admin role. 2. Enter the ficonCupSet modereg command to set the FICON CUP mode register bits for the local switch. Example of setting the mode register bit HCP to off: switch:admin> ficoncupset modereg HCP 1 Mode register bit HCP has been set to 1. Example of setting the mode register bit ACP to on: switch:admin> ficoncupset modereg ACP 1 Mode register bit ACP has been set to 1.
3 Persistently enabling and disabling ports for CUP switch:admin> ficoncupset modereg ASM 1 Active=Saved Mode bit is set to 1. 5. Use the portEnable and portDisable commands to enable and disable ports as necessary. The ports remain enabled or disabled after a switch reboot.
Chapter 4 Administering FICON Extension Services In this chapter • FICON emulation overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • FCIP configuration requirements for FICON extension . . . . . . . . . . . . . . . . . • Configuration requirements for switches and directors . . . . . . . . . . . . . . . . • Configuring FICON emulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Modifying FICON emulation . . . . . . . . . . . . . . . .
4 FICON emulation overview XRC emulation The eXtended Remote Copy (XRC) application is a direct attached storage device (DASD) application that implements disk mirroring, as supported by the disk hardware architecture and a host software component called System Data Mover (SDM). Within this application a specific application channel program invokes a well constrained type of channel program called a Read Record Set (RRS) channel program.
FICON emulation overview 4 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.
4 FCIP configuration requirements for FICON extension FIGURE 12 Tape Read Pipelining Platforms supporting FICON extension over IP Fabric OS supports SAN extension between Brocade 7500 storage routers, or between FR4-18i blades. The Brocade 7500 and the FR4-18i blade both have 16 physical Fibre Channel ports and 2 physical GbE ports. FCIP configuration requirements for FICON extension FICON extension uses FCIP for transport.
Configuration requirements for switches and directors 4 Configuration of sufficient buffer credits The 7500 defaults to 8 BB credits per port. If the performance for a specific port is not sufficient for FICON, increasing the BB credits can improve performance. It is recommended that FICON ISLs or CHPID ports should be configured to 16 BB credits or greater.
4 Configuration requirements for switches and directors Traffic Isolation zoning The Traffic Isolation Routing feature may be used to control the flow of interswitch traffic through the Brocade 7500 SAN router or FR4-18i VE_Port or E_Port connections. This feature can be used with Allow/Prohibit settings on M-Series directors to create complete flow through paths between end points connected through M-Series and Fabric OS products.
Configuring FICON emulation 4 . FIGURE 14 Cross-coupled configuration 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, read “FICON emulation overview” on page 37. ATTENTION Make sure both ends of the tunnel match before bringing it up or the tunnel will not form. 1.
4 Configuring FICON emulation 8. If you have more than one tunnel being configured, take the following actions: • If there is more then one tunnel to the same destination and their tunnel commit rates are different, configure the link cost values the same. • Configure TI Zones ensuring that if there are multiple E_ports of different link costs, from one switch to another switch within TI zones, configure the link cost values to be the same.
Modifying FICON emulation 4 For a Brocade 7800 and FX8-24 blade, use the portShow fciptunnel command to determine the FICON emulation settings.
4 Displaying FICON emulation performance statistics 3. Use the command appropriate for your switch or blade model: • For the Brocade 7500 switch or FR4-18i, use the portCfg ficon modify command. • For the Brocade 7800 switch or FX8-24, use the portCfg fciptunnel modify command. 4. Make matching FICON emulation changes to both ends of the tunnel. 5. Enable the FCIP tunnel.
4 Displaying FICON emulation performance statistics For example, the value 2463016406050001 breaks down as follows. State VE HD HP DD DP LP CU DV 24 63 01 64 06 05 00 01 A value of zero indicates emulation is idle. Any non-zero value indicates emulation is active.
4 Displaying FICON emulation performance statistics |0x103B7C00|24B102B20F11092B|H| 0x00|0000|000F|0000|0F52| 46658|212| 25910| 16283| |0x104B4400|24B102B20F1109F7|H| 0x00|0000|000F|0000|0C42| 4159|147| 39379| 23225| |0x104B4800|24B102B20F1109F8|H| 0x00|0000|000F|0000|1112| 4038|147| 41523| 26894| |0x104B5400|24B102B20F1109F9|H| 0x00|0000|000F|0000|05E8| 4185|155| 38116| 22943| |0x104B5C00|24B102B20F1109FD|H| 0x00|0000|000F|0000|07E2| 3755|143| 40929| 24885| +----------+----------------+-+-----+
Chapter 5 Maintaining and Troubleshooting FICON In this chapter • Firmware management in a FICON environment . . . . . . . . . . . . . . . . . . . . . • Configuration restoration in a FICON environment . . . . . . . . . . . . . . . . . . . . • Traffic Isolation Zoning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Port Fencing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • FICON information . . . . . . . . . .
5 Configuration restoration in a FICON environment Firmware upgrade disruption Loading new firmware is a non-disruptive process except for the following: • During the firmware download process a failover to the backup processor occurs. Any outstanding CUP commands are lost and result in a time-out. 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.
Traffic Isolation Zoning 5 If fmsmode is enabled in a configuration file, but is disabled on the switch, the configDownload command fails and displays an error message. This prevents undesirable conditions that could result from enabling fmsmode on a switch that does not require it. Traffic Isolation Zoning Traffic Isolation (TI) Zoning allows data paths to be specified. In a FICON fabric you need Fabric OS v6.2.0 or later.
5 Traffic Isolation Zoning • • • • Brocade 5300 Brocade 7800 Brocade DCX Brocade DCX-4S Triangular topology The triangular topology shown in Figure 15 is a common FICON deployment for managing data center recovery functions. In this topology, a director is located in each of three sites and connected to the other two forming a triangle.
Traffic Isolation Zoning 5 To get around the multiple-hop issue, use Enhanced TI Zoning to prohibit the connection between E_Ports on the directors. For this setup you must define a device in two zones with failover disabled. Figure 16 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.
5 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 directors cascaded together using the System Data Mover (SDM) application. The storage differs between the sites. In the production site, the storage is DASD to support fast access for production applications.
Traffic Isolation Zoning FIGURE 18 5 System Data Mover topology using Enhanced TI Zones Figure 18 on page 55 shows the following Enhanced TI Zones definitions for the System Data Mover topology: • • • • Green zone includes Host A, ISL 1, and CU B. Orange zone includes CU A, ISL 2, and Host B. Red zone includes Host A and CU A. Blue zone includes Host B and CU B. Using these definitions with failover disabled achieves the desired behavior.
5 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.
Port Fencing 5 Figure 19 on page 56 shows the following Enhanced TI Zoning definitions for the emulation topology: • Green TI zone includes channel 0, ISL 80, ISL 81, Grid 1, and Grid 4. • Blue TI zone includes channel 1, ISL 82, ISL 83, and CU Grid-4. The unique characteristic of these zones is that each channel is defined with two control unit device ports and one of the control unit device ports, CU Grid-4, is in both zones.
5 FICON information • Low 0 • High 1,000 errors per minute FICON information You can display link incidents, registered listeners, node identification data, and FRU failures, as described in the following sections. Link incidents The registered link incident record (RLIR) ELS contains the link incident information sent to a listener N_Port.
Port swapping 5 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 Example of LIRR output: switch_4:FID4:admin> ficonshow lirr {Fmt Type PID Listener Port WWN 0x18 N c10100 50:05:07:64:01:ff:ff:01 0x18 N c10200 50:05:07:64:01:ff:ff:02 0x18 N c10300 50:05:07:64:01:ff:ff:03 Switch Port WWN 20:01:00:05:1e
5 Blade swapping 1. Connect to the switch and log in using an account assigned to the admin role. 2. Enter the portSwapEnable command to enable the command for port swapping. 3. Enter the portDisable command to disable the two ports to be swapped. 4. Enter the portSwap command to swap the ports. Any port in the switch can be used as the alternate for any other port within the same switch. 5. Re-enable the ports using the portEnable command. 6.
IU Pacing 5 • 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. NOTE This feature is not supported on the FX8-24 DCX Extension blade. For more information on blade swapping, refer to the Fabric OS Administrator’s Guide.
5 Common FICON issues Symptom Path to a device does not come online Probable cause and recommended action Make sure binding or zoning does not prevent the connection. Validate the following with the data center's system programmer: • Correct switch addresses (not switch IDs) are used in Link statements. Remember that the switch address is the domain ID converted to hex and may have an offset. • The Switch ID, used in the CHPID statements, was defined with the correct switch address.
Common FICON issues 5 When using multimode fiber, make sure that all fiber is either all 50u or all 62.5u. A common mistake is to mix 50u and 62.5u fiber cables, which causes errors at patch panels. Example of a Boxed Channel In this example, the customer complained that the CHPIDs with 2-byte addressing did not come online. He was instructed to configure the CHPID offline and then try to configure the CHPID back online.
5 Troubleshooting FICON R_A_TOV: (4000..120000) [10000] E_D_TOV: (1000..5000) [2000] WAN_TOV: (0..30000) [0] MAX_HOPS: (7..19) [7] Data field size: (256..2112) [2112] Sequence Level Switching: (0..1) [0] Disable Device Probing: (0..1) [0] Suppress Class F Traffic: (0..1) [0] Per-frame Route Priority: (0..1) [0] Long Distance Fabric: (0..1) [0] BB credit: (1..
Troubleshooting FICON 5 By default, the FICON group in the supportShow output is disabled. To enable the capture of FICON data in the supportShow output, enter the supportShowCfgEnable ficon command.
5 Troubleshooting FICON • Have you verified that no additional license is required to enable your FICON configuration? • Have you verified that your switch does not have a special mode setting turned on for FICON? NOTE There is no requirement to have a secure fabric in a switched point-to-point topology. Brocade Advanced features software package (Trunking, Fabric Watch, Extended Fabric) license activation is required.
Troubleshooting FICON CUP 5 Also refer to the most recent version of the Fabric OS Release Notes for notes on FICON setup and configuration. • Is this a switched point-to-point or cascaded environment? • Is the FICON group enabled for supportshow? Check at the top of the supportshow. If not, use supportShowCfgEnable ficon and re-run the test that was failing.
5 68 Troubleshooting FICON NPIV FICON Administrator’s Guide 53-1001771-01
Appendix A Configuration Information Record You can use the following worksheet for recording FICON configuration information.
A 70 Configuration Information Record FICON Administrator’s Guide 53-1001771-01
Appendix EBCDIC Code Page B 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 037 is an EBCDIC code page with full Latin-1-charset.
B 72 EBCDIC Code Page FICON Administrator’s Guide 53-1001771-01
Index A addressing modes, 21 B binding, 11 C cascade mode topology checklist, 66 cascaded configuration, 7 clearing the management database, 22 clearing the RLIR database, 13 configuration file fmsmode, 51 restoring in a FICON environment, 50 configuring switch, single, 15 Control Unit Port cannot access the switch, 63 CUP, 13, 23 D disabling IDID mode, 13 disabling the managment server mode, 13 displaying information, 58 DLS, 65 domain ID, insistent, 2 Dynamic Load Sharing, 65 E enabling IDID mode, 13
LIRR, 13 M mainframe RMF utility, 64 N node identification data, 59 node identification, display, 14 U unable to ’vary online’, 64 X XRC, 38 Z zoning and PDCM considerations, 13 P packets being dropped, 62 persistently enabling/disabling ports, 35 port and switch naming standards, 26 port swapping, 59 R recording configuration information, 33 registered listeners, 13, 59 RLIR clearing the database, 13 link incidents, displaying, 13 RNID node identification, 14 S security policy, create, 20 single-sw
