DECnet/OSI_for_Digital_UNIX_________________________ Installation and Configuration Order Number: AA-Q0H3E-TE June 1996 This book explains how to install and configure the DECnet/OSI for Digital UNIX software and how to perform the postinstallation steps. Revision/Update Information: This manual supersedes the DECnet/OSI for Digital UNIX Installation and Configuration, Version 3.2. Operating System: Digital UNIX Version 4.0 Software Version: DECnet/OSI Version 4.0 for Digital UNIX Digital Equipment Corporation Maynard, Massachusetts ________________________________________________________________ June 1996 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 conducts its business in a manner that conserves the environment and protects the safety and health of its employees, customers, and the community. © Digital Equipment Corporation 1996. All rights reserved. The following are trademarks of Digital Equipment Corporation: Bookreader, DDCMP, DEC, DECdirect, DECnet, DECNIS, DECserver, DECsystem, DECwindows, Digital, DNA, InfoServer, OpenVMS, ULTRIX, VAX, VAX DOCUMENT, VAXstation, VMS, and the DIGITAL logo. The following are third-party trademarks: OSF/1 is a registered trademark of Open Software Foundation, Inc. OSI is a registered trademark of CA Management, Inc. UNIX is a registered trademark in the United States and other countries, licensed exclusively through X/Open Co., Ltd. All other trademarks and registered trademarks are the property of their respective holders. _________________________________________________________________ Contents Preface................................................... ix Part I Planning for the Installation 1 Planning for the Installation 1.1 Steps to a Successful Installation............ 1-1 1.1.1 Planning Tasks............................ 1-2 1.1.2 Installation Tasks........................ 1-3 1.1.3 Configuration Tasks....................... 1-3 1.1.4 Postinstallation Tasks.................... 1-4 1.2 Deciding Which Software Subsets to Install.... 1-4 1.2.1 Subsets to Install for Full-Capability DECnet/OSI Installation................... 1-5 1.2.2 Subsets to Install for DECnet for Small Configurations (DNALITE).................. 1-12 1.2.3 Subsets to Install for RFC 1006-Only Installation.............................. 1-14 1.2.4 Subsets for MOP-Standalone Installation... 1-15 1.3 Your Software License PAK..................... 1-16 1.3.1 The End System PAK........................ 1-17 1.3.2 The Extended System PAK................... 1-18 Part II DECnet/OSI Installation and Configuration iii 2 Installing DECnet/OSI for Digital UNIX 2.1 Preparing Your System for Installation........ 2-1 2.1.1 Acquiring Superuser Privileges............ 2-2 2.1.2 Checking Your Disk Space.................. 2-2 2.1.2.1 Disk Space Requirements for Full-Capability DECnet/OSI Installation............................ 2-2 2.1.2.2 Disk Space Requirements for DECnet Small Configurations (DNALITE) Installation... 2-3 2.1.2.3 Disk Space Requirements for RFC 1006-Only Installation.................. 2-3 2.1.2.4 Disk Space Requirements for MOP-Standalone Installation............. 2-3 2.1.3 Performing System Backup.................. 2-3 2.1.4 Deleting Old Versions of DECnet/OSI....... 2-3 2.1.4.1 Deleting Subsets........................ 2-4 2.1.5 Using LMF to Register Your Software License PAK............................... 2-6 2.1.6 Creating a Guest Account.................. 2-8 2.1.7 Deciding on the Type of Installation...... 2-9 2.2 Copying the Subsets from the Distribution Media......................................... 2-11 2.2.1 CD-ROM Installation....................... 2-11 2.2.2 Using RIS Over a Local Area Network....... 2-12 2.2.3 Selecting the Software Subsets............ 2-12 2.2.3.1 Full-Capability DECnet/OSI Installation............................ 2-15 2.2.3.2 DECnet for Small Configurations (DNALITE) Installation.................. 2-15 2.2.3.3 RFC 1006-Only Installation.............. 2-16 2.2.3.4 MOP-Standalone Installation............. 2-17 2.2.3.5 DECnet Over TCP/IP...................... 2-17 2.2.3.6 DECnet-Internet Gateway................. 2-18 2.2.3.7 OSI Applications Software............... 2-18 2.2.4 Installing the Software on Your System.... 2-19 2.2.4.1 Completion Messages..................... 2-20 2.3 Choosing a Configuration Procedure............ 2-21 2.4 Configuration Interfaces...................... 2-22 2.4.1 Terminal-Based Configuration Interface.... 2-22 iv 2.4.2 Graphical Configuration Interface......... 2-23 2.4.2.1 Options Provided from the Menu Bar...... 2-25 2.4.2.2 Toggle Switches......................... 2-29 2.4.2.3 Function Buttons........................ 2-30 2.4.2.4 Customizing Your Local Implementation of the Graphical Interface................. 2-32 3 Basic Configuration 3.1 When to Use the Basic Configuration........... 3-1 3.2 About the Basic Configuration Procedure....... 3-2 3.2.1 Changing Your Answers..................... 3-3 3.2.2 Default Values............................ 3-3 3.2.3 Stopping the Configuration Procedure...... 3-4 3.2.4 Getting Help.............................. 3-4 3.3 Basic Configuration Defaults.................. 3-4 3.3.1 Phase IV Prefix........................... 3-4 3.3.2 Node Synonym Directory.................... 3-4 3.3.3 Naming Search Path........................ 3-5 3.3.4 Network Addresses......................... 3-5 3.3.5 DECdns, DTSS, and Servicing of MOP Requests.................................. 3-5 3.4 How DECnet/OSI Uses the Naming Search Path.... 3-5 3.4.1 Configuring the Naming Search Path........ 3-7 3.4.2 Displaying the Search Path Information.... 3-8 3.4.3 Modifying the Naming and Backtranslation Search Paths.............................. 3-8 3.5 Starting the Configuration Procedure.......... 3-10 3.5.1 Starting the Terminal-Based Script........ 3-10 3.5.2 Starting the Graphical Interface.......... 3-11 3.6 Specifying Your DECnet/OSI Node Name.......... 3-11 3.6.1 Using a Local Namespace................... 3-13 3.6.2 Using a DECdns Distributed Namespace...... 3-14 3.6.3 Using the DNS/BIND Naming Service......... 3-14 3.7 Giving Your System a Node Synonym............. 3-14 3.7.1 Specifying Your Node Synonym.............. 3-15 3.8 Communicating with Phase IV Nodes............. 3-15 3.8.1 Supplying an Address...................... 3-16 3.9 Configuring Multiple Communications Devices... 3-16 3.10 Configuring a Token Ring Communications Device........................................ 3-17 3.10.1 Setting the Token Ring Station Speed...... 3-17 v 3.11 Confirming Your Answers and Starting the DECnet/OSI Software........................... 3-18 3.11.1 Additional Configuration Tasks............ 3-21 3.12 Configuring the DECnet-Internet Gateway....... 3-22 3.13 Configuring the OSI Applications Software..... 3-22 3.14 Verifying the Basic Configuration Procedure... 3-22 4 Advanced Configuration 4.1 When to Use the Advanced Configuration........ 4-2 4.1.1 About the Advanced Configuration Procedure................................. 4-4 4.1.1.1 Changing Your Answers................... 4-5 4.1.1.2 Default Values.......................... 4-5 4.1.1.3 Stopping the Configuration Procedure.... 4-5 4.1.1.4 Getting Help............................ 4-6 4.2 How DECnet/OSI Uses the Naming Search Path.... 4-6 4.2.1 Configuring the Naming Search Path........ 4-7 4.2.2 Displaying the Search Path Information.... 4-8 4.2.3 Modifying the Naming and Backtranslation Search Paths.............................. 4-9 4.3 Starting the Configuration Procedure.......... 4-11 4.3.1 Starting the Terminal-Based Script........ 4-11 4.3.2 Starting the Graphical Interface.......... 4-12 4.4 Specifying Your DECnet/OSI Node Name.......... 4-12 4.4.1 Using a Local Namespace................... 4-14 4.4.2 Using a DECdns Distributed Namespace...... 4-15 4.4.3 Using the DNS/BIND Naming Service......... 4-15 4.5 Giving Your System a Node Synonym............. 4-15 4.5.1 Specifying Your Node Synonym.............. 4-16 4.6 Communicating with Phase IV Nodes............. 4-16 4.6.1 Supplying an Address...................... 4-17 4.6.2 Supplying a Phase IV Prefix............... 4-17 4.7 Using an Alternate Node Synonym Directory..... 4-18 4.8 Configuring Network Addresses................. 4-18 4.8.1 Choice 1: Autoconfiguring Addresses....... 4-19 4.8.2 Choice 2: Manually Configuring Addresses................................. 4-19 4.8.2.1 If You Have a Phase IV Compatible Address................................. 4-20 4.8.2.2 If You Do Not Have a Phase IV Compatible Address................................. 4-21 4.9 Configuring Multiple Communications Devices... 4-21 vi 4.10 Configuring a Token Ring Communications Device........................................ 4-22 4.10.1 Setting the Token Ring Station Speed...... 4-22 4.11 Configuring DECdts............................ 4-23 4.11.1 Configuring Your System as a DECdts Clerk or Server................................. 4-24 4.12 Configuring the DECnet-Internet Gateway....... 4-24 4.13 Configuring DECnet Applications to Run Over a TCP/IP Connection............................. 4-25 4.14 Configuring to Service MOP Requests........... 4-26 4.15 Confirming Your Answers and Starting the DECnet/OSI Software........................... 4-26 4.15.1 Additional Configuration Tasks............ 4-29 4.16 Configuring DECnet/OSI to Use Wide Area Networking Support for Digital UNIX and X.25 Services...................................... 4-30 4.16.1 Addressing Issues......................... 4-31 4.16.2 How to Configure DECnet/OSI to Use X.25... 4-33 4.16.2.1 Configuring OSI Transport to Use CONS... 4-34 4.16.2.2 Configuring Routing to Use an X.25 Dynamically Established Data Link....... 4-35 4.16.2.3 Testing OSI Transport Over CONS......... 4-36 4.16.2.4 Using CONS Attributes................... 4-37 4.16.3 Using dnax25setup to Complete X.25 Configuration............................. 4-37 4.17 Configuring Mailsetup......................... 4-37 4.18 Configuring the OSI Applications Software..... 4-37 4.19 Verifying the Advanced Configuration Procedure..................................... 4-38 5 Postinstallation Tasks 5.1 Finishing the Name Service Configuration...... 5-1 5.1.1 Finishing the Local Namespace Configuration............................. 5-2 5.1.2 Finishing the DECdns Namespace Configuration............................. 5-2 5.1.2.1 Connecting to a Remote Server in a DECdns Distributed Namespace............ 5-4 5.1.3 Finishing the DNS/BIND Configuration...... 5-5 5.2 Performing Local and DECdns Namespace Activities.................................... 5-5 vii 5.2.1 Local Namespace Tasks..................... 5-5 5.2.1.1 Update_Nodes............................ 5-6 5.2.1.2 Running Update_Nodes.................... 5-6 5.2.1.3 Copying a DECnet Phase IV Node Database................................ 5-7 5.2.2 DECdns Distributed Namespace Tasks........ 5-7 5.2.2.1 Registering Subsequent DECnet/OSI Systems................................. 5-7 5.2.2.2 First DECnet/OSI System on a Network with Phase IV Nodes .................... 5-8 5.2.2.3 First DECnet/OSI System on a Network with No Phase IV Nodes ................. 5-9 5.3 Configuring the DECnet-Internet Gateway....... 5-9 5.3.1 Testing the DECnet-Internet Gateway....... 5-10 6 Running the Configuration Verification Procedure 6.1 Configuration Verification Procedure Requirements.................................. 6-1 6.2 Running the Configuration Verification Procedure..................................... 6-1 6.2.1 Supplying a Full Name..................... 6-2 6.2.2 Checking the State of DECnet/OSI.......... 6-2 6.2.3 Checking the DECdns Clerk................. 6-3 6.2.4 Reaching a Remote System.................. 6-4 6.2.5 Testing Local and Remote Systems.......... 6-5 Part III Configuration for FTAM and Virtual Terminal 7 Configuring FTAM and Virtual Terminal 7.1 FTAM and Virtual Terminal Installation........ 7-1 7.2 FTAM and Virtual Terminal Terminology......... 7-1 7.3 About the OSI Application Entity Database..... 7-2 7.4 Getting Started Configuring Initiating and Responding Entities........................... 7-2 7.4.1 Setting Up Responding Entities............ 7-3 7.4.2 Setting Up Initiating Entities............ 7-4 7.4.3 Example: Performing an FTAM File Copy..... 7-5 7.4.4 Example: Performing a Virtual Terminal Login..................................... 7-8 7.5 About /usr/sbin/osiapplsetup.................. 7-10 7.5.1 About Configuring Local Addresses......... 7-11 viii 7.5.2 Getting Help, Stopping the Configuration Procedure, and Using Defaults............. 7-12 7.6 Starting the OSI Applications Configuration Procedure..................................... 7-21 7.7 Autoconfiguring Local Addresses............... 7-22 7.8 Manually Configuring Local Addresses.......... 7-29 7.8.1 Configuring OSI Transport Listeners....... 7-30 7.8.2 Configuring RFC 1006 Transport Listeners................................. 7-31 7.8.3 Configuring Source Aliases................ 7-32 7.8.4 Configuring X.500 Entries for Local Listeners................................. 7-33 7.8.5 Starting Listeners........................ 7-35 7.8.6 Running the FTAM and VT IVPs.............. 7-36 7.8.7 Exiting the Manual Configuration Procedure................................. 7-37 7.9 Configuring Addresses for Remote FTAM and VT Applications.................................. 7-38 7.9.1 Adding Distinguished Name Format Entries................................... 7-39 7.9.2 Adding Address Format Entries............. 7-41 7.9.3 Adding Pattern Format Entries............. 7-43 7.9.4 Exiting Remote Address Configuration...... 7-45 7.10 Configuring Local Listeners for Startup....... 7-46 7.11 Rebuilding the Internal Table of Commands..... 7-48 7.12 Verifying the Installation.................... 7-48 7.13 Verifying the FTAM-FTP Gateway Installation .............................................. 7-48 7.13.1 To Check the OSI Portion of the FTAM-FTP Gateway................................... 7-48 7.13.2 To Check the Internet Portion of the FTAM-FTP Gateway.......................... 7-49 Part IV Appendixes ix A Sample DECnet/OSI Installations A.1 Sample Log for Full-Capability Installation... A-1 A.2 Sample Log for a DECnet for Small Configurations (DNALITE) Installation......... A-6 A.3 Sample Log for RFC 1006-Only Installation..... A-8 A.4 Sample Log for MOP-Standalone Installation.... A-10 B Sample DECnet/OSI Configurations B.1 Sample DECnet/OSI Advanced Configuration...... B-1 B.2 Sample DECnet/OSI Basic Configuration......... B-6 B.3 Sample RFC 1006 Configuration................. B-10 B.4 Sample MOP-Standalone Configuration........... B-10 B.5 Sample X.25 Configuration..................... B-11 B.6 Sample Configuration Verification Procedure... B-13 C Software Subsets and Installation Requirements C.1 DECnet/OSI for Digital UNIX Software Subsets....................................... C-1 Index Figures 2-1 Graphical Interface for Basic Configuration ............................ 2-23 2-2 Graphical Interface for Advanced Configuration ............................ 2-24 3-1 Basic Configuration Checklist............. 3-2 4-1 Advanced Configuration Checklist.......... 4-2 Tables 1-1 Full-Capability DECnet/OSI Installation - Required Software Subsets................. 1-6 1-2 Full-Capability DECnet/OSI Installation - Optional Software Subsets................. 1-7 1-3 Installation for Small Configurations (DNALITE) - Required Subsets.............. 1-12 x 1-4 Installation for Small Configurations (DNALITE) - Optional Subsets.............. 1-14 1-5 RFC 1006-Only Installation................ 1-15 1-6 MOP-Standalone Installation............... 1-16 2-1 Choosing the Installation Type............ 2-10 2-2 Graphical Interface Options............... 2-25 2-3 Toggle Switches........................... 2-29 2-4 Function Buttons.......................... 2-31 7-1 Autoconfiguration Checklist............... 7-13 7-2 Manual Configuration Checklist............ 7-15 7-3 Remote Application Checklist.............. 7-17 7-4 Listener Startup Worksheet................ 7-18 7-5 Address Format Worksheet.................. 7-19 7-6 Distinguished Name Format Worksheet....... 7-20 7-7 Pattern Format Worksheet.................. 7-21 C-1 Summary of DECnet/OSI Software Subsets and Disk Space................................ C-1 xi _________________________________________________________________ Preface Intended Audience This book is for a user installing DECnet/OSI software on a running Digital UNIX[R] system; ideally, a person who has system administration experience. If the system being installed is the first DECnet/OSI node in the network, the installer should read the DECnet /OSI Planning Guide before attempting the installation. The DECnet/OSI Planning Guide contains important planning activities to perform before the DECnet/OSI installation. Document Structure This document consists of four parts: o Part I-Describes the main steps for planning a successful installation of DECnet/OSI. It includes the following chapter: - Chapter 1 - Planning for the Installation. o Part II-Explains how to install and configure DECnet/OSI for Digital UNIX and how to perform the postinstallation tasks. Part II includes the following chapters: - Chapter 2 - Installing DECnet/OSI for Digital UNIX - Chapter 3 - Basic Configuration - Chapter 4 - Advanced Configuration - Chapter 5 - Postinstallation Tasks - Chapter 6 - Running the Installation and Verification Procedure ix o Part III-Explains how to configure the File Transfer, Access, and Management (FTAM) software and Virtual Terminal (VT) software. It includes the following chapter: - Chapter 7 - Configuring FTAM and Virtual Terminal o Part IV-Includes sample installations and configurations and discusses the software subsets and installation requirements. It includes the following appendixes: - Appendix A - Sample DECnet/OSI Installations - Appendix B - Sample DECnet/OSI Advanced and Basic Configurations - Appendix C - Software Subsets and Installation Requirements Related Documents The DECnet/OSI for Digital UNIX Introduction and User's Guide lists the documents included with the DECnet/OSI distribution kit. For information on the DECnet/OSI products and services, access the Digital OpenVMS World Wide Web site. Use the following URL: http://www.openvms.digital.com Reader's Comments Digital welcomes your comments on this manual or any of the DECnet/OSI documents. Send us your comments through any of the following channels: Internet openvmsdoc@zko.mts.dec.com Fax 603 881-0120, Attention: OSSG Documentation, ZKO3-4/U08 Mail OSSG Documentation Group, ZKO3-4/U08 110 Spit Brook Rd. Nashua, NH 03062-2698 x How To Order Additional Documentation Use the following table to order additional documentation or information. If you need help deciding which documentation best meets your needs, call 800-DIGITAL (800-344-4825). Conventions The following conventions apply to this book. ___________________________________________________________ Convention_______Meaning___________________________________ special type Indicates a literal example of system output or user input. In text, indicates command names, keywords, node names, file names, directories, utilities, and tools. On a Digital UNIX system, enter the word or phrase in the exact case shown. italic Indicates a variable. bold Indicates a new term defined either in the text or in the DECnet/OSI for Digital UNIX Introduction and User's Guide. Indicates that you press the Return key. Indicates that you press the Control key while you type the key noted by x. [ ] In command format descriptions, indicates optional elements. You can enter as many as you want. { } In command format descriptions, indicates you must enter at least one listed element. % The standard Digital UNIX system prompt. # The Digital UNIX superuser prompt. xi ___________________________________________________________ Convention_______Meaning___________________________________ command() Cross-references to specific command documentation include the section number in the reference book where the commands are documented. For example, ocp(1) indicates that you can find the material on the ocp command in Section 1 of the reference pages. ... Indicates that the preceding item can be _________________repeated_one_or_more_times._______________ All Ethernet addresses are hexadecimal; all other numbers are decimal unless otherwise noted. xii Part I _________________________________________________________________ Planning for the Installation Part I describes the main steps for planning a successful installation of DECnet/OSI and summarizes the steps to take after completing your installation. It includes the following chapter: o Chapter 1-Planning for the Installation 1 _________________________________________________________________ Planning for the Installation This chapter discusses the major steps for planning a successful installation of DECnet/OSI. Before you begin, read the DECnet/OSI Planning Guide and refer to the DECnet/OSI DECdns Management guide to help you decide whether to use the Local namespace, a DECdns distributed namespace, or the Domain Name System (DNS)/BIND distributed name service (for TCP/IP). DECnet/OSI allows you to use either a distributed namespace or a local namespace as your primary name service. The main function of DNS/BIND is to map names to IP addresses and provide name-to-address translations in response to queries. DNS also supports other record types such as network service access points (NSAPs) and is commonly used for supporting mail addressing (MX records). BIND (Berkeley Internet Name Domain) is a UNIX implementation of DNS. 1.1 Steps to a Successful Installation There are four major task areas necessary for installing your software: o Planning o Installation o Configuration o Postinstallation Planning for the Installation 1-1 1.1.1 Planning Tasks Before you set up a new DECnet/OSI network, you need to: o Document the proposed network configuration. o Develop an implementation strategy. o Evaluate software options. You should complete the appropriate checklist for your configuration. Refer to: o Figure 3-1 for basic configuration o Figure 4-1 for advanced configuration These checklists help to ensure that you have all the information you need to configure the DECnet/OSI software on your system. Consider these planning questions: o What namespace will you use? Will you use a Local namespace? Or, will you make your system a DECdns clerk and join an existing DECdns distributed namespace? o Will your node be a DECdns server? o How will you use DECdts? Will your system be a DECdts clerk or server? o Will you use only the basic Phase IV DECnet functionality (file transfer, remote login, send and receive electronic mail)? o Do you have a system with memory and disk space limitations that might restrict which DECnet software subsets can be supported? o Do you need only to run the Maintenance Operations Protocol (MOP) standalone? o Do you need only RFC 1006 software (to run OSI applications over TCP/IP)? o Which configuration procedure will you use, basic or advanced? 1-2 Planning for the Installation 1.1.2 Installation Tasks Prepare your system and load it with the software subsets. Chapter 2 describes how to perform these installation tasks: o Check your system's available disk space. Section 1.2 indicates disk space requirements for installing the software of your choice. o Choose the software subsets you want to install and copy the subsets from the distribution media to your system's disk. o Ensure you have the correct Product Authorization Key (PAK) and that your software license is registered. ________________________ Note ________________________ DECnet/OSI for Digital UNIX supports the Digital UNIX features of symmetric multiprocessing (SMP) and the dynamic loading of kernel components. This dynamic loading capability eliminates the requirement to build the kernel after installing a layered product such as DECnet/OSI. ______________________________________________________ 1.1.3 Configuration Tasks Use the guidelines in Section 2.3 to determine the configuration procedure you should use; then refer to the indicated chapter for a description of the procedure. Configure the software using the appropriate procedure. Examples of configuration tasks include: o Specifying system name and address information o Selecting a namespace for your own system o Selecting how your system will use DECdts o Specifying optional parameters such as multiple communications devices and distributed namespace information o Configuring your system to use the File Transfer, Access, and Management (FTAM) and Virtual Terminal (VT) software Planning for the Installation 1-3 1.1.4 Postinstallation Tasks After configuration, you might have to perform additional tasks to assure your system's operation in the network. The postinstallation tasks for your system will vary depending upon your system's configuration. Chapter 5 and Chapter 6 describe postinstallation tasks. Other tasks are described in DECnet/OSI Network Management and DECnet/OSI DECdns Management. Examples of postinstallation tasks include: o Registering the first DECnet/OSI system on the network o Running the configuration verification procedure o Configuring OSI applications (FTAM and Virtual Terminal) o Configuring DECdns server software with a new namespace ( DECnet/OSI DECdns Management) 1.2 Deciding Which Software Subsets to Install Before you begin the installation, decide which subsets you need to install and assess the memory and disk space limits for your system. You can choose from four types of installations: o Full-capability DECnet/OSI - For systems requiring DECnet/OSI functionality, such as OSI, RFC 1006 (OSI over TCP/IP), DECnet over TCP/IP, or X.25 software. Section 1.2.1 describes the subsets and associated requirements for this installation. o DECnet for Small Configurations (DNALITE) - For systems with limited disk space and memory, or requiring only basic DECnet Phase IV functionality (mail, file transfer, and remote login). Section 1.2.2 describes the subsets and associated requirements to install for this installation. (The DECnet for Small Configurations software supports DECnet over TCP/IP.) o RFC 1006-only - For systems requiring only the RFC 1006 feature to run OSI applications over TCP/IP. Section 1.2.3 describes the subsets and associated requirements to install for this installation. 1-4 Planning for the Installation o MOP-standalone - For systems requiring the Maintenance Operations Protocol (MOP) to run standalone (without DECnet/OSI software). Section 1.2.4 describes the subsets and associated requirements for this installation. Appendix C lists all subsets alphabetically. 1.2.1 Subsets to Install for Full-Capability DECnet/OSI Installation Table 1-1 gives information about the required subsets that provide a minimum configuration for the full-capability DECnet installation, and Table 1-2 gives information about the optional subsets for additional functionality. The dependencies indicated for each subset are the other subsets that must be installed prior to the given subset. The minimum full-capability DECnet/OSI installation (that is, without the optional subsets) requires approximately 32 MB of disk space on your system. For more details, see Section 2.1.2.1. ________________________ Note ________________________ The OSFBASE400 and OSFDCMT400 subsets mentioned as dependencies in these tables are described as follows: o OSFBASE400-Digital UNIX Base System o OSFDCMT400-Digital UNIX Document Preparation Tools ______________________________________________________ Planning for the Installation 1-5 Table 1-1 Full-Capability DECnet/OSI Installation - Required __________Software_Subsets_______________________________________ Disk Space Subset_________Function___________________(KB)_______Dependencies DECnet/OSI Provides the DECnet/OSI 6266 OSFBASE400 Base for Digital UNIX function /usr DNANETMAN400 Components that enables you to share DNABASE400 information with remote DECnet users and programs over the network. This subset includes the DECdns clerk and DECdts components. (The DECdns server is in a separate subset, DNADNSSRV400. See Table 1-2.) This subset also includes the FTAM and Virtual Terminal OSI applications. (FTAM allows file operations with other systems that contain a FTAM implementation. Virtual Terminal enables network terminal access to systems that are OSI- compliant.) DECnet/OSI Provides the elements of 0 OSFBASE400 Kernel the base components in /usr Components the UNIX kernel required 1405 DNAKBIN400 for DECnet functionality. /var DECnet/OSI Provides the Network 11027 OSFBASE400 Network Command Language (NCL) /usr Management components that you use DNANETMAN400 to manage DECnet/OSI for Digital UNIX. (continued on next page) 1-6 Planning for the Installation Table 1-1 (Cont.) Full-Capability DECnet/OSI Installation - __________________Required_Software_Subsets______________________ Disk Space Subset_________Function___________________(KB)_______Dependencies _________________________________________________________________ Total (KB) 17293 /usr 3405 /var+ +The_total_for_/var_includes_2000_KB_for_the_installation._______ _________________________________________________________________ Table 1-2 Full-Capability DECnet/OSI Installation - Optional __________Software_Subsets_______________________________________ Disk Space Subset_________Function___________________(KB)_______Dependencies CTF Collector Common Trace Facility 1986 OSFBASE400 Component (CTF), a tool used for /usr ZZAUTIL300 CTABASE300 tracing DECnet/OSI end 486 systems and routers. /var CTF User Provides utilities for 4342 OSFBASE400 Environment analyzing trace data. /usr CTABASE300 CTAANAL300 (continued on next page) Planning for the Installation 1-7 Table 1-2 (Cont.) Full-Capability DECnet/OSI Installation - __________________Optional_Software_Subsets______________________ Disk Space Subset_________Function___________________(KB)_______Dependencies DECdns Server The Digital Distributed 1015 OSFBASE400 DNADECDNSSRV400Name Service (DECdns) /usr DNABASE400 server enables a DNATRANSITION400 DECnet/OSI system to function as a DECdns server in a DECdns distributed namespace. If you are installing this subset, you need to also install the DECnet/OSI Transition Tools subset (DNATRANSITION400). (continued on next page) 1-8 Planning for the Installation Table 1-2 (Cont.) Full-Capability DECnet/OSI Installation - __________________Optional_Software_Subsets______________________ Disk Space Subset_________Function___________________(KB)_______Dependencies DECnet/OSI The DECnet-Internet 254 DNABASE400 Gateways Gateway provides mail, /usr DNAGATEWAYS400 remote login, and file transfer interoperability between DECnet systems and Internet (TCP/IP) systems using your system as a gateway. The FTAM- FTP gateway enables file operations between OSI systems and Internet (TCP/IP) systems. The VT/Telnet gateway provides bidirectional communications between an OSI system and an Internet system. The LAT /VT gateway provides communications from a LAT system to a remote OSI system. The VT/CTERM gateway provides bidirectional communications between an OSI system and a DECnet system. (continued on next page) Planning for the Installation 1-9 Table 1-2 (Cont.) Full-Capability DECnet/OSI Installation - __________________Optional_Software_Subsets______________________ Disk Space Subset_________Function___________________(KB)_______Dependencies DECnet/OSI Contains utilities and 1365 OSFBASE400 Miscellaneous sample software supplied /usr Software on an "as-is" basis for DNAUTIL400 general customer use. However, Digital neither supports these utilities nor covers them under any Digital support contracts. DECnet/OSI Downloads workstations 423 DNANETMAN400 MOP Utilities and terminal servers. /usr DNAKBIN400 DNAMOP400 Used by utilities such as Remote Installation Service (RIS). DECnet/OSI The Network Management 2281 DNANETMAN400 Network GUI (dna_mgmt) provides /usr Management a hierarchical graphical Graphical approach to managing User DECnet/OSI. The dna_ Interface mgmt utility provides DNANETMANGUI400an easy way to become familiar with management modules, entities, and subentities, as well as with Network Control Language (NCL) syntax. DECnet/OSI Provides libraries and 6644 OSFBASE400 Programming header files necessary /usr Tools to write programs to DNAPGMR400 the DECnet and OSI interfaces. (continued on next page) 1-10 Planning for the Installation Table 1-2 (Cont.) Full-Capability DECnet/OSI Installation - __________________Optional_Software_Subsets______________________ Disk Space Subset_________Function___________________(KB)_______Dependencies DECnet/OSI Provides online system 65 OSFDCMT400 Reference reference information. /usr Pages Gives the diagnostic DNAMAN400 messages, restrictions, and examples for commands, system calls, and subroutines. Also provides online reference information for OSI applications. Gives the syntax, description, diagnostic messages, and restrictions for FTAM and Virtual Terminal commands and routines. DECnet/OSI Provides system and 1095 OSFBASE400 Transition network managers with /usr DNABASE400 Tools tools to ease the DNATRANSITION40transition from DECnet Phase IV to DECnet/OSI. Digital UNIX Provides utilities used 1228 OSFBASE400 WAN Utilities by the Common Trace /usr ZZAUTIL300 Facilities. Also used 245 by the WANDD and X.25 /var software (Wide Area Networking Support for Digital UNIX). _________________________________________________________________ Total (KB) 19713 /usr ____________________________________________731/var______________ Planning for the Installation 1-11 1.2.2 Subsets to Install for DECnet for Small Configurations (DNALITE) Table 1-3 describes the required subsets for the DECnet for Small Configurations (DNALITE) installation. Table 1-4 describes the optional subsets that you can install. The dependencies indicated for each subset are the other subsets that must be installed prior to the given subset. The minimum DNALITE installation (that is, without the optional subsets) requires approximately 13 MB of disk space on your system. For more details, see Section 2.1.2.2. Table 1-3 Installation for Small Configurations (DNALITE) - __________Required_Subsets_______________________________________ Disk Space Subset_________Function___________________(KB)_______Dependencies (continued on next page) 1-12 Planning for the Installation Table 1-3 (Cont.) Installation for Small Configurations (DNALITE) __________________-_Required_Subsets_____________________________ Disk Space Subset_________Function___________________(KB)_______Dependencies DECnet Provides DECnet/OSI for 10131 DNAKBIN400 for Small systems with limited /usr Configurations memory or disk space or requiring nothing DNALITE400 more than the basic Phase IV functionality (file transfer, remote login, and mail). The DECnet functionality is contained in only one subset. DNALITE includes parts of the DECnet /OSI subsets that are necessary for the basic Phase IV functionality. Optionally, you can additionally install the DECnet/OSI Reference Pages (DNAMAN400) and DECnet/OSI Miscellaneous Software (DNAUTIL400) subsets. DECnet/OSI Provides the elements of 0 OSFBASE400 Kernel the base components in /usr Components the UNIX kernel required 1405 DNAKBIN400 for DECnet functionality. /var _________________________________________________________________ Total (KB) 10131 /usr 3405 /var+ +The_total_for_/var_includes_2000_KB_for_the_installation._______ _________________________________________________________________ Planning for the Installation 1-13 Table 1-4 Installation for Small Configurations (DNALITE) - __________Optional_Subsets_______________________________________ Disk Space Subset_________Function___________________(KB)_______Dependencies DECnet/OSI Contains utilities and 1365 OSFBASE400 Miscellaneous sample software supplied /usr Software on an "as-is" basis for DNAUTIL400 general customer use. However, Digital neither supports these utilities nor covers them under any Digital support contracts. DECnet/OSI Provides online system 65 OSFDCMT400 Reference reference information. /usr Pages Gives the diagnostic DNAMAN400 messages, restrictions, and examples for commands, system calls, and subroutines. Also provides online reference information for OSI applications. Gives the syntax, description, diagnostic messages, and restrictions for FTAM and Virtual Terminal commands and routines. _________________________________________________________________ Total (KB) 1430 __________________________________________/usr___________________ 1.2.3 Subsets to Install for RFC 1006-Only Installation Table 1-5 describes the subsets you need to install for an RFC 1006-only installation. The dependencies indicated for each subset are the other subsets that must be installed prior to the given subset. 1-14 Planning for the Installation The RFC 1006-only installation requires approximately 11.5 MB of disk space on your system. For more details, see Section 2.1.2.3. Table_1-5_RFC_1006-Only_Installation_____________________________ Disk Space Subset_________Function___________________(KB)_______Dependencies DECnet/OSI Provides the elements of 0 OSFBASE400 Kernel the base components in /usr Components the UNIX kernel required 1405 DNAKBIN400 for DECnet functionality. /var DECnet/OSI Provides the Network 11027 OSFBASE400 Network Command Language (NCL) /usr Management components that you DNANETMAN400 use to manage DECnet /OSI for Digital UNIX. Contains the DECnet/OSI XTI extensions library (libxtiosi.so) needed for RFC 1006. _________________________________________________________________ Total (KB) 11027 /usr 2000 /var+ +The_total_for_/var_includes_2000_KB_for_the_installation._______ _________________________________________________________________ 1.2.4 Subsets for MOP-Standalone Installation Table 1-6 describes the subsets you need to install for a MOP standalone installation. The dependencies indicated for each subset are the other subsets that must be installed prior to the given subset. Planning for the Installation 1-15 The MOP-standalone installation requires approximately 12 MB of disk space on your system. For more details, see Section 2.1.2.4. Table_1-6_MOP-Standalone_Installation____________________________ Subset Subset_________Function___________________Size_______Dependencies DECnet/OSI Provides the elements of 0 OSFBASE400 Kernel the base components in /usr Components the UNIX kernel required 1405 DNAKBIN400 for DECnet functionality. /var DECnet/OSI Provides the Network 11027 OSFBASE400 Network Command Language (NCL) /usr Management components that you DNANETMAN400 use to manage DECnet /OSI for Digital UNIX. Contains the DECnet/OSI XTI extensions library (libxtiosi.so) needed for RFC 1006. DECnet/OSI Downloads workstations 423 DNANETMAN400 MOP Utilities and terminal servers. /usr DNAKBIN400 DNAMOP400 Used by utilities such as Remote Installation Service (RIS). _________________________________________________________________ Total (KB) 11450 /usr 2000 /var+ +The_total_for_/var_includes_2000_KB_for_the_installation._______ _________________________________________________________________ 1.3 Your Software License PAK A software license Product Authorization Key (PAK) enables you to install and use specific software elements. There are two DECnet/OSI for Digital UNIX software PAKS: o End System PAK (DECNET-OSI-END) 1-16 Planning for the Installation o Extended System PAK (DECNET-OSI-EXT) 1.3.1 The End System PAK The following list shows the functionality enabled by the End System PAK: o DECnet/OSI for Digital UNIX - Software that allows a DECnet/OSI system to act as an end node on a DECnet/OSI network. This software also provides the DECnet-Internet Gateway, which offers bidirectional functions between DECnet and Internet systems. o File Transfer, Access, and Management (FTAM) - The OSI application that provides the ability to manipulate files in a multivendor environment. o Virtual Terminal (VT) - Software that supports the ISO Virtual Terminal protocol. Enables remote logins and access to other OSI-compliant systems. o The Digital Distributed Time Service (DECdts) - Provides precise, fault-tolerant clock synchronization for systems in local and wide area networks. o The Digital Distributed Name Service (DECdns) client - Enables a DECnet/OSI system to use DECdns to store and retrieve information. o The Local namespace - A discrete, self-contained local namespace that provides a local database of names. The Local namespace stores all name and addressing information on the system that uses it. Depending on the number of address towers stored, the Local namespace is designed to scale to at least 100,000 nodes. o RFC 1006 - Software that allows OSI applications to run over TCP/IP, based on the Requests for Comments (RFC) 1006 standard. You can install and configure this software independently of DECnet. o DECnet over TCP/IP - Software that allows DECnet applications such as mail, cterm and fal to run over TCP/IP. DECnet over TCP/IP is based on informational RFC 1859, an extension to RFC 1006. Planning for the Installation 1-17 DECnet over TCP/IP uses the TCP/IP and BIND functionality provided by the Digital UNIX operating system. Before configuring DECnet/OSI, the TCP/IP and BIND functionality must be configured on the Digital UNIX operating system. o Wide Area Network device drivers - Provide wide area network connectivity using the High-Level Data Link Control (HDLC) protocol and device drivers for point- to-point full-duplex connections. The DECnet/OSI license includes this functionality which is installed from the Wide Area Networking Support for Digital UNIX software included on the Digital UNIX Layered Product Consolidated Software CD-ROM. o LLC2 Services - ISO 8881, "Use of X.25 Packet Level Protocol in Local Area Networks," provides connection- oriented network service over a local area network to another suitably configured X.25 system on the same LAN. You can also make X.25 logical connections through a connector system using LLC2. The DECnet/OSI license includes this functionality that is installed from the Wide Area Networking Support for Digital UNIX included on the Digital UNIX Layered Product Consolidated Software CD-ROM. o Online Manuals - All the DECnet/OSI and Wide Area Networking Support for Digital UNIX documentation is available in Bookreader format. The DECnet/OSI license includes this functionality, which is available from the Documentation CD-ROM. 1.3.2 The Extended System PAK The Extended System PAK enables these functions: o All components and functions of the End System PAK. o FTAM-FTP gateway - Allows OSI and Internet systems to exchange files with each other. o VT/Telnet gateway - Provides bidirectional communications between an OSI system and an Internet system. o VT/CTERM gateway - Provides bidirectional communications between an OSI system and a DECnet system. 1-18 Planning for the Installation o LAT/VT gateway - Provides communications from a LAT terminal to a remote OSI system. o The Digital Distributed Name Service (DECdns) server - Enables a DECnet/OSI system to function as a DECdns server in a DECdns distributed namespace. Planning for the Installation 1-19 Part II _________________________________________________________________ DECnet/OSI Installation and Configuration Part II explains how to install and configure DECnet/OSI for Digital UNIX and how to perform the postinstallation tasks. Part II includes the following chapters: o Chapter 2 - Installing DECnet/OSI for Digital UNIX o Chapter 3 - Basic Configuration o Chapter 4 - Advanced Configuration o Chapter 5 - Postinstallation Tasks o Chapter 6 - Running the Configuration and Verification Procedure 2 _________________________________________________________________ Installing DECnet/OSI for Digital UNIX This chapter describes how to install the DECnet/OSI software on your system and how to prepare your system for the configuration process. It includes: o Preparing your system for the installation o Copying the software from the distribution media o Rebooting your system o Choosing the correct configuration procedures 2.1 Preparing Your System for Installation Before installing your software, prepare your system by following these steps: 1. Make sure Digital UNIX Version 4.0 is installed on your system. 2. Make sure you have superuser privileges (Section 2.1.1). 3. Check your system's disk space (Section 2.1.2). 4. Back up your system disk (Section 2.1.3). 5. Register your Product Authorization Key (PAK) (Section 2.1.5). 6. Create a guest account in your system password file (Section 2.1.6). 7. Decide whether you want a DNALITE, full-capability DECnet/OSI, RFC 1006-only, or MOP-standalone installation (Section 2.1.7). 8. Decide whether you want a basic or advanced configuration (Section 2.3). Note that neither configuration is necesssary if you are doing an RFC 1006-only or MOP-standalone installation. Installing DECnet/OSI for Digital UNIX 2-1 2.1.1 Acquiring Superuser Privileges To install and configure DECnet/OSI, you must have superuser privileges. The command to acquire superuser privileges is su. You must then enter the root password. Refer to the Digital UNIX Guide to System Administration for details on acquiring superuser privileges. 2.1.2 Checking Your Disk Space Verify that you have enough free disk space to install and configure the software subsets of your choice. The installation could fail if it runs out of disk space while copying the subsets from the distribution media. To check the available disk space in /usr, /var, and root (/), enter these commands: # df -k / # df -k /usr # df -k /var You can find a complete description of the space requirements for each subset in Section 1.2. The whole installation kit requires approximately 65 MB of total disk space including: o 20 KB maximum required in / (root file system) for all subsets o 50 MB in /usr for subsets o 5 MB in /var for database files 2.1.2.1 Disk Space Requirements for Full-Capability DECnet/OSI Installation The minimum full-capability DECnet/OSI installation requires approximately 34 MB of total disk space including: o 20 KB in / (root file system) for all subsets o 20 MB in /usr for subsets o 4 MB in /var for data files Note also that if you load a large number of nodes in the local node database, the disk space requirements for /var increase. 2-2 Installing DECnet/OSI for Digital UNIX 2.1.2.2 Disk Space Requirements for DECnet Small Configurations (DNALITE) Installation The DNALITE installation requires approximately 13 MB of total disk space including: o 11 MB in /usr for the required subsets o 2 MB in /var for data files Note that the requirements and limitations for a DNALITE installation also reflect many of the requirements and limitations for a UNIX installation for small configurations. Note also that if you load a large number of nodes in the local node database, the disk space requirements for /var increase. 2.1.2.3 Disk Space Requirements for RFC 1006-Only Installation The RFC 1006-only installation requires approximately 13 MB of total disk space including: o 11 MB in /usr for the required subsets o 2 MB in /var for data files 2.1.2.4 Disk Space Requirements for MOP-Standalone Installation The MOP-standalone installation requires approximately 14 MB of total disk space including: o 12 MB in /usr for the required subsets o 2 MB in /var for data files 2.1.3 Performing System Backup Before you install the subsets, back up your system disk. For information on backing up your system, refer to Digital UNIX Guide to System Administration. 2.1.4 Deleting Old Versions of DECnet/OSI Before you begin the installation, check to see if a previous version of DECnet/OSI exists on your system. If it does, you must delete the subsets before you install the new DECnet/OSI for Digital UNIX subsets. ________________________ Note ________________________ When you delete existing DECnet/OSI for Digital UNIX subsets, the operation shuts down DECnet, saves any Installing DECnet/OSI for Digital UNIX 2-3 existing DECdns clerk data files, and leaves the existing NCL scripts. The existing DECdns clerk data files will be restored when you install the new DECnet /OSI for Digital UNIX subsets. ______________________________________________________ Use the following command to see if DECnet/OSI subsets are installed on the system, where DNA is the subset name prefix of DECnet/OSI: # setld -i | egrep "^DNA|^CTA|^ZZA" If any subsets with one of these product codes exists on your system, the utility displays an installed message, such as the following example for DECnet/OSI for Digital UNIX Version 3.0: DNABASE300 installed DECnet/OSI Base Components If a previous version of DECnet/OSI exists, use the steps in Section 2.1.4.1 to delete all subsets. Then follow the instructions in Section 2.1.5 to ensure that you have the correct PAK before you continue with the installation. 2.1.4.1 Deleting Subsets To delete the software from your system, log in as superuser and issue the setld command with the -d option, where subset is the name of the DECnet/OSI software subsets you want to delete: # setld -d subset [...] The following example deletes DECnet/OSI V3.2A Miscellaneous Software and DECnet-Internet Gateway subsets: # setld -d DNAUTIL320 DNAINETGW320 Be aware of these considerations when deleting DECnet/OSI software from your system: o If you are removing more than one subset from your system, make sure that you specify the network management subset (DNANETMANxxx) last. Without the network management subset still installed, you cannot delete other subsets. 2-4 Installing DECnet/OSI for Digital UNIX o Other Digital software products require the network management subset (DNANETMANxxx software subset. Before deleting the network management subset, make sure that it is not needed by other products you have installed. For example, the Wide Area Networking Support for Digital UNIX product (X.25) requires this subset. See the other Digital software product documentation to determine if they require the network management subset. You can also use the deinstall feature to delete software from your system. The following example illustrates how to use the decnetsetup deinstall command to deinstall a previous version, with sample output. Note that deinstall does not delete the Common Trace Facility (CTF) subsets. Use the setld -d command to delete any unwanted CTF subsets. # decnetsetup deinstall DECnet/OSI for Digital UNIX V4.0-0 DECnet/OSI Configuration Procedure. There will be a pause while this procedure gathers some information from your system. Copyright (c) Digital Equipment Corporation. 1993-1996. All Rights Reserved. All DECnet/OSI subsets will now be removed from this system. Removing directories and symbolic links for DNADECDNSSRV321 ... done. Deleting "DECnet/OSI DECdns Server " (DNADECDNSSRV321). Removing directories and symbolic links for DNANETMANGUI321 ... done. Deleting "DECnet/OSI Network Management GUI " (DNANETMANGUI321). Removing directories and symbolic links for DNARFC1006321 ... done. Deleting "DECnet/OSI RFC1006 (OSI/TCP) " (DNARFC1006321). Removing directories and symbolic links for DNAPGMR321 ... done. Deleting "DECnet/OSI Programming Tools " (DNAPGMR321). Removing directories and symbolic links for DNAUTIL321 ... done. Deleting "DECnet/OSI Miscellaneous Software " (DNAUTIL321). Removing directories and symbolic links for DNAMAN321 ... done. Deleting "DECnet/OSI Reference Pages " (DNAMAN321). Removing directories and symbolic links for DNAGATEWAYS321 ... done. Deleting "DECnet/OSI Gateways " (DNAGATEWAYS321). Installing DECnet/OSI for Digital UNIX 2-5 Removing directories and symbolic links for DNAMOP321 ... done. Deleting "DECnet/OSI MOP Utilities " (DNAMOP321). Removing directories and symbolic links for ZZAUTIL121 ... done. Deleting "Digital UNIX WAN Utilities " (ZZAUTIL121). Removing directories and symbolic links for DNADLI321 ... done. Deleting "DECnet/OSI Datalink Components " (DNADLI321). Shutting down DECnet/OSI Removing directories and symbolic links for DNABASE321 ... done. Deleting "DECnet/OSI Base Components " (DNABASE321). The following subsets need "DECnet/OSI Network Management " (DNANETMAN321) to operate correctly: CTF Collector Components (CTABASE141) Are you sure you wish to delete "DECnet/OSI Network Management " (DNANETMAN321)? (y/n): y Removing directories and symbolic links for DNANETMAN321 ... done. Deleting "DECnet/OSI Network Management " (DNANETMAN321). decnetsetup completed successfully. # 2.1.5 Using LMF to Register Your Software License PAK The next step in the installation procedure is to register your Product Authorization Key (PAK) using the License Management Facility (LMF). LMF is a system management software tool that enables you to comply with your license agreement. LMF offers options for the variety of license agreements. The terms and conditions of your contract determine your legal use of this software. LMF maintains the file of registered software license PAKs and keeps a library of functions used by licensed software. ________________________ Note ________________________ To run the OSI application gateways, you need an Extended System PAK; see Section 1.3.2. ______________________________________________________ The following instructions show how you might register an End-System software license PAK using LMF: 1. Make sure that you have your PAK. 2. Log in to your system as a superuser. 2-6 Installing DECnet/OSI for Digital UNIX 3. Issue an lmfsetup command: # lmfsetup 4. After you issue this command, you receive the following confirmation prompt: Register PAK (type q or quit to exit) [template] 5. Press Return. After you do this, you are prompted to answer a series of questions. These questions correspond to the fields on your PAK form. Use the information from your DECnet /OSI for Digital UNIX PAK to reply to each question. Any fields that are left blank on the PAK should be left blank as you enter the data. 6. After you respond to all the questions, you should receive a completion message similar to the following: PAK registered for template successfully 7. Exit lmfsetup by entering quit: Register PAK (type q or quit to exit) [template] quit 8. After you enter q or quit to exit, you are informed that you have registered at least one PAK and that you must load each PAK by using the lmf reset command or the lmf load command, or by rebooting your system. Otherwise, software that depends on each PAK will be treated as if the PAK has not been registered. Then you receive the following prompt: Would you like a lmf reset to be performed at this time? [Yes] 9. Press Return. 10.Finally, issue an lmf list command to verify your registration: # lmf list Installing DECnet/OSI for Digital UNIX 2-7 ________________________ Note ________________________ If you attempt to load a PAK and a PAK has already been loaded, you receive an error message similar to the following: Combine DECNET-OSI-END SQM014419 with DECNET-OSI-END SQM010892 If you receive this message, do the following: 1. List the license PAK templates using the following command: # lmf list full for DECNET-OSI-END 2. Compare the information in the templates, and note the authorization number of the software license PAK you want to delete. 3. Use the following command to delete the old PAK: # lmf delete DECNET-OSI-END DEC authorization-number 4. Issue another lmf reset command. ______________________________________________________ If you want to know how to obtain a license and PAK or how you use the LMF facility, refer to the Digital UNIX Guide to Software License Management, or the lmf and lmfsetup reference pages (lmf(8) and lmfsetup(8)) for additional information. 2.1.6 Creating a Guest Account A guest account allows remote DECnet users (who use the DECnet file transfer utility) access to world-readable files on your system without having to supply access control information for each remote operation. The default user account for the DECnet file transfer utility is guest. To define a guest account, log in as superuser and enter the adduser command. When the command prompts you for the login name of the new user, enter the name guest in lowercase letters. For example: 2-8 Installing DECnet/OSI for Digital UNIX # adduser Enter login name for new user (for example, john): guest The system then prompts you for the following information about the new user: o Login name (enter guest) o UID o Full name o Login group o Any other login group o Parent directory o Login shell (choices are displayed for you) o New password To ensure that the guest cannot be used interactively by remote users (a potential security risk), use the vipw command to enter the string Nologin in the password field. ________________________ Note ________________________ The decnetsetup terminal-based script does not check any distributed account information in attempting to determine if a guest account currently exists. Digital suggests that you add this account to the local password file. ______________________________________________________ For further instructions on using adduser to create a new account, refer to the Guide to System Environment Setup in your operating system documentation set. 2.1.7 Deciding on the Type of Installation You can choose from four types of installation: o DNALITE installation for systems with limited memory and disk space, or requiring only basic DECnet Phase IV functionality. (This installation also supports DECnet over TCP/IP.) Installing DECnet/OSI for Digital UNIX 2-9 o Full-capability DECnet/OSI installation for systems requiring additional DECnet functionality such as OSI, RFC 1006, DECnet over TCP/IP, DECdns server, DECdts clerk or server, or Wide Area Networking Support for Digital UNIX software (X.25). o RFC 1006-only installation for systems requiring only the RFC 1006 feature to run OSI applications over TCP /IP. o MOP-standalone installation for systems to perform downline loading and upline dumping, not requiring DECnet/OSI software. Table 2-1 provides guidelines for choosing the appropriate installation for your system and needs. Table_2-1_Choosing_the_Installation_Type___________________ If_your_system_has...________________Use...________________ 32 MB of memory or less DNALITE Limited free disk space DNALITE Requirements for only basic DECnet DNALITE Phase IV functionality such as mail, file transfer, and remote login Requirements for DECnet over TCP/IP DNALITE Full-capability DECnet /OSI Requirements for OSI or RFC 1006 Full-capability DECnet /OSI Requirements for DECdns server, Full-capability DECnet DECdts clerk or server, wide area /OSI networking/X.25 services, OSI applications or gateways software, DECnet-Internet Gateway Requirements only for the RFC 1006 RFC-only feature to run OSI applications over TCP/IP (continued on next page) 2-10 Installing DECnet/OSI for Digital UNIX Table_2-1_(Cont.)_Choosing_the_Installation_Type___________ If_your_system_has...________________Use...________________ Requirements for MOP without DECnet MOP-standalone /OSI_______________________________________________________ 2.2 Copying the Subsets from the Distribution Media The next step in installing the software is to copy the DECnet/OSI subsets from the distribution media to the target system. The steps to accomplish this task vary, depending on whether you are using the Digital UNIX Layered Product Consolidated Software Distribution disk (CD-ROM) or the Remote Installation Service (RIS) over a local area network. 2.2.1 CD-ROM Installation If you are installing the software from a CD-ROM, use this procedure: 1. Determine the directory of the DECnet/OSI files. Refer to the Master Index table in the Consolidated Software Distribution Disk User's Guide for the name of the directory on the CD-ROM that contains the DECnet/OSI software. 2. Insert the disk into the drive to determine the device name for the drive. The drive is either RRD40, RRD42, or RRD45. Use the following command to list the available disk devices: # file /dev/rr*c 3. Mount the disk using the following command and device's name: # mount -r -d /dev/device_name /mnt 4. Install the software onto your system, using the software's directory name and this setld(8) command: # setld -l /mnt/directory_name Installing DECnet/OSI for Digital UNIX 2-11 2.2.2 Using RIS Over a Local Area Network You can install DECnet/OSI for Digital UNIX over your network using the Remote Installation Service (ris) utility. Refer to the Remote Installation Service document and ris(8) in the Reference Pages, Section 8, for requirements. If you are using RIS over a local area network to install the software, use the command, setld -l hostname:, where hostname is the name of the host from which you are loading the software. 2.2.3 Selecting the Software Subsets The next task is to choose the subsets you need to install from the distribution media. The following sections discuss the procedure for the four types of installations: o Full-capability o DNALITE o RFC 1006-only o MOP-standalone In addition, installation and configuration details are discussed about DECnet for TCP/IP, DECnet-Internet Gateway, and OSI applications software. Run setld, then select from the menu of subsets displayed by typing the numbers of the options that you want to install. Separate each number with a space, not a comma. You can specify a range of numbers using a hyphen to join them, as in the following example: ________________________ Note ________________________ The setld script does not display subsets that are already installed on your system. ______________________________________________________ 2-12 Installing DECnet/OSI for Digital UNIX # setld -l /mnt/DNA400 DECnet/OSI for Digital UNIX V4.0-0 Copyright (c) Digital Equipment Corporation. 1993-1996. All Rights Reserved. To install and configure DECnet/OSI on this system, choose all subsets from the Standard Run-time Environment, and any of the other subsets desired for additional functionality. Please see the installation guide for further details on selecting subsets. Press Return to continue: 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. - DECnet/OSI Standard Run-time Environment: 1) DECnet/OSI Base Components 2) DECnet/OSI Kernel Components 3) DECnet/OSI Network Management - Lightweight DECnet Configuration Environment: 4) DECnet for Small Configurations --- MORE TO FOLLOW --- Enter your choices or press Return to display the next screen. Choices (for example, 1 2 4-6): 1-3 - Optional DECnet/OSI Components: 5) DECnet/OSI DECdns Server 6) DECnet/OSI Gateways 7) DECnet/OSI MOP Utilities 8) DECnet/OSI Miscellaneous Software 9) DECnet/OSI Network Management GUI 10) DECnet/OSI Programming Tools 11) DECnet/OSI Reference Pages 12) DECnet/OSI Transition Tools - Optional Trace Facility Components: 13) CTF Collector Components 14) CTF User Environment 15) Digital UNIX WAN Utilities --- MORE TO FOLLOW --- Add to your choices or press RETURN to display the next screen. Installing DECnet/OSI for Digital UNIX 2-13 Choices (for example, 1 2 4-6): The following choices override your previous selections: 16) ALL of the above 17) CANCEL selections and redisplay menus 18) EXIT without installing any subsets Add to your choices, choose an overriding action or press RETURN to confirm previous selections. Choices (for example, 1 2 4-6): 1-3 5-15 After entering your choices, the procedure prompts you to verify your choices. If you chose the wrong options, type no to indicate that the subsets are not correct; the subset menu redisplays, and you can reselect your subsets. If you chose the correct options, type yes, as in the following example. The procedure also checks to make sure you have enough file space to install the subsets you select. You are installing the following optional subsets: - DECnet/OSI Standard Run-time Environment: DECnet/OSI Base Components DECnet/OSI Kernel Components DECnet/OSI Network Management - Optional DECnet/OSI Components: DECnet/OSI DECdns Server DECnet/OSI Gateways DECnet/OSI MOP Utilities DECnet/OSI Miscellaneous Software DECnet/OSI Network Management GUI DECnet/OSI Programming Tools DECnet/OSI Reference Pages DECnet/OSI Transition Tools - Optional Trace Facility Components: CTF Collector Components CTF User Environment Digital UNIX WAN Utilities Is this correct? (y/n): y Checking file system space required to install selected subsets: 2-14 Installing DECnet/OSI for Digital UNIX File system space checked OK. 14 subset(s) will be installed. 2.2.3.1 Full-Capability DECnet/OSI Installation For the minimum DECnet/OSI for Digital UNIX configuration, you must install the following three subsets: o DECnet/OSI Base Components o DECnet/OSI Kernel Components o DECnet/OSI Network Management Run setld and select options 1 through 3. The remaining subsets you select are optional. Appendix A includes a script of a sample installation. To configure the DECnet/OSI software, use either the basic or advanced configuration procedure (Section 2.3 describes the criteria for selecting either the basic or advanced procedure). Appendix B includes a script of a sample basic and advanced configuration procedure. ________________________ Note ________________________ The installation script refers to the three subsets required for full-capability DECnet/OSI as optional. However, the script is referring to them as optional relevant to the Digital UNIX operating system rather than the DECnet/OSI for Digital UNIX software. ______________________________________________________ 2.2.3.2 DECnet for Small Configurations (DNALITE) Installation If you only need basic DECnet Phase IV functionality, you need only install the following subsets: o DECnet for Small Configurations (DNALITE400) o DECnet/OSI Kernel Components (DNAKBIN400) Optionally, you can select the DECnet/OSI Reference Pages (DNAMAN400) and DECnet/OSI Miscellaneous Software (DNAUTIL400) subsets. Installing DECnet/OSI for Digital UNIX 2-15 Run setld and select options 2 and 4 to install the required subsets. Appendix A includes a script of a sample installation. Then run the basic configuration procedure to configure the DECnet software (or you can use the advanced configuration procedure). Appendix B includes a script of a sample configuration procedure. ________________________ Note ________________________ If either the DECnet/OSI Network Management (DNANETMAN400) or DECnet/OSI Base Components (DNABASE400) subset is already installed on your system, you cannot install the DECnet for Small Configurations subset. The setld will not display the DECnet for Small Configurations subset as an installation option. ______________________________________________________ 2.2.3.3 RFC 1006-Only Installation If you use only the RFC 1006 feature (as opposed to the OSI Transport) to run OSI applications over TCP/IP, you need only install the following subsets: o DECnet/OSI Kernel Components (DNAKBIN400) o DECnet/OSI Network Management (DNANETMAN400) You can use the following command to install these subsets: # setld -l DNAKBIN400 DNANETMAN400 Appendix A includes a script of a sample installation for these subsets. The DECnet/OSI XTI extensions library (libxtiosi.so) needed for RFC 1006 is in the Network Management subset. You may also want to install the OSI applications from the Base Components (DNABASE400) subset, which you can configure to use the RFC 1006 functionality. You configure the RFC 1006 software by running rfc1006setup, using the command line in the following example. You do not need to run the basic or advanced configuration procedure. # /usr/sbin/rfc1006setup 2-16 Installing DECnet/OSI for Digital UNIX Appendix B includes a script of a sample configuration procedure. 2.2.3.4 MOP-Standalone Installation If you want to run MOP standalone without DECnet/OSI, you need only install the following subsets: o DECnet/OSI Kernel Components (DNAKBIN400) o DECnet/OSI Network Management (DNANETMAN400) o DECnet/OSI MOP Utilities (DNAMOP400) You can install these subsets by using the following command: # setld -l DNAKBIN400 DNANETMAN400 DNAMOP400 Appendix A includes a script of a sample installation for these three subsets. To configure and run MOP standalone without the rest of DECnet/OSI, use the following command. This also configures the needed components in DNAKBIN400 and DNANETMAN400 subsets. You do not need to run the basic or advanced configuration. # /usr/sbin/mopsetup Appendix B includes a script of a sample configuration procedure. Note that if you want DECnet/OSI software (that is, you do not want to run MOP standalone), you can use the advanced configuration procedure to configure DECnet/OSI to service MOP requests. See Section 4.14. 2.2.3.5 DECnet Over TCP/IP The DECnet/OSI full-capability and the DECnet for Small Configurations installations include software that allows DECnet applications to run over TCP/IP. Called DECnet over TCP/IP, this software enables DECnet applications to accept IP names and addresses. These names and addresses are translated by BIND servers. The DECnet applications include Digital-supplied applications, third-party applications, and user-written applications. Installing DECnet/OSI for Digital UNIX 2-17 The DECnet over TCP/IP software can be configured automatically in either the basic or advanced configuration procedure if you specify as the Phase V node name the DOMAIN: namespace nickname with the fully qualified domain name for the system you are configuring. This makes DNS /BIND the primary name service. If you want to use the local namespace or DECdns as the primary name service, you can configure DECnet over TCP/IP software in the advanced configuration procedure. The procedure asks you if you want to configure DECnet over TCP/IP software. DECnet over TCP/IP uses the TCP/IP and BIND functionality provided by the Digital UNIX operating system. Before configuring DECnet/OSI, the TCP/IP and BIND functionality must be configured on the Digital UNIX operating system. To configure the DECnet over TCP/IP (RFC 1859) software on Digital UNIX systems, the following subsets must be installed on your system: o DECnet/OSI Kernel Components (DNAKBINxxx) o DECnet/OSI Network Management (DNANETMANxxx) o DECnet/OSI Base Components (DNABASExxx) 2.2.3.6 DECnet-Internet Gateway If you want to use the DECnet-Internet Gateway software, you need to install the DECnet/OSI Gateways (DNAGATEWAYS400) subset. You can configure the software after the basic configuration procedure (Section 3.12) or during the advanced configuration procedure (Section 4.12). 2.2.3.7 OSI Applications Software The OSI applications (FTAM and Virtual Terminal) are installed with the DECnet/OSI Base Components subset (DNABASE400). Configure the OSI applications software after completing the basic or advanced configuration procedure, as explained in Chapter 7. 2-18 Installing DECnet/OSI for Digital UNIX 2.2.4 Installing the Software on Your System After you select the subsets you want to install, the procedure copies them from the installation media to your disk. The following example shows a partial display as the procedure copies selected software subsets: Digital UNIX WAN Utilities Copying from . (disk) Verifying DECnet/OSI Kernel Components Copying from . (disk) Verifying DECnet/OSI Network Management Copying from . (disk) Verifying DECnet/OSI Base Components Copying from . (disk) Verifying DECnet/OSI Gateways Copying from . (disk) Verifying DECnet/OSI Network Management GUI Copying from . (disk) Verifying DECnet/OSI Reference Pages Copying from . (disk) Verifying DECnet/OSI MOP Utilities Copying from . (disk) Verifying DECnet/OSI Transition Tools Copying from . (disk) Verifying DECnet/OSI DECdns Server Copying from . (disk) Verifying Installing DECnet/OSI for Digital UNIX 2-19 DECnet/OSI Miscellaneous Software Copying from . (disk) Verifying DECnet/OSI Programming Tools Copying from . (disk) Verifying CTF Collector Components Copying from . (disk) Verifying CTF User Environment Copying from . (disk) Verifying If verification fails, look in /var/adm/fverify.log and /var/admin/setld.log for information to help you correct the error. Make the correction and restart the installation by using the setld -l command. 2.2.4.1 Completion Messages When the copy is complete, the procedure displays completion information on the subsets you chose to install, such as shown in the example that follows. You must reboot your system before you configure any of the DECnet/OSI software. Linking "Digital UNIX WAN Utilities" Configuring "Digital UNIX WAN Utilities " (ZZAUTIL300) Configuring "DECnet/OSI Kernel Components " (DNAKBIN400) Configuring "DECnet/OSI Network Management " (DNANETMAN400) Configuring "DECnet/OSI Base Components " (DNABASE400) Configuring "DECnet/OSI Gateways " (DNAGATEWAYS400) Configuring "DECnet/OSI Network Management GUI " (DNANETMANGUI400) Configuring "DECnet/OSI Reference Pages " (DNAMAN400) Configuring "DECnet/OSI MOP Utilities " (DNAMOP400) Configuring "DECnet/OSI Transition Tools" (DNATRANSITION400) Configuring "DECnet/OSI DECdns Server " (DNADECDNSSRV400) 2-20 Installing DECnet/OSI for Digital UNIX Configuring "DECnet/OSI Miscellaneous Software " (DNAUTIL400) Configuring "DECnet/OSI Programming Tools " (DNAPGMR400) Linking "CTF Collector Components" Configuring "CTF Collector Components " (CTABASE300) Linking "CTF User Environment" To complete your installation of DECnet/OSI for Digital UNIX V4.0-0, please perform the following step: - Configure or reconfigure DECnet/OSI by executing either of the following commands (the first is for a graphical configuration utility and the second is terminal-based): utility): # /usr/sbin/dxdecnetsetup # /usr/sbin/decnetsetup [basic|advanced] Please refer to the Installation Guide for details. Press to continue: Configuring "CTF User Environment " (CTAANAL300) # 2.3 Choosing a Configuration Procedure To configure the DECnet/OSI software, you must supply information about your system. You can choose two modes of configuration: basic or advanced. Use the advanced configuration procedure if: o You want to configure your system as a DECdts server. o Your system has multiple communication devices, and you want them to run a mix of protocols (some DECnet/OSI and some Internet, for instance). o You want to use an alternate node synonym directory. o You want to manually configure your network addresses. o You want to configure DECnet over TCP/IP software without using DNS/BIND as the primary name service. o You want to configure your DECnet/OSI software to use wide area networking/X.25 services. Installing DECnet/OSI for Digital UNIX 2-21 Use the basic configuration procedure if you want a simpler configuration, and you do not want any of this extra functionality. Chapters 3 and 4 explain how to invoke and use the basic and advanced configuration procedures, respectively. 2.4 Configuration Interfaces You can use either of two interfaces to configure DECnet /OSI: o A terminal-based script o A graphical interface Both the terminal-based script and the graphical interface record your responses in the defaults file /var/dna /decnetsetup_defaults. This file stores your responses as defaults to be used when you next run the configuration procedure. For example, after the first configuration, you will not have to reenter the node name in subsequent reconfigurations. You can use as a default the node name specified during the first configuration. When you select the Reset button using the graphical user interface, the procedure writes the values stored in the decnetsetup_ defaults file to your screen, replacing any values you have recently set. 2.4.1 Terminal-Based Configuration Interface The terminal-based interface is a script (decnetsetup) that is available for all environments. The terminal-based interface presents a series of questions that prompt you for information. Before DECnet/OSI is actually configured, you are asked to confirm all your answers. You can use that opportunity to restart the configuration procedure and change your answers. You can get help for any of the questions asked by responding to any of the prompts with a question mark (?) and pressing Return. 2-22 Installing DECnet/OSI for Digital UNIX 2.4.2 Graphical Configuration Interface The graphical interface (dxdecnetsetup) is available with DECnet/OSI for Digital UNIX (Version 4 or higher). Your Digital UNIX system must have a graphics capability, Motif Version 1.2 software, and at least 32 MB of main memory. The interface is available by command and is also integrated into the Common Desktop Environment (CDE), the default Windows manager for Digital UNIX Version 4.0. The graphical interface displays a Setup window that lets you point and click on fields to enter your responses. The screen prompts you for information in the same order as the script, but you can supply information in any order. When you choose to actually configure the DECnet/OSI software, the configuration procedure first checks that you have made the minimum required settings. Figure 2-1 shows an example of the graphical interface screen for the basic configuration procedure. Figure 2-1 Graphical Interface for Basic Configuration Figure 2-2 shows the screen for the advanced configuration procedure. Note that to configure DECnet to support mailsetup, OSI applications, or X.25 services, you use procedures commands and utilities independently of the graphical-based and terminal-based configuration procedures, as explained in Chapter 4. Installing DECnet/OSI for Digital UNIX 2-23 Figure 2-2 Graphical Interface for Advanced Configuration ________________________ Note ________________________ If your system is operating under Enhanced Security, to use privileged functions, first become a root user (super user) before you start the graphical interface (that is, at the system prompt, enter the su command to switch to root, then start the graphical interface). ______________________________________________________ The graphical interface provides pointer-sensitive help. Wherever you place your pointer, a Help box automatically displays explanatory text. You can turn this feature on or off. Unavailable options or fields are dimmed. For example, in Figure 2-2, the node synonym directory and service MOP requests fields are inactive. Other examples when fields are dimmed include the following: o If the Distributed Computing Environment (DCE) software is configured on your system, the interface dims the DTSS options to indicate the options are unavailable. DECnet will use DCE time services. (DTSS is the network management module that synchronizes and manages the system clocks in a distributed DECnet/OSI network; it contains all DECdts management functions.) o If the DECnet/OSI Gateways subset is not installed, the interface dims the prompt, "Configure as a DECnet- Internet Gateway?". o If the DECnet/OSI MOP Utilities subset is not installed, the interface dims the prompt, "Service MOP Requests?" 2-24 Installing DECnet/OSI for Digital UNIX The last line of the pointer-sensitive help message indicates the reason that an option is not available. 2.4.2.1 Options Provided from the Menu Bar The File menu selected from the menu bar has one option, Exit. Select Exit to quit the configuration procedure. If you are a root user, select the Exit option to save current input as defaults. If you are not a root user, the Exit option has the same effect as the Cancel button at the bottom of the screen, quitting the procedure without saving current input. You can select one of several options from the Options menu in the menu bar. Table 2-2 describes these options. Table_2-2_Graphical_Interface_Options______________________ Option___________Description_______________________________ Pointer Help Determines whether pointer-sensitive help messages are displayed. When on, these messages appear in the Help box near the bottom of the screen as the mouse pointer moves across items on the screen. When off, the pointer-sensitive messages are not displayed. (continued on next page) Installing DECnet/OSI for Digital UNIX 2-25 Table_2-2_(Cont.)_Graphical_Interface_Options______________ Option___________Description_______________________________ Use Invalid Turns highlighting of invalid responses Highlights on or off. When on, invalid responses are highlighted. By default, they are highlighted with reversed colors, or in colors specified in your customized resource file (see the discussion of the Create Resource File option). When off, invalid responses are not highlighted. Note that error messages are always displayed, whether this option is on or off. Invalid Highlights applies only to fields that accept user input. They do not apply to toggle responses (selecting yes or no, for example). The configuration procedure does not allow you to give an invalid response to a toggle-it forces the correct answer. (continued on next page) 2-26 Installing DECnet/OSI for Digital UNIX Table_2-2_(Cont.)_Graphical_Interface_Options______________ Option___________Description_______________________________ Verbose Determines whether supplementary messages Configuration are displayed during configuration. If on, when you select the Configure button, the procedure displays more detailed messages in the DECnet/OSI Configuration Messages box, such as log messages and information about "substeps." When off, the procedure displays only information about the major steps. The supplementary messages displayed when Verbose Configuration is on are set apart by indentation. These messages give you a more accurate sense of the progress of the configuration. For example, when the system is slow, the supplementary messages enable you to see the progress of each configuration substep. Verbose Configuration is also helpful for debugging. You can determine the exact stage where a problem occurs. All messages are also logged to /var/dna/dxdecnetsetup_config.log. (continued on next page) Installing DECnet/OSI for Digital UNIX 2-27 Table_2-2_(Cont.)_Graphical_Interface_Options______________ Option___________Description_______________________________ su to root Allows a non-root user to become root (super user). Only root can configure DECnet and shut down DECnet. When you select the su to root option, the configuration procedure prompts you for the root password. If you enter the correct password, the Configure and Shut Down DECnet functions are enabled. These functions are not available to non-root users. Non-root users can use the graphical interface to examine the configuration settings but not to change them. If the non-root user is not a member of the system group, the su to root option is unavailable. If your system is operating under Enhanced Security, to use privileged functions, first become a root user (super user) before you start the graphical interface. Shut Down Available to root users only, this option DECnet will shut down DECnet (DECnet must be shut down before configuring). Create Resource Creates the resource file DXdecnetsetup in File your current directory. This file contains settings that you can modify to affect the appearance of the graphical interface. Edit the file to customize the settings, and then store a copy either in your home directory or in the directory to which the XAPPLRESDIR environment variable points. The initial, application-defined default values defined for all users are stored in the file of the same name in usr/lib/Xll _________________/app-defaults.____________________________ 2-28 Installing DECnet/OSI for Digital UNIX 2.4.2.2 Toggle Switches At the top of the screen, a Setup Type prompt allows you to select, or switch between, basic or advanced configuration mode. In advanced mode, the graphical user interface includes several toggle switches, as described in Table 2-3. Table_2-3_Toggle_Switches__________________________________ Switch___________Description_______________________________ Autoconfigure Determines whether the configuration network procedure automatically configures the addresses network entity titles (NETs) or you manually configure them. The default is yes. If you select no, a DECnet/OSI Network Entity Title Setup box appears, prompting you for the three NETs. Note that if you have specified a Phase IV compatible address for your system, then the configuration procedure automatically calculates the first NET based on the Phase IV address. You cannot modify the first NET if a Phase IV node address was provided. For more information on auto- and manual configuration, see Section 4.8. Communications Determines the devices you wish to Devices configure. By default, all devices known to your system are selected. Note that selected devices are not stored in the decnetsetup_defaults file. Therefore, when you select the Reset button or reconfigure the DECnet/OSI software, the previously configured devices are not retained. You must select them again. DTSS Determines whether your system will be a DTSS clerk, a DTSS server, or neither. (continued on next page) Installing DECnet/OSI for Digital UNIX 2-29 Table_2-3_(Cont.)_Toggle_Switches__________________________ Switch___________Description_______________________________ Configure Determines whether the DECnet-Internet DECnet-Internet Gateway is configured. The default is no. Gateway Configure Determines whether DECnet applications DECnet over will run over TCP/IP. The default is no, TCP/IP unless the namespace Domain (for Domain Name System (DNS)/BIND) has been selected. Service MOP Determines whether the system will Requests? recognize MOP requests for loading or dumping devices and nodes on the LAN. The default is no. Routing Mode Determines the mode that routing will use, segregated or integrated. The default is _________________segregated._______________________________ 2.4.2.3 Function Buttons The graphical interface includes several buttons at the bottom of the screen. The buttons and the functions they initiate are described in Table 2-4. 2-30 Installing DECnet/OSI for Digital UNIX Table_2-4_Function_Buttons_________________________________ Button_____Function________________________________________ Configure Available only to root, selecting this button causes the configuration procedure to do the following, in the order listed: 1. Validate the configuration settings that you have entered 2. Check that DECnet is not currently running (it should be shut down) 3. Configure the software to reflect the settings you entered If, after selecting Configure, you realize you made a mistake or supplied the wrong information, do not halt the process. Wait for the configuration process to complete, shut down DECnet, make the appropriate changes, and then reconfigure. The configuration procedure automatically reinstates the previously configured values for all settings you do not change. Reset Allows you to reset the values displayed on your screen to the last-saved defaults (or, if you have not saved defaults previously, to the system defaults). The configuration procedure can detect whether you have run the basic or advanced configuration. If you have run the advanced configuration procedure and you set values unique to the advanced configuration, then the next time you invoke the configuration procedure, it automatically starts in advanced mode. If you switch to basic, the advanced mode settings are deleted from the screen. However, if you subsequently select the Reset button, the procedure reinstates the advanced settings and returns you to advanced mode. (continued on next page) Installing DECnet/OSI for Digital UNIX 2-31 Table_2-4_(Cont.)_Function_Buttons_________________________ Button_____Function________________________________________ Cancel Allows you to quit the configuration procedure without saving changes. After a successful configuration, the label on this button changes to Done. If, after a successful configuration, you change information on the screen again, the label changes back to Cancel so that you can quit without saving those changes. Show NETs Available only in advanced mode, this button allows you to display the DECnet/OSI Network Entity Title Setup box which lists the network entity titles (NETs) currently defined for your system. You can modify them if you have selected ___________no_for_the_Autoconfigure_switch.________________ 2.4.2.4 Customizing Your Local Implementation of the Graphical Interface The Create Resource File button allows you to create a resource file in which you can store default values defining the appearance of the interface (see Table 2-4). Note that this file enables you to create a non-English interface. Values you can customize include o Colors used for the invalid highlighting option o Fonts used for displayed text o The prompts displayed o Initial settings for the options Pointer Help, Use Invalid Highlights, and Verbose Configuration. o Labels for the buttons o Names of the menus o Titles of the windows 2-32 Installing DECnet/OSI for Digital UNIX For local customization, place the customized file in usr/lib/Xll/app-defaults, in your home directory, or in a directory specified by the XAPPLRESDIR environment variable. Installing DECnet/OSI for Digital UNIX 2-33 3 _________________________________________________________________ Basic Configuration This chapter discusses the following about basic configuration: o When to use the basic configuration procedure and how to start it o Specifying your DECnet/OSI node name and node synonym o Communicating with Phase IV nodes o Configuring a Token Ring communications device o Configuring the DECnet-Internet Gateway o Configuring the OSI applications software o Starting DECnet/OSI software o Configuring DECdns or the Local namespace 3.1 When to Use the Basic Configuration Use the basic DECnet/OSI configuration procedure if you are installing the DECnet for Small Configurations (DNALITE) subset. (You can also use the advanced configuration for this subset.) Or, use the basic configuration procedure if any of the following conditions apply: o Your system is a DECdts clerk only. o You do not need any additional functionality such as: - Multiple communication devices running on a mix of protocols - Wide-area networking/X.25 services - Manual configuration of network addresses (during configuration procedure) - Use of an alternate node synonym directory Basic Configuration 3-1 - Use of DECnet over TCP/IP software with DECdns or the local namespace as the primary name service Before you run the basic configuration procedure, fill out the checklist shown in Figure 3-1 to ensure you have all necessary information. Figure 3-1 Basic Configuration Checklist 3.2 About the Basic Configuration Procedure The configuration procedure displays a series of questions that prompt you for information about your system's configuration. Appendix A shows a log of a sample terminal- based basic configuration. The following list describes the information you are asked to provide for your system during the basic configuration script. Some of the information is optional and depends upon your system's configuration. o DECnet/OSI (Phase V) node name o Phase IV compatible synonym o Phase IV compatible node address o Token Ring speed for device o DECnet-Internet Gateway configuration 3-2