DECnet/SNA_Gateway-ST_______________________________ Installation (ULTRIX) Order Number: AA-PHLAA-TE This document contains instructions for installing and configuring the DECnet/SNA Gateway-ST software on the ULTRIX operating system. This document applies to DECnet/SNA Gateway-ST Version 1.2 and subsequent maintenance updates. Revision/Update Information: This is a new manual. Operating System and Version: ULTRIX V4.2 Software Version: DECnet/SNA Gateway-ST Version 1.2 ________________________________________________________________ July 1991 The information in this document is subject to change without notice and should not be construed as a commitment by Digital Equipment Corporation. Digital Equipment Corporation assumes no responsibility for any errors that may appear in this document. The software described in this document is furnished under a license and may be used or copied only in accordance with the terms of such a license. No responsibility is assumed for the use or reliability of software on equipment that is not supplied by Digital Equipment Corporation or its affiliated companies. Restricted Rights: Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer Software clause at DFARS 252.227-7013. Copyright ©1988, 1991 Digital Equipment Corporation All Rights Reserved The following are trademarks of Digital Equipment Corporation: DEC TK50 VAXcluster DECUS ULTRIX VMS DECnet UNIBUS DECnet-ULTRIX VAX DIGITAL IBM is a registered trademark of International Business Machines Corporation. CICS, DISOSS and TSO are trademarks of International Business Machines Corporation. PostScript is a registered trademark of Adobe Systems, Inc. This manual was produced by Telecommunications and Networks Publications. _________________________________________________________________ Contents Preface................................................... vii 1 Preparing for DECnet/SNA Gateway-ST Installation 1.1 Release Notes.................................... 1-2 1.2 Installing from RIS as a Client ................. 1-2 1.3 Installing Into an RIS Server Area .............. 1-2 1.4 Installing DECnet/SNA Gateway-ST Into a DMS Server Area ..................................... 1-3 1.5 License Registration............................. 1-4 1.6 Checking the Media Software Distribution Kit..... 1-5 1.7 Installation Procedure Requirements.............. 1-5 1.7.1 Time Requirements ............................. 1-5 1.7.2 Login Privileges .............................. 1-6 1.7.3 Hardware Requirements ......................... 1-6 1.7.4 Software Requirements ......................... 1-9 1.7.4.1 Preparing the IBM SNA Environment........... 1-9 1.7.4.2 Preparing the DECnet Environment............ 1-10 1.7.4.3 Preinstallation ULTRIX Software............. 1-11 1.7.5 Determining Which Subsets to Load ............. 1-12 1.7.6 Determining Disk Space Requirements ........... 1-13 1.7.6.1 Checking Disk Space for Installation on a Local Node.................................. 1-14 1.7.6.2 Checking Disk Space for Installation into a Diskless Environment ....................... 1-15 1.7.6.3 Increasing Disk Space Available for DECnet/SNA Gateway-ST Installation.......... 1-16 1.8 Backing Up Your System Disk...................... 1-16 1.9 Stopping the Installation........................ 1-16 1.10 Error Recovery................................... 1-17 iii 2 Installing DECnet/SNA Gateway-ST 2.1 Installing DECnet/SNA Gateway-ST Locally......... 2-1 2.1.1 Starting the Installation Procedure ........... 2-1 2.1.1.1 Using TK50 or Magnetic Tape Distribution Media....................................... 2-2 2.1.1.2 Installing DECnet/SNA Gateway-ST from an RIS Server ..................................... 2-2 2.1.2 Responding to Installation Procedure Prompts .. 2-3 2.1.2.1 Selecting Subsets........................... 2-3 2.1.2.2 Monitoring Displays During the Subset Loading Process............................. 2-4 2.2 Installing DECnet/SNA Gateway-ST into a Server Environment ..................................... 2-5 2.2.1 DMS Server Installations ...................... 2-6 2.2.2 RIS Server Installations ...................... 2-8 3 Completing the Installation: Verifying, Configuring, Loading 3.1 Running IVPs..................................... 3-1 3.2 Configuring your Gateway......................... 3-2 3.2.1 Understanding the snaconfig utility ........... 3-2 3.2.2 Using snaconfig ............................... 3-3 3.3 Loading Your Gateway............................. 3-31 3.3.1 Before Loading the Gateway-ST ................. 3-31 3.3.2 Checking the Load Host Connection ............. 3-31 3.3.3 Enabling Event Logging on the Load Host ....... 3-32 3.3.4 Loading the Software from the Hardware Unit ... 3-33 3.3.5 Loading the Software from a Terminal .......... 3-33 3.3.5.1 Receiving Event Messages.................... 3-33 3.3.5.2 Using the load and trigger Commands ........ 3-35 3.3.6 Checking the Gateway Node to Load Host Connection..................................... 3-36 A Files Installed on Your System iv B Sample Listings for Installation and Verification B.1 Installation of DECnet/SNA Gateway-ST on a VAX/ULTRIX System Using Tape Media............... B-1 B.2 Installation Verification for DECnet/SNA Gateway-ST on a VAX/ULTRIX System................ B-3 B.2.1 IVP for Gateway Management Subset ............. B-3 B.2.2 IVP for Base Software Subset .................. B-3 Index Tables 1-1 DEC MicroServer-SP Port Speeds ................ 1-7 1-2 DEC MicroServer Port Speeds ................... 1-7 1-3 Ethernet Line and Circuit Characteristics ..... 1-11 1-4 Worksheet for Subset Sizes (Kilobytes Required) on RISC Systems ............................... 1-13 1-5 Worksheet for Subset Sizes (Kilobytes Required) on VAX Systems ................................ 1-14 A-1 Installed DECnet/SNA Gateway-ST Files ......... A-1 v _________________________________________________________________ Preface Purpose of This Guide This guide describes how to install DECnet/SNA Gateway for Synchronous Transport software (called DECnet/SNA Gateway- ST or Gateway-ST in this manual) on both VAX and RISC processors that are running the ULTRIX operating system. The installation procedure creates Gateway-ST directory structures subordinate to the /usr/lib directory and loads Gateway-ST subsets to these directories. The installation also loads Gateway-ST man pages to the standard man page directory structures. Keep this document with your distribution kit. You can use it to install maintenance updates or to reinstall the Gateway-ST software. At the back of this document is a Reader's Comments form. If you have any comments about this document, fill out the form and mail it. Your comments are considered for subsequent installation guides. Intended Audience The audience for this guide is the person who installs Gateway-ST software on either an ULTRIX VAX or ULTRIX RISC system as follows: o A system manager who manages a node-specific system o A Diskless Management Services (DMS) manager who manages a DMS server area o A Remote Installation Services (RIS) manager who manages a RIS server area vii o A system manager who expects to install Gateway-ST from the RIS server area of a remote system Structure of this Document This manual is organized as follows: o Chapter 1, which describes the operating system and hardware requirements for Gateway-ST installation and related procedures that you complete before installing the Gateway-ST software. o Chapter 2, which describes the installation procedures for local, server, and client installations. o Chapter 3, which describes the installation verification and the initial configuration of DECnet/SNA Gateway-ST. o Appendix A, which describes the hierarchy and contents of Gateway-ST directories. o Appendix B, which contains sample listings for Gateway- ST installation and verification. Manuals in the DECnet/SNA Gateway-ST Documentation Set In addition to this guide, the Gateway-ST documentation set includes the following material: o DECnet/SNA Gateway-CT and Gateway-ST Management (ULTRIX) o DECnet/SNA Gateway-ST Problem Solving (ULTRIX) o DECnet/SNA Gateway-ST Guide to IBM Parameters o DECnet/SNA Gateway-ST release notes o DECnet/SNA Gateway-ST man pages Related Manuals DECnet/SNA Gateway-ST hardware documentation o Installing the DEC MicroServer o Installing the DEC MicroServer-SP o DEC MicroServer Systems Configuration Card ULTRIX system management documentation o ULTRIX Guide to Server Setup viii o ULTRIX Guide to Diskless Management Services o ULTRIX Guide to Remote Installation Services DECnet-ULTRIX documentation o DECnet-ULTRIX NCP Command Reference o DECnet-ULTRIX Network Management o DECnet-ULTRIX Use Figure 1 lists the Gateway-ST manuals according to the major tasks that they describe. The arrows in the figure suggest an order in which to read the books. This installation guide is highlighted in the figure. A primary reference source for DECnet/SNA Gateway-ST is the online man pages (reference pages). They are installed at these locations in /usr/man: sna_gm(7), snap(8), snaconfig(8), snancp(8), and snatrace(8). The DECnet/SNA Gateway-ST release notes contain information that is not included in the printed manuals or the online documentation. ix Conventions These conventions apply to this installation guide: ULTRIX terms Indicates, in the running text, ULTRIX commands, options, arguments, pathnames, files, and directories. ncp> trigger node node- Indicates ULTRIX command syntax id and command examples. Note that you can enter some arguments for DECnet/SNA Gateway-ST utilities in uppercase as well as lowercase. Red type indicates user input in command examples. Italic type denotes variables in command examples, command syntax, and directory structures. The user or the system supplies a value at that point. ? Denotes a single-character variable in an ULTRIX pathname. % Indicates the prompt in ULTRIX command lines. # Indicates the superuser prompt. Indicates that you press the enclosed key. Indicates that you hold down the key while you press another key represented by x. x Abbreviations and Acronyms This manual uses some or all of the following abbreviations and acronyms: ACF/NCP Advanced Communications Function with Network Control Program (also referred to as IBM NCP) API DECnet/SNA VMS Application Programming Interface APPC/LU6.2 DECnet/SNA VMS APPC/LU6.2 Programming Interface CICS/VS Customer Information Control System/Virtual Storage (also referred to as CICS) DECnet NCP Digital's Network Control Program (also referred to as NCP) DDXF DECnet/SNA VMS DISOSS Document Exchange Facility DHCF DECnet/SNA VMS Distributed Host Command Facility DSPRINT MVS/TSO/VTAM Data Set Print Facility DTF DECnet/SNA Data Transfer Facility EDE External Document Exchange with DISOSS GAS Gateway Access Server IBM NCP IBM's Network Control Program IMS/VS Information Management System/Virtual Storage (also referred to as IMS) JES2 Job Entry Subsystem 2 JES3 Job Entry Subsystem 3 LU Logical unit LU1 Logical unit type 1 LU2 Logical unit type 2 LU3 Logical unit type 3 LU6.2 Logical unit type 6.2 MVS IBM's Multiple Virtual Storage operating system MR/S VAX Message Router/S Gateway MR/P VAX Message Router/P Gateway xi NCP Network Control Program. This manual uses NCP to refer to the Digital product and IBM NCP to refer to the IBM product. PLU Primary logical unit PrE DECnet/SNA VMS Printer Emulator PU Physical unit PU2 Physical unit type 2 RH Request/response header RJE DECnet/SNA VMS Remote Job Entry RU Request/response unit SDLC Synchronous Data Link Control SLU Secondary logical unit SNA IBM's Systems Network Architecture SNANCP DECnet/SNA Gateway Network Control Program SNAP DECnet/SNA Gateway Management display utility SNATRACE DECnet/SNA Gateway Management protocol trace utility SSCP System services control point 3270 DS DECnet/SNA VMS 3270 Data Stream Programming Interface 3270 TE DECnet/SNA VMS 3270 Terminal Emulator TH Transmission header TSO IBM's Time Sharing Option VM IBM's Virtual Machine operating system VSE/SP Virtual Storage Extended/System Package VTAM Virtual Telecommunications Access Method xii 1 _________________________________________________________________ Preparing for DECnet/SNA Gateway-ST Installation Before starting the installation procedures in Chapter 2, you should complete the preparation requirements outlined in this chapter. The sections in this chapter provide the necessary information to make your installation run smoothly. You need to know about and be aware of your installation options and information related to the installation procedure. This chapter helps you determine the following: o Whether you need to read the release notes o Whether you are installing DECnet/SNA Gateway-ST from distribution media or using the ULTRIX Remote Installation Service (RIS) o Whether you are installing Gateway-ST locally or into a Diskless Management Services (DMS) server area for diskless clients o How to register your License Product Authorization Key (PAK) o If installing Gateway-ST from media, whether your distribution kit includes all the components listed on the Bill of Materials (BOM) o Whether you need superuser privileges for the system on which you install Gateway-ST o If the system on which you install Gateway-ST meets the Gateway-ST hardware, software, and disk space requirements o Which optional Gateway-ST subsets you should install o How much disk space you need Preparing for DECnet/SNA Gateway-ST Installation 1-1 o Whether you have to back up your system disk 1.1 Release Notes Your documentation includes the DECnet/SNA Gateway-ST release notes, which you should read before using the product. Gateway-ST provides online release notes, which are stored in snacst120.release_notes in /usr/lib/snagwy. The release notes may contain information about changes to the Gateway-ST software and documentation. Your documentation may also include the DECnet/SNA Gateway- ST cover letter (see your Bill of Materials). This letter discusses information that is important for you to know before installing Gateway-ST; information that may not be included either in this installation guide or the release notes. 1.2 Installing from RIS as a Client If you expect to install Gateway-ST subsets from a Remote Installation Services (RIS) server area of a remote system, check with your site system administrator to make sure that: o A Gateway-ST kit is installed in the RIS server area and is available for use o Your system is registered as an RIS client If Gateway-ST subsets are available to you on a RIS server system, you need the name of that system to start the installation procedure described in this guide. 1.3 Installing Into an RIS Server Area If you manage a Remote Installation Services (RIS) server area and intend to install Gateway-ST into your server area, read the following sections of this guide: o Section 1.6 for information about contents of the media kit o Section 1.7 for hardware and software requirements, for the names and numbers of software subsets, and for disk space requirements 1-2 Preparing for DECnet/SNA Gateway-ST Installation o Sections 2.1.2.1 and 2.1.2.2 explain the displays and prompts that are specific to Gateway-ST installations To install Gateway-ST on an RIS server system and register client nodes, use the ris utility (See Section 2.2). Do not use the setld command. You use setld subsequently on a client node to install the software from the RIS server. 1.4 Installing DECnet/SNA Gateway-ST Into a DMS Server Area If you manage a DMS server area and want to install Gateway-ST into a DMS server area, read the following sections of this guide: o Section 1.6 for information about contents of the media kit o Section 1.7 for hardware and software requirements, the names and numbers of software subsets, and for disk space requirements o Sections 2.1.2.1 and 2.1.2.2 explain the displays and prompts that are specific to Gateway-ST installations To start the installation procedure, do not use the setld command. Use the dms utility (see Section 2.2). In a local (node-specific) installation, the system on which you are installing Gateway-ST uses its own disks when Gateway-ST is run. A local (node-specific) installation procedure loads Gateway-ST files on the disks that belong to the system where you perform the installation. When Gateway-ST is run, its executable files are mapped into memory on the same system. In a diskless client environment, the system on which you are installing Gateway-ST is a server for Diskless Management Services (DMS). It provides the disks for client systems running Gateway-ST software. This installation environment is referred to as "diskless" because the client system uses Gateway-ST software accessed through the network by Network File System (NFS) software. When Gateway-ST is run by users logged into a client system, Gateway-ST executables are mapped into memory on the client system rather than the server system. From the perspective of the client node, Gateway-ST installation is handled entirely by the manager of the DMS server area. Preparing for DECnet/SNA Gateway-ST Installation 1-3 ________________________ Note ________________________ The diskless server area does not provide Gateway- ST software to users logged in to the server system itself. Installing Gateway-ST into the diskless environment provides Gateway-ST software only to client systems. Therefore, if users at your site need to use Gateway-ST when logged in to the local server system, you must perform a local (node-specific) installation of Gateway-ST in addition to the diskless installation. ______________________________________________________ 1.5 License Registration Gateway-ST includes support for the ULTRIX License Management Facility (LMF). A License Product Authorization Key (License PAK) must be registered in the License Database (LDB) in order to use Gateway-ST on a newly- licensed node. The License PAK may be shipped along with the kit if you ordered the license and media together; otherwise, it is shipped separately to a location based on your license order. To register a license under ULTRIX, first log in as superuser. Then, before installing Gateway-ST, edit an empty PAK template with the lmf register command as follows. Include all the information on your License PAK: # lmf register After you register your license, use the following lmf reset command to copy the license details from the License Database (LDB) to the kernel cache. # lmf reset For complete information on using the ULTRIX License Management Facility, see the ULTRIX Version 4.0 Guide to Software Licensing or the lmf(8) reference page. 1-4 Preparing for DECnet/SNA Gateway-ST Installation 1.6 Checking the Media Software Distribution Kit For installations from media, use the Bill of Materials (BOM) to check the contents of your software distribution kit. The kit includes this installation guide, the rest of the documentation set and one of the following: o The TK50 tape cartridge, labeled DECnet/SNA Gateway- ST V1.2, for systems with TK50 or TK70 tape cartridge drives o The 9-track magnetic tape (MT9), labeled DECnet/SNA Gateway-ST V1.2, for systems with magnetic tape drives Your distribution kit also includes a cover letter titled DECnet/SNA Gateway-ST. This letter contains information that is important for you to know before installing Gateway-ST; information that may not be included in this installation guide or in the release notes. You should locate the cover letter and read it now. 1.7 Installation Procedure Requirements This section discusses various requirements for installing Gateway-ST. 1.7.1 Time Requirements A local installation requires 5 to 10 minutes once the media is mounted; a DMS server installation, approximately 20 to 25 minutes; an RIS server installation, approximately 20 to 25 minutes. Installation times depend upon the type of media and your system configuration. Installation time for an RIS client might vary from 5 to 20 minutes because it is dependent on network configuration and load. If the network is not active, you should expect an RIS client installation time roughly equal to a local installation time. Running each of the two Installation Verification Procedure (IVPs) on your system takes 1 to 2 minutes. Preparing for DECnet/SNA Gateway-ST Installation 1-5 1.7.2 Login Privileges You must be able to log in as superuser on the system where you are installing Gateway-ST. Only the superuser has sufficient privileges to install the Gateway-ST software. 1.7.3 Hardware Requirements This section discusses hardware requirements and the combinations of communications equipment that you can use for the Gateway-ST. Connecting the Gateway-ST to Ethernet As a node in an Ethernet local area network (LAN), the Gateway-ST can be either directly or indirectly connected to the Ethernet. For direct connection to the Ethernet cable, use an Ethernet transceiver, such as an H4005. The H4005 transceiver, with its accessories, connects a single system to the Ethernet cable. For indirect connection to the Ethernet cable, use a Local Network Interconnect (DELNI). A DELNI can group together more than one Ethernet device and can then connect the devices to the Ethernet using a single line. These two types of local area network connections appear the same to the Gateway user. Connecting the Gateway-ST to the SNA Network The following sections outline the line support available when using the DEC MicroServer-SP or the DEC MicroServer. o DEC MicroServer-SP Line Support The line interface that connects the DEC MicroServer-SP to the IBM SNA network has one port for one synchronous communication link. The DEC MicroServer-SP can handle data communications speeds of up to 19.2K bps. Table 1-1 shows the line configuration available with the DEC MicroServer-SP. 1-6 Preparing for DECnet/SNA Gateway-ST Installation Table_1-1_DEC_MicroServer-SP_Port_Speeds___________________ Data Speeds (in bits per Number second)__________of_Lines____Ports_________________________ Up_to_19.2K_bps__1___________0_____________________________ o DEC MicroServer Line Support The line interface that connects the DEC MicroServer to the IBM SNA network has four ports for up to four synchronous communication links. The DEC MicroServer can handle data communication speeds of up to 256K bps. The range of speeds is divided into three bands. In each band, a certain number of the synchronous ports are available for use. The following table shows the three speed bands, the number of ports available in each band, and the identification of these ports. Table_1-2_DEC_MicroServer_Port_Speeds______________________ Data Speeds (in bits per Number second)__________of_Lines____Ports_________________________ Up to 64K 4 0,1,2,3 Above 64K 2 0 and 1 up to 128K Above 128K 1 0 only up_to_256K_________________________________________________ Preparing for DECnet/SNA Gateway-ST Installation 1-7 Using Modems The SDLC lines used with the DECnet/SNA Gateway-ST must be attached to a modem, modem eliminator, or an IBM direct attach line. The type of modem or modem eliminator you need for each line depends on factors such as line speed, duplex setting of the line, distance between modems, and data transfer rate. (For example, a Bell 2096 modem can be used at 9.6K bps full duplex on most networks.) You can use any modem that provides synchronous communication at between 2.4K bps and 256K bps on full-duplex or half-duplex lines. Each communication link connects ultimately to an IBM 37xx communications controller. ________________________ Note ________________________ The Gateway-ST does not provide internal clocking. The Gateway-ST clock parameter internal setting is for diagnostic purposes only. The clock parameter is set to external as part of the configuration procedures supplied with Gateway-ST. ______________________________________________________ Choosing Adapter Cables The synchronous communication port(s) on the Gateway-ST are identical: each is a 50-pin male connector. Depending on the type of modem you are using, you need one of the following adapter cables to connect the port to the modem: ___________________________________________________________ Modem Part Interface_____Number____Description________________________ V.24/EIA- BS19D-02 25-pin D-Type connector (ISO 2110). 232-D Also suitable for the RS-232-C interface with adapter. The adapter enables the adapter cable to be used on RS-232-C lines. V.35 BC19F-02 34-pin connector with balanced ________________________electrical_interface.______________ Connecting the load host to the Ethernet cable You can use the same devices for attaching the load host to the Ethernet as for connecting the Gateway to the Ethernet (See the discussion above). Ensure that the load host is 1-8 Preparing for DECnet/SNA Gateway-ST Installation physically connected to the Ethernet cable that is attached to the Ethernet port on the Gateway-ST. Also, check the hardware installation documentation for your load host system. Ensuring that you have a software distribution device (if installing from media) You need a distribution device that corresponds with the software distribution media. For example, if you have a TK50 software kit, you need a TK50 or TK70 tape drive. You must know how to load the media supplied with the software distribution kit on the appropriate drive. The documentation for the tape or disk drive that you are using explains how to load media. Using a terminal at the load host You can use either a hardcopy or video terminal to communicate with the operating system and respond to prompts from the installation procedure for Gateway-ST. 1.7.4 Software Requirements 1.7.4.1 Preparing the IBM SNA Environment To allow the DECnet/SNA access routines to communicate with an IBM SNA network through the Gateway-ST, you have to prepare certain software components in the IBM environment. The DECnet/SNA Gateway-ST Guide to IBM Parameters identifies the IBM parameters required for successful communication between the IBM host and the Gateway-ST. To ensure that the IBM parameters are correctly defined, the IBM system administrator must be familiar with the DECnet/SNA Gateway-ST Guide to IBM Parameters. This book contains a checklist of the information and parameters the system programmer must use to set up the IBM system. For details of how IBM parameter settings affect parameter settings for various Gateway components, see Chapter 3 of this manual. ________________________ Note ________________________ Since IBM system programmers at your site may reconfigure and generate their systems according to a set schedule (for example, every month), try to give Preparing for DECnet/SNA Gateway-ST Installation 1-9 them as much advance notice as possible to prepare for the Gateway-ST. ______________________________________________________ 1.7.4.2 Preparing the DECnet Environment Do the following to prepare your DECnet environment: 1. Verify the status of the load host's Ethernet line and circuit with the following ncp commands: ncp>show line line-id status ncp>show circuit circuit-id status where line-id UNA-n, QNA-n, SVA-n, or BNA-n, depending on your system. circuit- UNA-n, QNA-n, SVA-n, or BNA-n, depending on your system. id The line and circuit must both be ON. If they are not, use the ncp set line and set circuit commands to set them to the ON state. 2. Check the DECnet definition of the load host's Ethernet line and circuit with the following ncp commands: ncp>show line line-id characteristics ncp>show circuit circuit-id characteristics ncp> show node node-id characteristics where line-id UNA-n, QNA-n, SVA-n, or BNA-n, depending on your system. circuit- UNA-n, QNA-n, SVA-n, or BNA-n, depending on your system. id The preceding commands display parameters that you specify for the line, circuit, and gateway node. Table 1-3 shows the default values for some of these parameters. If the parameters for your line and circuit do not correspond to the values shown, you can change these values with NCP commands. 1-10 Preparing for DECnet/SNA Gateway-ST Installation Table_1-3_Ethernet_Line_and_Circuit_Characteristics________ ___________________Line_Characteristics____________________ Protocol ETHERNET ___________________________________________________________ __________________Circuit_Characteristics__________________ Type ETHERNET ___________________________________________________________ ___________________Node_Characteristics____________________ Service_________ENABLED____________________________________ 3. Enable event logging at the DECnet load host if not already enabled. Event logging records all system and network events or errors. Event logging is also used to diagnose problems that might occur with the Gateway. Use the ncp set logging command to enable event logging. For complete information on DECnet event logging, refer to DECnet-ULTRIX Network Management. 1.7.4.3 Preinstallation ULTRIX Software DECnet/SNA Gateway-ST Version1.2 requires ULTRIX Version 4.0 or higher to be installed. In addition, Gateway-ST requires the following ULTRIX software subsets to be loaded on the system where you install Gateway-ST: o UDTBASE4?? (for RISC) or ULTBASE4?? (for VAX), which is named "ULTRIX Base System" o DNPBASE4?? (for RISC) or DNUBASE4?? (for VAX), which is DECnet Phase IV o UDTMOP4?? (for RISC) or ULTMOP4?? (for VAX), which is Maintenance Operations Protocol software To install the Gateway-ST man pages, the following ULTRIX software subset must be installed on the system where you install Gateway-ST: o UDTDCMT4?? (for RISC) or ULTDCMT4?? (for VAX) which is named "Document Preparation Software" Preparing for DECnet/SNA Gateway-ST Installation 1-11 If you are installing Gateway-ST in a local (node-specific) environment, perform the following steps to determine whether the preceding ULTRIX subsets are loaded: 1. Log in to the system where you plan to install Gateway- ST. 2. Enter the following commands: % /etc/setld -i | grep BASE4 % /etc/setld -i | grep DCMT4 % /etc/setld -i | grep MOP4 Check the displayed rows for the relevant subset names and for any related patch names. The word installed appears in a row after the subset identifier code when a subset is loaded. If the word installed does not appear (the second column in a row is blank), the subset or patch is not loaded. In this case, you must load the missing ULTRIX software before installing Gateway-ST. 1.7.5 Determining Which Subsets to Load You must choose the Gateway-ST subsets you want to load. The Gateway-ST subsets have the following titles and descriptions: o SYVBASE120 for VAX/ULTRIX SYRBASE120 for RISC/ULTRIX This subset includes the Gateway-ST image and online release notes. It is loaded to and runs in the remote Gateway node. o CTVGM100 for VAX/ULTRIX CTRGM100 for RISC/ULTRIX This subset contains the gateway management software. This software runs on the load host, and you use the software to configure and manage Gateway-ST nodes. o CTVMAN100 for VAX/ULTRIX CTRMAN100 for RISC/ULTRIX This subset includes the Gateway-ST man pages (reference pages). The man pages are located on the load host and can be accessed from the ULTRIX shell by using the man command. 1-12 Preparing for DECnet/SNA Gateway-ST Installation 1.7.6 Determining Disk Space Requirements The disk space requirements discussed in this section apply to the disks where you load the Gateway-ST subsets. Tables 1-4 and 1-5 list the disk space requirements for loading Gateway-ST software subsets on VAX/ULTRIX and RISC/ULTRIX systems. These tables specify disk space requirements by file system for the convenience of those doing installations on systems where these file systems are mount points for different disk partitions. Table 1-4 Worksheet for Subset Sizes (Kilobytes Required) on RISC __________Systems________________________________________________ /usr /usr /usr /lib /lib /lib Subset Subset /snagwy /snagwy /usr /usr /usr Title_______Name________/snagwy/bin_____/etc_____/man___/bin___/etc Gateway- SYRBASE120 536 0 0 0 0 0 ST image Gateway- CTRGM100 139 1056 477 0 3 3 ST gateway manage- ment Gateway- CTRMAN100 0 0 0 20 0 0 ST man pages Totals: (--) (--) (--) (--) (--) (--) _______________________________________________________________ Preparing for DECnet/SNA Gateway-ST Installation 1-13 Table 1-5 Worksheet for Subset Sizes (Kilobytes Required) on VAX __________Systems________________________________________________ /usr /usr /usr /lib /lib /lib Subset Subset /snagwy /snagwy /usr /usr /usr Title_______Name________/snagwy/bin_____/etc_____/man___/bin___/etc Gateway- SYVBASE120 536 0 0 0 0 0 ST image Gateway- CTVGM100 139 648 349 0 3 3 ST gateway management Gateway- CTVMAN100 0 0 0 20 0 0 ST man pages Totals: (--) (--) (--) (--) (--) (--) _______________________________________________________________ Using the disk space requirements table for a VAX or a RISC system that applies to your system, total the values for the subsets that you plan to load in each file system. Compare the space required for subsets with the free space currently on the disks where Gateway-ST files will reside. 1.7.6.1 Checking Disk Space for Installation on a Local Node To determine the current amount of free space for a directory path, log in to the system where you plan to install Gateway-ST. You can check which file systems are mounted and where they are by displaying the file /etc/fstab. For example: # more /etc/fstab /dev/rd0a:/:rw:1:1:ufs:: /dev/rd0g:/usr:rw:1:2:ufs:: /usr/staff/r1/leslie@bigsys:/usr/staff/r1/leslie:rw:0:0:nfs:bg: /usr/man@bigsys:/usr/man:ro:0:0:nfs:bg: 1-14 Preparing for DECnet/SNA Gateway-ST Installation This display indicates that the system has only one local disk drive, /dev/rd0, and that /usr is mounted to the g partition on that disk drive. So /dev/rd0g is the mount point for /usr and for the Gateway-ST files that are subordinate to /usr. The files are to reside in the g partition of the disk. Enter the df command to determine total space and free space for the file system where Gateway-ST files will reside. The previous display of the /etc/fstab file shows that only /usr is a mount point, and you only need to inspect free space in the /usr file system: # df /usr Filesystem Total kbytes kbytes % node kbytes used free used Mounted on /dev/rd0g 122598 54447 55892 49% /usr This display indicates that there are 55892Kb free. This free space must accommodate subset requirements listed in Tables 1-4 and 1-5 for the /usr/lib/snagwy/bin, /usr /lib/snagwy/etc, /usr/lib/snagwy, /usr/man directory structures. On systems where you load the Gateway-ST files to devices other than /usr, enter the following command: # df [filesystem...] The free space must accommodate subset requirements listed in Tables 1-4 and 1-5 for the /usr/lib/snagwy/bin, /usr /lib/snagwy/etc, /usr/lib/snagwy, /usr/man directory structures. 1.7.6.2 Checking Disk Space for Installation into a Diskless Environment For Gateway-ST installations into the diskless environment, the disks where Gateway-ST subsets reside are on a server system. Therefore, for installations into diskless environments, log in to the server system to check disk space requirements. Inspect the free space in the following locations: o /dlenv?/root0.mips/usr (root area for ULTRIX RISC installations) or /dlenv?/root0.vax/usr (root area for ULTRIX VAX installations) Preparing for DECnet/SNA Gateway-ST Installation 1-15 o /dclient?/client?.root (client area) For installations into a diskless environment, the disk space requirements specified in Table 1-4 and Table 1-5 for the noted directory structures are requirements for both the root area and each client area. If multiple root areas serve the Gateway-ST software, each root area requires space for all the installed subsets. For more information about installing into a diskless environment, see ULTRIX Guide to Diskless Management Services. 1.7.6.3 Increasing Disk Space Available for DECnet/SNA Gateway-ST Installation If you find that there is insufficient disk space for the Gateway-ST subsets, and know that you have additional space on alternative disks or disk partitions for your system, you can take the following steps before installing Gateway- ST: 1. Log in as superuser. 2. Create this directory: /usr/lib/snagwy. 3. Specify in the /etc/fstab file that one or more of the newly created directories are mount points to new disk partitions where there is additional space. 4. Enter the mount -a command so that the new mount points take effect. 1.8 Backing Up Your System Disk Digital recommends that you back up your system disk before installing any software. Use the backup procedures established at your site. For details on performing a system disk backup, see your ULTRIX documentation. 1.9 Stopping the Installation You can stop the installation procedure at any time by using . After doing so, use setld -i to inventory the Gateway-ST subsets and their contents. Then you can execute setld -d to delete each of the subsets, and rm to delete installed files. 1-16 Preparing for DECnet/SNA Gateway-ST Installation Appendix A lists the files and directories created during the installation. 1.10 Error Recovery If errors occur during the installation, the system displays failure messages. Errors can occur during the installation if any of the following conditions exist: o The operating system version is incorrect o The prerequisite software version is incorrect o The system parameter values for successful installation are insufficient For descriptions of error messages generated by these conditions, refer to diagnostics portion of the man pages for setld. If you are notified that any of these conditions exist, take the action noted in the man page description. For information on system requirements, see Section 1.7.4. Preparing for DECnet/SNA Gateway-ST Installation 1-17 2 _________________________________________________________________ Installing DECnet/SNA Gateway-ST This chapter describes the installation procedures for DECnet/SNA Gateway-ST. Before you start, read Chapter 1 which describes the general options and requirements that apply to installing Gateway-ST. Gateway-ST can be installed in a number of ways: o Locally from tape, cartridge, or from Remote Installation Services (RIS) media (for RIS clients). Section 2.1 explains how to do a local installation. o Remotely into a Diskless Management Services (DMS) or RIS server area for future client use. Note that these installation procedures assume that you have already created your server environment and are ready to add Gateway-ST to it. Section 2.2 explains how to do a DMS and RIS server installation. 2.1 Installing DECnet/SNA Gateway-ST Locally This installation procedure loads Gateway-ST files on a disk that belongs to the system where you perform the installation. When Gateway-ST is run, its executable images are mapped into memory on this system. This section explains how to start a local installation procedure and how to respond to installation procedure prompts. 2.1.1 Starting the Installation Procedure If you are installing Gateway-ST from tape media, start with Section 2.1.1.1. If you are installing Gateway-ST on a client system using a RIS kit, start with Section 2.1.1.2 Installing DECnet/SNA Gateway-ST 2-1 2.1.1.1 Using TK50 or Magnetic Tape Distribution Media If you are installing Gateway-ST from tape media, start the installation procedure as follows: 1. Mount the media on the appropriate tape drive. 2. Log in as superuser (login name root) to the system where you are installing Gateway-ST. 3. Make sure that you are at the root (/) directory by entering the following command: # cd / 4. Enter a setld command that specifies the -l (load) function and the device special file name for the tape drive where the media is mounted. For example, if you load a magnetic tape on tape unit 0, enter the following command: # setld -l /dev/rmt0h The installation procedure displays the following information and prompt: Please make sure your installation tape is mounted and on-line. Are you ready (y/n)? 5. After all tape rewind and wind operations are complete and the tape drive indicates online status, enter y. Go to Section 2.1.2 to continue the installation. 2.1.1.2 Installing DECnet/SNA Gateway-ST from an RIS Server To install Gateway-ST from a Remote Installation Services (RIS) server to a RIS client you must first install Gateway-ST in your RIS server environment. See your RIS manager if Gateway-ST is not already installed in the RIS server. To install Gateway-ST subsets that reside in an /var /adm/ris distribution area on a remote system, start the installation procedure as follows: 1. Log in as superuser (login name root) to the system where you are installing Gateway-ST. 2-2 Installing DECnet/SNA Gateway-ST 2. Make sure that you are at the root (/) directory by entering the following command: # cd / 3. Enter a setld command that requests the load function and identifies the system where Gateway-ST subsets are located. For example, if you are loading Gateway-ST subsets from a RIS distribution area on node BIGSYS, enter the following command: # setld -l bigsys: If you receive an error, verify that you correctly followed the preparation steps in Section 1.2. See Section 2.1.2 to continue the installation. 2.1.2 Responding to Installation Procedure Prompts This section explains the installation procedure prompts and displays. 2.1.2.1 Selecting Subsets After you enter the setld command for local (node-specific) installations or after you start the dms or ris utility for server installations, the installation procedure displays descriptions of Gateway-ST subsets and asks you to specify the subsets that you want to load. Note that the order in which the subsets appear depends upon the installation media. This section and Appendix B describe installations from tape distribution media. When installing from tape: *** Enter Subset Selections *** The subsets listed below are optional: 1) DECnet/SNA Gateway Management 2) DECnet/SNA Gateway-ST Base Software 3) DECnet/SNA Gateway Mgmt Man Pages 4) All of the Above 5) None of the Above 6) Exit without installing subsets Enter your choice(s): When installing from a RIS server, note that the subset numbers may vary depending on what products are available in the RIS area. Installing DECnet/SNA Gateway-ST 2-3 If you specify more than one number at the prompt, separate each number with a space, not a comma. Next, the script lets you verify your choice. For example, for an installation from tape, if you enter 4 in response to the previous prompt, you see the following display: You are installing the following subsets: DECnet/SNA Gateway Management DECnet/SNA Gateway-ST Base Software DECnet/SNA Gateway Mgmt Man Pages Is this correct? (y/n): If the displayed subsets are not the ones you intended to choose, enter n. In this case, the subset selection menu reappears, and you can correct your choice of optional subsets. If the displayed subsets are the ones you want to load, enter y. 2.1.2.2 Monitoring Displays During the Subset Loading Process The procedure displays a message that the installation is starting. The following appears for a VAX/ULTRIX system, during installation from tape. Note that the order in which these messages appear is different for installation from disk (see the note below). Copying DECnet/SNA Gateway Management (CTVGM100) from tape Verifying DECnet/SNA Gateway Management (CTVGM100) Copying DECnet/SNA Gateway-ST Base Software (SYVBASE120) from tape Verifying DECnet/SNA Gateway-ST Base Software (SYVBASE120) Copying DECnet/SNA Gateway Mgmt Man Pages (CTVMAN100) from tape Verifying DECnet/SNA Gateway Mgmt Man Pages (CTVMAN100) Beginning DECnet/SNA Gateway Management V1.0 installation © Digital Equipment Corporation. 1991. All Rights Reserved. ________________________ Note ________________________ If you install from disk and choose All of the Above, the procedure may install the Gateway-ST base software before the gateway management software. When this 2-4 Installing DECnet/SNA Gateway-ST happens, the following lines appear prior to the Copying... and Verifying... messages: DECnet/SNA Gateway-ST V1.2 Base Software is not viable until DECnet/SNA Gateway Management is installed. Do you wish to continue? (y|n) [y]: Enter either y or and continue with the installation. ______________________________________________________ After the Copying... and Verifying... messages, the installation procedure continues with queries about verifying the installation and configuring your Gateway. You can carry out these tasks during the installation or do them separately. Chapter 3 discusses verification and configuration. If, during the course of the installation, you encounter errors from the setld utility, see the Diagnostics section of the setld(8) reference page for an explanation of the error and the appropriate action to take. If the verification process fails, you can look in the file /usr/var/adm/fverifylog to find information that can help you diagnose the problem. You might also find useful information in the file /etc/setldlog. 2.2 Installing DECnet/SNA Gateway-ST into a Server Environment This section explains how to start the installation procedure and load software subsets when you are installing Gateway-ST into an environment controlled by DMS (Diskless Management Services) or RIS (Remote Installation Services). For installation from TK50 and MT9 media kits, mount the media on the appropriate device of the server node. You are prompted later to enter the name of the special file for that device. Section 2.2.1 explains how to install Gateway-ST into a DMS server environment. Section 2.2.2 explains how to install Gateway-ST into a RIS server environment. Installing DECnet/SNA Gateway-ST 2-5 2.2.1 DMS Server Installations The following procedure lets you install Gateway-ST with the ULTRIX Version 4.0 dms utility into the diskless server area. The examples in this section show how to install the subsets to /dlenv0/root0.mips for RISC/ULTRIX clients. For VAX/ULTRIX clients, the root directories are /dlenv? /root?.vax. Your dms server may have other diskless server areas (dlenv?) and other root directories (root?.mips) shared by clients within each area. 1. Log in and become the superuser. 2. To invoke the dms utility, enter the following command: # /etc/dms 3. Select the Install Software option from the following menu by typing i: DISKLESS MANAGEMENT SERVICES (DMS) UTILITY MENU a - Add Client Processor m - Modify Client Parameters r - Remove Client Processor l - List Registered Clients s - Show Products in Diskless Environments i - Install Software c - Create Diskless Area on Disk k - Kernel Rebuild or Copy e - Exit Enter your choice: i 4. Choose option 2 in the following menu: The menu below offers you two software installation alternatives: 1) You can install an operating system to a new diskless area. 2) You can install additional software to an existing diskless area that already contains an operating system. Diskless Area Software Installation Menu: 1 Install Operating System to New Area 2 Add Software to Existing Area 3 Return to Previous Menu 2-6 Installing DECnet/SNA Gateway-ST Enter your choice: 2 5. The following message lists the available installation directories: You have chosen to install additional software into an existing diskless environment. These are the available installation directories: If there is more than one installed root?.mips directory in the diskless server area, choose the appropriate directory from the menu that lists existing root?.mips directories. For example: 1. /dlenv0/root0.mips 2. /dlenv0/root1.mips 3. /dlenv0/root0.vax Enter your choice: 1 6. You are next prompted for an input device name: Enter the device special name or mount point of the distribution media, for example, /dev/rmt0h: /dev/rmt0h 7. If you want all registered clients to automatically have access to Gateway-ST, enter y to the following question: The product software will automatically be propagated to every registered client. Is this alright? (y/n): y If you answer n, DMS returns you to the main menu. 8. If your distribution media is tape, a message appears asking you to confirm that the tape is ready and on line. If it is, type y. Please make sure your installation tape is mounted and on-line. Are you ready (y/n)? y Positioning Tape 9. The next message lists the software subsets you select for automatic installation. See Section 2.1.2.1 to specify the subsets you want to load. See Section 2.1.2.2 to monitor the displays during the subset load process and to complete the installation procedure. Installing DECnet/SNA Gateway-ST 2-7 Repeat these installation procedures for each root?.mips directory shared by clients that will need access to the Gateway-ST software. Refer to ULTRIX Guide to Diskless Management Services for additional detail. The dms top level menu appears for your next selection. 2.2.2 RIS Server Installations The following sample session describes how to add the Gateway-ST product to the ris0.mips area: 1. Log in and become the superuser. 2. Invoke the ris utility by entering the following command: # /etc/ris 3. Select the Install Software option from the Remote Installation Services (RIS) Menu by typing i: REMOTE INSTALLATION SERVICES (RIS) MENU a - Add Client r - Remove Client s - Show Products in Remote Installation Environments m - Modify Client i - Install Software e - Exit Enter your choice: i 4. Choose option 2 from the RIS Software Installation Menu: The menu below offers you two software installation alternatives: 1) You can create a new area to serve either RISC or VAX clients by installing a software product. The ris utility automatically creates the new area. 2) You can install additional software to an existing area that serves either RISC or VAX clients. RIS Software Installation Menu: 1 Install Software to a New Area. 2 Add Software to an Existing Area. 3 Return to Previous Menu 2-8 Installing DECnet/SNA Gateway-ST Enter your choice: 2 5. A list of available environments appears from which you might select ris0.mips: You have chosen to add a new product into an existing environment. Select the remote installation environment: 1 /var/adm/ris/ris0.mips ULTRIX V4.0/ULTRIX WS V4.0 MANDATORY SUPPORTED (RISC) 2 /var/adm/ris/ris0.vax ULTRIX V4.0/ULTRIX WS V4.0 SUPPORTED (VAX) Enter your choice: 1 6. You are next prompted for an input device name: Enter the device special file name or the path of the directory where the software is located, for example, /dev/rmt0h: /dev/rmt0h 7. If your distribution media is tape, a message appears asking you to confirm that the tape is ready and on line. If it is, type y: Please make sure your installation tape is mounted and on-line. Are you ready (y/n)? y Positioning Tape 8. The next message lists the software subsets you select for automatic installation. See Section 2.1.2.1 to specify the subsets you want to load. See Section 2.1.2.2 to monitor the displays during the subset load process and to complete the installation procedure. 9. After the subsets are installed, the following message appears: Media extraction complete. 10.Repeat the following steps, a through f, for each RIS client allowed to install Gateway-ST. a. The ris main menu appears for your next selection. Select the Modify Client option from the Remote Installation Services (RIS) Menu by typing m: Installing DECnet/SNA Gateway-ST 2-9 REMOTE INSTALLATION SERVICES (RIS) MENU a - Add Client r - Remove Client s - Show Products in Remote Installation Environments m - Modify Client i - Install Software e - Exit Enter your choice: m b. Enter the name of the client to be modified from the list of available clients: The following clients are available to modify: clienta clientb Enter the client processor's hostname: clienta c. Verify the client processor's hardware Ethernet address. Press to choose the address assigned ([default- address]) when the client was added to the RIS environment. Enter the client processor's hardware Ethernet address, for example, 08-00-2b-02-67-e1 [08-00-2b-14-ac-d1]: d. Choose the products to which you want this client to have access. You are shown the client's currently selected RIS environment and the products that the selected client can already access. At the prompt, enter the products you would like this client to be able to install including Gateway-ST. Separate each choice with a space. The existing environment is /usr/var/adm/ris/ris0.mips. The client currently can install the following products from /usr/var/adm/ris/ris0.mips: 'ULTRIX V4.0/ULTRIX WS V4.0 MANDATORY SUPPORTED (RISC) ' Select one or more products for the client to install from /usr/var/adm/ris/ris0.mips: 2-10 Installing DECnet/SNA Gateway-ST Product Description 1 'ULTRIX V4.0/ULTRIX WS V4.0 MANDATORY SUPPORTED (RISC) ' 2 'DECnet/SNA Gateway-ST' Enter one or more choices, for example, 1 2: 1 2 e. If the list of products available to this client is correct, type y. If the list is not correct, type n to return to step d and reenter the products. You chose the following products: 1 'ULTRIX V4.0/ULTRIX WS V4.0 MANDATORY SUPPORTED (RISC) ' 2 'DECnet/SNA Gateway-ST' Is that correct (y/n)? [y]: y f. After modifying the client's records with the new list of installable products available, the following confirmation message appears: clienta has been modified Installing DECnet/SNA Gateway-ST 2-11 3 _________________________________________________________________ Completing the Installation: Verifying, Configuring, Loading This chapter explains what you need to do after the software is copied from the installation media to make DECnet/SNA Gateway-ST ready for use. Note that you can carry out these tasks (except for loading the software) either as part of the interactive installation procedure (see Chapter 2) or separate from it. 3.1 Running IVPs You should run the Installation Verification Procedures (IVPs) to be sure that Gateway-ST is correctly installed. At the time that you install the Gateway-ST base software subset or the gateway management subset, the installation procedure asks if you want to run the IVP for that subset. There is no IVP for the man pages subset. You can run either IVP after the installation to verify that the software is available on your system. You might also want to run the IVPs after a system failure to be sure that users can access Gateway-ST. To run the IVP after an installation, enter the following command: # setld -v subsetname For VAX systems choose SYVBASE120, or CTVGM100 for subsetname. For RISC systems use choose SYRBASE120, or CTRGM100 for subsetname. For complete samples of Gateway-ST Installation Verification Procedures, see Appendix B. Completing the Installation: Verifying, Configuring, Loading 3-1 3.2 Configuring your Gateway 3.2.1 Understanding the snaconfig utility After installing the Gateway-ST software on the load host, you must configure the Gateway-ST system. Digital Equipment Corporation provides a program, snaconfig, to assist you with the initial configuration. You can do this as part of the interactive installation procedure (see Appendix B) after you copy the base software subset from the media. Alternatively, you can run snaconfig separately as described here. The snaconfig utility performs the following steps by using both default information and information that you provide: 1. Defines the Gateway node and snaini object in the load host's DECnet database. A copy of the commands you need to define the gateway node is saved in the following script file: /var/snagwy/define_gateway-node-name_on_load-host-node-name This script file remains on the system should you need to reexecute the commands in the future, for example if you reconfigure DECnet-ULTRIX. 2. Creates and displays a script file that configures the SNA components in the Gateway database. This script contains snancp commands and has the following file specification: /var/snagwy/snagateway_gateway-node-name_sna This script is used every time the Gateway-ST is reloaded. 3. Creates and displays a script file that configures DECnet components in the Gateway-ST database. This script contains ncp commands and snancp commands, and has the following file specification: /var/snagwy/snagateway_gateway-node-name_dna This script is used every time the Gateway-ST is reloaded. 3-2 Completing the Installation: Verifying, Configuring, Loading After the Gateway-ST is initially configured and loaded, you can customize the configuration for your site. Use snancp and ncp commands to interactively change the behavior of the Gateway. DECnet/SNA Gateway-CT and Gateway- ST Management (ULTRIX) describes the snancp commands. DECnet-ULTRIX NCP Command Reference describes the ncp commands. When you enter commands interactively, the definitions or changes you make take effect immediately. However, these definitions or changes stay in effect only while the Gateway-ST is running. When the Gateway-ST is reloaded, the values used are those in the script files that you created during the initial configuration. 3.2.2 Using snaconfig On the following pages, a sample snaconfig dialogue appears on consecutive left-hand pages with text highlighted by callout numbers. Explanations of the highlighted material appear with the corresponding callouts on the right-hand pages. The procedure begins with the snaconfig st command. You must be the superuser to execute the command. The st option signifies the Gateway-ST. Default answers to the snaconfig queries appear in brackets following the queries. You can enter a question mark (?) at any time for help, and you can stop the procedure with . Completing the Installation: Verifying, Configuring, Loading 3-3 # snaconfig st DECnet/SNA Gateway-ST V1.2 Configuration Procedure. © Digital Equipment Corporation. 1991. All Rights Reserved. The configuration is divided into three parts: Part 1: Defining the Gateway node in the load host's DECnet database. Part 2: Creating a script file that is used to configure the SNA database in the Gateway each time it is loaded. Part 3: Creating a script file that is used to configure the DECnet database in the Gateway each time it is loaded. This configuration procedure prompts you to see if you want to run each of the three parts. All parts must be completed before the Gateway can be loaded. Enter "?" at any time for help. DECnet/SNA Gateway-ST node name []: bounty ==================================================================== Part 1: Defining the Gateway node in the load host DECnet database ==================================================================== Do you wish to create this script file? (y/n) [y]: y 1 DECnet node address of bounty? (aa.nnnn) []: 4.443 2 Ethernet hardware address of bounty?(12 hex digits)[]: 08002b08ccb3 3 Directory for dump file on the load host? [/var/snagwy]: 4 Load host's ethernet circuit name? (circuit-id) [bnt-0]: 5 All questions for Part 1 have been answered. 3-4 Completing the Installation: Verifying, Configuring, Loading 1 Do you wish to create this script file? (y/n) [y]: If you are certain that the load host already has the Gateway node definition, and that the snaini object and the appropriate proxy login information are defined (from a previous installation), type n. If you type y, the system prompts you for the information in the following sections. The default answer is y. 2 DECnet node address of gateway-node-name (aa.nnnn) []: Specify the DECnet address of the Gateway node in the following way: aa Specifies the (optional) DECnet area number and is a decimal number ranging from 1 to 63. nnnn Specifies the DECnet node number and is a decimal number ranging from 1 to 1023. 3 Ethernet hardware address of gateway-node-name (12 hex digits) []: Specify the Ethernet hardware address of the Ethernet port for the Gateway node. Enter this address either as 12 hexadecimal digits or as six pairs of hexadecimal digits separated by hyphens. For example, these two expressions specify the same address: 08002b08ccb3 08-00-2b-08-cc-b3 4 Directory for dump file on the load host [/var/snagwy]: Specify the device and directory on the load host that will contain the dump file if the Gateway node performs an up-line dump. The dump file is not created until it is required. The default device and directory is /var/snagwy. Ensure that the specified device always has enough free space for the dump file. Each version of the dump file is approximately 2250 Kilobytes (KB). If less than 2250KB are available on the specified device, a warning message is issued. 5 Load host's Ethernet circuit name (circuit-id) [QNA-0]: Completing the Installation: Verifying, Configuring, Loading 3-5 Specify the name of the Ethernet circuit that connects the load host to the Gateway-ST. The Gateway node makes service requests for loading and dumping on this circuit. The default value varies with the load host processor. 3-6 Completing the Installation: Verifying, Configuring, Loading The following ncp commands will be used to define the Gateway node and 6 snaini object in the load host's DECnet database. In addition, a proxy login will be established for the Gateway Initialization process. #! /bin/sh5 -v #------------------------------------------------------------------- # Start of file: /var/snagwy/define_bounty_on_netsea # DECnet/SNA Gateway-ST V1.2, Load Host Database Setup # Created: Wed Apr 3 21:27:31 1991 by snaconfig # Host node: netsea, User: jpjones #------------------------------------------------------------------- NUL=/dev/null ncp purge object snaini all 2> $NUL ncp clear object snaini all 2> $NUL ncp purge node 4.443 all 2> $NUL ncp purge node bounty all 2> $NUL ncp clear node 4.443 all 2> $NUL ncp clear node bounty all 2> $NUL ncp <. The following occurs: o A DECnet proxy entry is created on the load host for the Gateway node. A message appears indicating this. o The command procedure is run, executing the ncp commands. The command procedure displays as it runs. If you answer n and press , this part of the configuration is run again, allowing you to provide different values for the items. 3-8 Completing the Installation: Verifying, Configuring, Loading Creating proxy login for bounty::sna$go #! /bin/sh5 -v #------------------------------------------------------------------- # Start of file: /var/snagwy/define_bounty_on_netsea # DECnet/SNA Gateway-ST V1.2, Load Host Database Setup # Created: Wed Apr 3 21:27:31 1991 by snaconfig # Host node: netsea, User: jpjones #------------------------------------------------------------------- NUL=/dev/null ncp purge object snaini all 2> $NUL ncp clear object snaini all 2> $NUL ncp purge node 4.443 all 2> $NUL ncp purge node bounty all 2> $NUL ncp clear node 4.443 all 2> $NUL ncp clear node bounty all 2> $NUL ncp <, this part of the configuration is run again, allowing you to provide different values for the items. Press to accept the default n. Completing the Installation: Verifying, Configuring, Loading 3-11 ============================================================================= Part 2: Creating a script file to configure the SNA database in the Gateway ============================================================================= Do you wish to create this script file? (y/n) [y]: 9 Number of lines to be configured? (1-4) [1]: 10 +---------------+ | Line SYN-0 | +---------------+ Is the line full duplex? (y/n) [n]: 11 3-12 Completing the Installation: Verifying, Configuring, Loading 9 Do you wish to create this script file? (y/n) [y]: If you type y, the information you provide goes into the following script in the form of snancp commands: /var/snagwy/snagateway_gateway-node-name_ sna This script initializes the SNA components each time the Gateway-ST is loaded. You can edit this file to customize your configuration. If you edit this file, you must make sure that the statement that sets the line, circuit and PU characteristics appears before the statement that sets the line and circuit states to ON. 10 Number of lines to be configured (1-4) [1]: The line parameters in this section define the physical lines the Gateway uses to transfer data to the IBM communications controller. ________________________ Note ________________________ If you are using a DEC MicroServer-SP, do not attempt to configure more than one line. ______________________________________________________ 11 Is the line full duplex? (y/n) [n]: The line duplex mode controls modem signaling. The duplex mode of the line can be HALF (half duplex) or FULL (full duplex). Type y if you want the mode to be FULL. The mode must be the same as that defined for the IBM modem. To determine the IBM modem setting, refer to the DUPLEX and ADDRESS parameters for the IBM ACF/NCP LINE macro. ________________________ Note ________________________ This line duplex parameter sets only the physical characteristics of the communications line, not the data transfer mode. The snaconfig utility queries you about the data transfer mode further along in this procedure. ______________________________________________________ Completing the Installation: Verifying, Configuring, Loading 3-13 Does the line use NRZI signalling? (y/n) [n]: 12 Is the modem an IBM diagnostic modem? (y/n) [n]: 13 Line buffer size? (bytes) [265]: 14 +---------------+ | Circuit SDLC-0| +---------------+ Station address? (2 hex digits) [01]: 15 Extended Response mode on circuit? (y/n) [n]: 16 3-14 Completing the Installation: Verifying, Configuring, Loading 12 Does the line use NRZI signaling? (y/n) [n]: Specify the signaling convention to be used on the line. Type y if the line uses non-return-to-zero inverted (NRZI) bit encoding; press if not. This setting must correspond with that for the IBM ACF/NCP LINE macro. 13 Is the modem an IBM diagnostic modem? (y/n) [n]: Specify whether the modem is an IBM diagnostic modem. If the line uses modems without diagnostics, press . The default, which is n, specifies a modem that does not have diagnostic capabilities. This parameter controls how the Gateway device driver interprets the Test Indicator (TI) modem lead (CCITT 142). IBM diagnostic modems use this lead to indicate the modem is handling signals from a host Link Problem Determination Aid (LPDA) test. _______________________ Caution _______________________ If you are not using IBM diagnostic modems, be sure to answer n to the prompt (that is, set the modem to NORMAL operations). Some modems provide a clocking signal on the TI lead. If the modem type is set to DIAGNOSTIC, any clocking signals on the TI lead will severely degrade the performance of the Gateway. ______________________________________________________ 14 Line buffer size? (bytes) [265]: This value must match the value specified for MAXDATA in the IBM ACF/NCP PU macro. Obtain this value from the IBM systems programmer. The value you specify for MAXDATA size is used to set the RECEIVE BUFFER size and the PU SEGMENT size. The default is 265. 15 Station address (2 hex digits) [01]: Specify the SDLC station address. Enter two hexadecimal digits. The value must correspond with the ADDR parameter setting for the IBM ACF/NCP PU macro. The default address is 01. 16 Extended Response mode on circuit? (y/n) [n]: Completing the Installation: Verifying, Configuring, Loading 3-15 Specify whether the circuit operates with NORMAL (modulo 8) or EXTENDED (modulo 128) frame numbering. Modulo 128 frame numbering is supported only on IBM ACF/NCP V4 or later. The setting must correspond with the MODULO parameter for the IBM ACF/NCP LINE macro. 3-16 Completing the Installation: Verifying, Configuring, Loading Is the data transfer mode full duplex? (y/n) [n]: 17 Station identifier? (8 hex digits) [00000000]: 8760eb13 18 +---------------+ | PU SNA-0 | +---------------+ Enter the list of available LU addresses (number or range) [1-255]: 19 Completing the Installation: Verifying, Configuring, Loading 3-17 17 Is the data transfer mode full duplex? (y/n) [n]: The circuit duplex specification controls how the data is transferred. Specify whether the data transfer is to be two-way simultaneous (FULL) or two-way alternate (HALF). On a circuit in FULL duplex mode, frames can be sent and received at the same time. On a HALF duplex mode circuit, each end must wait until the other end has finished sending before it can send. The circuit duplex must agree with the DATMODE parameter in the IBM ACF/NCP GROUP or PU macro. If the DATMODE parameter is specified as FULL, the circuit is full duplex and if the DATMODE parameter is specified as HALF, the circuit is half duplex. The following combinations of circuit duplex and line duplex are allowed: o A full-duplex line and a full-duplex circuit o A full-duplex line and a half-duplex circuit o A half-duplex line and a half-duplex circuit Remember, for full-duplex data transfer, not only the line but also the circuit must be operating in full-duplex mode. If you set the circuit to FULL, the corresponding line duplex parameter must also be set to FULL. However, you can run a half-duplex circuit over a full-duplex line if you wish. 18 Station identifier (8 hex digits) [00000000]: The SDLC station identifier (XID) is used on dial-up (switched) lines to verify the identity of the station. Specify the identifier as eight hexadecimal digits. The first three digits must correspond with the setting of the IDBLK parameter for IBM ACF/VTAM PU macro. The last five digits must correspond with the setting of the IDNUM parameter for the IBM ACF/VTAM PU macro. 19 Enter the list of available LU addresses (number or range) [1-255]: 3-18 Completing the Installation: Verifying, Configuring, Loading The LU list specifies the logical units (LUs) that are defined for the PU; the number of defined LUs is not equal to the number of concurrent sessions supported by the Gateway-ST (see the Gateway-ST release notes). Enter the LUs as a list of decimal number ranges separated by commas. For example, define LUs 1 through 10, LU 12, and LUs 20 through 30 as follows: 1-10,12,20-30 A process on the SNA host node can use only those LUs defined in the list. Any request for communication with an LU not in the list is rejected. The LUs listed must correspond with the LU addresses defined in the LOCADDR parameter for the IBM ACF/VTAM LU macro. Completing the Installation: Verifying, Configuring, Loading 3-19 +--------------+ | Access names | +--------------+ This section asks for information about one or more access names. Press when you have no more to enter. Access name? (1-16 chars) []: cics 20 IBM application name? (1-8 chars) []: cics17 21 IBM logon mode name? (1-8 chars) []: 22 IBM user data? (1-32 chars) []: bligh_appl 23 You will now be prompted for one or more PU/LU pairs. Press when you have no more to enter. PU name? (SNA-n) []: sna-0 24 LU list? (number or range) [1-255]: 1-5 PU name? (SNA-n) []: Access name? (1-16 chars) []: 3-20 Completing the Installation: Verifying, Configuring, Loading 20 Access name? (1-16 chars)[]: Enter the access name as 1 to 16 characters; for example, CICS. If you type an access name, additional prompts appear. After you define all the information for a particular access name, the initial access name prompt appears again. If you enter a second access name, the process begins again, starting with the prompt for LU list. When you have finished defining access names, press in response to the access name prompt. If there are more circuits to be configured, snaconfig returns to the previous questions concerning circuits. If there are no more circuits to be configured, snaconfig goes on to the queries about servers. 21 IBM application name? (1-8 chars) []: The name of the IBM application for the access name. Enter 1 through 8 characters. Sessions established with this access name connect to the designated IBM application. If you need to specify this parameter, ask the IBM systems programmer for the name. 22 IBM logon mode name? (1-8 chars)[]: Enter 1 through 8 characters to specify an IBM ACF/VTAM Logon Mode Table entry for use at the start of each session. The Logon Mode Table entry can specify the protocol rules for the session. If you specify no logon mode name, the default entry for the LU address as defined on the IBM system is used. The name should correspond with the operand label of an IBM ACF/VTAM MODEENT macro. 23 IBM user data? (1-32 chars) []: Enter 1 through 32 characters. This specifies an optional string of user data, which is passed to the session partner. The format of the data is specific to the IBM application acting as the session partner. 24 PU name (SNA-n) []: LU list (number or range) [1-255]: Completing the Installation: Verifying, Configuring, Loading 3-21 You are prompted for one or more PU/LU pairs. Press when you have no more to enter. The PU name specifies the PU used to access the IBM system. Enter the PU in the format SNA-n. You can define more than one PU per access name. You are prompted for further PU/LU pairs until you press in response to the PU name prompt. You must enter at least one PU per access name. The LU list identifies which LUs, for a given PU, can use this access name. Enter a list of numbers and/or number ranges separated by commas (for example, 1-8,10,15-30), and press . 3-22 Completing the Installation: Verifying, Configuring, Loading +--------------+ | Servers | +--------------+ Server SNA-ACCESS 25 No questions for this server. Server RJE 26 No questions for this server. Server DHCF 27 This section requests a list of LUs allocated to DHCF for each PU. Press if you do not wish to define any LU for a given PU. LU list allocated to DHCF for PU SNA-0? (number or range) []: 1-3 28 All questions for Part 2 have been answered. The following snancp commands will be used to set the SNA database 29 in the Gateway each time it is loaded. #------------------------------------------------------------------- # Start of file: /var/snagwy/snagateway_bounty_sna # DECnet/SNA Gateway-ST V1.2, SNA Configuration File # Created: Wed Apr 3 21:33:10 1991 by snaconfig # Host node: netsea, User: jpjones #------------------------------------------------------------------- /usr/bin/snancp < at the prompt. 28 LU list allocated to DHCF for PU SNA-0? (number or range) []: The configuration procedure also defines all parameters for the DHCF server except for the LU list information. The configuration procedure prompts you for this optional DHCF information. Enter a list of LUs to be allocated to the DHCF server, for example, 1-3, and then press . Press if you do not wish to define any LUs for a given PU. 29 The following snancp commands will be used to set the SNA database in the Gateway each time it is loaded. The system then displays the snancp commands in the configuration script. The script that is displayed contains both information you specified for the SNA components and default system information. 3-24 Completing the Installation: Verifying, Configuring, Loading set PU SNA-0 \ circuit SDLC-0 \ LU list 1-255 \ segment size 265 \ logging warning set circuit SDLC-0 state on set line SYN-0 state on set access name cics \ application cics17 \ data "bligh_appl" \ pu SNA-0 \ lu list 1-5 set server SNA-ACCESS \ logging warning \ note "Gateway Access Server" \ state on set server RJE \ logging warning \ note "Remote Job Entry" \ state on set server DHCF \ pu sna-0 lu list 1-3 set server DHCF \ state on \ logging warning \ note "Host Command Facility" exit #------------------------------------------------------------------- # End of file: /var/snagwy/snagateway_bounty_sna #------------------------------------------------------------------- Do you wish to redo Part 2? (y/n) [n]: 30 The script file you have created has been saved in: /var/snagwy/snagateway_bounty_sna You can edit this script file to change the configuration of the SNA database in the Gateway. Any changes you make will take effect the next time the Gateway is reloaded. Completing the Installation: Verifying, Configuring, Loading 3-25 30 Do you wish to redo Part 2? (y/n) [n]: If you answer y and press , Part 2 of the configuration is run again. You can provide different values at the prompts. Press to accept the default n. The configuration procedure continues as shown. 3-26 Completing the Installation: Verifying, Configuring, Loading ================================================================================ Part 3: Creating a script file to configure the DECnet database in the Gateway ================================================================================ Do you wish to create this script file? (y/n) [y]: 31 Privileged username? (1-16 chars ) []: netbligh 32 Privileged password? (1-16 chars) []: netbounty All questions for Part 3 have been answered. The following commands will be used to set the DECnet database in the Gateway each time it is loaded. #------------------------------------------------------------------- # Start of file: /var/snagwy/snagateway_bounty_dna # DECnet/SNA Gateway-ST V1.2, DECnet Configuration File # Created: Wed Apr 3 21:39:43 1991 by snaconfig # Host node: netsea, User: jpjones #------------------------------------------------------------------- /usr/bin/snancp <, Part 3 runs again, and you can answer the queries differently. If you press to accept the default, n, the configuration procedure proceeds to completion. 3-30 Completing the Installation: Verifying, Configuring, Loading 3.3 Loading Your Gateway This section describes how to down-line load the Gateway-ST software from the load host into the DEC MicroServer or DEC MicroServer-SP. You must complete the installation and configuration procedures before you can load the Gateway-ST software. Unlike installation and configuration, loading the software is not an optional part of the interactive installation procedure. You must load it separately as discussed in this section. You load the Gateway-ST software in one of two ways: o For the initial loading of the software, plug in the DEC MicroServer or DEC MicroServer-SP to power it up. As part of its power-up sequence, the unit requests a load of the software from the load host. o For subsequent loading of the software, issue an ncp trigger node command, an ncp load node command, or invoke either the load or trigger utility (/etc/load or /etc/trigger). Loading should take about five minutes. The time varies according to the following: o The type of CPU and disks on the load host o The amount of other work the load host is processing o The traffic on the local area network (LAN) 3.3.1 Before Loading the Gateway-ST Before attempting to load the Gateway-ST software, check the connection between the DEC MicroServer or DEC MicroServer-SP and the load host. You should enable event logging. 3.3.2 Checking the Load Host Connection Check the following items before trying to load the Gateway-ST software: o The line associated with the Ethernet circuit over which the software will be loaded must be defined and set to ON (use the ncp show line command). o The circuit on the load host must be set to ON (use the ncp show circuit command). Completing the Installation: Verifying, Configuring, Loading 3-31 o The Gateway node as defined on the load host must have the proper parameter settings. The service circuit, hardware address, load file, and dump file parameters must have correct values. Also, the service parameter must be set to ENABLED. Use the ncp show node characteristics command to check these parameters. For more information on the DECnet-ULTRIX ncp commands, see DECnet-ULTRIX NCP Command Reference. 3.3.3 Enabling Event Logging on the Load Host Managing DECnet Event Logging By default, all DECnet events are logged to the default console (/dev/console). SNA events are also sent by default to this device, and Digital recommends that you refer to the console device for event information. If you do not have a suitably configured console device, you can enable DECnet event logging to a terminal connected to the load host. ________________________ Note ________________________ To enable logging at a terminal connected to the load host, you need to be the superuser. ______________________________________________________ The following command sets up event logging at a special file for the terminal ttyp0. The events are logged in ASCII format. ncp> set logging console known events name /dev/ttyp0 For more information about DECnet event logging, refer to DECnet-ULTRIX Network Management. Managing SNA Event Logging By default, the Gateway sends all SNA-specific events to the snaevl (SNA event logger) utility on the load host, and snaevl logs them to the default console device /dev /console. You can direct the logging elsewhere if you do not have a suitably configured console device or if you wish to log SNA events somewhere else at load time. Do this by editing your SNA configuration script to include, as the first snancp command, a command like the following: set logging console name /dev/ttyp0 state on 3-32 Completing the Installation: Verifying, Configuring, Loading This command directs SNA event logging to the terminal ttyp0 as well as to the console device. (Note that you miss SNA events that are sent before the SNA configuration script is executed.) 3.3.4 Loading the Software from the Hardware Unit To initiate the loading of the Gateway software, power up the hardware unit (either the DEC MicroServer or the DEC MicroServer-SP). If the unit is already powered up, press the DUMP button. This method of loading the Gateway-ST software produces a dump file. 3.3.5 Loading the Software from a Terminal You can use variations of the ncp trigger node command, the ncp load node command, and the load and trigger utilities to start loading the Gateway software. The ncp trigger node command and the trigger utility set off a bootstrap mechanism in the DEC MicroServer or DEC MicroServer-SP. This command causes the unit to send a request-to-load message to all hosts on the Ethernet local area network. Gateway load hosts are configured to receive the message. The first load host that responds to the request-to-load message loads the Gateway image into the Gateway node. The ncp load node command and the load utility load software into the hardware unit by using the specified circuit or the circuit obtained from the DECnet database on the host where the command is issued. 3.3.5.1 Receiving Event Messages If there are no errors during loading, the load host's console displays the following DECnet/SNA event messages; the exact messages and sequence might vary: DECNET/SNA event 266.10, Logging sink state change From node aa.ssss (nodename), dd-mmm-yyyy hh:mm:ss.ss Logging sink type = monitor, Severity = informational Sink node = aa.ssss (nodename) New state = on, old state = off Completing the Installation: Verifying, Configuring, Loading 3-33 DECnet/SNA event 266.0, Gateway initialization From node aa.ssss (nodename), dd-mmm-yyyy hh:mm:ss.ss SNA gateway management, Severity = informational Started, DECnet/SNA Gateway-ST V1.2. DECnet/SNA event 266.2, Initialization message From node aa.ssss (nodename), dd-mmm-yyyy hh:mm:ss.ss SNA gateway management, Severity = informational Default node database loaded DECnet/SNA event 266.2, Initialization message From node aa.ssss (nodename), dd-mmm-yyyy hh:mm:ss.ss SNA gateway management, Severity = informational Setting gateway DECnet configuration DECnet/SNA event 266.2, Initialization message From node aa.ssss (nodename), dd-mmm-yyyy hh:mm:ss.ss SNA gateway management, Severity = informational Setting gateway SNA configuration DECNET/SNA event 256.0, Line state change From node aa.ssss (nodename), dd-mmm-yyyy hh:mm:ss.ss Line SYN-n, Severity = informational New state = on, old state = off When the software has been loaded and initialized without error, you see the following display: DECnet/SNA event 266.0, Gateway initialization From node aa.ssss (nodename), dd-mmm-yyyy hh:mm:ss.ss SNA gateway management, Severity = informational Complete, status = success When the IBM system responds to the Gateway-ST, you see the following display: DECnet/SNA event 257.0, Circuit state change From node aa.ssss (nodename), dd-mmm-yyyy hh:mm:ss.ss Circuit SDLC-0, Severity = informational New state = on, old state = on-starting If there are errors during loading, the load host's console displays (in place of the preceding messages) any errors detected during loading and Gateway-ST initialization. For a list of snancp error messages and how to recover from them, see the DECnet/SNA Gateway-CT and Gateway-ST Management manual. 3-34 Completing the Installation: Verifying, Configuring, Loading If any errors occur when loading the configuration file, the errors are reported to the DECnet/SNA event log. DECnet/SNA Gateway-CT and Gateway-ST Management lists and explains all initialization messages generated by the Gateway-ST software. If you issue an ncp trigger node command from any node on the Ethernet LAN and the Gateway node fails to start, you might try starting the load at the hardware unit (see Section 3.3.4). See the DECnet/SNA Gateway-ST Problem Solving (ULTRIX) if you need help finding the source of a failure. 3.3.5.2 Using the load and trigger Commands This section describes the syntax and use of the ncp load node and ncp trigger node commands. You can also use the ULTRIX load and trigger utilities to load your Gateway. For details, refer to the man pages for trigger and load . Issue the ncp trigger node command using the following format: ncp>trigger node node-id where node-id Identifies the name of the Gateway node The following is an example of the ncp trigger node command: ncp>trigger node snagwy ncp>trigger via dev-c physical address nn-nn-nn-nn-nn-nn where dev-c Is the Ethernet circuit id nn-nn-nn-nn- Is the Gateway Ethernet address nn-nn Issue the ncp load node command using the following format: ncp>load node node-id Completing the Installation: Verifying, Configuring, Loading 3-35 where node-id Identifies the name of the Gateway node. Issue the ncp load via command using the following format: ncp>load via dev-c physical address nn-nn-nn-nn-nn-nn where dev-c Is the Ethernet circuit id nn-nn-nn-nn- Is the Gateway Ethernet address nn-nn Use the ncp tell command to obtain the Ethernet address of the Gateway: ncp>tell gateway_node_name show executor status When you issue a command, any information needed to load the software (such as the circuit to be used and the name of the files being loaded) but not specified on the command line is taken from the DECnet database of the load host. 3.3.6 Checking the Gateway Node to Load Host Connection When you have successfully loaded the Gateway-ST software, you should check the connection between the Gateway node and the load host. When the Gateway node boots, verify that the link from the load host to DECnet is working properly, as follows: 1. Verify that the load host can communicate with the Gateway node, by issuing the ncp set executor node command with the Gateway node ID. If you get an error message after entering this command, see the DECnet/SNA Gateway-ST Problem Solving (ULTRIX) manual for help. 2. Check the results of the ncp set executor node command with the following command: ncp>show executor status If you get an error message after this command, see the chapter Configuring the Gateway in the manual DECnet /SNA Gateway-ST Problem Solving (ULTRIX). Also, check the DECnet/SNA event log for a message showing circuit activity with the DECnet node since the Gateway-ST was booted. 3-36 Completing the Installation: Verifying, Configuring, Loading Refer to the DECnet-ULTRIX Network Management and the DECnet-ULTRIX NCP Command Reference for further details on connections within a DECnet network. Completing the Installation: Verifying, Configuring, Loading 3-37 A _________________________________________________________________ Files Installed on Your System Table_A-1_Installed_DECnet/SNA_Gateway-ST_Files__________________ Pathname________________________Description______________________ /usr/lib/snagwy/snacst120.sys Gateway-ST image /usr/lib/snagwy Gateway-ST release notes /snacst120.release_notes /usr/lib/snagwy/snancp.hlbu snancp help text /usr/lib/snagwy/snatrace_ snatrace EBCDIC/DMCS tratbl translation table /usr/lib/snagwy/msg394.plib snancp message file /usr/lib/snagwy/msg395.plib snaevl message file /usr/lib/snagwy/msg516.plib snatrace message file /usr/lib/snagwy/bin/snatrace tracing utility /usr/lib/snagwy/bin/snancp SNA Network Control Program /usr/lib/snagwy/bin/snap resource utilization monitor /usr/bin/snatrace link to snatrace /usr/bin/snap link to snap /usr/bin/snancp link to snancp (continued on next page) Files Installed on Your System A-1 Table_A-1_(Cont.)_Installed_DECnet/SNA_Gateway-ST_Files__________ Pathname________________________Description______________________ /usr/lib/snagwy/etc/snaevl event logging utility /usr/lib/snagwy/etc/snaconfig configuration utility /usr/lib/snagwy/etc/snaini gateway initialization procedure /usr/etc/snaconfig link to snaconfig /usr/etc/snaevl link to snaevl /usr/etc/snaini_________________link_to_snaini___________________ A-2 Files Installed on Your System B _________________________________________________________________ Sample Listings for Installation and Verification This appendix provides these sample listings: o An installation from tape media (without IVPs) of all the Gateway-ST subsets on a VAX/ULTRIX system. It is assumed that Gateway-ST has not been installed on the system earlier. o The Installation Verification Procedure (IVP) for the Gateway-ST gateway management software o The Installation Verification Procedure (IVP) for the Gateway-ST base software (the Gateway image) B.1 Installation of DECnet/SNA Gateway-ST on a VAX/ULTRIX System Using Tape Media These notes apply to this section: o Installation from a disk can generate a different order in the subset lists, and corresponding differences in system output and queries. o If you choose to install a single subset, the system output and queries differ from those shown. o The installation listing does not include Gateway- ST configuration. Chapter 3 has a listing of the configuration procedure. # cd / # setld -l /dev/rmt0h Sample Listings for Installation and Verification B-1 *** Enter Subset Selections *** The subsets listed below are optional: 1) DECnet/SNA Gateway Management 2) DECnet/SNA Gateway-ST Base Software 3) DECnet/SNA Gateway Mgmt Man Pages 4) All of the Above 5) None of the Above 6) Exit without installing subsets Enter your choice(s): 4 You are installing the following subsets: DECnet/SNA Gateway Management DECnet/SNA Gateway-ST Base Software DECnet/SNA Gateway Mgmt Man Pages Is this correct? (y/n): y Copying DECnet/SNA Gateway Management (CTVGM100) from tape Verifying DECnet/SNA Gateway Management (CTVGM100) Copying DECnet/SNA Gateway-ST Base Software (SYVBASE120) from tape Verifying DECnet/SNA Gateway-ST Base Software (SYVBASE120) Copying DECnet/SNA Gateway Mgmt Man Pages (CTVMAN100) from tape Verifying DECnet/SNA Gateway Mgmt Man Pages (CTVMAN100) Beginning DECnet/SNA Gateway Management Installation © Digital Equipment Corporation. 1991. All Rights Reserved. The procedure now prompts you to run the IVP as part of this installation. However, you may also invoke the IVP at any time by executing the command: setld -v CTVGM100 Do you wish to run the IVP for DECnet/SNA Gateway Management? (y/n) [y]: n Ending DECnet/SNA Gateway Management installation with success. Beginning DECnet/SNA Gateway-ST V1.2 Base Software installation © Digital Equipment Corporation. 1991. All Rights Reserved. The procedure now prompts you to run the IVP as part of this installation. However, you can also invoke the IVP at any time by executing the command: setld -v STVBASE120 Do you want to run the IVP for DECnet/SNA Gateway-ST? (y/n) [y]: n Ending DECnet/SNA Gateway-ST Base Software V1.2 installation with success. Do you wish to configure your DECnet/SNA Gateway-ST node? (y/n) [y]: n B-2 Sample Listings for Installation and Verification If you decide to configure the Gateway-ST node later, execute the following command: /usr/etc/snaconfig st Beginning DECnet/SNA Gateway Management Man Pages V1.0 installation © Digital Equipment Corporation. 1991. All Rights Reserved. Ending DECnet/SNA Gateway Management Man Pages V1.0 installation with success. B.2 Installation Verification for DECnet/SNA Gateway-ST on a VAX/ULTRIX System B.2.1 IVP for Gateway Management Subset # setld -v CTVGM100 Beginning DECnet/SNA Gateway Management IVP. This IVP checks that the required files have been correctly installed from the kit and that the management utilities are functioning properly. Files ok... snaini ok... snaconfig ok... snap ok... snancp ok... snatrace ok... Ending DECnet/SNA Gateway Management V1.0 IVP with success. B.2.2 IVP for Base Software Subset # setld -v STVBASE120 Beginning DECnet/SNA Gateway-ST V1.2 IVP. This IVP checks that the required files have been correctly installed from the kit, that the proxy authorization file dnet_proxy exists, and that the directory /var/snagwy exists for creating DECnet/SNA Gateway-ST configuration files. Files ok... Proxy file ok... Directory ok... Sample Listings for Installation and Verification B-3 Ending DECnet/SNA Gateway- ST Base Software V1.2 IVP with success. B-4 Sample Listings for Installation and Verification _________________________________________________________________ Index A Configuring the Gateway-ST _______________________________ (cont'd) Access names, 3-21 load host Ethernet circuit Adapter cables, 1-8 name, 3-5 logon mode name, 3-21 B______________________________ LU lists, 3-21 Base software, 2-3 modem types, 3-15 password for Gateway-ST C______________________________ functions, 3-29 Configuring the Gateway-ST, PU names, 3-21 3-2 script files created, 3-2 access names, 3-21 servers, 3-24 DECnet node address for signaling convention for Gateway node, 3-5 lines, 3-15 directory for dump file, 3-5 station address for circuits, duplex mode for circuits, 3-15 3-18 station identifier for duplex mode for lines, 3-13 circuits, 3-18 Ethernet address of Gateway understanding snaconfig, 3-2 node, 3-5 D extended response mode for _______________________________ circuits, 3-15 DEC MicroServer IBM application name, 3-21 available data speeds for, IBM user data, 3-21 1-7 line buffer size, 3-15 DEC MicroServer-SP lines to be configured, 3-13 available data speeds for, list of LU addresses, 3-18 1-6 Index-1 DECnet environment Event checking load host Ethernet logging, 3-32 circuit, 1-10 messages, 3-33 checking load host Ethernet line, 1-10 F______________________________ preparing for Gateway-ST Files created during installation, 1-10 installation, A-1 DECnet event logging, 3-32 DECnet node address for G Gateway node, 3-5 _______________________________ Disk space requirements Gateway connection to load for installation, 1-13 host RISC/ULTRIX systems, 1-13 checking, 3-36 VAX/ULTRIX systems, 1-13 Gateway management subset, DMS server 1-12 checking disk space for Gateway node installation, 1-15 checking connection to load installing Gateway-ST host, 3-36 software into, 1-3, 2-6 configuration file Dump file directory on load specification, 3-2 host, 3-5 Gateway-ST Duplex mode for Gateway-ST files created during circuits, 3-18 installation, A-1 Duplex mode for Gateway-ST gateway management software, lines, 3-13 1-12 gateway management subset, E______________________________ 2-3 Error recovery image, 1-12, 2-3 during installation, 1-17, man pages, 1-12, 2-3 2-5 Gateway-ST subsets Ethernet contents of, A-1 connecting the Gateway to, descriptions, 1-12 disk space requirements, 1-13 1-6, 1-8 order of installation, 2-4 Ethernet circuit name of load selecting during installation host, 3-5 , 2-3 Ethernet hardware address of verifying installation of, Gateway, 3-5 3-1 Index-2 Installing the Gateway-ST H______________________________ (cont'd) Hardware requirements for disk space requirements, 1-13 installation, 1-6 error recovery, 1-17, 2-5 adapter cables, 1-8 from an RIS server, 1-2, 2-2 checking for software from tape media, 2-2 distribution device, 1-9 hardware requirements, 1-6 checking the terminal at the increasing disk space, 1-16 load host, 1-9 into a DMS server, 1-3, 2-6 connecting the Gateway to the into an RIS server, 1-2, 2-8 DECnet network, 1-6 on a local node, 2-1 connecting the Gateway to the on local node versus DMS Ethernet, 1-6 server, 1-3 using modems, 1-8 preparing the DECnet environment, 1-10 I preparing the IBM environment _______________________________ , 1-9 IBM application name, 3-21 privileges required, 1-6 IBM environment required preinstallation preparing for Gateway-ST ULTRIX software, 1-11 installation, 1-9 sample listing, B-1 IBM logon mode name, 3-21 screen displays during IBM user data, 3-21 installation, 2-4 image selecting subsets, 2-3 see also Base software software requirements, 1-9 Image, 1-12 stopping the installation, Installation Verification 1-16 Procedures subsets available, 1-12 see IVPs time required, 1-5 Installing the Gateway-ST, 2-1 IVPs backing up your system disk, definition, 3-1 1-16 running, 3-1 checking disk space on DMS sample listings, B-3 server, 1-15 checking disk space on local node, 1-14 connecting the Gateway to the SNA network, 1-6 Index-3 L______________________________ P______________________________ License PAK Password for Gateway-ST registering, 1-4 functions, 3-29 Line buffer size for Gateway- Privilege requirements for ST, 3-15 Gateway-ST installation, 1-6 Lines on Gateway node to be PU names, 3-21 configured, 3-13 Loading the Gateway-ST, 3-31 R______________________________ checking the load host Registration connection, 3-31 of License PAK, 1-4 DECnet event logging, 3-32 Release notes, 1-2 enabling event logging, 3-32 RIS client event messages, 3-33 local node as, 2-2 from a terminal, 3-33 RIS server from the hardware unit, 3-31, installing Gateway-ST from, 3-33 1-2, 2-2 load utility, 3-31, 3-33 installing Gateway-ST ncp load node command, 3-31, software on, 1-2, 2-8 3-33, 3-35 ncp trigger node command, S 3-31, 3-33, 3-35 _______________________________ SNA event logging, 3-32 Server trigger utility, 3-31, 3-33 DHCF, 3-24 Local node RJE, 3-24 installation on, 2-1 SNA-ACCESS, 3-24 installing on, compared with Signaling convention for DMS server, 1-3 Gateway-ST lines, 3-15 LU lists, 3-21 snaconfig overview of, 3-2 M______________________________ sample dialogue, 3-3 man pages, 1-12 script files created, 3-29 Modems, 1-8 script files created by, 3-2, types of, 3-15 3-8, 3-13 using to configure Gateway-ST , 3-3 SNA event logging, 3-32 SNA network Index-4 SNA network (cont'd) System disk connecting the Gateway to, backing up before 1-6 installation, 1-16 Software distribution kit checking, 1-5 T______________________________ Software requirements for Tape media installation, 1-9 installation from, 2-2 Station address for Gateway-ST Time requirements circuits, 3-15 for Gateway-ST installation, Station identifier for 1-5 Gateway-ST circuits, 3-18 Stopping the installation, V______________________________ 1-16 Verifying Gateway-ST Subsets installation, 3-1 see Gateway-ST subsets see also IVPs Index-5