Compaq_SNA_Peer_Server______________________________ Installation and Configuration Part Number: AA-Q1P8E-TE September 1999 This document describes how to install and configure the Compaq SNA Peer Server for Tru64 UNIX software on an Alpha system running the Compaq Tru64 UNIX operating system. Revision/Update Information: This is a revised manual. Operating System and Version: Compaq Tru64 UNIX V5.0 Software Version: Compaq SNA Peer Server V1.5 Electronic Data Systems Corporation and Compaq Computer Corporation make no representations that the use of their products in the manner described in this publication will not infringe on existing or future patent rights, nor do the descriptions contained in this publication imply the granting of licenses to make, use, or sell equipment or software in accordance with the description. Possession, use or copying of the software described in this publication is authorized only pursuant to a valid written license from Compaq or an authorized sublicensor. The information in this document is subject to change without notice and should not be construed as a commitment from Electronic Data Systems Corporation or Compaq Computer Corporation. Electronic Data Systems Corporation and Compaq Computer Corporation assume no responsibility for any errors that may appear in this document. © 1999, 1997 Electronic Data Systems Corporation. All Rights Reserved. © 1993 Digital Equipment Corporation. All Rights Reserved. The following are trademarks of Compaq Computer Corporation: DEC, DECnet, OpenVMS, ULTRIX, VAX, and the Compaq logo. The following are third-party trademarks: Advanced Peer-to-Peer Networking, APPN, IBM, NetView and OS/2 are registered trademarks of International Business Machines Corporation. AS/400,CICS, DISOSS, Displaywriter, OS/2, OS/2 EE, OS/400 PROFS, TSO, and VTAM are trademarks of International Business Machines Corporation. UNIX is a registered trademark in the United States and other countries, licensed exclusively through X/Open Company Ltd. _________________________________________________________________ Contents Preface................................................... ix Part I Installation 1 Preparing to Install the Compaq SNA Peer Server for Tru64 UNIX Software 1.1 Inspecting the Distribution Kit............... 1-1 1.2 System Requirements........................... 1-1 1.2.1 Required Hardware......................... 1-1 1.2.2 Required Software......................... 1-2 1.2.3 Optional Software......................... 1-3 1.2.4 Peer Server Subsets....................... 1-4 1.2.5 Installation Time......................... 1-4 1.3 Preparing to Install.......................... 1-4 1.3.1 Obtaining Superuser Privileges............ 1-5 1.3.2 Verifying Disk Space...................... 1-5 1.3.3 Backing Up Your System.................... 1-5 1.3.4 Deleting Old Versions of the Peer Server.................................... 1-5 1.3.5 Registering the Product Authorization Key (PAK)..................................... 1-6 1.4 Stopping the Installation..................... 1-7 2 Installing the Peer Server 2.1 Installation from the CD-ROM or Your Network....................................... 2-1 2.1.1 Installing from a CD-ROM Drive............ 2-1 2.1.2 Installing over the Local Area Network with Remote Installation Service (RIS).... 2-4 iii 2.2 Running wddsetup to Configure the Underlying Data Links.................................... 2-5 2.3 Rebooting the System.......................... 2-10 2.4 Configuring the Compaq Tru64 UNIX Operating System for the Peer Server.................... 2-10 2.5 Rebooting the System.......................... 2-12 Part II Planning and Configuration 3 Beginning the Peer Server Configuration Process 3.1 The Configuration Process..................... 3-1 3.2 Planning Activities........................... 3-2 3.3 Using the Peer Server's Configuration Utility....................................... 3-3 3.3.1 Invoking the Configuration Utility........ 3-4 3.3.2 Input and Output Files.................... 3-6 3.3.3 The Configuration Dialog.................. 3-7 4 Configuring the Peer Server's SNA Access Server 4.1 Planning for the SNA Access Server............ 4-2 4.2 Dialog Section 1: SNA Access Server Configuration................................. 4-4 5 Configuring the Peer Server's Data Links 5.1 Planning the Peer Server Data Links........... 5-1 5.1.1 Planning for SDLC Data Links.............. 5-2 5.1.2 Planning for QLLC Data Links.............. 5-4 5.1.3 Planning for LLC2 Data Links.............. 5-6 5.2 Dialog Section 2: Data Link Layer Configuration................................. 5-8 5.2.1 Dialog Section 2.1: SDLC Configuration.... 5-9 5.2.2 Dialog Section 2.2: QLLC Configuration.... 5-14 5.2.3 Dialog Section 2.3 - LLC2 Configuration... 5-18 iv 6 Configuring the Peer Server's Logical Units 6.1 Planning the Peer Server's SNA LU Services.... 6-1 6.1.1 Planning the LU Authorizations............ 6-2 6.1.2 Planning Logical Units Using the List Method.................................... 6-4 6.1.3 Planning Logical Units Using the Populate Method.................................... 6-7 6.1.4 Planning Access Names..................... 6-9 6.1.5 Planning Partner LUs...................... 6-11 6.2 Dialog Section 3: SNA Logical Unit Services Configuration................................. 6-13 6.2.1 Dialog Section 3.1: Authorization Configuration............................. 6-13 6.2.2 Dialog Section 3.2: Logical Unit Configuration............................. 6-17 6.2.3 Dialog Section 3.3: Access Name Configuration............................. 6-26 6.2.4 Dialog Section 3.4: Partner LU Configuration............................. 6-29 7 Configuring the Peer Server's Control Point 7.1 Planning the Peer Server's Control Point...... 7-1 7.2 Dialog Section 4: SNA CP Services Configuration................................. 7-5 8 Completing the Peer Server's Configuration Process 8.1 Generating an NCL Script File................. 8-1 8.2 Running the Configuration Script File......... 8-2 8.3 Solving Configuration Problems................ 8-2 8.4 Modifying the Configuration with NCL.......... 8-2 8.5 Reconfiguring the Peer Server................. 8-3 9 Starting and Shutting Down the Peer Server 9.1 Starting the Peer Server...................... 9-1 9.1.1 Checking the Status of the Startup........ 9-1 9.2 Shutting Down the Peer Server................. 9-2 v Part III Appendixes A Compaq SNA Peer Server for Tru64 UNIX NCL Startup Scripts B Peer Server Configuration Error Messages C Synchronous Data Link Control (SDLC) on the Peer Server C.1 SDLC Modem Control Configurations............. C-1 C.1.1 Point-to-Point Full-Duplex (4-wire) SDLC Data Links................................ C-2 C.1.2 Point-to-Point Half-Duplex (2-wire) SDLC Data Links................................ C-2 C.1.3 Single-Station Full-Duplex Multipoint Secondary (4-wire)........................ C-3 C.1.4 Multiple-Station Full-duplex Multipoint Secondary (4-wire)........................ C-4 C.1.5 Single-Station Half-Duplex Multipoint (2-wire).................................. C-5 C.1.6 Multiple-Station Half-Duplex Multipoint (2-wire).................................. C-5 C.1.7 Multipoint Primary........................ C-6 C.2 SDLC Link Station 'Modulo' Characteristic..... C-6 D Qualified Logical Link Control (QLLC) on the Peer Server D.1 The Peer Server and the Compaq Wide Area Networking for Tru64 UNIX Configuration....... D-1 D.2 X.25 Relay Considerations..................... D-1 E Logical Link Control Type 2 (LLC2) on the Peer Server E.1 SAP Link Remote MAC Address Format............ E-1 E.2 MAC Address Format when DECnet-Plus is Running....................................... E-2 E.3 Comparison of NCL Attributes and IBM Parameters.................................... E-3 vi F Supporting More Than 128 Concurrent Sessions F.1 Supporting Up to 4,096 Concurrent DECnet Connections................................... F-1 F.2 Supporting Up to 10,000 Concurrent DECnet Connections................................... F-2 F.2.1 Calculating System Memory Requirements.... F-2 F.2.2 Modifying System Configuration Files...... F-3 F.2.3 Rebuilding the Kernel..................... F-5 F.2.4 Modifying System Startup Scripts.......... F-5 F.2.5 Modifying DECnet Startup Scripts.......... F-6 F.2.6 Rebooting the System...................... F-7 G Installing the Required Compaq Wide Area Networking for Tru64 UNIX Subsets G.1 Installation from the CD-ROM or Your Network....................................... G-1 G.1.1 Installing from a CD-ROM Drive............ G-1 G.1.2 Installing over the Local Area Network with Remote Installation Service (RIS).... G-6 Examples 4-1 Configuration Example (Section 1)......... 4-7 5-1 SDLC Configuration Example (Section 2.1)...................................... 5-13 5-2 QLLC Configuration Example (Section 2.2)...................................... 5-17 5-3 LLC2 Configuration Example (Section 2.3)...................................... 5-21 6-1 Configuration of an Authorization (Section 3.1)...................................... 6-16 6-2 Configuration Using Populate Option (Section 3.2)............................. 6-22 6-3 Configuration Using List Option (Section 3.2)...................................... 6-24 6-4 Configuration of Access Names (Section 3.3)...................................... 6-28 6-5 Configuration of a Partner LU (Section 3.4)...................................... 6-31 A-1 Mainframe Example (T2.0 Dependent LUs).... A-2 vii A-2 AS/400 Example (T2.1 Independent LUs)..... A-6 Tables 3-1 Peer Server Configuration Utility Editing Keys...................................... 3-4 4-1 The SNA Access Server Objects Worksheet... 4-4 5-1 The SDLC Link Information Worksheet....... 5-3 5-2 The QLLC Link Information Worksheet....... 5-5 5-3 The LLC2 SAP Link Information Worksheet... 5-7 6-1 The LU Authorizations Worksheet........... 6-3 6-2 The SNA Logical Units Worksheet (List Method)................................... 6-6 6-3 The SNA Logical Units (Populate Method) Worksheet................................. 6-8 6-4 The Access Names Worksheet................ 6-10 6-5 The Partner LUs Worksheet................. 6-12 7-1 The General SNA Information Worksheet..... 7-4 E-1 Relationship Between NCL Attributes and IBM Parameters............................ E-3 viii _________________________________________________________________ Preface Compaq Computer Corporation's Compaq SNA Peer Server for Tru64 UNIX software allows users of TCP/IP and DECnet[TM] networks to communicate with programs running on IBM® systems. These systems must be part of a network configured according to IBM's Systems Network Architecture (SNA). Objectives Compaq SNA Peer Server Installation and Configuration contains information about installing and configuring the Peer Server. Audience This manual is written for anyone responsible for managing and maintaining the Peer Server and related products. Structure This manual consists of the following chapters and appendixes: o Chapter 1 lists prerequisites for installing the Peer Server. o Chapter 2 describes the installation of the Peer Server on your Compaq system. o Chapter 3 describes how to begin the Peer Server configuration process. o Chapter 4 describes how to plan for and configure the Peer Server's SNA Access Server. o Chapter 5 describes how to plan for and configure the Peer Server's data links. ix o Chapter 6 describes how to plan for and configure the Peer Server's SNA logical units and associated information. o Chapter 7 describes how to plan for and configure the Peer Server's control point. o Chapter 8 describes how to finish the Peer Server configuration process. o Chapter 9 describes how to start and stop the Peer Server. o Appendix A provides example NCL startup script configurations for SDLC in two different environments. o Appendix B lists the error messages generated by the Peer Server Configuration utility. o Appendix C contains additional information about configuring SDLC data links. o Appendix D contains additional information about configuring QLLC data links. o Appendix E contains additional information about configuring LLC2 data links. o Appendix F describes the DECnet-Plus and Tru64 UNIX configuration changes that are required to support up to 10,000 concurrent DECnet connections. o Appendix G describes the installation of the required Compaq Wide Area Networking for Tru64 UNIX software subsets on your system. Associated Compaq SNA Peer Server Documents You should have available for reference the following documents in the Compaq SNA Peer Server for Tru64 UNIX product set: o Compaq SNA Peer Server Management o Compaq SNA Peer Server Network Control Language Reference o Compaq SNA Peer Server Guide to IBM Resource Definition x Associated IBM Documents You may find the following IBM documents useful: o Enterprise Networking with SNA Type 2.1 Nodes (IBM Order No. GG24-3433) o An Introduction to Advanced Program-to-Program Communication (APPC) (IBM Order No. GG24-1584) o SNA Type 2.1 Node Reference (IBM Order No. SC30-3422) o Systems Network Architecture Concepts and Products (IBM Order No. GC30-3072) o Systems Network Architecture Reference Summary (IBM Order No. GA27-3136) o Systems Network Architecture Technical Overview (IBM Order No. GC30-3073) Conventions Used in This Guide The following documentation conventions are used throughout this manual: Special type This special type in examples indicates system output or user input. System output is in plain type; user input is shown in bold type. In examples, the symbol (#) is used to represent the system prompt. This prompt may be different on your system. lowercase- Lowercase italic type in command syntax italics or examples indicates variables for which either the user or the system supplies a value. { } Braces indicate a choice you must make. Braces enclose values that either are separated by a vertical bar (|) or are listed vertically. Choose either from the values separated by the vertical bar or from the list enclosed by the braces. Do not type the braces in the line of code. xi [ ] Brackets enclose operands or symbols that are either optional or conditional. Specify the operand and value if you want the condition to apply. Do not type the brackets in the line of code. | A vertical bar indicates a choice you must make from the values separated by the bar. Do not type the vertical bar in the line of code. Indicates that you should hold the Ctrl key down and press the key specified by the x. The server displays the key combination as ^x. Indicates that you should press the Return key. The Return key, which you must press to execute commands, is assumed in most command examples. Therefore, the Return key is not always shown in command examples. Acronyms The following acronyms appear throughout this manual: BOM Bill of Materials CP control point DLC Data Link Control DTE data terminal equipment FDDI Fiber Distributed Data Interface I-frame Information frame LAN Local Area Network LDB License Database LLC2 Logical Link Control type 2 LMF License Management Facility LU logical unit NCL Network Control Language xii NPSI X.25 Network Control Program Packet Switching Interface NRZI non-return-to-zero-inverted PAK Product Authorization Key PIU path information unit PLU primary logical unit PSDN X.25 Packet Switched Data Network PU physical unit QLLC Qualified Logical Link Control RIS Remote Installation Service RU request/response unit SAP Service Access Point SDLC Synchronous Data Link Control SLU secondary logical unit SNA Systems Network Architecture SNRM set normal response mode SNRME set normal response mode extended SPD Software Product Description SSCP system services control point SSA System Support Addendum TG transmission group WAN Wide Area Network Terminology This manual uses the following terminology: DIGITAL UNIX Refers to Compaq's version of the UNIX operating system, formerly known as DIGITAL UNIX, now called Compaq Tru64 UNIX. Interconnect Refers to the Compaq SNA Peer Server for system Tru64 UNIX software. Interconnect Refers to the Compaq SNA Peer Server for products Tru64 UNIX and the SNA access routines. xiii Network manager Refers to the person responsible for the installation and management of an interconnect product. Non-SNA Refers to a TCP/IP or DECnet system. xiv Part I _________________________________________________________________ Installation This part describes how to prepare for the Peer Server software installation and how to use the setld utility to install the the Peer Server software. 1 _________________________________________________________________ Preparing to Install the Compaq SNA Peer Server for Tru64 UNIX Software This chapter discusses the planning you must do prior to installing the Compaq SNA Peer Server for Tru64 UNIX product (referred to in this document as the Peer Server). Planning issues covered here include an overview of the installation procedure, system requirements, installation choices, software license Product Authorization Key (PAK) requirements, and other system dependencies. 1.1 Inspecting the Distribution Kit The software Bill of Materials (BOM) that shipped with your Peer Server media distribution kit lists the contents of the kit. Carefully compare the items you received with the items listed in the BOM. If any components are missing or damaged, contact your Compaq representative before continuing. Before proceeding with the installation, Compaq strongly recommends that you read the Release Notes which ship as part of the online documentation. 1.2 System Requirements This section lists and describes the hardware and software requirements your site must meet before you install the Peer Server. 1.2.1 Required Hardware To install the Peer Server successfully, you must have the following minimum hardware configuration: o Alpha workstation or server o 64 MB RAM recommended (minimum) to Install the Compaq SNA Peer Server for Tru64 UNIX Software 1-1 See the Software Product Description (SPD) for a list of the processors which support the Peer Server. 1.2.2 Required Software The Peer Server requires the following software: o Compaq Tru64 UNIX Version 5.0 or later In addition to Compaq Tru64 UNIX software, the Peer Server requires the following software subsets from the Compaq Wide Area Networking for Tru64 UNIX software product (Version 3.1 or later): o CTF Collector Components (CTABASEnnn) o CTF User Environment (CTAANALnnn) o DECnet-Plus Network Management (DNANETMANnnn) o DECnet-Plus Kernel Components (DNAKBINnnn) o WAN Utilities Base (ZZAUTILnnn) o WDD Base Component (WDABASEnnn) o WDD Datalink Protocols (WDADATALNKSnnn) If you plan to use an SDLC data link, the Peer Server requires the following additional Compaq Wide Area Networking for Tru64 UNIX software subset: o WDD Synchronous Device Drivers (WDADRIVERSnnn) If you plan to use an LLC2 data link, the Peer Server requires the following additional Compaq Wide Area Networking for Tru64 UNIX software subset: o DECnet-Plus Base Components (DNABASEnnn) The Compaq Wide Area Networking for Tru64 UNIX subsets must be installed before you install the Peer Server software. See Appendix G for information about how to install the subsets. 1-2 Preparing to Install the Compaq SNA Peer Server for Tru64 UNIX Software 1.2.3 Optional Software The following software allows the Peer Server to support additional functionality: o DECnet-Plus for Tru64 UNIX Version 5.0 or later The Peer Server supports both DECnet and TCP/IP networks. If you plan to have DECnet/SNA access routines, you must install DECnet-Plus for Tru64 UNIX software on the Peer Server. If you do not plan to use DECnet/SNA access routines, you do not need to install DECnet-Plus for Tru64 UNIX software on the Peer Server system. _______________________ Caution _______________________ If you need to install or upgrade DECnet-Plus for Tru64 UNIX software on a system already running a version of the Peer Server software, you must delete the Peer Server subsets before installing or upgrading the DECnet-Plus software. Once you have installed and configured the DECnet-Plus software, you should install the Peer Server V1.5 software. See Section 1.3.4 for information about how to delete Peer Server subsets. ______________________________________________________ o Compaq Wide Area Networking for Tru64 UNIX Version 3.1 or later The Compaq Wide Area Networking for Tru64 UNIX software allows the Peer Server to send and receive data over X.25 Packet Switched Data Networks (PSDNs) using the Qualified Logical Link Control (QLLC) protocol. This allows the non-SNA applications using the Peer Server to communicate with IBM systems using SNA protocols over X.25 networks. The Peer Server's QLLC implementation supports both direct synchronous communications link access (LAPB) and LAN access to an X.25 relay node (LLC2). To use the Compaq Wide Area Networking for Tru64 UNIX software you must also have companion software installed and configured on the IBM system (for example, the X.25 Network Control Program Packet Switching Interface (NPSI) software for IBM front-end communications to Install the Compaq SNA Peer Server for Tru64 UNIX Software 1-3 processors). If you do not plan to use the QLLC protocol, you do not need to install Compaq Wide Area Networking for Tru64 UNIX software on the Peer Server system. _______________________ Caution _______________________ If you need to install or upgrade Compaq Wide Area Networking for Tru64 UNIX software on a system already running a version of the Peer Server software, you must delete the Peer Server subsets before installing or upgrading the Compaq Wide Area Networking for Tru64 UNIX software. Once you have installed and configured the Compaq Wide Area Networking for Tru64 UNIX software, you should install the Peer Server V1.5 software. See Section 1.3.4 for information about how to delete Peer Server subsets. ______________________________________________________ 1.2.4 Peer Server Subsets The following subsets are included in the Peer Server kit. o Compaq SNA Peer Server Management (T21MGMT150) o Compaq SNA Peer Server (T21SRVR150) 1.2.5 Installation Time Installation of the Peer Server requires approximately 5 minutes. 1.3 Preparing to Install Before you begin the actual installation, prepare your system for the Peer Server. Preparation includes the following activities: o Obtaining superuser privileges. o Checking for sufficient system disk space. o Optionally, backing up your system disk. Compaq strongly recommends that you perform a full system backup before installation. o Registering your Product Authorization Key (PAK). 1-4 Preparing to Install the Compaq SNA Peer Server for Tru64 UNIX Software 1.3.1 Obtaining Superuser Privileges To install and configure the Peer Server, you must have superuser privileges. To acquire these privileges, enter the following command followed by the root password. See the Compaq Tru64 UNIX system manager documentation for more details. % su - root password: password # 1.3.2 Verifying Disk Space Check the free disk space on your system. You must have sufficient free space to install and configure the Peer Server. The installation will fail if there is insufficient space for copying the software from the distribution media. Minimum space requirements for the Peer Server are as follows: o 8 MB in the /usr partition. To check the free space in the /usr partition, enter the following command: # df -k /usr 1.3.3 Backing Up Your System Before installing the Peer Server, back up your system disk. See the document Compaq Tru64 UNIX Guide to System Administration for further details. 1.3.4 Deleting Old Versions of the Peer Server Before you begin the installation, check to see whether a previous version of the Peer Server exists on your system. If it does, you must delete those subsets before you install the new Peer Server software. NCL scripts or answer files previously created will remain in the /var/sna directory for use with the new software version. Use the following command to see whether the Peer Server is installed on your system, where T21 is the subset name prefix of the Peer Server subsets: # setld -i | grep -e "^T21" to Install the Compaq SNA Peer Server for Tru64 UNIX Software 1-5 The system displays a list of subsets. If the word "installed" follows the name of the subset, then that subset is installed. To delete the software from your system, log in as superuser and enter the setld command with the -d option, as follows: # setld -d subset [subset...] where subset is the name of one of the Peer Server subsets listed in Section 1.2.4. 1.3.5 Registering the Product Authorization Key (PAK) The Peer Server supports the License Management Facility (LMF). You must register your license PAK in the License Database (LDB) to use the Peer Server on a newly licensed node. LMF maintains a file of registered software license PAKs. Also, LMF keeps a library of functions used by Compaq licensed software. To register the Peer Server license PAK using LMF, proceed as follows: 1. Log on to your system as superuser: % su - root password: password # 2. Enter the following command from the superuser prompt. Press Return after the confirmation message appears: # lmfsetup Register PAK (type q or quit to exit) [template] 3. After you confirm the procedure, the system prompts you for information related to the fields on your PAK form. This form ships with your Peer Server distribution kit if you ordered the license and media together. Otherwise, Compaq ships it separately to a location based on your license order. Using the information from your Peer Server PAK form, reply to each question. Any fields left blank in your PAK form should be left blank when you enter the data. 1-6 Preparing to Install the Compaq SNA Peer Server for Tru64 UNIX Software 4. After you have answered all questions, the system displays the following completion message. Enter quit and press Return: Register PAK (type q or quit to exit) [template] quit 5. After leaving lmfsetup, enter the following reset command: # lmf reset 6. If you attempted to load a PAK when a previous PAK was already installed, a message similar to the following appears: Combine SNA-PEER-SERVER-USER auth-num with SNA-PEER-SERVER-USER auth-num 7. After completing the LMF procedure, verify your registration: # lmf list For further information concerning the use of the LMF software or for more details about obtaining a license and PAK, see the document Compaq Tru64 UNIX Guide to Software License Management. You can also reference the lmf and lmfsetup man pages (lmf(8) and lmfsetup(8)). This completes the preinstallation procedure for the Peer Server. Chapter 2 describes the actual Peer Server installation process. 1.4 Stopping the Installation To stop the installation at any time, press Ctrl/C. You must then delete files created up to this point interactively. The directories and files created during Peer Server installation are listed in the Peer Server's Release Notes. to Install the Compaq SNA Peer Server for Tru64 UNIX Software 1-7 2 _________________________________________________________________ Installing the Peer Server This chapter describes the Compaq SNA Peer Server for Tru64 UNIX installation process. Before installing the Peer Server, you must register your software license Product Authorization Key (PAK) using the License Management Facility (LMF). See Chapter 1 for details. 2.1 Installation from the CD-ROM or Your Network You can install the Peer Server software from two locations: the Consolidated Software Distribution CD-ROM or a remote node in your local-area network using the Remote Installation Service (RIS). 2.1.1 Installing from a CD-ROM Drive To install the Peer Server subset from the Consolidated Software Distribution CD-ROM, do the following: 1. Determine the location of the Peer Server files on the CD-ROM. See the master index table in the document Consolidated Software Distribution Disk User's Guide for the directory containing the files. 2. Insert the CD-ROM into the drive and mount the disk using the drive's device name. If you do not know the device name, enter the following command to list available drives. The drive is either RRD40 or RRD42. # file /dev/rr*c To mount the disk, enter the following command, where dev-name is the block device name of your drive. # mount -r -d /dev/dev-name /mnt For example, a character special device of /dev/rrz4c, shown by the command file /dev/rr*c, would be entered as the block device /dev/rz4c. Installing the Peer Server 2-1 3. Install the Peer Server software using the following setld command, where T21150/kit is the name of the directory on the CD-ROM where the Peer Server files are located: # setld -l /mnt/T21150/kit After you enter the setld command, the system displays the following messages. When you have read them, press Return to continue. Compaq SNA Peer Server for Tru64 UNIX V1.5-0 (Rev. 1) Copyright Electronic Data Systems Corporation 1999, 1997. All Rights Reserved. Copyright Digital Equipment Corporation 1996. All Rights Reserved. This software is proprietary to and embodies the confidential technology of Digital Equipment Corporation. Possession, use, duplication or dissemination of this software and media is authorized only pursuant to a valid written license from Digital Equipment Corporation or an authorized sublicensor. RESTRICTED RIGHTS: Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in Subparagraph (c)(1)(ii) of DFARS 252.227-7013, or in FAR 52.227-19, or in FAR 52.227-14 Alt. III, as applicable. To install and configure the DIGITAL SNA Peer Server on this system, choose all subsets in the following selection. To install just the management support, select just those subsets in the DIGITAL SNA Peer Server Management section. The installation will complete in 3-5 minutes depending on processor type. Consult the DIGITAL SNA Peer Server Installation & Configuration guide for more details. Hit to continue: You now select the combination of optional subsets you wish to install from a menu. You are required to install the two Peer Server subsets. Enter the number of your selection and press Return. The system asks for confirmation. The subsets listed below are optional: There may be more optional subsets than can be presented on a single screen. If this is the case, you can choose subsets screen by screen or all at once on the last screen. All of the choices you make will be collected for your confirmation before any subsets are installed. 2-2 Installing the Peer Server - DIGITAL SNA Peer Server 1) DIGITAL SNA Peer Server - DIGITAL SNA Peer Server Management: 2) DIGITAL SNA Peer Server Management Or you may choose one of the following options: 3) ALL of the above 4) CANCEL selections and redisplay menus 5) EXIT without installing any subsets Enter your choices or press RETURN to redisplay menus. Choices (for example, 1 2 4-6): 3 You are installing the following optional subsets: - DIGITAL SNA Peer Server: DIGITAL SNA Peer Server - DIGITAL SNA Peer Server Management: DIGITAL SNA Peer Server Management Is this correct? (y/n): y Once you have verified your selection, the system installs the subsets and displays a series of in-progress messages. Checking file system space required to install selected subsets: File system space checked OK. 2 subset(s) will be installed. Loading 1 of 2 subset(s).... DIGITAL SNA Peer Server Management Copying from /mnt/T21150/kit (disk) Verifying Loading 2 of 2 subset(s).... DIGITAL SNA Peer Server Copying from /mnt/T21150/kit (disk) Verifying 2 of 2 subset(s) installed successfully. Installing the Peer Server 2-3 Installing Compaq SNA Peer Server for Tru64 UNIX V1.5-0 (Rev. 1) Copyright Electronic Data Systems Corporation 1999, 1997. All Rights Reserved. Copyright Digital Equipment Corporation 1996. All Rights Reserved. Creating softlinks for T21MGMT150 ... done. Configuring "DIGITAL SNA Peer Server Management " (T21MGMT150) Installing Compaq SNA Peer Server for Tru64 UNIX V1.5-0 (Rev. 1) Copyright Electronic Data Systems Corporation 1999, 1997. All Rights Reserved. Copyright Digital Equipment Corporation 1996. All Rights Reserved. Creating softlinks for T21SRVR150 ... done. Configuring "DIGITAL SNA Peer Server " (T21SRVR150) The system next displays some instructions on how to complete the installation process. After you have read them, press Return to continue. To complete the installation and configuration of the DIGITAL SNA Peer Server software and the underlying WAN Datalink Protocols and WAN Device Drivers (if any), please execute the command # /usr/sbin/wddsetup Reboot the kernel if you get such an instruction while running wddsetup and execute the command # /usr/sbin/t21setup Refer to the DIGITAL SNA Peer Server Installation & Configuration guide for details. Hit to continue: This completes the setld phase of the installation process. Proceed to Section 2.2 to continue the installation process. 2.1.2 Installing over the Local Area Network with Remote Installation Service (RIS) If you are installing the Peer Server over your local area network, use the RIS utility. See the document Sharing Software on a Local Area Network for RIS requirements. Enter the following command, where host-name is the name of the node from which you are loading the software. # setld -l host-name: 2-4 Installing the Peer Server The installation then proceeds as described in the previous section. 2.2 Running wddsetup to Configure the Underlying Data Links After completing the installation script as described in Section 2.1.1, you must run the wddsetup script included in the Compaq Wide Area Networking for Tru64 UNIX software to configure the underlying data links that the software implements. # /usr/sbin/wddsetup The wddsetup script begins by configuring several of the required Compaq Wide Area Networking for Tru64 UNIX subsets: Configuring "CTF Collector Components" (CTABASE310) WAN Device Drivers for DIGITAL UNIX Configurator. (c) Digital Equipment Corporation. 1998. All Rights Reserved. Configuring "WDD Base Component" (WDABASE310) Configuring "WDD Datalink Protocols" (WDADATALNKS310) Now you specify the hardware devices on which you want the WAN Device Drivers and Datalink Protocols (WDA) software to be run. The system displays the devices supported on your system and asks you to choose. The system prompts you for your choice and asks for confirmation before proceeding. ________________________ Note ________________________ The choices discussed in this section do not address data link considerations outside the scope of the Peer Server. If you have other network applications on the system, they may use other data link protocol combinations not discussed in this section. This may require you to change your answers to some of the following questions. For example, consider the case where the system, in addition to supporting the Peer Server, is independently supporting an application that uses the X.25 relay node feature of the Compaq Wide Area Networking for Tru64 UNIX software. Further, assume that you are configuring the Peer Server to support Installing the Peer Server 2-5 only SDLC data links and therefore no Level 2 datalink protocol is needed. Despite the fact that the Peer Server requires no Level 2 datalinks, you must choose both HDLC/LAPB and LLC2 protocols when prompted to select the datalink protocol options. ______________________________________________________ Configuring "WDD Synchronous Device Drivers" (WDADRIVERS310) You must now specify the hardware device(s) on which you want the WAN Device Drivers and Datalink Protocols (WDA) software to be run. Note that with the LLC2 datalink protocol, no synchronous drivers need to be specified as this protocol operates over a LAN. The synchronous devices supported on your system are: scc - DEC 3000 (all models) synchronous line dsy - TURBOchannel T1/E1 synchronous line option none - No synchronous device driver is required Please specify which device(s) {dsy scc none} are to be used. Note that the modem connect lines will use the devices according to the order they appear in (i.e. line line-0 will use the first device and so on). [scc]: The scc driver will be configured. Is this correct? (y/n) [y]: The script next prompts you to specify which datalink protocols are needed for your Peer Server installation. If you are using only SDLC, choose option (1) to indicate that you do not need any Level 2 protocol. If you are using QLLC over local synchronous datalinks, choose option (2) to indicate that you require only HDLC/LAPB support. If you are using LLC2 or you are using QLLC over an X.25 relay node, choose option (3) to indicate that you require only LAN datalink support. If you are using a combination of QLLC and LLC2 or both QLLC over an X.25 relay node and QLLC over local synchronous datalinks, choose option (4), indicating that you need both HDLC/LAPB support and LAN datalink support. The example that follows selects an installation option for a Peer Server that supports SDLC connections, QLLC connections, and LLC2 connections. 2-6 Installing the Peer Server Select one of the following datalink protocol options: 1) No Level 2 datalink protocol is required. 2) The HDLC/LAPB Synchronous datalink protocols are required. 3) The LLC2 (LAN) datalink protocol is required. 4) All datalink protocols (HDLC/LAPB/LLC2) are required. Enter datalink protocol option(s) required [2]: 4 You have selected both the WAN (HDLC/LAPB) and LAN (LLC2) datalinks. Is this correct? (y/n) [y]: Next, you specify which of the synchronous ports you have selected will operate in half-duplex mode. Specify half- duplex for point-to-point half-duplex lines. Specify full- duplex for full-duplex multipoint lines. The specification of the line as multipoint is made during the Peer Server configuration process. See Chapter 5 for more information about configuring the SDLC entities. See Appendix C for a discussion of the possible SDLC configurations. You must now specify which of the synchronous ports you have configured will operate in half-duplex mode. The ports you have configured on your system are: sscc0 Please specify which port(s) will operate in half-duplex mode. [none]: No lines will operate in half-duplex mode. Is this correct? (y/n) [y]: Enter the line speed to be used on half-duplex point-to- point and multipoint lines. The Peer Server software uses this value to run the half-duplex modem control protocols properly. If you do not enter a value for a line, then the Peer Server software assumes the line is running at 1200 bps. _______________________ Warning _______________________ The actual clocking on the line is always derived from the DCE. If your line modem is operating at a different line speed than the one you specify here, the data link may not synchronize properly or communication may be highly error prone. If your Installing the Peer Server 2-7 line modem changes line speed dynamically, you should specify the lowest line speed supported by the modem. ______________________________________________________ You must enter the line speed for any ports which will be used for IBM multipoint. Line speed must be entered in bits/second. Eg. 19.2Kbits/sec should be entered as "19200". Enter the Line Speed for port sscc0 [no default] : 9600 Port sscc0 will run at 9600 BPS. Is this correct? (y/n) [y]: Next, the script asks you to enter those lines that use nonreturn-to-zero-inverted (NRZI) bit encoding to maintain bit synchronization across longer frames. _______________________ Warning _______________________ It is mandatory that you specify those devices that use NRZI encoding. A misconfigured link will result in the total inability to receive or transmit data with no apparent cause for the failure. ______________________________________________________ Some communication devices utilize NRZI (nonreturn-to-zero-inverted) bit encoding to maintain bit synchronization across longer frames. From the list of device ports displayed, select those that you want to use NRZI encoding. A port should only be selected to use NRZI encoding if its hardware and the remote device(s) are configured to require it. If you are uncertain as to the correct response, check with your network administrator. The ports you have configured on your system are: sscc0 Please specify which port(s) are to use NRZI. [none]: No lines will use NRZI encoding. Is this correct? (y/n) [y]: 2-8 Installing the Peer Server The script now prints a series of messages telling you how to complete the configuration of the WAN Support for DIGITAL UNIX software. _______________________ CAUTION _______________________ DO NOT FOLLOW THE INSTRUCTION TO RUN THE /usr/sbin/wansetup SCRIPT. These instructions are for users of the full Compaq Wide Area Networking for Tru64 UNIX product. ______________________________________________________ To complete the configuration of WAN Support for DIGITAL UNIX, create a WAN network configuration by running the command: /usr/sbin/wansetup [BASIC|ADVANCED] NOTE: If you wish to verify that WAN Support has installed correctly, you may verify the Wide Area Device Driver component by executing the command: setld -v WDABASE310 X.25 components may be verified by executing the command: setld -v .lk Running either of these verifications will invalidate any existing BASIC or ADVANCED configuration information and you will have to reboot the system. Wide Area Configuration is complete. The script now prints a series of messages telling you how to either restart the Compaq Wide Area Networking for Tru64 UNIX product or reboot the system to have the modifications you made take effect. _______________________ CAUTION _______________________ DO NOT FOLLOW THE INSTRUCTION TO RUN THE /usr/sbin/wanstartup SCRIPT. These instructions are for users of the full Compaq Wide Area Networking for Tru64 UNIX product. You should reboot the system using either the shutdown or reboot program. ______________________________________________________ Installing the Peer Server 2-9 For the WAN configuration modifications to take effect, either restart the WAN services by running the following command: /usr/sbin/wanstartup [START|RESTART] or reboot the system with the following command. /usr/sbin/shutdown -r now The script then completes and exits. wddsetup completed successfully. 2.3 Rebooting the System The /usr/sbin/t21setup script, discussed in the next section, tests whether the required data links drivers have been installed and whether these drivers are loaded. Therefore, you must reboot the system before continuing. To reboot the system containing the Peer Server software, enter either of the following commands: o # shutdown -r now o # /sbin/reboot 2.4 Configuring the Compaq Tru64 UNIX Operating System for the Peer Server Once the system has been rebooted, you must configure the Compaq Tru64 UNIX operating system for the Peer Server software. Enter the following command: # /usr/sbin/t21setup The system needs to know what Data Link Control (DLC) interfaces to include in the Peer Server configuration. It prompts you to identify which of these interfaces (SDLC, LLC2, and QLLC) you want to include in the system. # /usr/sbin/t21setup DIGITAL SNA Peer Server V1.5-0 for DIGITAL UNIX CONFIGURATION PROCEDURE Copyright Electronic Data Systems Corporation 1999, 1997. All Rights Reserved. Copyright Digital Equipment Corporation 1996. All Rights Reserved. 2-10 Installing the Peer Server There will be a pause while this procedure gathers some information from your system. DIGITAL SNA Peer Server updating dependent products done. This procedure allows you to add DIGITAL SNA Peer Server support to your DIGITAL UNIX kernel. The SNA Peer Server must be configured with one or more of the following datalink control interfaces: SDLC (WAN synchronous connect), LLC2 (LAN connect), or QLLC (SNA over X.25). LLC2 is required for SNA over token ring. Do you wish to configure SDLC? (y/n) [n]: y You have chosen to include the SDLC datalink Is this correct? (y/n) [y]: SDLC included... Do you wish to configure QLLC? (y/n) [n]: You have chosen to not include the QLLC datalink Is this correct? (y/n) [y]: Do you wish to configure LLC2? (y/n) [n]: You have chosen to not include the LLC2 datalink Is this correct? (y/n) [y]: The script creates and links the Peer Server special files. The script displays the following informational messages: DIGITAL SNA Peer Server creating system startup/shutdown links DIGITAL SNA Peer Server creating streams special files ... done. Next, the script gives you an opportunity to invoke the Peer Server's Configuration utility to create the initial Peer Server startup configuration. This manual assumes that you will need to plan for the Peer Server's configuration and therefore suggests that you delay configuration until you have read the remaining chapters in this manual. See Chapter 3 for information on using the Peer Server's Configuration utility at a later time. The script displays the following prompt: Do you wish to configure the DIGITAL SNA Peer Server startup now? [y] n Installing the Peer Server 2-11 The script also gives you the opportunity to invoke the Configuration utility for the TN3270 Server that ships as part of the Peer Server. You can configure the server to listen on multiple TCP/IP ports for incoming TN3270 client requests with each separate port mapped by the TN3270 server to use a specific access name defined in the Peer Server. The TN3270 Configuration Utility dialog is described in the Compaq SNA Peer Server Management manual. ________________________ Note ________________________ If you want to configure the TN3270 Server configuration at some later time, execute the script file /usr/sbin/tn3270_setup. ______________________________________________________ The script displays the following prompt: Do you wish to configure the tn3270 server? [y] n t21setup completed successfully. 2.5 Rebooting the System Reboot the system containing the Peer Server software. You can enter either of the following commands: o # shutdown -r now o # /sbin/reboot This completes the installation of the Compaq SNA Peer Server for Tru64 UNIX software on your Tru64 UNIX operating system. 2-12 Installing the Peer Server Part II _________________________________________________________________ Planning and Configuration This part describes how to plan for and configure the Peer Server software. 3 _________________________________________________________________ Beginning the Peer Server Configuration Process 3.1 The Configuration Process To configure the Peer Server, follow these steps: 1. Install the Peer Server software (discussed in Chapter 2). 2. Plan the SNA and Data Link Control (DLC) operating parameters needed for a successful Peer Server configuration (see Section 3.2 and Chapters 4 through 7). You may also wish to read the introductory material in the document Compaq SNA Peer Server Management to better understand the structure of the Peer Server software. 3. Configure the Peer Server using the Configuration utility and create the Network Control Language (NCL) script file (see Section 3.3 and Chapters 4 through 8). 4. Configure the host IBM system. The document Compaq SNA Peer Server Guide to IBM Resource Definition discusses the configuration of the IBM host systems. 5. Use the startup NCL script to initialize the Peer Server. (If the configuration was done on a different system, copy the startup NCL script to the Peer Server system first.) 6. If necessary, modify the Peer Server configuration with NCL. Beginning the Peer Server Configuration Process 3-1 3.2 Planning Activities Before you begin the actual configuration process, you should gather the information that you will need during the Peer Server's configuration. To better correlate the planning activities with the configuration activities, Chapters 4 through 7 discuss both the planning activities and configuration activities for the manageable entities that make up the Peer Server. The planning sections include worksheets that you can use to capture the information you will need during the configuration stage. To use the information in these chapters most effectively, you should make 2 passes through these chapters. First, read the brief planning section and then use the information in the configuration section to help you determine your answers. Second, use the information in the configuration sections if you encounter problems as you proceed through the configuration dialog. The following list itemizes the information that you must have before configuring the Peer Server and references the chapter that discusses the information. o SNA Access Server object parameters (see Chapter 4) o DLC information based on your data link type: (see Chapter 5) - Logical Link Control type 2 (LLC2) Service Access Point (SAP) and link parameters - Qualified Logical Link Control (QLLC) link and station parameters - Synchronous Data Link Control (SDLC) link and station parameters o SNA logical unit (LU) information: (see Chapter 6) o LU authorization parameters o Local LU parameters o Access name parameters o Partner LU parameters 3-2 Beginning the Peer Server Configuration Process o Control point (CP) parameters (see Chapter 7) Proceed to Chapter 4 and begin your planning activities. You may wish to read additional material in the document Compaq SNA Peer Server Management to aid you in the planning process. After you have completed your planning, proceed to Section 3.3. 3.3 Using the Peer Server's Configuration Utility After you have completed the planning activities discussed in the planning sections of Chapter 4 through 7, you should use the Peer Server Configuration utility to create an NCL startup script file which starts the Peer Server software. The file contains the NCL commands necessary to create the various Peer Server management entities (such as SDLC Link and Station entities and SNA LU Services LU and Access Name entities). The Configuration utility prompts you for the information necessary to build the NCL script file using a simple command-line interface that you can use from any terminal or terminal emulator that generates ANSI escape sequences. The utility saves your responses in an answer file and can read the answer file to obtain default answers. The utility can read, edit, and resave the answer file, so you can run the utility repeatedly until you are satisfied with the results. By default, the Configuration utility writes the NCL script to a file whose name stems from an output answer file name appended with the .ncl extension. If the output answer file name is t21_answer.ans, then the NCL script file name is t21_answer.ncl (see Section 8.1). You can then copy this file to the Peer Server startup script (/var/sna/t21_init_sna_server.ncl). In this way, you can create multiple configurations using different answer file names and NCL script files. For any special commands that are needed that the Configuration utility does not prompt for, you have the option of supplying an additional file containing NCL commands that is appended to the NCL script file generated Beginning the Peer Server Configuration Process 3-3 by the Configuration utility when the NCL script file is written. 3.3.1 Invoking the Configuration Utility Before you invoke the Configuration utility, you should set your default directory to the location where you wish to keep the answer files, the NCL startup files, and optional NCL files. (The installation procedure creates the directory /var/sna to store the Peer Server startup NCL script; you might choose to keep the associated files there as well.) To invoke the Configuration utility, enter the following command: # /var/sna/t21icu The utility provides command-line recall and editing. Table 3-1 lists editing keys. ________________________ Note ________________________ The Configuration utility provides context-sensitive help for all questions. If you enter a question mark (?) in response to any question, the utility will present you with text to explain the current question or syntax. ______________________________________________________ Table_3-1_Peer_Server_Configuration_Utility_Editing_Keys___ Editing_Key___________Function_____________________________ (sometimes Exit the program. labeled "Exit") , Recall previous entry (go up the , or command stack). or Go down the command stack. Move the cursor left. (continued on next page) 3-4 Beginning the Peer Server Configuration Process Table 3-1 (Cont.) Peer Server Configuration Utility Editing __________________Keys_____________________________________ Editing_Key___________Function_____________________________ Move the cursor right. or Go to the beginning of the line. Go to the end of the line. Delete one character to the left. Delete one character to the right. Delete one word to the left. Delete from the cursor to the beginning of the line. or Redisplay the line. , , Toggle insert/overstrike mode. or ______________Toggle_CRT/hardcopy_mode.____________ When you invoke the Configuration utility, it displays the following information. # /var/sna/t21icu Compaq SNA Peer Server for Tru64 UNIX Configuration Procedure V1.5 Copyright Electronic Data Systems Corporation 1999, 1997. All Rights Reserved. Copyright Digital Equipment Corporation 1996. All Rights Reserved. Please respond to the questions that follow, providing configuration input specific to your Peer Server installation. After all questions are answered, an NCL script file will be created. The configuration questions are grouped into several sections, with the option to repeat each section as you go along. Enter ? at any time for help. Enter F10 at any time to quit. Completed sections are saved in the specified answer file, which can be used for default input values the next time the procedure is run. You can terminate a configuration dialog at any time by entering F10 in response to a question. The Configuration utility will save all your answers through the last completed section. You can continue a terminated session later by using the saved partial answer file as the input answer file in a future run of the Configuration utility. Beginning the Peer Server Configuration Process 3-5 ________________________ Note ________________________ When editing a preexisting configuration, either by repeating a section or by reading and editing a preexisting answer file, you can delete an entity by entering a space and pressing Return. ______________________________________________________ 3.3.2 Input and Output Files The Configuration utility prompts you to enter the name of a saved answer file generated during a previous configuration dialog: Input answer file name : o If you have saved the Configuration utility answer file and wish to use it, enter the file name. Press Return if you do not have an answer file or do not wish to use it. Answer files created with earlier versions of the Configuration utility are automatically updated to this version of the utility. o If you specify an input answer file, the Configuration utility reads the information in the file until it reaches the end of a section then you are asked whether you want to repeat the section. If you answer yes, the utility repeats the section without reading the input answer file contents until the next section. o If you are using a saved answer file that you created during an incomplete dialog, the Configuration utility generates a warning message and switches back to prompting you for all information when it reaches the end of the saved answer input file. The Configuration utility prompts you to enter the name of an output answer file that will save the answers you provide. Output answer file name : The input answer file name you specified becomes the default name for the output answer file name. If you did not specify an input answer file name, t21_init_sna_ server.ans is the default output answer file name. To 3-6 Beginning the Peer Server Configuration Process override the default, you must provide a name. Note the following rules for answer file names: o If you accept the default output answer file name (that is the same name as the input answer file name), the utility overwrites the answer file. The utility saves the previous version in a backup file with the same name as the original input file name appended with a "~". If the input answer file name is t21_answ.ans, the backup name then becomes t21_answ.ans~. o If you specify an output answer file that is different than the input answer file name, and the file already exists, the utility saves the original file contents in a backup file with a name derived from the previous rule. 3.3.3 The Configuration Dialog After getting the input and output file information, the Configuration utility enters the first of the dialog sections. The following list shows the four Configuration utility dialog sections and references the chapter that discusses the section. o Section 1 - SNA Access Server Configuration - see Chapter 4 o Section 2 - DLC Configuration - see Chapter 5 o Section 3 - SNA LU Services Configuration - see Chapter 6 o Section 4 - SNA CP Services Configuration - see Chapter 7 After completing dialog Section 4, the Configuration utility enters the script file generation phase. Chapter 8 discusses the questions in this phase and how to run the resulting script file. Beginning the Peer Server Configuration Process 3-7 4 _________________________________________________________________ Configuring the Peer Server's SNA Access Server The configuration dialog lets you create SNA Access Server objects. These are used by the Peer Server to create outbound sessions to the TCP/IP or DECnet network that are initiated on receipt of a BIND request from the IBM network. You can reference these object names when you create the Peer Server's logical units (LUs). If you are not using outbound sessions, you do not need to define SNA Access Server objects. Go to Chapter 5. Configuring the Peer Server's SNA Access Server 4-1 4.1 Planning for the SNA Access Server Use the SNA Access Server Objects worksheet (Table 4-1) to record information about the non-SNA applications that IBM users can gain access to by way of the SNA Access Server. These applications are available to the SNA network. IBM users connect to one of these applications by connecting to Peer Server LUs that you link to one of the SNA Access Server objects. For each object you create, the utility asks for the type of network transport to use to connect to the remote object. You can select tcpip, decnet, or local. Next, the utility asks you to identify the application and its location, as follows: o For DECnet transport, indicate the node where the application resides and the DECnet object number or task name of the application on the node. The DECnet object number can range from 0 to 255. The object number 0 is a special case; use this object number to identify the application by task name instead of by DECnet object number. See the documentation for the SNA access routines you will be using to find the DECnet object numbers, if any, that each SNA access routine uses. o For TCP/IP transport, indicate the IP node name where the application resides and the port number or service name of the application. If you enter a port number the Service name prompt is omitted (since you may set one field or the other but not both). o For objects residing on the local system (the one the Peer Server is running on), you can create TCP/IP or DECnet connections using the DECnet or TCP/IP parameters, or you can use the local transport. In this case, you can specify the command to be issued and the local user name to run the command under. The command specifies the full path of a shell script or program to run. For more detailed information about the SNA Access Server dialog questions, see the prompt discussions in Section 4.2. 4-2 Configuring the Peer Server's SNA Access Server For each object, enter the name of the object, the transport that the Peer Server should use to reach the object, and the appropriate transport-specific information about the object. Repeat the process for all objects the Peer Server supports. Make additional copies of the worksheet if you need more space. Configuring the Peer Server's SNA Access Server 4-3 Table_4-1_The_SNA_Access_Server_Objects_Worksheet__________ Object name: __________________________ Transport (TCPIP, DECnet, _______________ local) [TCPIP]: Node/internet node: __________________________ Object/port number (0-32767) ____ ____ ____ ____ [0]: ____ Task/service name: ___________________________ Object name: __________________________ Transport (TCPIP, DECnet, _______________ local) [TCPIP]: Node/internet node: __________________________ Object/port number (0-32767) ____ ____ ____ ____ [0]: ____ Task/service name: ___________________________ Object name: __________________________ Transport (TCPIP, DECnet, _______________ local) [TCPIP]: Node/internet node: __________________________ Object/port number (0-32767) ____ ____ ____ ____ [0]: ____ Task/service name: ___________________________ ___________________________________________________________ 4.2 Dialog Section 1: SNA Access Server Configuration Section 1 of the configuration dialog lets you create the Peer Server's SNA Access Server objects. These are used by the Peer Server to create outbound sessions in the TCP/IP or DECnet network initiated on receipt of a BIND request from the IBM network. You reference the object names in Section 3 when creating logical units. If you are not using 4-4 Configuring the Peer Server's SNA Access Server outbound sessions, you can skip this dialog section by pressing Return at the Object name: prompt. Section 1 - SNA Access Server Configuration. -------------------------------------------- The following questions gather Object information for zero or more Objects. Enter the object name; it must be a name from 1 to 32 characters long. Pressing Return with no object name indicates that no more object names follow. Object name [] : The Configuration utility prompts you to enter the transport protocol used to reach the object. Enter tcpip, decnet, or local; the default is tcpip. Transport [TCPIP] : If you entered either tcpip or decnet in response to the transport prompt, the Configuration utility uses one of the following prompts to ask you to enter the name of the node to which to connect. Enter an internet host name or a DECnet node name; the default is none. Internet node [] : Node [] : If you entered either tcpip or decnet in response to the Transport prompt, the Configuration utility uses one of the following prompts to ask you the TCP port number or DECnet object number on the remote node. Enter the TCP port number from 0 to 32767 or DECnet object number from 0 to 255. If you wish to access the object by service name or task name, press Return. Port number [] : Object number [0] : If you entered either tcpip or DECnet in response to the Transport prompt and you indicated that you wanted to access the object by name, the Configuration utility uses one of the following prompts you to ask you the TCP service name or DECnet task name on the remote node. The default is none. Configuring the Peer Server's SNA Access Server 4-5 Service name [] : Task [] : If you entered local in response to the Transport prompt, the Configuration utility prompts you for information about the local task. First, it prompts you for the command string that the Peer Server should use to invoke the local task. If the local task is NOT expected to be running, enter the appropriate command line. The default is no command string. Next, the utility asks for the local user name under which it should run the indicated command. If the local task is NOT expected to be running, enter the appropriate user name. The default is root. Finally, the Configuration utility prompts you for the name of the local task. If the local task IS expected to be running, enter the appropriate task name. The default is no task name. Command [] : Local User Name [root] : Task [] : The Configuration utility repeats this series of prompts for another object. When you have defined all the objects, you can continue to the next section by pressing Return. Object name [] : The utility asks if you wish to repeat the section. Press Return to continue: Do you wish to repeat Section 1, SNA Access Server Configuration [N] ? Example 4-1 uses the Configuration utility to create one object to connect to port 2534 on internet node gratis.eng.bigcorp.com and another to connect to DECnet object 231 on DECnet node .corp.mynode. 4-6 Configuring the Peer Server's SNA Access Server Example 4-1 Configuration Example (Section 1) Section 1 - SNA Access Server Configuration. -------------------------------------------- The following questions gather Object information for zero or more Objects. Object name [] : cpicprog Transport [TCPIP] : tcpip Internet node [] : gratis.eng.bigcorp.com Port number [] : 2534 Object name [] : dspiprog Transport [TCPIP] : decnet Node [] : .corp.mynode Object number [0] : 231 Object name [] : Do you wish to repeat Section 1, SNA Access Server Configuration [N] Configuring the Peer Server's SNA Access Server 4-7 5 _________________________________________________________________ Configuring the Peer Server's Data Links 5.1 Planning the Peer Server Data Links The configuration dialog ask you several question to define the Peer Server's data links. You refer to these data links when you define the Peer Server's transmission groups. The Peer Server supports the following data links: o synchronous data links using the Synchronous Data Link Control (SDLC) protocol o synchronous data links using the Qualified Logical Link Control (QLLC) protocol o local area network (LAN) data links using the Logical Link Control type 2 (LLC2) protocol Configuring the Peer Server's Data Links 5-1 5.1.1 Planning for SDLC Data Links Use the SDLC Link Information worksheet (Table 5-1) to record information about the Peer Server's SDLC links. For each link, you must define the following information: o SDLC link name - Modem Connect Line name - Configuration type (point-to-point or multipoint) - Link station capability (primary, secondary, or negotiable) - Receive frame size - Maximum number of retries o SDLC station name - SDLC station address - Group address - Transfer mode (two-way-alternate or two-way- simultaneous) - Modulo (normal or extended) - Window size - Inactivity timer value - Send frame size For more detailed information about the SDLC link and station dialog questions, see the prompt discussions in Section 5.2.1. Some of the planning you do for SDLC data links must be done in conjunction with planning the underlying Modem Connect Line entity. Appendix C discusses the possible configurations and resulting physical line characteristics. Repeat the process for all SDLC links the Peer Server supports. Make additional copies of the worksheet if you need more space. 5-2 Configuring the Peer Server's Data Links Table_5-1_The_SDLC_Link_Information_Worksheet______________ SDLC link name [SDLC-0]: __________________________ Modem Connect Line: ________________ Configuration [point-to- ___________________________ point]: (point-to-point, multipoint) Link Station capability ___________________ [NEGOTIABLE]: (primary, secondary, negotiable) Receive frame (1-32765) __________ [1000]: Retry maximum (0-128) [15]: __________ SDLC station name [STN-0]: _____________________ Station address (01-FE) [40]: ____ ____ Group address (00 - FE) [00]: ____ ____ Transfer mode (twa/tws) [TWA]: _________ Modulo [NORMAL]: _____________________ (normal or extended) Window size (1-127) [7]: ____ ____ ____ Inactivity timer (0-7200) ____ ____ ____ ____ [30]: Send frame (1-32765) [1000]: ____ ____ ____ ____ ___________________________________________________________ Configuring the Peer Server's Data Links 5-3 5.1.2 Planning for QLLC Data Links Use the QLLC Link Information worksheet (Table 5-2) to record information about the Peer Server's QLLC links. For each link, you must define the following information: o QLLC link name - Filter name - Template name - DTE class o QLLC station name - QLLC usage type (outgoing, incoming, or both) - Maximum number of retries - Retry timeout in seconds - QLLC station capability (primary, secondary, or negotiable) - Remote DTE address - Maximum BTU size For more detailed information about the QLLC link and station dialog questions, see the prompt discussions in Section 5.2.2. Some of the planning you do for QLLC data links must be done in conjunction with planning the underlying X.25 entities. Appendix D discusses the critical X.25 parameters and describes the special case of using an X.25 relay. Repeat the process for all QLLC links the Peer Server supports. Make additional copies of the worksheet if you need more space. 5-4 Configuring the Peer Server's Data Links Table_5-2_The_QLLC_Link_Information_Worksheet______________ QLLC link name [QLLC-0]: ___________________________ Filter name [FILTER_QLLC]: ___________________________ Template name [TEMPLATE_QLLC]: ___________________________ DTE class [CLASS_QLLC]: ___________________ QLLC station name [STN-0]: _____________________ Usage type [BOTH]: _____________________ (outgoing, incoming, both) Retry Maximum (0 - 255) [4]: ____ ____ ____ Retry Timeout (1 - 600) [10]: ____ ____ ____ Link Station Capability _____________________ [NEGOTIABLE]: (primary, secondary, negotiable) Remote DTE Address: _____________________ Maximum BTU Size (128 - 512) ____ ____ ____ [512]: ___________________________________________________________ Configuring the Peer Server's Data Links 5-5 5.1.3 Planning for LLC2 Data Links Use the LLC2 SAP Link Information worksheet (Table 5-3) to record information about the Peer Servers LLC2 links. For each service access point (SAP), you must define the following information: o LLC2 SAP name - LAN station type - LAN station name - Local LSAP address o SAP link name - Maximum receive data size - Remote LSAP address - Remote MAC address (xx-xx-xx-xx-xx-xx) After configuring the LLC2 data link, the Configuration utility gives you a chance to configure the underlying data line. The Configuration dialog prompts you to enter the following: o Token Ring, CSMA-CD, or FDDI station name o Communication port name o For Token Ring data lines, the Token Ring speed (4 or 16 megabits per second) For more detailed information about the LLC2 SAP and link dialog questions, see the prompt discussions in Section 5.2.3. Some of the planning you do for LLC2 data links involves planning MAC address information. Appendix E contains a detailed discussion of how to determine and specify MAC addresses. Repeat the process for all LLC2 links the Peer Server supports. Make additional copies of the worksheet if you need more space. 5-6 Configuring the Peer Server's Data Links Table_5-3_The_LLC2_SAP_Link_Information_Worksheet__________ LLC2 SAP name [SNA-0]: __________________________ LAN station type [Token Ring]: _____________________ (Token Ring, Ethernet, FDDI) LAN station name [TRN-0]:1 _____________________ Local LSAP address (00 - FE) ____ ____ [04]: SAP link name [LINK-0]: __________________________ Maximum receive data size (1 - ____ ____ ____ ____ 65531) [1028]: ____ Remote LSAP address (00 - FE) ____ ____ [04]: Remote MAC address (xx-xx-xx-xx-xx-xx): ____ ____ - ____ ____ - ____ ____ - ____ ____ - ____ ____ - ____ Token Ring 2 station name __________________________ [TRN-0]:3 Communication port name __________________________ [TRA0]:4 Token Ring speed (4 or 16) ____ ____ [16]: ___________________________________________________________ 1 If the LAN station type specified is Ethernet, the default LAN station name is [CSMACD-0]. If the LAN station type specified is FDDI, the default LAN station name is [FDDI-0]. 2 Ethernet if you are configuring for CSMA/CD. FDDI if you are configuring for Fiber Distributed Data Interface (FDDI). 3 The Ethernet default value is [CSMACD-0]. The FDDI default value is [FDDI-0]. 4 The Ethernet default value is [ln0]. The FDDI default value is [fta0]. Configuring the Peer Server's Data Links 5-7 5.2 Dialog Section 2: Data Link Layer Configuration Section 2 of the configuration dialog lets you select the DLC type you wish to configure. The DLC entities available for configuration are SDLC, QLLC, and LLC2. The Configuration utility prompts you to start a DLC entity configuration. Enter yes, no or skip. If you have not already configured any link, the default is yes. Do you wish to configure dlc-type [YES] ? where dlc-type is SDLC, QLLC, or LLC2. ________________________ Note ________________________ Enter yes if you want to configure the data link type currently displayed by the Configuration utility. Enter skip if you want to maintain an existing configuration of this data link type, and continue on to the next DLC type or next section. Enter no if you want to omit this configuration, and at the same time void an existing configuration of this data link type. If you enter no and you already have a data link configured, you receive the following warning: WARNING: Your Data Link is already configured; answering NO will void the configuration. ______________________________________________________ 5-8 Configuring the Peer Server's Data Links 5.2.1 Dialog Section 2.1: SDLC Configuration Section 2.1 of the configuration dialog lets you configure SDLC links and stations that connect the Peer Server to the IBM SNA environment. For each SDLC link you configure, you also configure information for one or more (if configured as multipoint) remote SDLC stations on the link. Press Return at the LINK Name: prompt when you have completed the SDLC configuration section. For a more detailed discussion about configuring the different types of SDLC data links supported by the Peer Server, see Appendix C. Section 2.1 - SDLC Configuration. --------------------------------- This section gathers information for one or more SDLC links. The Configuration utility prompts you to enter a link name. Enter the name of the SDLC link to configure. Links are named with character strings of 1 to 32 characters; SDLC-0 is the default name of the first link. LINK name [SDLC-0] : The Configuration utility prompts you to enter a modem connect line name. Enter the name of the Modem Connect Line entity that this SDLC link will use to communicate with the remote system. The Peer Server has physical lines named "Modem Connect Line Line-n," where n is determined by the number and type of synchronous devices available on the system. Enter only the "line-n" part of the name. The default is LINE-0. Modem Connect Line name [LINE-0] : The Configuration utility prompts you to enter the configuration in which this link is to operate. If this link is the only device on the line being used, you can use the default configuration (pointtopoint). If this link is sharing the communication line with other SDLC devices, specify multipoint. You can enter p or m. For multipoint links, the Configuration dialog prompts you for more than one station name. Configuration [PointToPoint] : Configuring the Peer Server's Data Links 5-9 The Configuration utility prompts you to enter the capability of the stations on this link. SDLC stations on the link can be either primary or secondary stations. On links that negotiate roles, such as NCP attached lines coded with XID=YES or AS/400 controllers, you can use the default (negotiable). For multipoint links, the capability is set to secondary, and you are not prompted for this information. Capability [NEGOTIABLE] : The Configuration utility prompts you to enter the maximum frame size that can be received by this link. See the Peer Server Release Notes for any device-specific limitations. Enter a value from 1 to 32765; the default is 1000. Receive frame size [1000] : The Configuration utility prompts you to enter the number of times an SDLC frame is retransmitted before the Peer Server declares a fatal error has occurred and resets the link. Enter a value from 0 to 128; the default is 15. A value of zero implies unlimited retries. The default value should work for most configurations. Retry maximum [15] : After configuring the link parameters, you configure the parameters for the link's station (or stations for multipoint links). The Configuration utility prompts you to enter the station name. Stations are named with character strings of 1 to 32 characters; The default for the first station is STN-0. STATION name [STN-0] : The Configuration utility prompts you to enter the station address for this station. If the SDLC link is defined as secondary, or it is defined as negotiable and adopts a secondary role at run time, then the Peer Server uses this parameter for the station address. If the SDLC link is defined as primary, or it is defined as negotiable and adopts a primary role at run time, then the Peer Server does not use this parameter and the address of the secondary station is determined at run time. Enter the address in the form of two hexadecimal characters from 01 to FE; the default is 40. 5-10 Configuring the Peer Server's Data Links Station address [40] : Enter the group address for this station. This prompt is issued only if the SDLC link is configured as multipoint. Enter the address in the form of two hexadecimal characters from 00 to FE; the default is 00, which is interpreted as no group address. Group address [00] : The Configuration utility prompts you to enter the station's transfer mode. Enter the link level transmit/receive capabilities of the station: twa (Two- Way Alternate) corresponds to half-duplex communication, tws (Two-Way Simultaneous) corresponds to full-duplex communication. On links that negotiate roles, such as NCP attached lines coded with XID=YES or AS/400 controllers, the actual type of connection established depends on the capabilities of the two link stations. TWS is used if both stations support it. If negotiation is not performed then the value of this parameter must match the configuration of the remote system. A station cannot operate two-way simultaneous over a physical half-duplex line. The default is twa. Transfer mode [TWA] : The Configuration utility prompts you to enter the default modulus to use. normal modulus uses a modulus-8 numbering system for frames, and thus there can only be a maximum of 7 frames outstanding at any time. extended modulus uses modulus-128 numbering, which allows for up to 127 frames to be outstanding. On links that negotiate roles, such as NCP attached lines coded with XID=YES or AS/400 controllers, the modulus used is determined at run time from the configured window sizes (normal is used unless both systems have window sizes greater than 7). For links that do not perform negotiation, the value of this parameter must match the configuration of the remote system. The default is normal. Modulo [NORMAL] : Configuring the Peer Server's Data Links 5-11 The Configuration utility prompts you to enter the window size to set the number of frames the station can receive before sending an acknowledgment response. The value of this parameter is used to determine the modulus used on links that negotiate roles. Enter a value from 1 to 127; the default is 7. A station with modulo normal supports the range 1 to 7; a station with modulo extended supports the range 1 to 127. Unless you have a line with a high error rate, you should use the default value. Window size [7] : The Configuration utility prompts you to enter the station's inactivity timer value. This is the number of seconds the Peer Server waits for a message from the remote system before considering the line to have failed. This timeout is used when the Peer Server is operating as a secondary link station, and reflects the maximum amount of time expected between polls from the primary station. If the timer expires, then the link is disconnected. Enter a value from 0 to 7200 seconds; the default is 30 seconds. A value of 0 implies that the station does not time out due to inactivity on the line. Inactivity timer [30] : The Configuration utility prompts you to enter the maximum size of the frame that the station can send. This value can differ from station to station on the same link if the link is defined as multipoint with multiple secondary stations. Enter a value from 1 to 32765; the default is 1000. Send frame size [1000] : If you are defining a multipoint link, the Configuration utility repeats the series of station prompts for another station. When you have defined all the stations, you can continue to the next link by pressing Return: STATION name [] : The Configuration utility repeats this series of prompts for another link. When you have defined all the links, you can continue to the next section by pressing Return: LINK name [] : 5-12 Configuring the Peer Server's Data Links The utility asks if you wish to repeat the section. If you want to create a different SDLC configuration, answer yes; if not, press Return to continue: Do you wish to repeat Section 2.1, SDLC Configuration [N] ? Example 5-1 uses the Configuration utility to configure a multipoint SDLC link and station operating over Modem Connect Line line-0. It uses a receive frame size of 265 bytes. Example 5-1 SDLC Configuration Example (Section 2.1) Section 2.1 - SDLC Configuration. --------------------------------- This section gathers information for one or more SDLC links. LINK name [SDLC-0] : Modem Connect Line name [LINE-0] : Configuration [PointToPoint] : multipoint Receive frame size [1000] : 265 Retry maximum [15] : STATION name [STN-0] : Station address [40] : Group address [00] : Transfer mode [TWA] : Modulo [NORMAL] : Window size [7] : Inactivity timer [30] : Send frame size [1000] : STATION name [] : LINK name [] : Do you wish to repeat Section 2.1, SDLC Configuration [N] ? Configuring the Peer Server's Data Links 5-13 5.2.2 Dialog Section 2.2: QLLC Configuration Section 2.2 of the configuration dialog lets you configure QLLC links and stations that connect the Peer Server to the IBM SNA environment. For each QLLC link you configure, you also configure information for one remote QLLC station on the link. Press Return at the LINK Name: prompt when you have completed the QLLC configuration section. For a more detailed discussion about configuring the underlying X.25 entities required by the Peer Server, see Appendix D. Section 2.2 - QLLC Configuration. --------------------------------- This section gathers information for a QLLC link. The Configuration utility prompts you to enter a link name. Enter the name of the QLLC link to configure. Links are named with character strings of 1 to 32 characters; QLLC-0 is the default name of the first link. LINK name [QLLC-0] : The Configuration utility prompts you to enter the filter name to be used for both QLLC incoming and outgoing connections. The name must match the name of an X25 Access Filter entity that exists in the node's X.25 configuration. The default name is FILTER_QLLC. Filter name [FILTER_QLLC] : The Configuration utility prompts you to enter the template name to be used for QLLC outgoing connections. The name must match the name of an X25 Access Template entity that exists in the node's X.25 configuration. If the name does not match, each outgoing connection attempt fails. The default name is TEMPLATE_QLLC. Template name [TEMPLATE_QLLC] : The Configuration utility prompts you to enter the DTE Class name. The name must match the name an X25 Access DTE Class entity that exists in the node's X.25 configuration. The default is CLASS_QLLC. DTE Class [CLASS_QLLC] : 5-14 Configuring the Peer Server's Data Links After configuring the link parameters, the utility prompts you to enter information for one or more stations that will operate over the link. Stations are named with character strings of 1 to 32 characters; STN-0 is the default for the first station. Station name [STN-0] : The Configuration utility prompts you to enter the type of connections using this station. The values are outgoing, incoming, and both. Enter incoming if only IBM-initiated connections use this station. Enter outgoing if only Peer Server initiated connections use this station. Enter both if both outgoing and incoming connections use this station, or you are unsure of the type of connections that use this station. The default is both. Usage Type [BOTH] : The Configuration utility prompts you to enter the maximum number of retries to attempt before disconnecting the connection. Enter a value from 0 to 255; the default is 4. A value of zero implies unlimited retries. The default value should work for most configurations. Retry Maximum [4] : The Configuration utility prompts you to enter the time in seconds to wait between retries. Enter a value from 1 to 600; the default is 10. Retry Timeout [10] : The Configuration utility prompts you to enter the capability of the stations on this link. QLLC stations on the link can be either primary or secondary stations. On links that negotiate roles, such as NCP attached lines coded with XID=YES or AS/400 controllers, you can use the default (negotiable). Capability [NEGOTIABLE] : The Configuration utility prompts you to enter the remote DTE address for this station. Enter the remote DTE address that corresponds to the remote station with which this station communicates. For a Peer Server initiated connection, this is the address to which the X.25 call is directed. For an incoming connection, if the usage type of Configuring the Peer Server's Data Links 5-15 the station is set to incoming, the Peer Server matches the caller's X.25 address against this value and if it does not match, rejects the connection. If you are using a direct X.25 connection, that is, no PSDN, then enter 0. Remote DTE Address [] : The Configuration utility prompts you to enter the maximum basic transmission unit (BTU) size for this station. Enter the size that SNA messages should be segmented into before being sent to the X.25 network. (The X.25 network may further segment packets based on the level 2 profile information being used.) Enter a value from 128 to 512; the default is 512. Maximum BTU Size [512] : The Configuration utility repeats the series of station prompts for another station. When you have defined all the stations, you can continue to the next link by pressing Return: STATION name [] : The Configuration utility repeats this series of prompts for another link. When you have defined all the links, you can continue to the next section by pressing Return: LINK name [] : The utility asks if you wish to repeat the section. If you want to create a different QLLC configuration, answer yes; if not, press Return to continue: Do you wish to repeat Section 2.2, QLLC Configuration [N] ? Example 5-2 uses the Configuration utility to configure a QLLC link and station. 5-16 Configuring the Peer Server's Data Links Example 5-2 QLLC Configuration Example (Section 2.2) Section 2.2 - QLLC Configuration. --------------------------------- This section gathers information for a QLLC link. LINK name [QLLC-0] : Filter name [FILTER_QLLC] : Template name [TEMPLATE_QLLC] : DTE Class [CLASS_QLLC] : STATION name [STN-0] : Usage Type [BOTH] : Retry Maximum [4] : Retry Timeout [10] : Capability [BOTH] : Remote DTE Address [] : 12345 Maximum BTU Size [512] : STATION Name [] : LINK Name [] : Do you wish to repeat Section 2.2, QLLC Configuration [N] ? Configuring the Peer Server's Data Links 5-17 5.2.3 Dialog Section 2.3 - LLC2 Configuration Section 2.3 of the configuration dialog lets you configure LLC2 SAPs and links that connect the Peer Server to the SNA environment by a LAN. Press Return at the SAP Name: prompt when you have completed the LLC2 configuration section. Section 2.3 - LLC2 Configuration. ------------------------------- This section gathers information for LLC2 links. The Configuration utility prompts you to enter the SAP name. Enter the name of the LLC2 SAP to configure. SAP are named with character strings of 1 to 32 characters. The default for the first SAP is SNA-0. SAP name [SNA-0] : The Configuration utility prompts you to enter the LAN station type. The supported station types are Token Ring, Ethernet, and FDDI. The default type is Token Ring. LAN Station type [Token Ring] : The Configuration utility prompts you to enter the LAN station to be used by the SAP. For Token Ring networks, the default for the first SAP is TRN-0. LAN Station name [TRN-0] : The Configuration utility prompts you to enter the local link service access point (LSAP) address. The lowest significant bit of the address must be clear, and the address must be unique. Enter the address in the form of 2 hexadecimal characters; the default is 04. Local LSAP Address [04] : The Configuration utility prompts you to enter the SAP link name. Enter the name of the SAP link with character strings of 1 to 32 characters. The default for the first link is LINK-0. LINK name [LINK-0] : 5-18 Configuring the Peer Server's Data Links The Configuration utility prompts you to enter the maximum data size that can be received by this link. Enter a value from 1 to 65531; the default is 1028. Maximum Data Size [1028] : The Configuration utility prompts you to enter the destination LSAP address to be used by the link. The lowest significant bit of the address must be clear, and the address must be unique. Enter the address in the form of two hexadecimal characters; the default is 04. Remote LSAP Address [04] : The Configuration utility prompts you to enter the destination medium access control (MAC) address to be used by the link. Enter the value of a valid LAN address. It is important for the remote MAC address to be specified in canonical format, which is derived by reversing each bit in a byte of the remote MAC address. For example, if the remote MAC address is 40-00-2D-EC-DE-C0, the canonical form of it is 02-00-B4-37-7B-03. For a detailed discussion about LLC2 remote MAC address format, see Appendix E. Remote MAC Address (xx-xx-xx-xx-xx-xx) [ ] : The Configuration utility repeats the series of link prompts for another link. When you have defined all the links, you can continue to the next SAP by pressing Return: LINK name [] : The Configuration utility repeats this series of prompts for another SAP. When you have defined all the SAPs, you can continue to the next section by pressing Return: SAP name [] : Before you complete this section, you are prompted to configure the specified LAN station. If you have not already done so, you need to configure the LAN module entity (Token Ring, Ethernet, or FDDI) and the LAN station now. You can omit this step if the LAN entity is already configured for use with DECnet or X.25. If you answer yes, the Configuration utility detects which LAN station type you entered (Token Ring, Ethernet, or FDDI) and issues the appropriate set of prompts. Configuring the Peer Server's Data Links 5-19 The Token Ring module entity and its subentity, station, are necessary for LLC2 operation over Token Ring LAN. The entities may have already been created while configuring DECnet or X.25. If not, you will need to do it now. Do you wish to configure Token Ring [YES] ? The Configuration utility displays the LAN station name used by the SAP. This name matches the one listed in the beginning of dialog Section 2.3 and is in agreement with the LAN station type (Token Ring, Ethernet, or FDDI). Configuring LAN station: station-name The Configuration utility prompts you to enter a communication port name. If you specified Token Ring as the LAN station type, the port name default is tra0; if you specified Ethernet as the LAN station type, the port name default is ln0; if you specified FDDI as the LAN station type, the port name default is fta0. Press Return to accept the default value or enter a name according to the syntax ddn, where dd represents an adapter name, and n represents the number. Communication port name [default] : If you specified Token Ring as the LAN station type, the Configuration utility prompts you to enter a Token Ring speed. You may choose 4 or 16 megabits per second as the speed. The default value is 16. Token Ring speed [16] : The utility asks if you wish to repeat the section. If you want to create a different LLC2 configuration, answer yes. Press Return to continue: Do you wish to repeat Section 2.3, LLC2 Configuration [N] ? Example 5-3 uses the Configuration utility to configure an LLC2 SAP and link. 5-20 Configuring the Peer Server's Data Links Example 5-3 LLC2 Configuration Example (Section 2.3) Section 2.3 - LLC2 Configuration. ------------------------------- This section gathers information for LLC2 links. SAP name [sna-0] : LAN Station type [Token Ring] : LAN Station name [TRN-0] : Local LSAP Address [04] : LINK name [LINK-0] : Maximum Data Size [1028] : Remote LSAP Address [04] : Remote MAC Address (xx-xx-xx-xx-xx-xx)[ ] : 08-00-cb-17-14-3c LINK Name [] : SAP Name [] : The Token Ring module entity and its subentity, station, are necessary for LLC2 operation over Token Ring LAN. The entities may have already been created while configuring DECnet or X.25. If not, you will need to do it now. Do you wish to configure Token Ring [YES] ? Configuring LAN Station: TRN-0 Communication port name [tra0] : Token Ring speed [16] : Do you wish to repeat Section 2.3, LLC2 Configuration [N] ? Configuring the Peer Server's Data Links 5-21 6 _________________________________________________________________ Configuring the Peer Server's Logical Units 6.1 Planning the Peer Server's SNA LU Services Planning for the Peer Server's logical units (LUs) involves the following tasks: o Planning for the authorization records that control the access to the Peer Server's LUs. o Planning for the Peer Server's LUs. o Planning for the shortcut access names that some SNA access routines can use to access the Peer Server's LUs. o Planning for the remote LUs that the Peer Server can contact. Configuring the Peer Server's Logical Units 6-1 6.1.1 Planning the LU Authorizations Use the LU Authorizations worksheet (Table 6-1) to record information about authorization records that control access to Peer Server LUs. You can specify from 2 to 6 fields for each authorization. Any field for which you specify a value causes the Peer Server to check the information a user supplies against that value. If no matches occur using all the authorizations you specified for the LU, the Peer Server denies the user access to the LU. Any field that you leave unspecified allows users specifying any value, including no value, to access the LUs protected by this authorization (unless other authorizations prevent access). Note that you can use wildcards in the terminal name and the user name. If the transport mode is DECnet, the node name is a DECnet node name. If the transport mode is TCP/IP, the node name is an internet node name. If the transport mode is local, the node name is not used. Repeat the process for as many authorizations as you need. Make additional copies of the worksheet if you need more space. 6-2 Configuring the Peer Server's Logical Units Table_6-1_The_LU_Authorizations_Worksheet__________________ Authorization name: _________________________ Transport (TCPIP, DECnet, ____________ local): Node name: __________________________ User name: __________________________ Terminal name: __________________________ Password: __________________________ Authorization name: _________________________ Transport (TCPIP, DECnet, ____________ local): Node name: __________________________ User name: __________________________ Terminal name: __________________________ Password: __________________________ Authorization name: _________________________ Transport (TCPIP, DECnet, ____________ local): Node name: __________________________ User name: __________________________ Terminal name: __________________________ Password: __________________________ _____________________________________________________