Front cover Getting Started with the McDATA Intrepid FICON Director Product, planning, and implementation information Realistic considerations and suggestions Helpful configuration examples Bill White Wolfgang Fries Manfred Lindenau ibm.
International Technical Support Organization Getting Started with the McDATA Intrepid FICON Director April 2003 SG24-6857-00
Note: Before using this information and the product it supports, read the information in “Notices” on page v. First Edition (April 2003) This edition applies to firmware version 4.1.0 (Build 12) of McDATA Intrepid FICON Director. © Copyright International Business Machines Corporation 2003. All rights reserved. Note to U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
Contents Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .v Trademarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vi Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The team that wrote this redbook. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.2 Activating the High Integrity feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.3 Enabling the Control Unit Port (CUP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.4 Building a fabric. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.4.1 Switch Binding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.
Notices This information was developed for products and services offered in the U.S.A. IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used.
Trademarks The following terms are trademarks of the International Business Machines Corporation in the United States, other countries, or both: ESCON® FICON™ IBM® IBM eServer™ OS/390® Perform™ Redbooks™ Redbooks(logo)™ S/390® SP™ Wave® z/OS™ zSeries™ Lotus® Word Pro® The following terms are trademarks of other companies: ActionMedia, LANDesk, MMX, Pentium and ProShare are trademarks of Intel Corporation in the United States, other countries, or both.
Preface This IBM Redbook discusses how to install, tailor, and configure the McDATA Intrepid FICON Director, in conjunction with the FICON topologies supported by zSeries and 9672 Generation 5 and Generation 6 servers. It focuses on the hardware installation as well as the software definitions needed to provide connectivity for supported FICON environments. This redbook provides planning information and FICON Director setup information.
Become a published author Join us for a two- to six-week residency program! Help write an IBM Redbook dealing with specific products or solutions, while getting hands-on experience with leading-edge technologies. You'll team with IBM technical professionals, Business Partners and/or customers. Your efforts will help increase product acceptance and customer satisfaction. As a bonus, you'll develop a network of contacts in IBM development labs, and increase your productivity and marketability.
1 Chapter 1. Introduction McDATA Intrepid FICON Directors are a product of a reseller agreement between IBM and McDATA Corporation. They are designed to provide enterprise-class availability and Fibre Channel connectivity for IBM servers and storage products supporting Fibre Channel (FC) and FICON protocols. The intent of this chapter is to provide background information about the zSeries FICON environment in which McDATA Intrepid FICON Directors are deployed.
1.1 Basic Fibre Channel terminology This section discusses some general terms used in the Fibre Channel (FC) environment. These terms are also used in FICON environments when installing, configuring, and operating in a switched point-to-point or cascaded FICON Director configuration, therefore, you will find these terms throughout this document. Node A node is an endpoint that contains or uses information.
FC port FC port Tx Rx Outbound Inbound Outbound Tx Inbound Rx Fibre Channel link Figure 1-1 Fibre Channel Link An FC link (port-to-port connection) can be: Node-to-node (N_Port-to-N_Port) Node-to-switch (N_Port-to-F_Port) Switch-to-switch (E_Port-to-E_Port) The FC link data rate is 1 Gbps (100 MBps) for zSeries and 9672 G5/G6 FICON feature ports, and 1 Gbps or 2 Gbps (200 MBps) for zSeries FICON Express feature ports.
Server (Node) WWNN1 Controller (Node) WWNN3 WWPN11 WWPN31 Switch (Node) WWNN2 N_Port N_Port WWPN22 WWPN21 F_Port F_Port F_Port F_Port WWPN23 WWPN24 N_Port WWPN12 N_Port WWPN32 Figure 1-2 Example of World-Wide Names 1.2 FICON overview There are a number of characteristics and functional areas that need to be understood in designing an I/O configuration that exploits FICON technology. This section introduces the basics of these areas for the FICON channel. 1.2.
Describes the signaling protocol of the high-performance serial link for support of higher-level protocols associated with HIPPI, IPI, FC-FCP (SCSI), FC-SB2 (FICON) and others. This architecture covers the Fibre Channel levels FC-1, FC-2, and some parts of the FC-3 level. The FC-FS architecture consolidates the relevant clauses of FC-PH (the initial Fibre Channel architecture), its amendments 1 and 3, and FC-PH-2 and FC-PH-3 protocols, but does not replace those protocols.
Note: The 9672 G5/G6 processors only support a single switch topology, known as switched point-to-point, whereas, the zSeries processors support single and dual switch topologies. A two-switch configuration is known as cascaded FICON Directors.
Channels and control unit links can be attached to the Fibre Channel switch in any combination, depending on configuration requirements and available resources in the Fibre Channel switch.
1.3.2 Cascaded FICON Director configuration In a cascaded FICON Director connection, at least three Fibre Channel (FC) links are needed in the channel-control unit path. One is between the FICON channel card (N_Port) and the FICON Director port (F_Port), then internally within the switch (through the backplane) to another port (E_Port) that connects to the second FICON Director E_Port via the second FC link, and then to a FICON adapter card in the control unit (N_Port) via the third FC link.
The communication path between a channel and a control unit is composed of two different parts, the physical channel path and the logical path. In a cascaded FICON Director topology, the physical paths are the FC links that provide the physical transmission path between a FICON channel and a control unit. A FICON (FC-SB-2) logical path is the relationship established between a FICON channel image and a control unit image for communication during execution of an I/O operation and presentation of status.
This support will not allow a switch address to be automatically changed when a duplicate switch address is added to the enterprise fabric. It requires overt operator action to change a switch address. Note: FICON Directors in a cascaded configuration require the High-Integrity feature . For more detailed information about FICON planning, implementation, and architecture, refer to FICON Native Implementation and Reference Guide, SG24-6266.
2 Chapter 2. Technical description This chapter provides a technical description for the McDATA Intrepid FICON Directors; included are: McDATA Intrepid FICON Director overview Hardware components Model configurations Software features: – Enterprise Fabric Connectivity Manager – High Integrity feature – Control Unit Port © Copyright IBM Corp. 2003. All rights reserved.
2.1 Introduction to the FICON Director This section provides an overview of the McDATA Intrepid FICON Directors and discusses the hardware components, models, configuration, and software. 2.1.1 FICON Director overview The McDATA Intrepid models implement Fibre Channel technology that provides high-performance scalable bandwidth, high available operation, and redundant switched data paths that support FICON-attached servers and storage devices.
Note: Protocol intermix is not supported by zSeries servers at this time. However, it is expected to be available during the first half of 2003. Interconnection With firmware version 4.1.0 (Build 12) and above, the McDATA Intrepid FICON Directors support High-Integrity Fabric (Feature Code 6006 for the Intrepid 6064 or Feature Code 6007 for the Intrepid 6140), which is required for cascaded FICON Directors configuration. 2.1.
Maintenance port FPM or UPM card SBAR Assembly CTP or CTP2 cards Power Supply Figure 2-1 Example of EFC Manager Hardware view of an Intrepid 6064 Director 2.1.3 EFC Server hardware requirements The following list summarizes hardware specifications for the EFC Server notebook platform. Current platforms may ship with more enhanced hardware such as a faster processor, additional random-access memory (RAM), or a higher-capacity hard drive or removable disk drive.
An EFC Server failure does not affect port connections or functions of an operational Director. The only operating affect of a server failure is loss of remote access, configuration, management, and monitoring functions. Chapter 4, “Setting up the EFC Server environment” on page 35, and Chapter 5, “Configuring the FICON Director” on page 45 discuss the EFC Manager functions in more detail. 2.1.
Note: Director firmware is upgraded concurrently (without disrupting operation). The backup CTP card takes over operation if the active card fails. Failover from a faulty card to the backup card is transparent to attached devices. Each card faceplate contains a green LED that illuminates if the card is operational and active, and an amber LED that illuminates if the card fails. Both LEDs are extinguished on an operational backup card. The amber LED blinks if FRU beaconing is enabled.
Fan Module Two Fan Modules, each containing three fans, provide cooling for the Director FRUs, as well as redundancy for continued operation if a fan fails. A Fan Module can be replaced while the Director is powered on and operating. An amber LED illuminates if one or more fans fail or rotate at insufficient angular velocity. Attention: A failing Fan Module must be replaced within ten minutes after its removal, otherwise, internal software will power off the Director.
McDATA Intrepid FICON Directors Intrepid 6064 Intrepid 6140 Figure 2-2 McDATA Intrepid FICON Director models The Directors come standard with all high-availability features in the base unit. You need only to select the number and type of port cards, the rack-mounting brackets (for factory or field installation in an FC-512 cabinet), and the power cord. The Director’s high-availability configuration offers redundancy and maintenance capabilities such as: All active components are redundant.
During channel initialization (if connected to a cascaded environment) the high integrity feature will be checked to ensure Enterprise Fabric Mode is enabled, by using a new command (Query Security Attributes). If this feature is not present or enabled, channel initialization will not continue. Section 5.2, “Activating the High Integrity feature” on page 48, describes how to establish Fabric Binding. 2.1.
20 Getting Started with the McDATA Intrepid FICON Director
3 Chapter 3. Pre-installation planning This chapter provides information and recommendations for planning the installation of a McDATA Intrepid FICON Directors for attachment to FICON or FICON Express channels on zSeries and 9672 G5/G6 servers.
3.1 Planning recommendations The following items should be considered during the installation planning phase of the McDATA Intrepid FICON Directors: Which topology will be implemented? – Switched point-to-point topology. For a more detailed explanation of this topology refer to 1.3.1, “Switched point-to-point configuration” on page 6. – Cascaded FICON Directors topology. For a more detailed explanation of this topology refer to 1.3.2, “Cascaded FICON Director configuration” on page 8.
3.2 Physical port layout Before installing the FICON Director, consider where to connect your FICON channels from the server and the control unit ports, as well as the ISLs (if applicable), based on your requirements. Distribute the channels among different FPM/UPM cards. If two channels are defined to access the same CU, plug both fiber optic cables into different FPM/UPM cards in the Director. Distribute the CU ports among different FPM/UPM cards.
Service LAN EFC Manager Client EFC Server Cabinet 1 C T P Corporate Network DHCP or Fixed IP address C T P 10.1.8.1 10.1.8.3 10.1.8.2 C T P C T P IP Network Cabinet 2 Figure 3-1 Recommended network connections In this configuration, the EFC Sever has two Ethernet adapters installed; one to connect the FICON Director and EFC Sever via the service LAN, and the second to provide connectivity for the client workstation via the corporate network.
3.4 Switch numbering Each FICON Director in a fabric must have a unique switch address (Domain ID) and a unique Switch ID. This Switch ID is used in IOCDS to define the link between the FICON channel and CU. The Switch ID can be any value between x’00” to x’FF’, while the switch address range may be restricted by the FICON Director firmware. The valid switch address range for a McDATA Director is between x‘61’ to x’7F’.
Note: These rules should be followed not only for a cascaded FICON Director configuration, but also for a switched-point-to-point configuration. If any single switch is to be merged into a fabric in the future, there will be no need to change the switch address (Domain ID) setting, which is a disruptive action. While the Switch ID in the CHPID statement is a logical switch number and defines the entry point to the fabric, the link address in the CNTLUNIT statement points to the exit port of the fabric.
Sample FICON IOCP A8-1 CU 8000-8700 A9-2 A10-3 zSeries ID (no change in ID statement for FICON) RESOURCE PARTITION=((A8,1),(A9,2),(A10,3)) CHPID PATH=(5A),SHARED,SWITCH=61,TYPE=FC CHPID PATH=(5B),SHARED,SWITCH=61,TYPE=FC CHPID PATH=(5C),SHARED,SWITCH=61,TYPE=FC CHPID PATH=(5D),SHARED,SWITCH=61,TYPE=FC Switch keyword Logical switch number Channel Entry switch.
Inter-Switch Links (ISLs) defined to HCD If HCD is used to build the IOCDS, we suggest the ports used for ISLs be marked as “occupied” in HCD. This prevents accidental attempts to define these ports to channels or CUs. If you are not familiar with HCD, refer to Input/Output Configuration Program Users Guide, SB10-7029 at: http://www.ibm.com/servers/resourcelink An example for this new function in HCD is shown in Figure 3-7.
Attaching an unauthorized N_Port to the FICON Director puts the F_Port into an “Invalid Attachment” state, and renders the port unusable until the assigned N_Port is attached. Since an N_Port is mapped directly to an F_Port within the FICON Director, there are some flexibility limitations with port binding. For example, port swapping within a FICON Director requires modifying the Bound WWN. See 5.5.3, “Configuring a port” on page 61 for an example.
Figure 3-8 shows a cascaded FICON Director environment with high integrity. The FICON Director prevents FC frames (user-data streams) from being delivered to the wrong destination if cables are incorrectly connected.
zSeries LPAR1 zSeries LPAR2 CHP(5A) LPAR3 CHP(60) CHP(5F) LPAR4 CHP(61) Zone2 Zone1 05 Zone3 0D 11 11 ISL SW61 10 14 CU1 SW62 Zoneset1 CU2 08 CU3 Figure 3-9 Configuration example of zoning In this example, we have several LPARs with paths to different CUs via two FICON Directors. Each LPAR must get access only to a specific CU, and no access to CUs belonging to other partitions.
The required distance between the FICON channel and the FICON CU has to be considered. Refer to Table 3-3 on page 33 for zSeries and 9276 G5/G6 FICON Channel distance specifications. Conversion kits may be required if the connectors are of differing types (LC Duplex, SC Duplex, or ESCON Duplex). When connecting a single mode port of the Director to an existing multimode cable, mode conditioning patch (MCP) cables are required at both ends of the existing multimode fiber optic cable.
FICON topology FC 2314 FC 2316 FC 2315 FC 2318 FC 2319a FC 2320a Cascaded FICON Directors No No Yesb Yesb Yesc Yesc a. Auto-negotiate (2 Gbps) support b. LIC CC needed to be enabled c. DRV3G with MCL(J11206) or later must be applied Check with your local service representative to ensure your zSeries or 9672 G5/G6 server has the required code levels. 3.8.
For all FICON features using repeaters, the end-to-end distance between the FICON channel and the FICON Director port can be up to 100 km. The same end-to-end distance is also available between the FICON Director port and the control unit port. However, the overall end-to-end distance between the FICON channel and control unit should not exceed 100 km. 3.8.
4 Chapter 4. Setting up the EFC Server environment This chapter describes how to set up the Enterprise Fabric Connectivity (EFC) Server environment.
4.1 Installation and setup The first steps to install the McDATA Intrepid FICON Director are described in the installation instructions shipped with the machine. The instructions guide you through the following steps: 1. Unpacking the FICON Director 2. Connecting the FICON Director to power 3. Unpacking and installing the EFC Server Once these steps are completed, the following steps can be used to help you through the setup process of the Enterprise Fabric Connectivity Manager environment. Step 1.
Connect the CTP, and the EFC Server to the Ethernet hub (known as the service LAN), using UTP cables with RJ-45 connectors. If remote access to the EFC Server is also required, then we suggest using the configuration depicted in Figure 3-1 on page 24. Step 5. Defining EFC Manager-to-FICON Director communication The Director has to be defined in EFC Server to initiate communication between the server and Director. Each Director, which should be managed by the server, has to be defined.
Double-click the Director icon for the Director you just added in the EFC Manager window. A new window opens displaying the hardware status of the Director. Click Product - Properties... and notice the firmware level of the Director. This is the currently installed and activated firmware in the Director. Click Maintenance - Firmware Library... to display firmware versions available in the Director. Notice the firmware version from the Firmware library panel shown in Figure 4-4.
Hardware (default) Port List Node List Performance FRU List Figure 4-5 shows a sample display when the Hardware tab is selected. Figure 4-5 Product (Director) display Product information Table 4-1 on page 39 lists the various types of information that can be found under the Product information tabs. This information is very useful when configuring the Director, as well as for fault isolation.
Port list Node list Performance FRU list FRU position X FRU status X FRU serial # X FRU part # X Block config X Port WWN X Port state X Port speed X Port type X B_to_B credit X X Port statistics X Link utilization X Error statistics X 4.2.2 Fabrics The Fabrics view displays information about your fabrics, and the Directors and ports within a given fabric (see Figure 4-6).
The area to the left is known as the Fabric Tree, and the area to the right is displayed as either the Topology view or the Zone Set view, by selecting tabs at the bottom of the Fabrics view area. The Topology view shows Directors in fabrics and the Inter-Switch Links (ISLs) between the Directors as solid black lines.
Audit log The Audit log shows a history of all user activities performed through the EFC Manager (see Figure 4-9). Figure 4-9 Audit log example Fabric log The Fabric log shows all changes that occurred to the fabric (see Figure 4-10). Figure 4-10 Fabric log example Event log The Event log provides information about the events in your fabric or products (Directors). See Figure 4-11 for a sample Event log display.
Figure 4-11 Event log example Link incident log The link incident log displays the most recent link incidents occurring on Director ports. All link incidents are recorded in this log, regardless of whether LIN alerts are configured through the Configure Ports dialog box. See Figure 4-12 for an example of the link incident log. Figure 4-12 Link incident log example Chapter 4.
44 Getting Started with the McDATA Intrepid FICON Director
5 Chapter 5. Configuring the FICON Director This chapter provides information about how to configure the McDATA Intrepid FICON Director in a switched point-to-point configuration or a cascaded FICON Director configuration.
5.1 Setting up a FICON Director After installing the FICON Director and establishing connectivity to the EFC Server (as described in Chapter 3, “Pre-installation planning” on page 21), only a few initial steps must be performed.
Verify Offline state Figure 5-2 Hardware view of the selected Director 2. Click the Configure tab -> Operating Parameters -> Switch Parameters (see Figure 5-3). Figure 5-3 Director parameters selection Chapter 5.
3. On the Configure Switch Parameters menu perform the following settings: – Define preferred Domain ID. Notice that each FICON Director must be set up with a unique Domain ID. It is recommended to be the same as the Switch ID used in IOCP/HCD. Enter the required Domain ID into the Preferred field of the menu. Entering a 1 into this field results in a Domain ID of x’61” and so on. – Check Insistent (only if this Director is in a cascaded topology).
Important: If the you decide to use 2-byte link addresses in your switched point-to-point configuration, then the Director must have the SANtegrity feature installed. See 3.5, “Binding and Insistent Domain ID” on page 28 for details. The following steps describe how to activate the SANtegrity feature: 1. Double-click the Director to activate the SANtegrity feature. Click the Configure tab, then the Features option, as shown in Figure 5-5.
Figure 5-6 Feature Key entry The installed SANtegrity feature allows E_Port functionality when operating in S/390 mode, which is required for a FICON cascaded topology. 5.3 Enabling the Control Unit Port (CUP) If the Management Server or CUP feature, FC 6302 (Intrepid 6064) or FC 6003 (Intrepid 6140) has to be activated, these steps have to be performed: 1. Click the Configuration tab on the Hardware view, then select Features. 2.
Figure 5-7 List of enabled features To enable the FICON Management Server feature, do the following: 1. Select Management Server from the Configure menu. Enable the management server by clicking the Enable Management Server option. Note: The following options are not required, and should be set to satisfy your requirements. 2. Click Director Clock Alert Mode. If this is enabled, the following occurs when users set the date and time through the Configure Date and Time dialog box.
– If Active=Saved is enabled (check mark), the IPL and the active address configuration are maintained as identical configurations. If a new configuration is activated through the Configure Addresses - "Active" dialog box, that configuration becomes the IPL address configuration. If the feature is enabled, the IPL file is locked to modification through the Configure Addresses - "Active" dialog box.
Figure 5-9 Verify settings of FICON Directors We used the default values for our configuration. However, the BB_Credit was changed for certain ports when we enabled long distance buffering, as shown in 5.5.3, “Configuring a port” on page 61. 4. Verify/apply settings on the second Director that will be included in the fabric. If you wish to use Switch Binding, ensure all the devices are attached to the Directors.
Figure 5-10 Enterprise Fabric Mode 7. Click Start. This enables all listed features as shown in Figure 5-11. Ensure the operation completes successfully, which indicates Enterprise Fabric is established. Figure 5-11 Features enabled with Enterprise Fabric Mode 8. After clicking OK to enable Enterprise Fabric Mode, wait for the message: Enterprise Fabric Mode update complete, then click the Close button to finish.
When Enterprise Fabric Mode is activated, a fabric membership list is automatically created containing the Domain ID and WWN of both Directors. 9. Verify the membership list by selecting Fabrics -> Fabric Binding -> Next -> Membership list. The list is shown in Figure 5-12. Figure 5-12 Membership List containing Directors included in the fabric Note: If any Director that is not in the membership list is connected to this Director, the ISL link will segment.
Figure 5-13 Established fabric with ISL link 5.4.1 Switch Binding If additional security is required, Switch Binding can be established to allow only specific devices (based on WWN or Nickname) to connected to a Director. As mentioned earlier, all devices which were connected during the Enterprise Fabric Mode enabling process will be automatically put into the membership list for Switch Binding.
Figure 5-14 Switch Binding selection Figure 5-15 shows a membership list for Switch Binding. You can add or delete devices based on WWN or Nicknames. A check box indicates if the devices are in the membership list. Chapter 5.
Checked after adding Figure 5-15 Add device to Switch Binding membership list The last step is to activate the changes by selecting the Activate button. To remove a device from the list, Switch Binding must first be disabled. Note: Switch Binding cannot be disabled while Enterprise Fabric Mode is active and the Director is online. 5.
Figure 5-16 Node List WWN display 3. Right-click the port and select Define Nickname... from the menu. In the Define Nickname window, the WWN of the device is shown, and there is a blank field to enter the nickname for the device. See the example in Figure 5-17. Figure 5-17 Enter Device nick Name 4. In the Nickname field, type in a meaningful Nickname describing the device connected to the port. Attention: Nicknames must be unique within the Director. 5.
1. From the Hardware view of the Director, click Configure - Addresses - Active... (see Figure 5-19). Figure 5-19 Configure dialog menu 2. The Configure Addresses panel opens. On this panel you can enter your port names, block ports, and prohibit communication between ports if required. To enter a name for a port double-click the Port Name field of the port. 3. Type in a meaningful name for that port in the Port Name field. 4. Click i the check box in the Blocked column if you want to block a port.
5.5.3 Configuring a port This section describes how to configure port options such as, long distance buffering, port binding, and speed. If the 10-100 km feature is enabled, more buffer-to-buffer credits are provided to a port in support of long distance links. The speed for each port should be set to the speed supported by the attached device: 1. Click Configure from the Products view of a Director, then select Ports from the menu. The Configure Ports panel is displayed, as shown in Figure 5-21.
5.6.1 Creating a zone 1. From the Fabrics view (as shown in Figure 5-22 on page 62), do the following: Select Fabrics. Select Zone Set. Select Configure. Select Zoning Library... Select Configure Select Zoning Library... Select Fabrics Select Zone Set Figure 5-22 EFC Manager Zoneset display Initially, the Zoning Library window (shown in Figure 5-23), will have no zone sets nor zones listed. Figure 5-23 Zoning Library 2. Click on the Zones tab, then on File - New to create a new Zone.
On the New Zone window shown in Figure 5-24 do the following to add new members to the zone: Type in a name for this zone. A zone name may have up 64 characters. Choose the option to add members by WWN or by Port. If Add by WWN is selected and a nickname for this port has been previously defined, the nickname is displayed. Click the port you want to add to the zone. Click the Add>> button to get the selected port into the member list in the right column.
64 zone sets can be defined in the zoning library and each zone set can group up to 1024 zones. 1. In the Zoning Library window (see Figure 5-23) click the Zone Sets tab. 2. On the menu bar, click File - New... to open the New Zone Set window. All zones defined in the zoning library are listed in the left column. See Figure 5-25 for the New Zone Set screen. 3. Type a name for the zone set. The name can have a maximum of 64 characters; then click the zone you want to add to the zone set. 4.
Figure 5-26 Zonesets in zoning library Restriction: Up to 64 zone sets can be defined in the zoning library. To verify that zones and zone members are correctly added to the zone set, click the zone set and select File - Properties from the menu bar. The complete zone set members and the zone members are displayed, as shown in Figure 5-27. Figure 5-27 Zoneset properties Once all your zone definitions are correct, close the zone set properties window. 5.6.
Important: If you deactivate the active zoneset and the default zone feature is enabled, then all nodes in the fabric will be able to communicate with all other nodes. This could in turn lead to violations of your security policies. If you want to disable the default zone feature, select Configure - Advanced Zoning Configure Default Zone from the menu bar. On the next panel you can enable or disable the default zone feature. It is not necessary to deactivate the current active zoneset.
6. On the next screen the name of the fabric and a list of the affected Directors is displayed. Ensure you have chosen the correct fabric and Directors for zone set activation. Applying the zoneset to an other fabric may impact the performance of these switches. 7. Click Next and Start to continue the zoneset activation, and wait for message: Activate zone set complete, then close the window. 8. On the EFC Manager window click the Zone Set tab.
5.
Figure 5-31 Zone Set export file display (xml format) Export and print the Configuration report for each switch. Select Configure - Export Configuration Report... from the menu bar. In the next displayed window select the subDirectory where the file should be stored and type in a filename. Click Save. The data is stored in txt format and can be viewed by any editor program, as shown in Figure 5-32.
Print this file and compare the configuration parameter for the fabric, Directors and ports with the configuration data in your worksheet. Back up of your configuration data. On each Director select Maintenance - Backup & Restore Configuration from the menu bar. Click Backup on next panel. The configuration data for the Director is saved on the EFC Server.
A Appendix A. Useful procedures This appendix provides procedures needed to supplement configuration tasks described in this document. In subsequent sections, you will find the following: Setting up a HyperTerminal Session Altering the IP address of a CTP card Installing EFC Management software © Copyright IBM Corp. 2003. All rights reserved.
Setting up a HyperTerminal session For some special functions in the McDATA Intrepid FICON Director, it is required to set up a HyperTerminal session. The communication is established via the Maintenance Connector on the rear of the director and a COM port in the workstation PC. 1. Select Start -> Programs -> Accessories -> HyperTerminal from your desktop (see Figure A-1). Intrepid Select Icon Figure A-1 HyperTerminal connection description 2.
3. Select COM1 and click OK. Ensure the null modem cable is connected to this port. The Port Settings window is displayed. Figure A-3 COM1 properties panel 4. On the COM1 properties screen set the following parameters: – – – – – Bits per second: 57600 Data Bits: 8 Parity: None Stop Bits: 1 Flow control: Hardware 5. Press Enter until the prompt > appears. Type in the password to establish the terminal session and to execute other commands.
>xxxxxxxx C>ipconfig MAC Address: 08 00 88 A0 DC DA IP Address: 10.1.8.8 Subnet Mask: 255.255.0.0 Gateway Address: 0.0.0.0 C>help ipconfig [] = optional | = or ^ = optional space () = required + = and/or ... = repetition IPCONFIG Configure IP parameters: [ [ [ ] ] ] C>ipconfig 10.1.8.2 255.0.0.0 0.0.0.0 IP address Mask Gateway Request Completed: OK C>ipconfig MAC Address: 08 00 88 A0 DC DA IP Address: 10.1.8.2 Subnet Mask: 255.0.0.0 Gateway Address: 0.0.0.
Installing EFC Manager server software This section describes how to install the EFC Manager server application on a workstation. In the EFC Manager server workstation both the server and the client component of the application have to be installed. On all other workstations, it is recommended to install only the client component of the application: 1. On the PC you want to install the EFC Server, exit and close all applications. 2. Run the McDATA server installation.
Installing EFC Management client software To install the EFC Management client application on a workstation, do the following: 1. Open a browser, and enter the host name or IP address of your EFC Manager server. The McDATA Enterprise Fabric Connectivity Management page appears as shown in Figure A-7. 2. To install the client software, follow the instructions supplied in this page for your workstation platform.
Figure A-8 New firmware version The New Firmware Version dialog box appears. 3. Select the appropriate file from its storage location and click New. 4. When the New Firmware Description dialog box displays, enter a description for the new firmware and click OK. Note: Use a date or some other text that identifies the new firmware. The Firmware Library dialog box displays with the version and description of the new firmware added to the text area. 5.
78 Getting Started with the McDATA Intrepid FICON Director
B Appendix B. Port location and mapping This appendix provides information about the physical layout of McDATA Intrepid FICON Director models. These models allow for a wide range of configuration options. The basic building block is the port module, which contains four Fibre Channel/FICON ports using 1 Gbps and/or 2 Gbps technology. For more configuration details go to 2.1.4, “Hardware components” on page 15.
Intrepid port numbering For the Intrepid (6064 and 6140) FICON Directors, the physical port numbers are the same as the port addresses. The Hardware Configuration Definition (HCD) and Input Output Configuration Program (IOCP) use port address information to define control unit link addresses. The physical port number is indicated either by a decimal or hexadecimal value, which can be found in the ECF Manager logs as identification for a given port.
CTP Cards FPM/UPM Cards FPM/UPM Cards 43 3F 3B 37 33 2F 2B 27 23 1F 1B 17 13 0F 0B 07 3F 63 3B 59 37 55 33 51 2F 47 2B 43 27 39 23 35 42 3E 3A 36 32 2E 2A 26 3E 62 3A 58 36 54 32 50 2E 46 2A 42 26 38 22 34 41 3D 39 35 31 2D 29 25 3D 61 39 57 35 53 31 49 2D 45 29 41 25 37 21 33 40 3C 38 34 1F 31 1B 27 17 23 13 19 0F 15 0B 11 07 07 03 03 30 2C 28 24 22 1E 1A 16 12 0E 0A 06 A C T I V E B A C K U P 3C 60 38 56 34 52 30 48 2C 44 28 40 24 36 20 32 15 14 13 12 11 10 9 1E 30 1A 26 16 22
Slot Numbers UPM Cards UPM Cards CTP Cards 31 30 29 28 27 26 25 83 7F 7B 77 73 6F 6B 67 23 24 75 62 5E 5A 56 72 6E 6A 66 71 6D 69 74 70 6C 68 65 64 7C 124 78 120 74 116 70 112 6C 108 68 104 64 100 60 96 40 3C 38 34 30 2C 28 24 3C 60 38 56 34 52 30 48 2C 44 28 40 24 36 20 32 41 3D 39 35 31 2D 29 61 5D 59 A C T I V E B A C K U P 25 3F 3B 37 14 13 12 11 9 54 53 4F 4B 47 52 4E 4A 46 51 4D 49 45 50 4C 48 44 5C 92 58 88 54 84 50 80 4C 76 48 72 44 68 40 64 20 1C 18 14
Slot 34 Slot 35 93 92 8F 143 8E 142 91 90 8D 141 8C 140 8C 8D 8E 8F 88 136 89 137 8A 138 8B 139 Slot 33 8B 8A 89 88 87 135 86 134 85 133 84 132 SBAR1 SBAR0 Figure B-4 Intrepid 6140 rear port mapping Appendix B.
84 Getting Started with the McDATA Intrepid FICON Director
C Appendix C. FICON Director configuration worksheet This appendix contains a worksheet, which aids in documenting the layout of your FICON Director. It can be applied as a tool to help understand how the ports are allocated for configuration and problem determination purposes. © Copyright IBM Corp. 2003. All rights reserved.
86 Getting Started with the McDATA Intrepid FICON Director Slot Number Port Number Port Address Laser Type: LX / SX FICON Director Ports HCD defined Switch ID _____ FICON Director Domain ID _____ Port Name (Switch ID) (Switch @) Model: ____ S/N _____________ Node Type CU / CHNL Machine Type Model Serial Number ISL CU I/F CPC CHPID Attached N_Ports / E_Ports (CU, CPC or ISL) Cascaded Directors No ___ Yes ___ Corresponding cascaded Director Domain ID _______ Fabric name _______________________
Related publications The publications listed in this section are considered particularly suitable for a more detailed discussion of the topics covered in this redbook. IBM Redbooks For information on ordering these publications, see “How to get IBM Redbooks” on page 87.
88 Getting Started with the McDATA Intrepid FICON Director
Index A arbitrated loop 6 architecture website 5 Audit log 42 auto-negotiate 3 B Backplane 17 BB_Credit 52 Bound WWN 28 C communication methods 13 Control Processor (CTP) 15 Control Unit Port (CUP) 50 conversion kit 22, 32 CTP 36 CTP cards 23 D definition terms 25 Director characteristics 12 Director configuration Intrepid 6064 17 Intrepid 6140 17 Domain ID 25, 55 E E_D_TOV 52 E_Port 2 EFC Manager software installation 75 EFC Server 14 Enterprise Fabric mode 54 Event log 42 export 69 export zoneset 68
interconnection 13 Interop Mode 52 Inter-Switch Link (ISL) 22 IP address 23, 36 IPI 5 ISL 23 Redbooks Web site 87 Contact us viii redundancy 12 RFI shield 16 S Management Server Function 50 membership list 28, 57 Mode Conditioning Patch (MCP) 22 mode conditioning patch (MCP) 32 multimode 33 S/390 Operating Mode 48 SANtegrity 48 SBAR Assembly 17 SBCON 5 SCSI 5 service LAN 23, 37 short wavelength (SX) 12, 32 single mode 33 small form factor (SFF) 12 Speed 48 supported distances 33 switch address range 25
Getting Started with the McDATA Intrepid FICON Director (0.2”spine) 0.17”<->0.
Back cover ® Getting Started with the McDATA Intrepid FICON Director Product, planning, and implementation information Realistic considerations and suggestions Helpful configuration examples This IBM Redbook discusses how to install, tailor, and configure the McDATA Intrepid FICON Director, in conjunction with the FICON topologies supported by zSeries and 9672 Generation 5 and Generation 6 servers.
