WAN_Support_for_DIGITAL_UNIX_Systems________________ Installation Guide Order Number: AA-PR2KG-TE May 1997 This document contains instructions for installing WAN Support for DIGITAL UNIX Systems[R], V3.0. The operating system required is DIGITAL UNIX[R], V4.0. Revision/Update Information: This revised manual supersedes Part Number AA-PR2KF-TE. Operating System and Version: DIGITAL UNIX, V4.0. Software Version: V3.0. Digital Equipment Corporation Maynard, Massachusetts ________________________________________________________________ First Printing March 1993 Revision May 1997 Digital Equipment Corporation makes no representations that the use of its products in the manner described in this publication will not infringe on existing or future patent rights, nor do the descriptions contained in this publication imply the granting of licenses to make, use, or sell equipment or software in accordance with the description. Possession, use, or copying of the software described in this publication is authorized only pursuant to a valid written license from Digital or an authorized sublicensor. © Digital Equipment Corporation 1993 All Rights Reserved Printed in United States of America The postpaid Reader's Comments forms at the end of this document request your critical evaluation to assist in preparing future documentation. The following are trademarks of Digital Equipment Corporation: DEC, DECnet, DECnet-DOS, DECserver, DECstation, DECsupport, DECsystem, DECUS, DECwindows, DNA, LAT, MUXserver, OpenVMS, PDP, Q-bus, TURBOchannel, ULTRIX, UNIBUS, VAX, VAXcluster, VAXstation, VMS, VT, XUI, and the DIGITAL logo. The following are third party trademarks: OSF/1 is a registered trademark of Open Software Foundation, Inc. PostScript is a registered trademark of Adobe Systems Incorporated. UNIX is a registered trademark in the United States and other countries, licensed exclusively through X/Open Company Ltd. This document is available on CDROM. This document was prepared using VAX DOCUMENT Version 2.1. _________________________________________________________________ Contents Preface................................................... vii 1 Preparing for WAN Support for DIGITAL UNIX Installation 1.1 Product Documentation......................... 1-1 1.2 Verifying the Media Software Distribution Kit........................................... 1-1 1.3 Backing Up Your System Disk................... 1-2 1.4 License Registration.......................... 1-3 1.5 Installation Procedure Requirements........... 1-4 1.5.1 Installation Time......................... 1-4 1.5.2 Login Privileges.......................... 1-4 1.5.3 Prerequisite Software..................... 1-4 1.5.4 Prerequisite Hardware..................... 1-4 1.5.5 Disk Space Requirements................... 1-5 1.6 Number of Pseudoterminal Devices.............. 1-5 1.7 Old Versions.................................. 1-5 1.8 Partial Installations......................... 1-6 2 Installing WAN Support for DIGITAL UNIX Systems 2.1 Required Subsets.............................. 2-1 2.2 Installing WAN Support for DIGITAL UNIX....... 2-4 2.2.1 Starting the Installation Script.......... 2-4 2.2.2 Responding to Installation Script Prompts................................... 2-5 2.2.3 Example Prompt and Response Sequence-AlphaServer 4100 Systems......... 2-5 2.2.4 Stopping the Installation................. 2-13 2.2.5 Running the WANDD Installation Verification Procedure.................... 2-14 2.2.6 Configuring the System.................... 2-14 2.3 Deinstalling Subsets.......................... 2-14 iii 3 Postinstallation Tasks 3.1 Verifying Your X.25 Network................... 3-1 3.2 Determining and Reporting Problems............ 3-2 A Disk Space Requirements B Subsets C Installation Verification Procedure C.1 Overview of the Installation Verification Procedure..................................... C-2 C.2 Running the Installation Verification Procedure..................................... C-7 C.3 Error Conditions.............................. C-7 D Installing DECnet Over HDLC D.1 Installation Procedure........................ D-1 D.2 Performance Tradeoffs Available to the User... D-3 D.2.1 Window Size............................... D-3 D.2.2 Data Buffers.............................. D-3 D.2.3 Number of Retries......................... D-4 D.2.4 Frame Acknowledgement..................... D-5 D.2.5 Acknowledge Timer......................... D-6 E Installing Without Datalink Protocols E.1 Installation Procedure........................ E-1 F Device-Specific Information F.1 Driver Information............................ F-1 F.1.1 SCC Device Driver......................... F-1 F.1.2 DSYT1 Device Driver....................... F-1 F.1.3 DNSES Device Driver....................... F-1 F.1.4 PBXDI and PBXDP Device Drivers............ F-1 F.1.5 DIGITAL 3000 ISDN Device Driver (BBA)..... F-2 iv G PBXDI ISA Synchronous Communications Adapter G.1 Introduction.................................. G-1 G.1.1 Supported Interface Types on PBXDI Card... G-1 G.1.2 Configuration............................. G-1 G.2 Installation of PBXDI-Ax Cards................ G-2 H Example of Null Modem Cable Wiring H.1 RS-232 Null Modem Cable with Clock Available at Both Ends.................................. H-1 H.2 RS-232 Null Modem Cable with Clock Available Only at One End............................... H-2 I Error Recovery I.1 Recovery Procedure............................ I-1 I.2 Error Messages................................ I-2 Index Figures C-1 Driver Loopback Test...................... C-2 C-2 Device Loopback Test...................... C-3 C-3 Local Loopback Test....................... C-4 C-4 Remote Loopback Test...................... C-5 C-5 HDLC/LAPB Loopback Test (to local modem).................................... C-6 Tables 2-1 Required Subsets.......................... 2-2 A-1 Worksheet for Subset Sizes (Kilobytes Required) ................................ A-1 B-1 Subset Interdependencies.................. B-3 v _________________________________________________________________ Preface This guide describes how to install WAN Support for DIGITAL UNIX Systems[R] software on an Alpha processor that is running the DIGITAL UNIX operating system. The guide includes information on installing the X.25 and ISDN components included in the product WAN Support for DIGITAL UNIX Systems. Keep this document with your distribution kit. You will need it to install maintenance updates or to reinstall WAN Support for DIGITAL UNIX Systems. Throughout the rest of this guide, WAN Support for DIGITAL UNIX Systems is referred to as WAN Support for DIGITAL UNIX. This reference includes the ISDN components of the product. Audience This guide is for use by anyone who wan ts to install WAN Support for DIGITAL UNIX software on a DIGITAL UNIX Alpha system, to install the ISDN components of WAN Support for DIGITAL UNIX, or to install DIGITAL UNIX over HDLC. Typically, this person will be a system manager. Structure of this Guide This guide comprises three chapters and a number of appendices: o Chapter 1, Preparing for WAN Support for DIGITAL UNIX Installation, describes the operating system, hardware, and disk requirements for WAN Support for DIGITAL UNIX installation. vii o Chapter 2, Installing WAN Support for DIGITAL UNIX Systems, describes the installation procedure and includes an annotated example prompt and response sequence. o Chapter 3, Postinstallation Tasks, describes the postinstallation tasks that should be performed. o Appendix A, Disk Space Requirements, provides a detailed breakdown of the disk space required for each of the subsets available in the WAN Support for DIGITAL UNIX kit. o Appendix B, Subsets, describes each of the subsets and details the interdependencies between those subsets. o Appendix C, Installation Verification Procedure, details how to run the Installation Verification Procedure. o Appendix D, Installing DECnet Over HDLC, details how to perform the installation of the HDLC component of WAN Support for DIGITAL UNIX if you want to run DECnet over HDLC. o Appendix E, Installing Without Datalink Protocols, details how to perform the installation of the WDD Synchronous Device Drivers component of WAN Support for DIGITAL UNIX if you intend to use an alternative DIGITAL layered product that provides its own datalink protocols. o Appendix F, Device-Specific Information, provides information about the drivers supported by WAN Support for DIGITAL UNIX. o Appendix H, Example of Null Modem Cable Wiring details how to construct a null modem cable. o Appendix I, Error Recovery, explains how to recover from errors that have occurred during the installation and provides a list of the error messages. At the end of this guide are two Reader's Comments forms. If you have any suggestions or criticisms that you think would improve this guide, please fill out one of the forms and return it to DIGITAL. viii Associated Documentation Product Documentation The following manuals from the WAN Support for DIGITAL UNIX Systems documentation set may be useful to the system manager: o WAN Support for DIGITAL UNIX Systems- Introduction This manual provides general information on the product and describes the concept of packet switching data networks. o WAN Support for DIGITAL UNIX Systems- Configuration Guide This guide explains how to configure the product. o WAN Support for DIGITAL UNIX Systems- Management Guide This guide describes how to manage and monitor an X.25 system, and details the tools provided to administer an X.25 system. o WAN Support for DIGITAL UNIX Systems- ISDN User's Guide- DEC 3000 Systems This guide describes how to configure, manage, and monitor ISDN, and details the tools provided to administer an ISDN system. NCL Information Information on Network Control Language (NCL), which is used to manage a WAN Support for DIGITAL UNIX network, is provided in the following manual: o DECnet/OSI for DIGITAL UNIX Systems- Network Control Language Reference Manual Conventions The following conventions are used in this guide: ix UPPERCASE and The DIGITAL UNIX operating system lowercase differentiates between lowercase and uppercase characters. Literal strings that appear in text, examples, syntax descriptions, and function descriptions must be typed exactly as shown. user input In interactive examples, user input is shown in bold print. system output This typeface is used in interactive and code examples to indicate system output. In text, this typeface is used to indicate the exact name of a command, option, partition, pathname, directory, or file. % In this guide, a percent sign (%) is used to represent the user prompt while using the system's root account. # A number sign is the default superuser prompt. In procedures, a sequence such as indicates that you must hold down the key labelled Ctrl while you press another key or a pointing device button. In procedures, a key name is shown enclosed to indicate that you press the corresponding key on the keyboard. x 1 _________________________________________________________________ Preparing for WAN Support for DIGITAL UNIX Installation This chapter provides information that you need to be aware of or consider before attempting to install WAN Support for DIGITAL UNIX. This information includes how to determine whether the system on which you intend to install WAN Support for DIGITAL UNIX meets the product requirements for hardware, software, and disk space. 1.1 Product Documentation Release Notes are provided as part of the WAN Support for DIGITAL UNIX software kit. DIGITAL strongly recommends that you read the Release Notes before attempting to install the product. The Release Notes contain information about undocumented features and alterations to the information provided in the WAN Support for DIGITAL UNIX documentation set. The Release Notes are provided on the DIGITAL UNIX Software Product Library CD-ROM in PostScript (.ps) and text (.txt) format in the directory /XXA300/documentation. The Release Notes are also supplied on the DIGITAL UNIX Online Documentation Library CD-ROM together with all other WAN Support for DIGITAL UNIX documentation. 1.2 Verifying the Media Software Distribution Kit The Bill of Materials details the content of your software distribution kit. The kit should include: o The DIGITAL UNIX Software Product Library CD-ROM; and o The DIGITAL UNIX Online Documentation Library CD-ROM. Both disks are suitable for use in the CD Reader supplied with your Alpha system. Preparing for WAN Support for DIGITAL UNIX Installation 1-1 Preparing for WAN Support for DIGITAL UNIX Installation 1.2 Verifying the Media Software Distribution Kit If the content of the kit does not match the list of items on the Bill of Materials, please contact your DIGITAL support representative. 1.3 Backing Up Your System Disk DIGITAL recommends that you back up your system disk before installing any software. Use the backup procedures that are established at your site. 1-2 Preparing for WAN Support for DIGITAL UNIX Installation Preparing for WAN Support for DIGITAL UNIX Installation 1.4 License Registration 1.4 License Registration To use WAN Support for DIGITAL UNIX, either one or two License Product Authorization Keys (License PAKs) must be registered in the License Database (LDB). There are two separate License PAKs. If you intend to use IP over ISDN, then you will need the ISDN License PAK or the X.25 License PAK. If you intend to use X.25 over a Wide Area Network, a Local Area Network, or over ISDN, then you will need the X.25 License PAK. The License PAKs may have been shipped with the kit if you ordered the license and media together, or shipped separately to a location based on your license order. If you are installing WAN Support for DIGITAL UNIX as an update on a node already licensed for this software, you have already completed the License PAK registration requirements. If you are installing WAN Support for DIGITAL UNIX for the first time, you should register at least one License PAK. To register a license under DIGITAL UNIX: 1. Log in as superuser. 2. Register the License PAK in the License Database (LDB). To do this: a. Edit an empty PAK template by entering the following command: # lmf register b. Enter the information supplied in your License PAK. c. Save the PAK and exit the license registration utility. 3. Activate the license database by issuing the command: # lmf reset This action causes the DIGITAL UNIX License Management Facility (LMF) to process the new registration. For complete information on using the DIGITAL UNIX License Management Facility, refer to the DIGITAL UNIX Guide to Software Licensing or the lmf(8) reference page. Preparing for WAN Support for DIGITAL UNIX Installation 1-3 Preparing for WAN Support for DIGITAL UNIX Installation 1.5 Installation Procedure Requirements 1.5 Installation Procedure Requirements This section discusses various requirements for installing WAN Support for DIGITAL UNIX. 1.5.1 Installation Time The installation and configuration of WAN Support for DIGITAL UNIX takes approximately 20 to 30 minutes depending on the complexity of your system configuration. If you want to install and configure only the ISDN component, you should allow approximately 15 minutes. 1.5.2 Login Privileges To install WAN Support for DIGITAL UNIX, you must have superuser privileges on the system where you intend to install the product. 1.5.3 Prerequisite Software The operating system required is DIGITAL UNIX V4.0. Refer to Appendix B for details of the subsets that must be present before installing the required WAN Support for DIGITAL UNIX subsets. 1.5.4 Prerequisite Hardware To perform the installation you need the following hardware: o A CD Reader; and o A terminal. You can use either a hardcopy or video terminal to communicate with the operating system and respond to prompts from the installation procedure for WAN Support for DIGITAL UNIX. 1-4 Preparing for WAN Support for DIGITAL UNIX Installation Preparing for WAN Support for DIGITAL UNIX Installation 1.5 Installation Procedure Requirements 1.5.5 Disk Space Requirements To install the full set of available WAN Support for DIGITAL UNIX subsets, the total disk space required is 83,794 Kb. This space is divided as follows: ___________________________________________________________ File_System______Space_(Kb)________________________________ /opt 400 /usr 61,412 /var_____________21,982____________________________________ If there is not enough space in a file system for WAN Support for DIGITAL UNIX files, you must increase the size of the partition that that file system occupies. If you do not intend to install all of the subsets, refer to the disk space worksheet given in Appendix A. The worksheet allows you to calculate how much disk space is required for any combination of subsets. 1.6 Number of Pseudoterminal Devices If you intend to use WAN Support for DIGITAL UNIX to handle incoming X.29 calls, you should consider increasing the number of pseudoterminal devices (ptys) configured on your system. This is because X.29 logins compete with rlogins and dlogins for the available ptys. Increasing the number of ptys will therefore reduce the possibility of exhausting the ptys used for incoming access. The DIGITAL UNIX System Administration Guide describes how to change the number of configured ptys. 1.7 Old Versions Deinstall old versions of the subsets, if any exist. See Section 2.3 for details. Preparing for WAN Support for DIGITAL UNIX Installation 1-5 Preparing for WAN Support for DIGITAL UNIX Installation 1.8 Partial Installations 1.8 Partial Installations You do not have to install the full set of available WAN Support for DIGITAL UNIX subsets. Refer to Section 2.1 for the required subsets for a variety of typical configurations. For example, if you intend to run DECnet /OSI for DIGITAL UNIX Systems over HDLC, you do not need to install the X.25 subsets. Details of subset interdependencies are provided in Appendix B. Examples of how to perform partial installations are provided in the following appendices: o Appendix D details how to perform the installation of the HDLC component of WAN Support for DIGITAL UNIX if you want to run DECnet/OSI for DIGITAL UNIX Systems over HDLC. o Appendix E details how to install the WDD Synchronous Device Drivers component of WAN Support for DIGITAL UNIX if you intend to use an alternative DIGITAL layered product that provides its own datalink protocols. 1-6 Preparing for WAN Support for DIGITAL UNIX Installation 2 _________________________________________________________________ Installing WAN Support for DIGITAL UNIX Systems This chapter describes how to: o Install WAN Support for DIGITAL UNIX; and o Deinstall WAN Support for DIGITAL UNIX subsets. 2.1 Required Subsets WAN Support for DIGITAL UNIX Systems is a large product providing considerable functionality for communications over local and wide area networks. Table 2-1 shows the subsets required to install some typical configurations of WAN Support for DIGITAL UNIX Systems. The subsets required to install each configuration are listed under the appropriate column heading. Entries in the column are either marked "m" for mandatory, "s" for selective, or "o" for optional, or are unmarked if the subset is not relevant to the configuration. At least one of the options marked "s" must be installed in each configuration. Column headings are as follows: o Column 1-X.25 over WAN o Column 2-X.25 over LAN o Column 3-X.25 over ISDN o Column 4-X.25 Relay over LAN or WAN o Column 5-TCP/IP over X.25 o Column 6-TCP/IP over ISDN o Column 7-DECnet over HDLC o Column 8-DECnet over X.25 Installing WAN Support for DIGITAL UNIX Systems 2-1 Installing WAN Support for DIGITAL UNIX Systems 2.1 Required Subsets Table_2-1_Required_Subsets_______________________________________ X25 IP IP DN DN Subset_____________X25WAN__X25LAN_/ISDN__X25RLY_/X25___/ISDN__/HDLC /X25 DECnet/OSI m m m m m m m m Network Management (DNANETMAN401) DECnet m m m m m m m m /OSI Kernel Components (DNAKBIN401) WAN Utilities m m m m m m m m Base (ZZAUTIL301) WDD Base m m m m m m m Component (WDABASE300) WDD Synchronous m m s s m s Device Drivers (WDADRIVERS300) WDD Datalink m m m m m m m Protocols (WDADATALNKS300) WDD Example o o o o o o o Programs (WDAEXAMPLES300) WDD Manual Pages o o o o o o o (WDAMAN300) X.25 Base m m m m m m Component (XXAACC300) X.25 IP Support m (XXAIP300) (continued on next page) 2-2 Installing WAN Support for DIGITAL UNIX Systems Installing WAN Support for DIGITAL UNIX Systems 2.1 Required Subsets Table_2-1_(Cont.)_Required_Subsets_______________________________ X25 IP IP DN DN Subset_____________X25WAN__X25LAN_/ISDN__X25RLY_/X25___/ISDN__/HDLC /X25 X.25 Manual o o o o o Pages (XXAMAN300) X.25 Relay m (XXARLY300) X.25 Example o o o o o Programs (XXAEXAMPLES300) DIGITAL UNIX m m ISDN Base Components (ISDBASE300) DIGITAL UNIX m m ISDN Driver Components for DEC 3000 (ISDBASE300) CTF Collector m m m m m m m m Components (CTABASE301) CTF User o o o o o o o o Environment (CTAANAL301)_____________________________________________________ Installing WAN Support for DIGITAL UNIX Systems 2-3 Installing WAN Support for DIGITAL UNIX Systems 2.2 Installing WAN Support for DIGITAL UNIX 2.2 Installing WAN Support for DIGITAL UNIX Before you attempt to install the product, it is recommended that you read Chapter 1, which contains details of preparatory tasks that you should complete before installing the product. This section provides details on: o How to install WAN Support for DIGITAL UNIX; o How to respond to installation script prompts; o How to stop the installation script; o How to run the Installation Verification Procedure (IVP); and o How to configure WAN Support for DIGITAL UNIX. 2.2.1 Starting the Installation Script The WAN Support for DIGITAL UNIX software is supplied on the DIGITAL UNIX Software Product Library CD-ROM in the /XXA300/kit directory. To install WAN Support for DIGITAL UNIX: 1. Load the Software Product Library CD-ROM into the CD Reader. 2. Log in as superuser on the system where you want to install WAN Support for DIGITAL UNIX. 3. Mount the CD-ROM filesystem. For example, if the CD Reader device is rz1c and the mount point is /mnt, enter the following command: # mount -r /dev/rz1c /mnt 4. Invoke setld to load the subsets. Enter the command: # setld -l mount-point/XXA300/kit For example: # setld -l /mnt/XXA300/kit To install WAN Support for DIGITAL UNIX over the network: 1. Set up a RIS area on the host machine. 2. Log in as superuser on the system where you want to install WAN Support for DIGITAL UNIX. 2-4 Installing WAN Support for DIGITAL UNIX Systems Installing WAN Support for DIGITAL UNIX Systems 2.2 Installing WAN Support for DIGITAL UNIX 3. Invoke setld to load the subsets. Enter the command: # setld -l host-name: The remainder of the installation procedure is detailed in the installation scripts. Annotated examples showing prompt and response sequences are shown in the following sections. 2.2.2 Responding to Installation Script Prompts Whenever an installation script requires data to be entered, the script prompts for that information by displaying a question and then waits for you to enter a response. To enter a response, key in the requested data and then press . At the end of each question is a value or setting in square brackets, "[value]", that indicates the default value or setting that is used if you press without entering any data in response to that prompt. In general, the default value is the most common value or setting. If you enter an invalid response to a question, an error message is displayed indicating the reason for the error. When the installation script is complete, the message No more questions is displayed and control is returned to the operating system. 2.2.3 Example Prompt and Response Sequence-AlphaServer 4100 Systems This section provides an annotated example that shows the prompt and response sequence displayed when the installation script is run to install all the available subsets on an AlphaServer 4100 system. In this example, numbered callouts (1, 2, 3, . . . ) are used to indicate parts of the prompt and response sequence for which additional explanatory notes are provided. These notes are given at the end of the example. Installing WAN Support for DIGITAL UNIX Systems 2-5 Installing WAN Support for DIGITAL UNIX Systems 2.2 Installing WAN Support for DIGITAL UNIX # setld -l /mnt/XX3300/kit 1 The subsets listed below are optional: There may be more optional subsets than can be presented on a single screen. If this is the case, you can choose subsets screen by screen or all at once on the last screen. All of the choices you make will be collected for your confirmation before any subsets are installed. - Common Trace Facility Components: 1) CTF Collector Components 2) CTF User Environment - DECnet/OSI Standard Run-time Environment: 3) DECnet/OSI Kernel Components 4) DECnet/OSI Network Management --- MORE TO FOLLOW --- Enter your choices or press RETURN to display the next screen. Choices (for example, 1 2 4-6): 2 - Optional DECnet/OSI Components: 5) DECnet/OSI Network Management GUI - WAN Device Drivers and Datalinks Components: 6) WDD Base Component 7) WDD Datalink Protocols 8) WDD Example Programs 9) WDD Manual Pages 10) WDD Synchronous Device Drivers - WAN Support Utilities Components: 11) ROAMABOUT Transport Server Support 12) WAN Kernel Programming Tools 13) WAN Utilities Base --- MORE TO FOLLOW --- Enter your choices or press RETURN to display the next screen. Choices (for example, 1 2 4-6): - X.25 for Digital UNIX Components: 14) X.25 Base Component 15) X.25 Example Programs 16) X.25 IP Support 17) X.25 Manual Pages 18) X.25 Relay Or you may choose one of the following options: 2-6 Installing WAN Support for DIGITAL UNIX Systems Installing WAN Support for DIGITAL UNIX Systems 2.2 Installing WAN Support for DIGITAL UNIX 19) ALL of the above 20) CANCEL selections and redisplay menus 21) EXIT without installing any subsets Enter your choices or press RETURN to redisplay menus. Choices (for example, 1 2 4-6): You are installing the following optional subsets: - Common Trace Facility Components: CTF Collector Components CTF User Environment - DECnet/OSI Standard Run-time Environment: DECnet/OSI Kernel Components DECnet/OSI Network Management - Optional DECnet/OSI Components: DECnet/OSI Network Management GUI - WAN Device Drivers and Datalinks Components: WDD Base Component WDD Datalink Protocols WDD Example Programs WDD Manual Pages Press RETURN to display the next screen: WDD Synchronous Device Drivers - WAN Support Utilities Components: ROAMABOUT Transport Server Support WAN Kernel Programming Tools WAN Utilities Base - X.25 for Digital UNIX Components: X.25 Base Component X.25 Example Programs X.25 IP Support X.25 Manual Pages X.25 Relay Is this correct? (y/n): 3 Checking file system space required to install selected subsets: File system space checked OK. 18 subset(s) will be installed. Loading 1 of 18 subset(s).... Copyright (c) Digital Equipment Corporation. 1993-1997. All Rights Reserved. Installing WAN Support for DIGITAL UNIX Systems 2-7 Installing WAN Support for DIGITAL UNIX Systems 2.2 Installing WAN Support for DIGITAL UNIX WAN Kernel Programming Tools 4 Copying from /mnt/XX3300/kit (disk) Verifying Loading 2 of 18 subset(s).... Copyright (c) Digital Equipment Corporation. 1993-1997. All Rights Reserved. WAN Utilities Base Copying from /mnt/XX3300/kit (disk) Verifying Loading 3 of 18 subset(s).... Copyright (c) Digital Equipment Corporation. 1993-1997. All Rights Reserved. X.25 Base Component Copying from /mnt/XX3300/kit (disk) Verifying Loading 4 of 18 subset(s).... Copyright (c) Digital Equipment Corporation. 1993-1997. All Rights Reserved. X.25 IP Support Copying from /mnt/XX3300/kit (disk) Verifying Loading 5 of 18 subset(s).... Copyright (c) Digital Equipment Corporation. 1993-1997. All Rights Reserved. X.25 Relay Copying from /mnt/XX3300/kit (disk) Verifying Loading 6 of 18 subset(s).... Copyright (c) Digital Equipment Corporation. 1993-1997. All Rights Reserved. ROAMABOUT Transport Server Support Copying from /mnt/XX3300/kit (disk) Verifying Loading 7 of 18 subset(s).... Copyright (c) Digital Equipment Corporation. 1993-1997. All Rights Reserved. X.25 Manual Pages Copying from /mnt/XX3300/kit (disk) Verifying Loading 8 of 18 subset(s).... Copyright (c) Digital Equipment Corporation. 1993-1997. All Rights Reserved. 2-8 Installing WAN Support for DIGITAL UNIX Systems Installing WAN Support for DIGITAL UNIX Systems 2.2 Installing WAN Support for DIGITAL UNIX X.25 Example Programs Copying from /mnt/XX3300/kit (disk) Verifying Loading 9 of 18 subset(s).... Copyright (c) Digital Equipment Corporation. 1993-1997. All Rights Reserved. WDD Base Component Copying from /mnt/XX3300/kit (disk) Verifying Loading 10 of 18 subset(s).... Copyright (c) Digital Equipment Corporation. 1993-1997. All Rights Reserved. WDD Synchronous Device Drivers Copying from /mnt/XX3300/kit (disk) Verifying Loading 11 of 18 subset(s).... Copyright (c) Digital Equipment Corporation. 1993-1997. All Rights Reserved. WDD Datalink Protocols Copying from /mnt/XX3300/kit (disk) Verifying Loading 12 of 18 subset(s).... Copyright (c) Digital Equipment Corporation. 1993-1997. All Rights Reserved. WDD Example Programs Copying from /mnt/XX3300/kit (disk) Verifying Loading 13 of 18 subset(s).... Copyright (c) Digital Equipment Corporation. 1993-1997. All Rights Reserved. WDD Manual Pages Copying from /mnt/XX3300/kit (disk) Verifying Loading 14 of 18 subset(s).... DECnet/OSI Kernel Components Copying from /mnt/XX3300/kit (disk) Verifying Loading 15 of 18 subset(s).... Copyright (c) Digital Equipment Corporation. 1993-1996. All Rights Reserved. Installing WAN Support for DIGITAL UNIX Systems 2-9 Installing WAN Support for DIGITAL UNIX Systems 2.2 Installing WAN Support for DIGITAL UNIX DECnet/OSI Network Management Copying from /mnt/XX3300/kit (disk) Verifying Loading 16 of 18 subset(s).... DECnet/OSI Network Management GUI Copying from /mnt/XX3300/kit (disk) Verifying Loading 17 of 18 subset(s).... Copyright (c) Digital Equipment Corporation. 1993-1997. All Rights Reserved. CTF Collector Components Copying from /mnt/XX3300/kit (disk) Verifying Loading 18 of 18 subset(s).... Copyright (c) Digital Equipment Corporation. 1993-1997. All Rights Reserved. CTF User Environment Copying from /mnt/XX3300/kit (disk) Verifying 18 of 18 subset(s) installed successfully. Linking "WAN Kernel Programming Tools" 5 Configuring "WAN Kernel Programming Tools " (ZZAKPGMR301) Linking "WAN Utilities Base" Configuring "WAN Utilities Base " (ZZAUTIL301) Linking "X.25 Base Component" Configuring "X.25 Base Component " (XXAACC300) Linking "X.25 IP Support" Configuring "X.25 IP Support " (XXAIP300) Linking "X.25 Relay" Configuring "X.25 Relay " (XXARLY300) Linking "ROAMABOUT Transport Server Support" Configuring "ROAMABOUT Transport Server Support " (XXAWLSSRV300) Linking "X.25 Manual Pages" Configuring "X.25 Manual Pages " (XXAMAN300) 2-10 Installing WAN Support for DIGITAL UNIX Systems Installing WAN Support for DIGITAL UNIX Systems 2.2 Installing WAN Support for DIGITAL UNIX Linking "X.25 Example Programs" Configuring "X.25 Example Programs " (XXAEXAMPLES300) Linking "WDD Base Component" Configuring "WDD Base Component " (WDABASE300) Linking "WDD Synchronous Device Drivers" Configuring "WDD Synchronous Device Drivers " (WDADRIVERS300) Linking "WDD Datalink Protocols" Configuring "WDD Datalink Protocols " (WDADATALNKS300) Linking "WDD Example Programs" Configuring "WDD Example Programs " (WDAEXAMPLES300) Linking "WDD Manual Pages" Configuring "WDD Manual Pages " (WDAMAN300) Configuring "DECnet/OSI Kernel Components " (DNAKBIN401) Configuring "DECnet/OSI Network Management " (DNANETMAN401) Configuring "DECnet/OSI Network Management GUI " (DNANETMANGUI401) Linking "CTF Collector Components" Configuring "CTF Collector Components " (CTABASE301) Linking "CTF User Environment" Wide Area Networking Support V3.0 for Digital UNIX installed successfully. To complete your installation you must configure kernel components and 6 network interfaces by running the following command: # /usr/sbin/wansetup kernel Press RETURN to continue: Configuring "CTF User Environment " (CTAANAL301) Installing WAN Support for DIGITAL UNIX Systems 2-11 Installing WAN Support for DIGITAL UNIX Systems 2.2 Installing WAN Support for DIGITAL UNIX Notes on Example Prompt and Response Sequence-AlphaServer 4100 Systems 1 The setld -l command invokes the installation script and points to the distribution file system (/mnt/XXA300/kit in this example). 2 A list of the available subsets is displayed and you are prompted to select the subsets to be installed. The example shows the full set of available subsets for the AlphaServer. If some of the subsets are already installed, those subsets are not displayed in the list. To select a subset, enter the number associated with that subset. If more than one subset is required, separate one subset number from the next with a space. Ranges of subset numbers can be specified by putting a dash between the first and last numbers of the required range. 3 In case you selected the wrong subsets, the list of subsets you have selected to be installed are displayed and you are prompted to confirm the selection made. - Enter "y" if the selection is correct. - Enter "n" if the selection is incorrect. In this case, the original list of available subsets is redisplayed so that you can reselect the subsets to be installed. 4 Each of the selected subsets is now loaded from the CD. A message indicating that a subset is being loaded is displayed for each subset. During loading, a subset is copied from the specified mount directory and the copy is then verified. If, during the course of the installation, you encounter errors from the setld utility, refer to 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, examine the file /var/adm/smlogs/setld.log to locate information that can help you diagnose the problem. 2-12 Installing WAN Support for DIGITAL UNIX Systems Installing WAN Support for DIGITAL UNIX Systems 2.2 Installing WAN Support for DIGITAL UNIX 5 Once copied and verified, each subset is now installed into the kernel. During this process configuration files are modified and softlinks created. A message indicating that a subset is being installed is displayed for each subset copied and verified. 6 The first stage of the installation procedure is now complete. The next step of the procedure is to configure a kernel containing the components that have been installed. Depending on the configuration selected, you may be required to rebuild the kernel. The kernel components of the WAN Support subsets are implemented mainly as dynamically loadable modules. To include the installed WAN components in a kernel configuration, issue the command: # /usr/sbin/wansetup kernel The wansetup utility prompts for additional information and calls other utilities that may be required to configure a particular component into the kernel. Some configurations of DEC 3000 systems require that modules be statically built into the kernel. If this is the case, you will be prompted to rebuild the kernel at an appropriate time. 2.2.4 Stopping the Installation You can stop the installation script at any stage by pressing . Any files created by the installation procedure up to that point are not deleted. Such files should be deleted prior to invoking the installation script again. Note that if you stop the installation script after the subsets have been loaded and verified, you can delete the files by deinstalling the relevant subsets. Full details of this procedure are given in Section 2.3. Installing WAN Support for DIGITAL UNIX Systems 2-13 Installing WAN Support for DIGITAL UNIX Systems 2.2 Installing WAN Support for DIGITAL UNIX 2.2.5 Running the WANDD Installation Verification Procedure The WANDD Installation Verification Procedure (IVP) should be run whenever the WAN subsets are installed. If run, the IVP must be run after rebooting and before configuring WAN Support for DIGITAL UNIX Systems. Further details on running the IVP are provided in Chapter 3 and Appendix C. 2.2.6 Configuring the System After configuring the kernel, you can complete configuration of WAN support by using the wansetup utility in one of the following modes: o The basic mode is used to create a basic working configuration. This mode provides a mechanism for configuring a system, without the need to have knowledge of, or understand, Enterprise Management Architecture (EMA) entities. o The advanced mode is used to create more complex working configurations. This mode of operation requires you to have a good understanding and working knowledge of EMA entities. Both modes are detailed in the WAN Support for DIGITAL UNIX Systems- Configuration Guide. 2.3 Deinstalling Subsets If one or more subsets are no longer required they can be deinstalled. Deinstallation of subsets removes configuration and operational files and scripts that are required to shut down X.25. For this reason, the wanshutdown utility must be run before deinstalling any WAN Support for DIGITAL UNIX subset. ________________________ Note ________________________ Deinstalling WAN subsets other than manual pages and programming examples removes files that are used to configure modules into the running kernel at boot time. In order to remove those components from the running kernel, you must reboot the system. ______________________________________________________ 2-14 Installing WAN Support for DIGITAL UNIX Systems Installing WAN Support for DIGITAL UNIX Systems 2.3 Deinstalling Subsets To run the shutdown utility, enter the following command: # /usr/sbin/wanshutdown The wanshutdown command deletes any X.25 entities and halts any X.25 applications or dæmons on the system. After invoking the wanshutdown command, you can deinstall the WAN Support for DIGITAL UNIX subsets. To determine which subsets have been installed, enter the command: # setld -i To deinstall a subset, enter the command: # setld -d subset1 subset2 ... subsetn For example, to deinstall the DIGITAL UNIX Relay and DIGITAL UNIX X.25 IP Support subsets, enter the following command: # setld -d XXARLY300 XXAIP300 The order in which the subsets must be specified is arbitrary. However, the DIGITAL UNIX X.25 subset (XXAACC300) should be specified last. If subsets have been installed that depend on a subset nominated for deinstallation, those subsets are displayed and you are prompted to confirm that you want to deinstall the nominated subset. _______________________ Caution _______________________ Removing a subset on which other subsets depend, without also removing those dependent subsets, should be performed only if that subset (or a later version of that subset) is to be reinstalled. If the subset is not reinstalled, the system will not be able to configure the dependent subsets into the running kernel at boot time. ______________________________________________________ For power users, the following command line will remove all subsets pertaining to X.25. Installing WAN Support for DIGITAL UNIX Systems 2-15 Installing WAN Support for DIGITAL UNIX Systems 2.3 Deinstalling Subsets _______________________ Caution _______________________ If you do not want to remove any DECnet subsets, then you should remove the string ^DNA| from the command line given below. ______________________________________________________ # setld -d `setld -i | grep installed | awk '/^DNA|^CTA|^ISD|^WDA|^XXA|^ZZA/ {printf ("%s ", $1)}'` To verify that all desired subsets have been removed, review the list by issuing the following command: # setld -i | grep installed 2-16 Installing WAN Support for DIGITAL UNIX Systems 3 _________________________________________________________________ Postinstallation Tasks 3.1 Verifying Your X.25 Network WAN Support for DIGITAL UNIX provides three verification utilities to test aspects of the installation and subsequent configuration of your X.25 network. These utilities are: o The WANDD Installation Verification Procedure (IVP), which performs a number of tests to ensure that your node can communicate with itself and with the local or remote modems, that is, it ensures that Layer 1 and Layer 2 datalink protocols are operating correctly. The IVP should be run whenever the WAN subsets are installed. It must be run before WAN Support for DIGITAL UNIX Systems is configured. Full details of how to run the IVP are provided in Appendix C. o The X.25 Configuration Test Procedure (CTP), which is used to verify that X.25 (Layer 3 protocol) is correctly installed and configured. The CTP should be run whenever X.25 subsets have been installed. Full details of how to run the CTP are provided in the WAN Support for DIGITAL UNIX Systems- Configuration Guide. o The ISDN Installation Verification Procedure (IVP), which performs a number of tests to ensure that your system can make and receive ISDN calls to and from a remote system, or to itself if the ISDN network permits it. You can run the ISDN IVP after configuring an ISDN device. See the WAN Support for DIGITAL UNIX Systems- ISDN User's Guide- DEC 3000 Systems for details. Postinstallation Tasks 3-1 Postinstallation Tasks 3.1 Verifying Your X.25 Network In addition, WAN Support for DIGITAL UNIX provides two verification utilities to test aspects of the installation and subsequent configuration of the ISDN component. These utilities are: o The isdnstat utility, which can be used to give reports on ISDN modules' status, detailed statistics, or counter values. o The isdnevl utility, which displays trace information for selected ISDN modules, or for all modules. Full details of how to run both these utilities are provided in the WAN Support for DIGITAL UNIX Systems- ISDN User's Guide- DEC 3000 Systems. 3.2 Determining and Reporting Problems If you encounter a problem while using WAN Support for DIGITAL UNIX, report it to DIGITAL. Depending on the type of support you have and the nature of the problem, take one of the following actions: o If you have a Software Product Services Support Agreement, contact your DIGITAL Customer Support Center (CSC), either by telephone or using the electronic means provided with your support agreement (such as DSNlink). The CSC provides telephone support for high-level advisory and remedial assistance. When you initially contact the CSC, please provide the following information: - The name and version number of the operating system being used; - The product name (WAN Support for DIGITAL UNIX Systems) and version number being used; - The hardware system being used, such as the model number; - A brief description of the problem; and - How critical the problem is. 3-2 Postinstallation Tasks Postinstallation Tasks 3.2 Determining and Reporting Problems When you submit information electronically or are speaking on the phone to the appropriate WAN Support for DIGITAL UNIX support specialist, you can provide more detailed information. This includes the specific commands used to compile and link the program, the error messages displayed, and the relevant detailed information (including source program listings where applicable). Please attempt to narrow the cause to a specific module or specific lines of code. CSC personnel may ask for additional information, such as listings of any command files, relevant data files, and so forth. If the program is longer than 50 lines, submit a copy of it electronically or provide machine- readable media (floppy diskette or magnetic tape). o If you have a Self-Maintenance Software Agreement, you can submit a Software Performance Report (SPR). o If you do not have any type of software services support agreement and you purchased WAN Support for DIGITAL UNIX within one year of the occurring problem, you can submit an SPR if you think the problem is caused by a software error. When you submit an SPR, please perform the following actions: 1. Describe as accurately as possible the circumstances and state of the system when the problem occurred. In the description, please provide: - The name and version number of the operating system being used; - The version number of WAN Support for DIGITAL UNIX being used; and - A concise description of the problem with specific examples. Include any error messages displayed, the commands used to compile and link the program, and so on. 2. Isolate the problem as far as possible. 3. Provide a listing of the program. 4. Include listings of any command files, relevant data files, and so forth. Postinstallation Tasks 3-3 Postinstallation Tasks 3.2 Determining and Reporting Problems 5. If the program is longer than 50 lines, submit a copy of it on machine-readable media (floppy diskette or magnetic tape). Where relevant, also submit a copy of the program library used to build the application. 6. Report only one problem per SPR. This will facilitate a faster response. 7. Mail the SPR package to DIGITAL. Many problem reports do not contain enough information to duplicate or identify the problem. Concise, complete information helps DIGITAL give you accurate and timely service to software problems. If the problem is related to WAN Support for DIGITAL UNIX documentation, choose one of the following methods to report the problem. The method to use will depend on the severity of the problem: o If you have a Software Product Services Support agreement, report the problem to the CSC. o Fill out and submit a Reader's Comments form (located at the back of every hardcopy manual). Use the form from the manual in which you found the error. Where appropriate, include the section and page number. To obtain information about purchasing a DIGITAL Software Product Services Support Agreement or other support services, please contact your local DIGITAL sales representative. 3-4 Postinstallation Tasks A _________________________________________________________________ Disk Space Requirements The disk space requirements discussed in this appendix apply to the file system where you intend to load the WAN Support for DIGITAL UNIX subsets. Table A-1 lists the disk space requirements for loading WAN Support for DIGITAL UNIX software subsets on a DIGITAL UNIX system. This table specifies disk space requirements by file system for the convenience of those installers performing installations on systems where these file systems exist on separate disk partitions. Table_A-1_Worksheet_for_Subset_Sizes_(Kilobytes_Required)__ /usr Subset_Title_________________________/opt___/opt___/var/opt CTF Collector Components 4 498 596 (CTABASE301) CTF User Environment (CTAANAL301) 1 4367 0 WAN Utilities Base (ZZAUTIL301) 0 992 324 X.25 Base Component (XXAACC300) 15 15784 2181 X.25 Example Programs 0 174 0 (XXAEXAMPLES300) X.25 IP Support (XXAIP300) 0 32 441 X.25 Manual Pages (XXAMAN300) 0 100 0 X.25 Relay (XXARLY300) 0 7 653 DIGITAL UNIX ROAMABOUT Server 0 681 0 Support (XXAWLSSRV300) (continued on next page) Disk Space Requirements A-1 Disk Space Requirements Table A-1 (Cont.) Worksheet for Subset Sizes (Kilobytes __________________Required)________________________________ /usr Subset_Title_________________________/opt___/opt___/var/opt DECnet/OSI Kernel Components 24 0 1375 (DNAKBIN401) DECnet/OSI Network Management 39 11206 26 (DNANETMAN401) DECnet/OSI Network Management GUI 0 2304 0 (DNANETMANGUI401) WDD Datalink Protocols 0 0 1366 (WDADATALNKS300) WDD Base Component (WDABASE300) 3 195 860 WDD Synchronous Device Drivers 0 193 2291 (WDADRIVERS300) WDD Example Programs 0 62 0 (WDAEXAMPLES300) WDD Manual Pages (WDAMAN300) 0 16 0 DIGITAL UNIX ISDN Base Components 295 1181 3098 (ISDBASE300) DIGITAL UNIX ISDN Driver Components 2 80 0 for_DEC_3000_(ISDBBAD300)__________________________________ Using Table A-1, total the sizes of the subsets that you plan to load for each file system. Compare the totals obtained with the free space available on the disk partitions where WAN Support for DIGITAL UNIX files will reside. To determine whether there is sufficient free space for the subsets you plan to install: 1. Display details about each of the file systems specified in Table A-1. For example, to display details about /usr /opt, enter the command: # df /usr/opt From the output displayed, record the amount of free space available on the specified file system. A-2 Disk Space Requirements Disk Space Requirements 2. Verify that the amount of free space is greater than the total space required for the subsets to be installed. If there is not enough space in either of the file systems for the WAN Support for DIGITAL UNIX subsets, increase the size of the partition on which that file system resides. Disk Space Requirements A-3 B _________________________________________________________________ Subsets This appendix describes each of the available subsets and provides details of the interdependencies between subsets. The subsets are presented in alphabetical order. The following WAN Support for DIGITAL UNIX subsets are available: o CTF Collector Components (CTABASE301)-contains the Common Trace Facility functionality to collect trace events from network protocols and distribute them to local and remote users who have requested tracing. o CTF User Environment (CTAANAL301)-contains the Common Trace Facility user level utilities necessary to initiate tracing of network protocols on local and remote nodes, and to analyze the trace records collected from those nodes. o WAN Utilities Base (ZZAUTIL301)- contains the kernel utilities common to all DIGITAL WAN products. o WAN Kernel Programming Tools (ZZAKPGMR300) - contains header files used by dependent layered products. This subset is not normally installed on a customer machine. o X.25 Base Component (XXAACC300)-provides a common programming and management interface to X.25 networking application programs and allows direct access to one or more PSDNs conforming to CCITT recommendation X.25. o X.25 Example Programs (XXAEXAMPLES300)-provides a set of example X.25 and X.29 programs. o X.25 IP Support (XXAIP300)-provides transmission of IP over X.25 networks. o X.25 Manual Pages (XXAMAN300)-provides online reference pages. Subsets B-1 Subsets o X.25 Relay (XXARLY300)-allows calls to be relayed (forwarded) from one DTE to another. o DECnet/OSI Kernel Components (DNAKBIN401)-provides LAN datalink components. o DECnet/OSI Network Management (DNANETMAN401)-contains network management utilities and shared libraries. o DECnet/OSI Network Management GUI (DNANETMANGUI401)- provides a graphical interface to network management. o WDD Datalink Protocols (WDADATALNKS300)- provides the Layer 2 datalink protocols (HDLC/LAPB/LLC2). o WDD Base Component (WDABASE300)- contains utility routines, data files, and setup scripts required by the other WANDD subsets. o WDD Synchronous Device Drivers (WDADRIVERS300)- contains Layer 1 code for device drivers, modem connect/ device management, and common driver code. o WDD Manual Pages (WDAMAN300)-provides online reference pages for the WAN application programming interface. o WDD Example Programs (WDAEXAMPLES300)-provides a set of example WAN application programs. o ISDN Base Components (ISDBASE300)-the mandatory subset containing all the base software for enabling ISDN. o DIGITAL UNIX ISDN Driver Components for DEC 3000 (ISDBBAD300)-the required Driver components for enabling ISDN on DEC 3000 architectures using the Base Board Audio device (BBA). Table B-1 shows the interdependencies between subsets. Note that the subset OSFBASE321 is required in addition to the specified subsets. B-2 Subsets Subsets Table_B-1_Subset_Interdependencies_________________________ Subset_to_be_Installed__________________Subsets_Required___ CTF Collector Components (CTABASE301) CTABASE301 ZZAUTIL301 CTF User Environment (CTAANAL301) CTAANAL301 WAN Utilities Base (ZZAUTIL301) ZZAUTIL301 X.25 Base Component (XXAACC300) XXAACC300 WDABASE300 X.25 Example Programs (XXAEXAMPLES300) XXAEXAMPLES300 XXAACC300 X.25 IP Support (XXAIP300) XXAIP300 XXAACC300 X.25 Manual Pages (XXAMAN300) XXAMAN300 XXAACC300 OSFDCMT400 X.25 Relay (XXARLY300) XXARLY300 XXAACC300 DECnet/OSI Kernel Components DNAKBIN401 (DNAKBIN401) DECnet/OSI Network Management DNANETMAN401 (DNANETMAN401) DECnet/OSI Network Management GUI DNANETMAN401 (DNANETMANGUI401) WDD Datalink Protocols WDADATALNKS300 (WDADATALNKS300) WDABASE300 WDD Base Component (WDABASE300) WDABASE300 CTABASE301 DNANETMAN401 DNAKBIN401 + WDD Synchronous Device Drivers WDADRIVERS300 (WDADRIVERS300) WDABASE300 +_The_subset_DNAKBIN401_is_required_only_if_you_intend_to__ run X.25 over LLC2. (continued on next page) Subsets B-3 Subsets Table_B-1_(Cont.)_Subset_Interdependencies_________________ Subset_to_be_Installed__________________Subsets_Required___ DIGITAL UNIX ISDN Base Components ZZAUTIL301 (ISDBASE300) CTABASE301 DNANETMAN401 DIGITAL UNIX ISDN Driver Components ISDBASE300 for_DEC_3000_(ISDBBAD201)__________________________________ B-4 Subsets C _________________________________________________________________ Installation Verification Procedure After installing the relevant WDD subsets on your DIGITAL UNIX system, you can run a series of tests to make sure that your node can communicate with itself and with the local or remote modems. Only a limited number of functional tests can be performed. To perform detailed tests for the HDLC/LAPB/LLC2 module requires the assistance of higher level software layers, such as DECnet. The installation verification procedure tests only synchronous communications; it does not use the LLC2 module. After performing the preliminary tests described in this appendix, DECnet or X.25 should be used to establish communications with another node. For details of the tests that may be performed using the higher level software layers, refer to the relevant documentation for the software layer used. Note that to run the installation verification procedure, you must have superuser privileges and the WDD Synchronous Device Drivers subset must be installed. Installation Verification Procedure C-1 Installation Verification Procedure C.1 Overview of the Installation Verification Procedure C.1 Overview of the Installation Verification Procedure A shell script and program combination is provided to carry out the series of tests depicted in Figure C-1 through Figure C-5. This installation verification procedure will test the software and hardware components of the device drivers installed. The tests are illustrated and discussed in the order that they should be performed. Each figure contains a brief description of the test to be performed. In each figure, a broken line represents the test path. Figure C-1 verifies that the driver has been correctly configured into the kernel, and that it is accessible by means of its software interface. Figure C-1 Driver Loopback Test C-2 Installation Verification Procedure Installation Verification Procedure C.1 Overview of the Installation Verification Procedure Figure C-2 determines whether the driver can communicate with the device itself by means of the device registers and interrupts. Figure C-2 Device Loopback Test Installation Verification Procedure C-3 Installation Verification Procedure C.1 Overview of the Installation Verification Procedure Figure C-3 verifies that the device is capable of transmitting and receiving data. The test also confirms that the hardware from the host to the modem (that is the device and cable) is operational. Figure C-3 Local Loopback Test Automatic switching of the modem into local loopback requires that both the modem and the device support circuit CCITT 141, Local Loopback Request. If this is not the case, then manual intervention is required. Refer to Appendix F for a description of the supported circuits for each device. This test will fail if no cable is available, or if the modem is not capable of being looped back under the modem control. If the test fails, you will be requested to intervene and either insert a loopback connector or manually switch the modem into local loopback. C-4 Installation Verification Procedure Installation Verification Procedure C.1 Overview of the Installation Verification Procedure Figure C-4 determines whether communications exist between the local and the remote modem. Figure C-4 Remote Loopback Test Automatic switching of the modem into remote loopback requires that both the modem and device support circuit CCITT 140, Remote Loopback. If this is not the case, then manual intervention is required. Refer to Appendix F for a description of the supported circuits for each device. This test will fail if no cable is available, or if the modem is not capable of being looped back under the modem control. If the test fails, you will be requested to intervene and either insert a loopback connector or manually switch the modem into remote loopback. Installation Verification Procedure C-5 Installation Verification Procedure C.1 Overview of the Installation Verification Procedure Figure C-5 determines whether the interface between the HDLC/LAPB module and the device driver is operational. The test is performed by using the last successful loopback mode. Figure C-5 HDLC/LAPB Loopback Test (to local modem) It is not possible to test the protocol module in detail without assistance from higher software layers. The test is performed using unsequenced data packets. Under these conditions, the link layer will not be initialized and brought into full operational mode. C-6 Installation Verification Procedure Installation Verification Procedure C.2 Running the Installation Verification Procedure C.2 Running the Installation Verification Procedure The installation verification procedure can be run only if the WDD Synchronous Device Drivers subset has been installed. To run the installation verification procedure, enter the command: # setld -v WDABASE300 Follow the instructions and answer the questions displayed on your terminal. If you need further information to answer a question, enter a question mark (?) at the prompt. Press to end all input lines. If you press without entering any input, the script will prompt you again. Note that you can interrupt the installation verification procedure at any time by pressing . When you are ready to resume the installation verification procedure, enter fg. If WANDD was correctly installed, the installation verification program prompts you to specify the line(s) that you want to test (DSYn, DNSn, SSCCn, and/or FSIn, where n is a value from 0 to 19). Please specify the physical line(s) (dsy)[]: dsy0 dsy1 The program then displays summary information showing the device and its state. If the installation verification program detects an error in one of the loopback tests it will attempt to run the HDLC/LAPB test using the last successful loopback mode. C.3 Error Conditions If the installation verification procedure fails, you should initially examine the file /var/adm/smlogs/fverify.log for information to help you diagnose the problem. Installation Verification Procedure C-7 Installation Verification Procedure C.3 Error Conditions The following list summarizes possible error conditions that may occur during each stage of the installation verification procedure and cause a test to fail. Information is also provided that will help you to solve the problem. 1. Driver loopback test A failure occurring at this stage indicates that some aspect of the installation failed. a. Verify that the WDD Device Driver files have been successfully copied to the correct directories by using fverify(8) with the -n option. For example: # cd / # /usr/lbin/fverify -n < /usr/.smdb./WDABASE300.inv b. Examine the console for messages generated at boot time. These messages indicate two different types of error: . Messages prefixed with wdd or hdlc management: indicate errors in the WDD device driver management. . Messages prefixed with dsyn:, dnsn:, fsin:, pwan:, or ssccn: (where n is a value from 0 to 19) indicate errors within a specific device driver. Any errors found on the console should be recorded and reported to the Customer Service Center. 2. Device loopback test A failure occurring at this stage indicates that some aspect of the device hardware has failed. You should: * Verify that the device control and status register switches have been set to the address defined in the system configuration file; and * Run the designated standalone diagnostics for the device; OR * Call the Customer Support Representative. 3. Local loopback test C-8 Installation Verification Procedure Installation Verification Procedure C.3 Error Conditions A failure occurring at this stage indicates that some aspect of the communications hardware is faulty. Ensure that: * The modem is in loopback mode; * All cable connections have been made; and * There is power supplied to the modem. If these conditions have been satisfied and the problem persists, contact either the local Field Service Representative, or the supplier of the modem. 4. Remote loopback test A failure at this stage indicates that some aspect of the communications hardware is faulty. You should ensure that: * All cable connections have been made; * The remote modem is in loopback mode; and * There is power supplied to both modems. If these conditions have been satisfied, refer to documentation supplied with the modem and ensure that all indications on the modems at each end of the line are correct. If these conditions have been satisfied, contact either the supplier of the modem equipment or your local telecommunications supplier. 5. HDLC/LAPB loopback test A failure at this stage indicates that some aspect of the installation has failed. Contact your local Customer Service Center to resolve the problem. Installation Verification Procedure C-9 D _________________________________________________________________ Installing DECnet Over HDLC This appendix details how to install the HDLC component of WAN Support for DIGITAL UNIX if you want to run DECnet/OSI for DIGITAL UNIX Systems over HDLC. The appendix is divided into two sections: o Section D.1 details aspects of the installation procedure specific to installing HDLC. o Section D.2 details some performance trade-offs available to users when running DECnet over HDLC. D.1 Installation Procedure To run DECnet over HDLC: 1. Ensure that the following subsets have been installed: CTABASE301 DNANETMAN401 WDABASE300 WDADATALNKS300 WDADRIVERS300 ZZAUTIL301 2. Run the DECnet/OSI for DIGITAL UNIX Systems kernel installation setup utility. When run, this utility automatically invokes the wddsetup utility. While running wddsetup: a. Select the required driver. b. Select one of the following datalink protocol options: 2) The HDLC/LAPB Synchronous datalink protocols are required. 4) All datalink protocols (HDLC/LAPB/LLC2) are required. Installing DECnet Over HDLC D-1 Installing DECnet Over HDLC D.1 Installation Procedure 3. Complete the installation of DECnet/OSI for DIGITAL UNIX Systems. 4. Run the Installation Verification Procedure (IVP). Details on how to run the IVP are provided in Appendix C of this guide. 5. Using the advanced mode of decnetsup, configure DECnet /OSI for DIGITAL UNIX Systems. When prompted for a synchronous device, choose a synchronous device corresponding to the selection you made in step 2a of this procedure. D-2 Installing DECnet Over HDLC Installing DECnet Over HDLC D.2 Performance Tradeoffs Available to the User D.2 Performance Tradeoffs Available to the User The trade-offs available to the user are associated with the management of the HDLC Link entity and relate to the following areas: o Window size; o Data buffers; o Number of retries; and o Frame acknowledgement. The HDLC Link entity provides attributes to control these areas, though values for these attributes should be chosen only after careful analysis of the network by an experienced network manager. Any changes to the values of the attributes detailed in Sections D.2.1 to D.2.5 should be made by editing the following file: /var/dna/scripts/start_datalink.ncl D.2.1 Window Size Larger window sizes will enable better channel utilization on long haul links, such as a satellite link, as transit times are large. However, a large window size will also affect system memory as all frames transmitted must be held by the sender until they have been acknowledged. The HDLC link characteristic attributes that the user may alter to affect window size are: o Sequence Modulus; and o Preferred Window Size. D.2.2 Data Buffers Data buffer size may adversely affect network performance. If this parameter is too large, valuable memory resources may be unnecessarily consumed. Additionally, on noisy channels, a smaller frame size may reduce channel congestion, as smaller frames are less susceptible to noise, and take less time to retransmit. Installing DECnet Over HDLC D-3 Installing DECnet Over HDLC D.2 Performance Tradeoffs Available to the User The HDLC link characteristic attributes that the user may alter to affect receive buffers are: o Maximum Data Size; o Preferred Maximum Data Size; and o Minimum Data Size. D.2.3 Number of Retries The number of times a frame is retransmitted before the channel is assumed to be faulty may also affect performance. If the value is too low on noisy links, throughput will be reduced due to the time taken to bring the link down, recognize that it is no longer faulty, and then reinstate communications. D-4 Installing DECnet Over HDLC Installing DECnet Over HDLC D.2 Performance Tradeoffs Available to the User This value may only be chosen after the network manager has determined the noise characteristics of the particular network link. The HDLC link characteristic attribute that the user may alter to affect the number of retries is: o Retry Maximum. D.2.4 Frame Acknowledgement Two questions arise with frame acknowledgement: o How long should the transmitter of the frame wait for an acknowledgement? If this time period is too small (that is, less than two times the propagation delay, plus the frame processing at the receiving end), then the channel may become saturated by frames that have been retransmitted unnecessarily. If this time period is too large, the channel will be idle, and throughput will be reduced. Generally, problems may arise by choosing too short a time period on long haul networks (such as satellite links), and too long a time period on local links. o How long should the receiver wait for an outgoing frame, on which an acknowledgement may be piggybacked? If the receiver were to wait longer than the sender's timeout period, the frame will be retransmitted, thus defeating the purpose of acknowledgement. Choosing values for these time periods may only be undertaken after the network manager has analyzed the transit time of each particular network link. The HDLC link characteristic attributes that the user may alter to affect frame acknowledgement are: o Acknowledge Timer, and o Holdback Timer. Installing DECnet Over HDLC D-5 Installing DECnet Over HDLC D.2 Performance Tradeoffs Available to the User D.2.5 Acknowledge Timer Assuming that the Acknowledge Timer will be much greater than the Holdback Timer, then an initial value for the Acknowledge Timer may be found using the formula: Acknowledge Timer = [1.2 * Maximum PDU Size * 8 * (1 + x)]/Line Speed where: x is either 3 or the window size, whichever is the smaller. This calculation does not take into account the propagation delay of the link. If the propagation delay is significant (for example, in the case of a satellite link), then the user should add the propagation delay to the value obtained using the formula shown above. D-6 Installing DECnet Over HDLC E _________________________________________________________________ Installing Without Datalink Protocols This appendix details how to install the WDD Synchronous Device Drivers component of WAN Support for DIGITAL UNIX if you intend to use an alternative DIGITAL layered product that provides its own datalink protocols. In this case, the datalink protocols provided in WAN Support for DIGITAL UNIX are not required. E.1 Installation Procedure ________________________ Note ________________________ The following procedure assumes that the installation procedure for your layered product has been set up to call wddsetup. ______________________________________________________ To install the WDD synchronous device drivers: 1. Ensure that the following subsets have been installed: CTABASE301 DNANETMAN401 WDABASE300 WDADRIVERS300 ZZAUTIL301 2. Run the setup utility relevant to installing your layered product. This utility automatically invokes the wddsetup utility. While running wddsetup you will be prompted to select the required driver. Note that you will not be asked to select the datalinks required. Instead, the following message is displayed: The WDADATALNKS subset was not installed. All questions relating to datalink protocols will be bypassed! 3. Complete the installation of your layered product. Installing Without Datalink Protocols E-1 Installing Without Datalink Protocols E.1 Installation Procedure 4. Run the Installation Verification Procedure (IVP). Details on how to run the IVP are provided in Appendix C. 5. Configure your layered product. When prompted for a synchronous device, choose a synchronous device corresponding to the selection you made in step 2 of this procedure. E-2 Installing Without Datalink Protocols F _________________________________________________________________ Device-Specific Information This appendix describes the required attributes of the range of devices supported by the WAN Support for DIGITAL UNIX Synchronous Device Drivers. F.1 Driver Information For more information refer to the WAN Support for DIGITAL UNIX Systems- Software Product Description-SPD 42.47.xx. F.1.1 SCC Device Driver The SCC is a one line interface. It provides RS-232-D connections to leased synchronous communications lines, and operates in bit-oriented mode. F.1.2 DSYT1 Device Driver The DSYT1 is the two line TURBOchannel option card for use in TURBOchannel systems. It provides RS-232-C, RS-422- A, RS-423-A, and V.35 connections to leased synchronous communications lines, and operates in both character- oriented and bit-oriented modes. F.1.3 DNSES Device Driver The DNSES is the two line EISA option card for use in EISA systems. It provides RS-232-C, RS-422-A, RS-423-A, and V.35 connections to leased synchronous communications lines, and operates in both character- and bit-oriented modes. F.1.4 PBXDI and PBXDP Device Drivers The PBXDI is a two line or four line option card for use in ISA and PCI systems. The card provides EIA-232, EIA- 530, V.24, V.35, and X.21 connections to leased synchronous communications lines. The ISA and PCI options are provided by different physical cards. This option must be selected when the card is purchased, and is not field-modifiable. Device-Specific Information F-1 Device-Specific Information F.1 Driver Information F.1.5 DIGITAL 3000 ISDN Device Driver (BBA) The BBA is a one line interface. It provides ISO/IEC 8877 connections for ISDN Basic Rate Access. F-2 Device-Specific Information G _________________________________________________________________ PBXDI ISA Synchronous Communications Adapter G.1 Introduction This appendix describes the software configuration as well as installation of the PBXDI ISA synchronous communications controller. G.1.1 Supported Interface Types on PBXDI Card The PBXDI device driver software will not support X.21 circuit switching. It does support X.21 electrical and connector interfaces as well as EIA-232-D (V.24), V.35 and EIA-530 interface types. G.1.2 Configuration There is only "semi-automatic" configuration of PBXDI ISA cards. PBXDI ISA cards must be configured at the system console. The console commands for configuring ISA cards are described in the user information manual provided with your system. (For example, the DIGITAL AlphaStation 400 Series-User Information Manual). Two similar configuration utilities are currently available-iconfig and isacfg. A sample configuration process, using the isacfg console command, is described later in this appendix. A similar procedure will be applicable if you use the iconfig command. To accommodate both 2 and 4 port PBXDI boards, the driver configuration always creates four device units (for example, fsi0, fsi1, fsi2, and fsi3). For two-port cards only the first two units will ever be available for use. At present the configurator wansetup allows the configuration of all four units regardless of whether or not the units correspond to real ports on the PBXDI boards. The user should configure only the devices that actually exist. PBXDI ISA Synchronous Communications Adapter G-1 PBXDI ISA Synchronous Communications Adapter G.2 Installation of PBXDI-Ax Cards G.2 Installation of PBXDI-Ax Cards Installing the PBXDI-Ax card requires the following steps: 1. Invoke the console utility ICONFIG to specify the adapter configuration parameters: i/o register base, IRQ, and memory base. 2. Set the adapter i/o register base through the adapter switches. The other adapter configuration parameters are set by operating system software from the values specified to the ICONFIG utility. 3. Set the jumpers for the electrical interface to be used (necessary only on boards supporting the EIA-232 and V.35 electrical interface). 4. Physically install the adapter into the system. It is recommended that the console configuration commands (step 2) be issued before setting the adapter IO register base so that any console detected resource conflict can be rectified BEFORE physically configuring the adapter IO register base. These steps will now be described in more detail. 1. Invoke the console utility ICONFIG, for example: >>> iconfig ISA CONFIGURATION UTILITY Name I/O IRQ DMA Mem Length Enabled MOUSE 60 12 Y KBD 60 1 Y COM1 3f8 4 Y COM2 2f8 3 Y LPT1 3bc 7 Y FLOPPY 3f0 6 2 Y On a UNIX system, enter PBXDI in the name field. On an OpenVMS Alpha system enter PBXDI-A2 (2-port PBXDI- Ax card) or PBXDI-A4 (4-port PBXDI-Ax card) or PBXDI-A (generic PBXDI-Ax card, number of ports unspecified) or PBXDI (generic PBXDI-Ax card, number of ports unspecified). G-2 PBXDI ISA Synchronous Communications Adapter PBXDI ISA Synchronous Communications Adapter G.2 Installation of PBXDI-Ax Cards The I/O base address must be a multiple of 0x10. The factory configured address is 0x300, which is not in use by any other device on this particular system so that may be selected. The IRQ must be one of 3, 5, 7, 10, 11, 12, or 15. The selected IRQ must not be in use by any other device. On this particular system IRQ 5 is the lowest PBXDI IRQ not in use by any other device so specify that. The PBXDI does not use a DMA channel so TAB over that field. The Mem value must be a multiple of 0x4000 (16K). On this particular system no other device uses any ISA memory so 0 may be selected. The Length field must be specified as 4000. The Enabled field must contain Y, otherwise the console will not tell the operating system about the device. After configuration: ISA CONFIGURATION UTILITY Name I/O IRQ DMA Mem Length Enabled MOUSE 60 12 Y KBD 60 1 Y COM1 3f8 4 Y COM2 2f8 3 Y LPT1 3bc 7 Y FLOPPY 3f0 6 2 Y PBXDI-A 300 5 0 4000 Y Subsequent PBXDI-Ax cards could be configured with I/O 310, 320 (etc), IRQ 10, 11 (etc.) and memory 4000, 8000 (etc). 2. Set the Adapter i/o register base address. See Section 5.11 of the accompanying manual. 3. Set the appropriate electrical interface. This is required only if a board supporting V.35 or RS-232 is to be installed. See Appendix B of the accompanying manual. PBXDI ISA Synchronous Communications Adapter G-3 PBXDI ISA Synchronous Communications Adapter G.2 Installation of PBXDI-Ax Cards 4. Physically install the adapter into the system. See the appropriate system manual for details on installing expansion adapters. G-4 PBXDI ISA Synchronous Communications Adapter H _________________________________________________________________ Example of Null Modem Cable Wiring The following RS-232/V.24 null modem cable wiring diagrams in no way represent the wiring of any cable supplied by DIGITAL. These cables have been found to be useful by the developers of the WDD Synchronous Device Drivers, and may be used as a starting point for users manufacturing their own cables. ________________________ Note ________________________ The cable shield is earthed to pin 1 at one end only. This is to prevent earth loops with the signal ground (pin 7). Speed Selector (pin 23) is connected to Ring Indicate (pin 22) and Local Loop (pin 18) is connected to Test Indicate (pin 25) to prevent ringing on unterminated lines. ______________________________________________________ H.1 RS-232 Null Modem Cable with Clock Available at Both Ends 25 pin Female 25 pin Female D--Shell D--Shell pin pin Cable Shield 1 ------------------------------ Connect at one end only Tx Data 2 ------------------------------ 3 Rx Data Rx Data 3 ------------------------------ 2 Tx Data Example of Null Modem Cable Wiring H-1 Example of Null Modem Cable Wiring H.1 RS-232 Null Modem Cable with Clock Available at Both Ends RTS 4 --+-------------------------- 8 DCD | CTS 5 --+ +-- 4 RTS | DCD 8 --------------------------+-- 5 CTS Ground 7 ------------------------------ 7 Ground DSR 6 ------------------------------ 20 DTR DTR 20 ------------------------------ 6 DSR Tx Clock 15 --+-------------------------- 17 Rx Clock | Clock 24 --+ +-- 24 Clock | Rx Clock 17 --------------------------+-- 15 Tx Clock RI 22 --+ +-- 22 RI | | Speed Select 23 --+ +-- 23 Speed Select Local Loop 18 --+ +-- 18 Local Loop | | Test Indicate 25 --+ +-- 25 Test Indicate H.2 RS-232 Null Modem Cable with Clock Available Only at One End 25 pin Female 25 pin Female D--Shell D--Shell pin pin Cable Shield 1 ------------------------------ Connect at one end only Tx Data 2 ------------------------------ 3 Rx Data Rx Data 3 ------------------------------ 2 Tx Data H-2 Example of Null Modem Cable Wiring Example of Null Modem Cable Wiring H.2 RS-232 Null Modem Cable with Clock Available Only at One End RTS 4 --+-------------------------- 8 DCD | CTS 5 --+ +-- 4 RTS | DCD 8 --------------------------+-- 5 CTS Ground 7 ------------------------------ 7 Ground DSR 6 ------------------------------ 20 DTR DTR 20 ------------------------------ 6 DSR Tx Clock 15 --------------------------+-- 15 Tx Clock | Clock 24 -- +-- 24 Clock | Rx Clock 17 --------------------------+-- 17 Rx Clock RI 22 --+ +-- 22 RI | | Speed Select 23 --+ +-- 23 Speed Select Local Loop 18 --+ +-- 18 Local Loop | | Test Indicate 25 --+ +-- 25 Test Indicate Example of Null Modem Cable Wiring H-3 I _________________________________________________________________ Error Recovery This appendix contains information to help you solve problems that may occur while installing WAN Support for DIGITAL UNIX . I.1 Recovery Procedure During installation, errors can occur if any of the following conditions exist: o There is insufficient disk space; o An incorrect version of the operating system is being used; or o An incorrect version of the prerequisite software is being used. If an error occurs, the installation of WAN Support for DIGITAL UNIX will be terminated as a result of one of the following interrupts: o Controlled interrupts occur when the script detects an error during installation and an error message is displayed. You can find the details of the error messages in Section I.2. After taking corrective action, restart the installation by entering the command: # setld -l mount-point Full details of the procedure to start the installation are provided in Section 2.2.1. o Uncontrolled interrupts are caused by an external action (for example, when you terminate the installation by pressing ); in this case, no error messages are displayed. Error Recovery I-1 Error Recovery I.1 Recovery Procedure To recover from an uncontrolled interrupt, you should proceed as follows: 1. Delete the subsets affected using the following command: # setld -d subset-name 2. Restart the installation. Refer to Section 2.2.1. This procedure applies to any selected subsets being loaded when the interrupt occurs. If an error occurs that you think is caused by a problem related to the WAN Support for DIGITAL UNIX software, then perform one of the following actions: o If you have a basic or DECsupport Software Agreement, call your Customer Support Center (CSC). o If you have a Self-Maintenance Software Agreement, submit a Software Performance Report (SPR). o If you purchased WAN Support for DIGITAL UNIX within the last 90 days, submit an SPR. If the error occurred due to lack of, or misleading, information provided in the WAN Support for DIGITAL UNIX documentation, please describe the error on one of the Reader's Comments forms at the back of the document containing the error and return the form to DIGITAL. Please include the section and page number where the error occurred. I.2 Error Messages This section contains the error messages returned from controlled interrupts. I-2 Error Recovery Error Recovery I.2 Error Messages ___________________________________________________________ Error_Message_________Effect,_Description_and_Action:______ Cannot install Effect: Installation stops. : Description: The software currently must be being installed () requires installed. to be installed on the target system. This message indicates that is absent. Action: Install using setld -l. Cannot install Effect: Installation stops. : a Description: A previous or different version of subsequent version of the subset already being installed () is exists. already present on the target machine. Consequently, this subset cannot be installed. Action: Remove the existing version of the specified software subset and reinstall . Error Recovery I-3 Error Recovery I.2 Error Messages ___________________________________________________________ Error_Message_________Effect,_Description_and_Action:______ ERROR: cannot update Effect: Installation stops. . Description: An attempt to change the system file failed. This may be caused by: o The superuser not having write permissions on the file; or o An error in the ed(1) script used to modify the file. Action: o Determine the permissions on the file , using ls -l. If superuser does not have write privileges on the file, change the permissions using chmod(1). o Restore from the most recent .sav{n} file. Attempt the installation again. If the error occurs again, then the error will be in the ed(1) script .x25. If the problem remains, contact your local DIGITAL support representative. I-4 Error Recovery Error Recovery I.2 Error Messages ___________________________________________________________ Error_Message_________Effect,_Description_and_Action:______ not Effect: Installation stops. found. Description: The specified file could not be found by the installation procedure. Action: The file in question may be either elsewhere within the filesystem, or absent from it. If this is the case, make sure that the target system has the appropriate DIGITAL UNIX version installed. If so, and the file does not exist anywhere in the filesystem, the system file will need to be recreated. Value out of range. Effect: Installation continues; previous question is repeated. A message showing permissible values is displayed. Description: The value given in response to the previous question was out of range or was not valid. ______________________Action:__Enter_a_value_that_is_valid. Error Recovery I-5 _________________________________________________________________ Index B determining free space, A-2 _______________________________ devices backing up system disks, 1-2 attributes, F-1 Bill of Materials, 1-1 disk space, 1-5 doconfig, 2-14 C______________________________ CD-ROM E______________________________ Online Documentation Library, error 1-1 recovery, I-1 Software Product Library, error messages 1-1 controlled interrupts, I-2 Configuration Test Procedure See CTP H______________________________ controlled interrupts, I-1, hardware requirements, 1-4 I-2 HDLC component CTF installation, D-1 subsets CTF Collector Components, I______________________________ B-1 installation kit CTF User Environment, B-1 contents, 1-1 CTP, 3-1 installation requirements disk space, 1-5 D______________________________ hardware, 1-4 DECnet/OSI Kernel Components privileges, 1-4 (subset), B-2 installation script DECnet/OSI Network Management starting, 2-4 (subset), B-2 Installation Verification DECnet/OSI Network Management Procedure GUI (subset), B-2 See IVP deinstalling subsets, 2-14 Index-1 installing WAN Support for DIGITAL UNIX, 2-4 N______________________________ interrupt, I-2 null modem wiring, H-1 controlled, I-1 error messages, I-2 P uncontrolled, I-1 _______________________________ ISDN Base Components (subset), PAK, 1-3 B-2 Product Authorization Key ISDN Driver Components See PAK (subset), B-2 isdnevl, 3-2 R______________________________ isdnstat, 3-2 Release Notes, 1-1 IVP, 2-14, 3-1, C-1 removing subsets, 2-14 error conditions device loopback test, C-8 S driver loopback test, C-8 _______________________________ HDLC loopback test, C-9 setld, 2-12 local loopback test, C-9 subsets remote loopback test, C-9 CTAANAL301, B-1 Licence Management Facility, CTABASE301, B-1 C-7 CTF Collector Components, tests performed B-1 device loopback, C-3 CTF User Environment, B-1 driver loopback, C-2 DECnet/OSI Kernel Components, HDLC loopback, C-6 B-2 local loopback, C-4 DECnet/OSI Network Management remote loopback, C-5 , B-2 DECnet/OSI Network Management L______________________________ GUI, B-2 License Product Authorization deinstalling, 2-14 Key DNAKBIN401, B-2 See PAK DNANETMAN401, B-2 license registration, 1-3 DNANETMANGUI401, B-2 LMF, 1-3 interdependencies, B-2 ISDBASE300, B-2 M ISDN Base Components, B-2 _______________________________ ISDN Driver Components Media Software Distribution DEC 3000, B-2 Kit, 1-1 list, B-1 removing, 2-14 selecting, B-1 sizes, A-1 WAN Kernel Programming Tools, B-1 WAN Utilities Base, B-1 Index-2 subsets (cont'd) WDABASE300, B-2 W______________________________ WDADATALNKS300, B-2 WANDD Installation WDADRIVERS300, B-2 Verification Procedure WDAEXAMPLES300, B-2 See IVP WDAMAN300, B-2 WAN Kernel Programming Tools WDD Base Component, B-2 subset, B-1 WDD Datalink Protocols, B-2 wansetup, 2-13, 2-14 WDD Example Programs, B-2 wanshutdown, 2-14 WDD Manual Pages, B-2 WAN Support for DIGITAL UNIX WDD Synchronous Device installation, 2-1 Drivers, B-2 WAN Utilities Base (subset), X.25 Base Component, B-1 B-1 X.25 Example Programs, B-1 WDD Base Component (subset), X.25 IP Support, B-1 B-2 X.25 Manual Pages, B-1 WDD Datalink Protocols X.25 Relay, B-2 (subset), B-2 XXAACC300, B-1 WDD Example Programs (subset), XXAEXAMPLES300, B-1 XXAIP300, B-1 B-2 XXAMAN300, B-1 WDD Manual Pages (subset), B-2 XXARLY300, B-2 wddsetup, E-1 ZZAKPGMR300, B-1 WDD Synchronous Device Drivers ZZAUTIL301, B-1 (subset), B-2 system disks WDD synchronous Device Drivers backing up, 1-2 component installation, E-1 T______________________________ time X______________________________ See installation time X.25 Base Component (subset), B-1 U______________________________ X.25 Configuration Test uncontrolled interrupts, I-1 Procedure utilities See CTP doconfig, 2-14 X.25 Example Programs (subset) isdnevl, 3-2 , B-1 isdnstat, 3-2 X.25 IP Support (subset), B-1 setld, 2-12 X.25 Manual Pages (subset), wansetup, 2-13, 2-14 B-1 wanshutdown, 2-14 X.25 Relay (subset), B-2 wddsetup, E-1 Index-3