EnterpriseExpress Adapter/ESCON PCI INSTALLATION ESCONGUIDE Adapter Installation Guide Part Number 40-01459-D0-001 129 Middlesex Turnpike, Burlington Ma. 01803 • (781) 272-8200 Fax (781) 272-0342 • www.bustech.
Federal Communications Commission (FCC) Statement WARNING: This equipment generates, uses, and can radiate radio frequency energy and if not installed and used in accordance with the instruction manual, may cause interference to radio communications. It has been tested and found to comply with the limits for a Class A computing device pursuant to Subpart J of Part 15 of FCC Rules, which are designed to provide reasonable protection against such interference when operated in a commercial environment.
Table of Contents• • • • ABOUT THIS PUBLICATION .............................iii CHAPTER 6. TROUBLESHOOTING ................... 47 Who Should Use This Publication ...................iii Hardware ......................................................... 47 How to Use This Publication ...........................iii ESCON Configuration .................................... 49 What is Included in This Publication ...............iii TCP/IP Direct Connect....................................
About This Publication This User's Guide provides the information necessary to install and configure BusTech's PCI ESCON Adapter (PBSA) to connect a Server to an IBM Mainframe.
CHAPTER 6. TROUBLESHOOTING – This chapter takes the reader through some troubleshooting steps to be tried when the adapter is not working properly. What’s New in this Release? Plug and Play drivers for Microsoft Windows 2000 Server have been added to the installation kit. Support for NetWare for SAA has been discontinued.
Chapter 1. INTRODUCTION The PCI ESCON Adapter from Bus-Tech, Inc. is a high performance adapter that enables PCI-based systems to communicate with mainframe systems through direct IBM channel attachment. The ESCON adapter acts as a control unit for Enterprise Systems Connections (ESCON); providing high speed throughput and excellent processing efficiencies for applications that require high-speed connectivity between a server and a mainframe.
Additionally, the PCI ESCON Adapter includes TCP/IP Direct Connect for the Windows 2000 and NT environments. Direct Connect provides a high-performance, point-to-point TCP/IP connections between the mainframe and the server’s TCP/IP stack and can be used with Bus-Tech’s MPC+ for Windows NT to provide HighSpeed Data Access Services (HSAS) and MPC Point-to-Point (MPCPTP) connections.
Minimum System Requirements Hardware The minimum hardware requirements for using the PCI ESCON Adapter are: - Pentium 100Mhz - 64MB RAM for Windows NT Systems -128MB RAM for Windows 2000 Systems - 1 Available PCI BusMaster Slot - 2 MB Hard Disk Space (for Bus-Tech Drivers) Software Windows The supported releases of Microsoft software are: - Windows 2000 Server - Windows NT Server version 4.0 with a minimum of Service Pack 3 applied - SNA Server version 3.0 or 4.0 - Host Integration Server version 1.
Chapter 2. HARDWARE INSTALLATION Installing the Adapter CAUTION! The PCI ESCON Adapter is a PC adapter card and as such can be damaged by Electrostatic Discharge. Before removing the adapter from it’s protective static bag, please ensure that you are free of static charge. At minimum, you should ground yourself to the system you are using. The PCI ESCON Adapter is a full size PCI adapter measuring 12.283 X 4.2 inches, Figure 2-1. The adapter hardware comes pre-configured and is ready to be installed.
4. Remove the adapter from its protective anti-static bag and insert the adapter into the chosen PCI bus slot. Make sure the adapter is fully inserted in the slot. Place a screw through the top of the mounting bracket and securely fasten to the system chassis. 5. Replace the system cover. 6. As shown in Figure 2-1, the adapter has two connectors at the card edge; a standard ESCON connector(top) and a serial port (bottom). Plug the IBM-compatible ESCON channel cable directly into the ESCON connector.
Chapter 3. DRIVER INSTALLATION The PCI ESCON Adapter offers drivers for Microsoft's Windows 2000 Server and Microsoft Windows NT Server. This chapter discusses installation of the drivers. Please refer to the section appropriate to your operating environment. Windows 2000 Note: Bus-Tech adapters include drivers for both Windows 2000 and Windows NT. These drivers are different and can only be installed in the appropriate environment.
Figure 3-2. Search the Floppy The hardware wizard will search the Windows directory and then the floppy disk. When it finds the PBSA drivers it will prompt you for approval to install (Figure 3-3). Figure 3-3. Confirm PBSA Driver Install Windows 2000 will install the new drivers. At the end of installation you will be prompted by a screen indication the New Found Hardware Wizard is completing (Figure 3-4). Click Finish.
Figure 3-4.
Windows NT The PBSA network driver is always required in order to allow Windows NT to communicate with the adapter. The driver must be installed once for each PCI ESCON Adapter installed in the system. The following step-by-step procedure will install the driver into your Windows NT Server. Step 1. From the Windows NT Server Control Panel, open Network (Figure 3-5). Figure 3-5. Network ICON on Control Panel 2. From the Adapters tab on the Network screen, click on the Add button (Figure 3-6).
Figure 3-6. Network Screen 3. From the Select Network Adapter screen (Figure 3-7), click the Have Disk... button. Figure 3-7.
4. The Insert Disk screen is displayed (Figure 3-8). Figure 3-8. Insert Disk Dialog Box With the floppy inserted into the floppy drive point to the root directory by entering "A: " where A is your floppy drive and press OK. 5. The Select OEM Option dialog box will be displayed (Figure 3-9). Highlight\select the Bus-Tech PCI ESCON Adapter and click OK. Figure 3-9. Select OEM Option Screen 6. Once the addition procedure is complete, the system will display the ESCON Configuration screen (Figure 3-10).
Figure 3-10. ESCON Configuration 7. As shown in Figure 3-11, the adapter should now be listed in the Network Adapters box. Clicking Close will cause the system to configure the network and prompt you to restart the system. Figure 3-11.
Chapter 4. ESCON CONFIGURATION Figure 4-1. ESCON Attached Controllers Overview ESCON controllers, including the PCI ESCON Adapter (PBSA), can be connected to the mainframe in more than one fashion. As shown in Figure 4-1, Controller 1 is attached directly to one of the mainframe’s ESCON channels. Assuming the mainframe is running a single Logical Partition (LPAR), this is simplest option for connecting an ESCON controller to the mainframe.
Finally, using both ESCON Directors and EMIF, it is possible for a single ESCON controller to communicate with multiple Logical Partitions (LPARs) running on multiple mainframes, using multiple ESCON channels. Because an ESCON controller may be attached to an ESCON director, which may be connected to multiple mainframes and Logical Partitions (LPARs), it is necessary to configure the ESCON controller in order to define how the unit will appear to each environment.
Channel Link – The address of the ESCON director port that connects to the mainframe this device is to communicate with. The value range is from 01-FE hexadecimal. In Figure 4-2 the mainframe uses a channel link address '02' to communicate with Server 1. Server 1 uses a channel link address '01' to communicate with the mainframe. In this example, the Channel Link in the adapter configuration is set to '01'. Figure 4-2.
Configuration ESCON configuration may be defined and viewed from any of the upper level software including the data link service for Microsoft’s Host Integration Server or SNA Server, data link control for Communications Server, TCP/IP Passthrough, TCP/IP Direct Connect, or MPC+ for Windows. Clicking a Configure ESCON button will immediately display the ESCON devices configured for the adapter (see Figure 4-6) and allow you to add, modify, or remove devices in the list.
In Windows NT the ESCON configuration may be accessed through the system Control Panel. From the main screen of Control Panel double click the Network Icon (See Figure 4-4). Figure 4-4. Windows NT Control Panel Select the Adapters tab (Figure 4-5). Figure 4-5.
The Bus-Tech PCI ESCON Adapter should be included in the list. Selecting the Bus-Tech adapter and clicking Properties will bring up the ESCON Configuration Screen (Figure 4-6). Figure 4-6. Bus-Tech’s ESCON Configuration Screen To configure a new device click Add… Figure 4-7.
device A0 and A1, enter 2. Optionally enter a Description to be associated with this device. Remember that for TCP/IP Passthrough and TCP/IP Direct Connect CTC connections you must define two consecutive devices. Additionally for TCP/IP Passthrough the first device must be even numbered (00, 02, 20, 40, A0, etc.) Press Add to add the device(s) to the ESCON configuration file. The ESCON Adapter Properties dialog will re-display, now showing the new devices (Figure 4-8). Figure 4-8.
Chapter 5. TCP/IP DIRECT CONNECT TCP/IP Direct Connect software included with the PCI ESCON Adapter provides high-performance, point-to-point TCP/IP communications between a Windows server (Windows 2000 or Windows NT 4.0) and the mainframe. TCP/IP Direct Connect operates over Channel-to-Channel (CTC) or Multi-Path Channel Plus (MPC+) links.
TCP/IP Direct Connect supports three link types across the ESCON channel: Channel-to-Channel (CTC), High-Speed Access Services (HSAS) for UDP, or MultiPath Channel Point-to-Point (MPCPTP). HSAS and MPCPTP require installation of MPC+ for Windows (MPC+). CTC links use two ESCON devices (one for read, one for write) to communicate with mainframe TCP/IP stacks such as OS/390 TCP/IP, MVS TCP/IP and VM TCP/IP. These links support simple TCP/IP applications such as Telnet, TN3270, and FTP.
2. Click OK when Setup displays it’s Welcome dialog (Figure 5-4). Figure 5-4. TCP/IP Direct Connect Install Confirmation 3. The TCP/IP Direct Connect Properties dialog will display (Figure 5-5). Figure 5-5. TCP/IP Direct Connect Properties You must define the Link type and Link properties in order to complete the install. Please refer to the Link Configuration section later in this chapter. 4. Once you have defined the Link click OK to continue the install.
defined by the install you have just completed. Right click the connection and select Properties (Figure 5-7). Figure 5-7. New Local Connection 6. Uncheck Client for Microsoft Networks, File and Printer Sharing for Microsoft Networks, and DLC Protocol since these services are not supported on the mainframe (Figure 5-8). Highlight Internet Protocol (TCP/IP) and click on Properties. Figure 5-8.
7. Enter an IP address and Subnet mask to be associated with this link on the server. This is the address a mainframe-based application will use to establish contact with the Windows 2000 server (Figure 5-9). The address must be in the same IP subnet as the address assigned to this link on the mainframe. Figure 5-9. TCP/IP Properties 8. Click OK two times to finish defining TCP/IP properties for this link.
Deleting a Link To remove a previously installed TCP/IP Direct Connect link from Windows 2000, you must uninstall the TCP/IP Direct Connect Adapter. This is accomplished using the Device Manager in the Windows 2000 Computer Management utility (Figure 5-10). Figure 5-10.
Windows NT The following step-by-step procedure will install the TCP/IP Direct Connect and configure it for use without MPC+. Installation and configuration of TCP/IP Direct Connect using MPC+ is discussed in the “MPC+ for Windows NT Installation Guide”. The PBSA driver must be installed before TCP/IP Direct Connect (see Page 10). Step 1. From the Windows NT Control Panel invoke Network configuration (Figure 5-11). Figure 5-11. Invoking Network Configuration 2. Click on the Adapters tab (Figure 5-12).
Figure 5-12. Adapter List with ESCON Adapter 3. Click the Add button to add a new adapter. The Select Network Adapter dialog box will display a list of adapters included with Windows NT (Figure 5-13.). Figure 5-13. Select Network Adapter 4. Click the Have Disk button. The Insert Disk dialog box will display (Figure 5-14).
Figure 5-14.Insert Disk 5. Insert the TCP/IP Direct Connect diskette into your floppy. Click OK. 6. The Select OEM Option dialog (Figure 5-15) will display TCP/IP Direct Connect. Click OK to install the driver. Figure 5-15. Select OEM Option 7. The TCP/IP Direct Connect Adapter Properties screen for Channel-to-Channel (CTC) link type (Figure 5-16) will display. If MPC+ for Windows NT is installed on the server HSAS and MPCPTP link types will be active. Otherwise only the CTC link type will be available.
Figure 5-16. Adapter Properties You must define the Link type and Link properties in order to complete the install. Please refer to the Link Configuration section later in this chapter. 8. After defining the fields click Close to save your values and return to the Network Adapters screen (Figure 5-17). Figure 5-17.
9. Click on Bindings. Show bindings for all adapters (Figure 5-18). Check that only the TCP/IP Protocol is bound to the TCP/IP Direct Connect Adapter. Disable any other service or protocol bound to TCP/IP Direct Connect. Figure 5-18. Adapter Bindings 10. Click Close to end network configuration. Windows NT will perform an automatic bind process. TCP/IP Direct Connect is bound to Microsoft’s TCP/IP stack on the server.
11. Use your mouse to select TCP/IP Direct Connect from the list of Adapters bound to TCP/IP (Figure 5-20). Figure 5-20. Select TCP/IP Direct Connect 12. Enter an IP Address and Subnet Mask; defining the address that the mainframe will use to communicate with the server (Figure 5-21). Note that the mainframe IP address and this address must be in the same subnet.
Figure 5-21. Assigning an IP Address to the ESCON Adapter 13. Click OK. Windows NT will complete the binding process and prompt you to reboot the server. You must reboot for network changes to take affect. Installation of TCP/IP Direct Connect is complete.
Link Configuration Figure 5-22. CTC Link Properties Figure 5-22 shows the properties that must be configured for CTC Links. Complete these fields as follows: Mainframe IP Address – The IP address of the mainframe this connection is to communicate with. This must match the HOME IP address assigned in the TCP/IP Profile. Link Description – A description of the link being defined. Channel Adapter – Use your mouse to select the PCI ESCON Adapter this connection is to be defined on.
MTU – Maximum Transmission Unit must match what is defined on the mainframe for this connection or packet loss will occur. The recommended MTU for CTC connections is 32000. To configure MPC+ links, either HSAS or MPCPTP, please refer to the MPC+ for Windows Installation Guide.
Mainframe Configuration This section discusses configuration of the mainframe for use with TCP/IP Direct Connect over a Channel-to-Channel (CTC) link. Mainframe configuration for Communications Server, SNA Server, TCP/IP Passthrough for Windows NT, and MPC+ for Windows is discussed in the user’s guide that accompanied each individual product. OS/390 Device Definition As discussed in the previous section, TCP/IP Direct Connect over CTC uses two adjacent sub-channel addresses.
TCP/IP Profile TCP/IP Direct Connect links require the IBM TCP/IP protocol stack running on your System/390. Your TCP/IP Profile will need to be modified to support the new link. The following is an example of the entries required to define a connection: ; CTC connection DEVICE DEVCTC1 CTC a00 IOBUFFERSIZE 65535 LINK LINKCTC1 CTC 0 DEVCTC1 ; HOME 201.168.1.33 LINKCTC1 GATEWAY ; ; Direct Routes - Routes that are directly connected to my interfaces.
IOCDS – LPAR 0 *** CHPID STATEMENTS *** CHPID PATH=((22)),TYPE=CNC,SWITCH=01,SHARED *** CNTLUNIT STATEMENTS *** CNTLUNIT CUNUMBR=002,CUADD=0,PATH=(22), UNITADD=((00,2)),UNIT=SCTC,LINK=(CB) *** IODEVICE STATEMENTS *** IODEVICE ADDRESS=(200,2),UNIT=SCTC IOCDS – LPAR 1 *** CHPID STATEMENTS *** CHPID PATH=((22)),TYPE=CNC,SWITCH=01,SHARED *** CNTLUNIT STATEMENTS *** CNTLUNIT CUNUMBR=002,CUADD=0,PATH=(22), UNITADD=((02,2)),UNIT=SCTC,LINK=(CB) *** IODEVICE STATEMENTS *** IODEVICE ADDRESS=(202,2),UNIT=SCTC DEVICE
TCP/IP Routing TCP/IP Direct Connect is a Network Driver Interface Specification (NDIS) compliant adapter driver. TCP/IP Direct Connect makes the PCI ESCON Adapter appear exactly like any other Network Interface Card (NIC) to the Windows server. As a result when TCP/IP Direct Connect and a PCI ESCON Adapter are installed along with one or more Local Area Network (LAN) adapters the Windows server becomes a multihomed system.
Subnet 0 207.168.12.1 – 207.168.12.62 Subnet 1 207.168.12.65 – 207.168.12.126 Subnet 2 207.168.12.129 – 207.168.12.190 Subnet 3 207.168.12.193 – 207.168.12.254 As shown, the Ethernet segment makes up subnet 0 and the Token-Ring makes up subnet 1. Subnets 2 and 3 are currently not used. The router’s Ethernet port is assigned an IP address in Subnet 0 and the Token-Ring port is assigned an address in subnet 1. Workstations on the Ethernet LAN are configured with their Default Gateway set to 207.168.
Figure 5-26. TCP/IP Direct Connect Configuration Screens Notice also that the subnet these two addresses are in is different than the subnet of the server’s LAN adapter (207.168.12.68). Microsoft’s TCP/IP stack can be configured to automatically forward IP packets between network adapters as long as those adapters are in different subnets. However, Microsoft’s TCP/IP cannot forward packets between to adapters when the IP addresses are in the same subnet.
Updating Workstation Configurations In most existing networks today it will not be necessary to update the TCP/IP configuration on a workstation in order to allow it to connect to the mainframe using an ESCON adapter and TCP/IP Direct Connect. Most workstations already point to an existing router and/or server as a default gateway and that will be all that is needed. The one notable exception to that rule is a single segment LAN with no gateways(Figure 5-27). Figure 5-27. Simple Network with No Gateways.
Figure 5-28.
Chapter 6. TROUBLESHOOTING If your PCI ESCON Adapter fails to initiate successfully this chapter will provide you with some general troubleshooting guidelines to help you identify and fix your problem. If after you have been through this troubleshooting chapter you are still unable to make your adapter work properly please refer to the section titled “Help and Service Information” on page 53 for information on obtaining help.
STEP 1. With your server powered on, check to make sure both LEDs are lit. If the top LED is Green and the bottom LED is Orange then the adapter has successfully completed POST and loaded firmware. This is the normal condition prior to starting the software. The adapter is operational. The bottom LED will remain Orange until the server is varied online at the mainframe console. Proceed to the troubleshooting section on ESCON configuration.
ESCON Configuration When the adapter loads the emulation it also loads the ESCON device configuration (see Chapter 4.). This configuration must match the configuration defined on your mainframe(s). In Windows 2000 you may display an ESCON adapter’s device configuration using the Device Manager in the Computer Management utility (Figure 6-1). Figure 6-1. Displaying Adapter Properties In Windows NT use the Network ICON on the Control Panel to display the server’s network adapters (Figure 6-2). Figure 6-2.
Highlight the ESCON adapter and click Properties. Figure 6-3. ESCON Device Configuration The ESCON Devices tab shows the devices configured for this adapter. Verify that the units defined here match those defined on the mainframe. Make sure you are using the correct device numbers in upper layers of software. Correct any discrepancies you find and reset the server.
TCP/IP Direct Connect If TCP/IP Direct Connect is configured with a link type of HSAS or MPCPTP, please refer to the section titled “Troubleshooting” in the “MPC+ for Windows NT Installation Guide”. In Windows 2000 the easiest way to tell if TCP/IP Direct Connect has failed to activate is to look at the system’s console(Figure 6-4). Since TCP/IP Direct Connect is seen as a LAN connection by Windows 2000, a disconnect icon will display if TCP/IP Direct Connect is not active. Figure 6-4.
Figure 6-5. TCP/IP Direct Connect Properties ; CTC connection DEVICE DEVCTC1 CTC a40 LINK LINKCTC1 CTC 0 DEVCTC1 ; Subchannel Address HOME 207.169.12.129 LINKCTC1 Home IP Address GATEWAY ; ; Direct Routes - Routes that are directly connected to my interfaces. ; ; Network First Hop Link Name Packet Size Subnet Mask Subnet Value 207.169.12.130 = LINKCTC1 4096 255.255.255.192 0.0.0.128 START DEVCTC1 Server’s IP Address Subnet Mask Figure 6-6. Mainframe TCP/IP Profile 2.
Help and Service Information If you have questions about your new Bus-Tech product, or require technical assistance, visit the Bus-Tech Web site at http:\\www.bustech.com. You can also get help and information through the Bus-Tech’s Technical Support line, Monday through Friday, 8:30 am – 5:00pm Eastern time. Response time may vary depending on the number and nature of the calls received. Step 1: Problem Solving You may be able to solve the problem yourself.
If possible, be at your computer. Your technical support representative might want to walk you through the problem during the call. Step 3: Placing the Call If you call after your warranty or maintenance contract has expired, you might be charged a fee. Support 8:30am – 5:00pm, Monday-Friday U.S.A. / Puerto Rico 1-800-284-3172 From Outside the U.S.A. 1-781-272-8200 Additional Technical Support Resources Online technical support is available through the Internet during the life of your product.
Customer Response If you have comments or suggestions regarding our products and documentation, please send them to: BUS-TECH, INC. 129 MIDDLESEX TURNPIKE BURLINGTON, MA 01803 ATTENTION: CUSTOMER SUPPORT Or, call us at: (781) 272-8200 FAX: (781) 272-0342. Or, visit our Web Site at: www.bustech.
Technical Specifications Physical Attributes Dimensions Standard Full Size PCI Adapter Length 12.283” Height 4.2” Power Requirements 5.5 Amp. at + 5V DC 20 mAmp. at + 12V DC 20 mAmp. at - 12V DC Operating Temperature 10 o - 40 o C Humidity Range 0% - 90% Standards PCI 2.
