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 Basic Configuration At the end of the terminal-based configuration procedure, you are prompted to confirm the configuration values that you entered. If you are using the graphical interface, you are not prompted to confirm the configuration values. In either case, you can: o Quit the procedure without saving the values. o Save the entries and exit the procedure. o Restart the procedure (with the graphical interface, reset the values to previously saved defaults). o Continue with the configuration by starting the DECnet /OSI software. 3.2.1 Changing Your Answers Do not be concerned if you make a mistake or supply the wrong information for a question. You can verify your answers before DECnet/OSI is actually configured. If you are using the terminal-based script, you can restart the configuration procedure to change your answers. If you are using the graphical interface, you can change your responses anytime before selecting the Configure button. You can also reset the values to those defined as defaults. 3.2.2 Default Values Many of the questions have default values associated with them. (Section 3.3 discusses the defaults used by the basic configuration procedure.) This information is contained in brackets at the end of the question, as in this example: What is the Phase IV compatible synonym? [WillyL]: Using the terminal-based script, if the default value, in this case WillyL, is correct, press Return. Using the graphical interface, if the default value is correct, you need not respond. It will be configured automatically when you press the Configure button. If you are rerunning this procedure (or, with the graphical interface, if you are resetting the values), the default values are based on the information that you supplied previously. Basic Configuration 3-3 3.2.3 Stopping the Configuration Procedure You can review your answers to the prompts and exit the configuration procedure before configuring DECnet by pressing Ctrl/C in the terminal-based script, or by selecting the Cancel button in the graphical interface. Do not stop the configuration process once it starts to configure the DECnet/OSI software. To change any information after this point: finish the configuration, shut down DECnet, then rerun the procedure with the new information. 3.2.4 Getting Help The configuration procedure prompts you for information. If you need help responding to any of these prompts in the terminal-based script, enter a question mark (?) and press Return to view the help text. The graphical interface displays pointer-sensitive help messages in a Help box. 3.3 Basic Configuration Defaults The basic configuration procedure uses the default values described in the following sections to configure your system. 3.3.1 Phase IV Prefix Basic configuration uses 49:: as the default value for the Phase IV prefix. Note that this is updated by an adjacent DECnet/OSI router if the network uses a different value. 3.3.2 Node Synonym Directory Basic configuration provides the default value for the node synonym directory. If you have an environment variable for decnet_migrate_dir_synonym defined, the default value for the node synonym directory is defined by that variable. If you do not use an environment variable, the default value is .DNA_NodeSynonym. 3-4 Basic Configuration 3.3.3 Naming Search Path During configuration, you specify the node's full name properly formatted for the name service to be searched first. From this information the configuration procedure constructs a properly formatted full name for the name service to be searched next and places this information in the search path file. For more information, see the DECnet /OSI Network Management guide.. 3.3.4 Network Addresses Basic configuration allows the system to autoconfigure network addresses. If you do not want the network addresses configured automatically, use the advanced configuration procedure. 3.3.5 DECdns, DTSS, and Servicing of MOP Requests By default, the basic configuration procedure sets up your system to service MOP requests and to be a DECdns clerk and a DTSS clerk. (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.) The advanced configuration procedure gives you a choice of whether you want your system to service MOP requests. It also allows you to set up your system as a DTSS server. To set up your system as a DECdns server, see the DECnet/OSI DECdns Management guide. 3.4 How DECnet/OSI Uses the Naming Search Path DECnet/OSI supports the Local namespace, the DECdns distributed name service, and the Domain Name Service (DNS /BIND). DECdns is Digital's network naming service. DNS /BIND is needed if you want DECnet/OSI to run applications over TCP/IP. DNS/BIND provides for the use of node synonyms (for backward compatibility with older applications that cannot use long domain names). DECnet/OSI for Digital UNIX includes support for NSAP addresses in DNS/BIND (see the DECnet/OSI Network Management guide). For more information about the Local namespace, the DECdns distributed namespace, and the DNS/BIND distributed name service, see the DECnet/OSI Planning Guide. (For additional information about managing the DNS/BIND Basic Configuration 3-5 namespace, see the appropriate TCP/IP documentation.) If you are not sure which name service to use and in which order, consult your network manager. The order in which DECnet/OSI searches the available name services for node name and address information is determined by the naming search path. The naming search path is set up during DECnet/OSI configuration and applies to DECnet applications systemwide. The naming search path describes: o The order in which the name services are to be searched for names and addressing information o How DECnet/OSI should interpret any abbreviated node names entered by users. The search path includes naming templates that tell DECnet/OSI how to interpret any abbreviated node names entered by users. The primary name service (the name service to be searched first) is listed before the secondary name services. The secondary name services are listed in the order in which they are to be searched after the primary name service. The ordering of the name services is very important. The first name service listed is the primary name service to use on the system. The primary name service is considered the first choice to use when looking up names and addressing information. The remaining name services listed are considered to be the secondary services to use on the system. The search path contains a list of name service keywords, each followed by a naming template that specifies a "defaulting rule" so users can enter shorter node names. Note that the search path information for a system is maintained in two separate search paths: o One for forward translation or naming (node-name-to- address translation). o One for backtranslation (address-to-node-name translation). 3-6 Basic Configuration 3.4.1 Configuring the Naming Search Path The DECnet/OSI configuration procedure sets up one or more name services on your system. You specify your node's full name properly formatted for the name service to be searched first. From this information, the configuration procedure constructs a properly formatted full name for the name service to be searched next. Running the configuration procedure creates /var/dna /decnet-dirsvc.conf, which contains the naming search path information for the node. Do not edit this file. If you must make changes to /var/dna/decnet-dirsvc.conf, use the NCL set commands described in Section 3.4.3 to modify the naming templates or rerun the configuration procedure to designate a new primary name service and change the order in which the name services are searched. If you specify a full name beginning with the namespace nickname LOCAL: (or local:), DECnet/OSI searches the Local namespace first for forward and backtranslation information. If DECnet/OSI does not find a Local namespace or the Local namespace does not contain name and addressing information for the specified node, then DECnet/OSI searches the DECdns namespace. If it does not find information for the node in the DECdns namespace, DECnet/OSI then searches the Local namespace. If the information is not found in the Local namespace, and DECnet over TCP/IP is configured, DECnet/OSI then searches DNS /BIND. Similarly, if you specify a full name containing a namespace nickname for a DECdns namespace (for example, ABCDE:.xyz.abc), then DECnet/OSI searches the specified DECdns namespace (ABCDE:) first for forward and backtranslation information. If it does not find information for the node, DECnet/OSI then searches the Local namespace. If the information is not found in the Local namespace, and DECnet over TCP/IP is configured, DECnet/OSI then searches DNS/BIND. ________________________ Note ________________________ If your node is a DECdns server, the primary name service must be DECdns. ______________________________________________________ Basic Configuration 3-7 If the system administrator specified a fully qualified domain name prefixed with the DOMAIN: nickname, DECnet /OSI searches the DNS/BIND namespace first for forward and backtranslation information. If DNS/BIND does not contain name and addressing information for the specified node, then DECnet/OSI searches the Local namespace. If DECnet /OSI does not find a Local namespace, or if the Local namespace does not contain name and addressing information for the specified node, then DECnet/OSI searches the DECdns namespace. 3.4.2 Displaying the Search Path Information To display information about the search path maintained for forward translation or naming (node name to address translation), use the following command: $ ncl show session control naming search path To display information about the search path maintained for backtranslation (address to node name translation), use the following command: $ ncl show session control backtranslation search path 3.4.3 Modifying the Naming and Backtranslation Search Paths Digital recommends that you rerun the configuration procedure to create a revised /var/dna/decnet-dirsvc.conf file whenever the name service information for the node requires modification. Whenever you run the configuration procedure, you are prompted to reenter your node full name. Include the LOCAL:, DECdns, or DOMAIN: namespace nickname to specify the primary name service. The naming search path set up by the configuration procedure contains an ordered list of name service keywords, each followed by a naming template that specifies a "defaulting rule" so users can enter shorter node names. In each template, the user-supplied portion of the name (usually the node's terminating name or rightmost simple name) is indicated with an asterisk (*). If you want the user-supplied name to be passed to the name service 3-8 Basic Configuration exactly as entered by the user, the template should simply be specified as follows: "*". Supply only one asterisk (*) per template. If more than one is supplied in the template, only the first occurrence is substituted with the user-supplied name. Any additional asterisks are passed to the name service as part of the full name. When you specify a template without an asterisk, the template string is passed to the name service unchanged. The following NCL set commands modify existing naming and backtranslation naming templates for a system. ncl> ncl set session control naming search path = { - [directory service=DECdns,template=*], - [directory service=DECdns,template=ACME:*], - [directory service=DECdns,template=ACME:.MGMT.*], - [directory service=local,template=*], - [directory service=local,template=local:.*], - [directory service=local,template=LOCAL:*], - [directory service=DOMAIN,template=*] [directory service=DOMAIN,template="*.cid.ces.com"]} ncl> ncl set session control backtranslation search path = { - [directory service=DECdns,template=*], - [directory service=local,template=*], - [directory service=Domain,template=*]} Given the search path defined for forward translation in this example, a user-supplied name of accnt would be searched as follows, in the order shown: ___________________________________________________________ OrdeName_Searched_____Namespace_Searched___________________ 1. accnt DECdns 2. ACME:accnt DECdns 3. ACME:.MGMT.accnt DECdns 4. accnt Local 5. local:.accnt Local 6. LOCAL:accnt Local 7. accnt DNS/BIND Basic Configuration 3-9 ___________________________________________________________ OrdeName_Searched_____Namespace_Searched___________________ 8.__accnt.cid.ces.com_DNS/BIND_____________________________ Given the search path defined for backtranslation searches in the preceding example, a user-supplied address would be searched for exactly as specified by the user, first in the DECdns namespace, then the local namespace, and then the DNS/BIND namespace. For any names found in the DECdns or local namespace, NSAP addresses are returned. DECnet/OSI uses these addresses to create logical links using DECnet Phase IV or OSI CLNP (Connectionless Network Protocol) protocols. For any names found in the DNS/BIND namespace, DECnet/OSI returns an IP address and sets up a DECnet over TCP/IP connection. 3.5 Starting the Configuration Procedure Before starting the terminal-based configuration procedure, create a log file of the configuration process to keep track of the configuration options you have selected. Use the following command to create the log file: #script /var/dna/filename.log After you complete the terminal-based configuration procedure, press Ctrl/D or type exit to save the log file. The graphical interface automatically logs messages to /var/dna/dxdecnetsetup_config.log. The settings used by the configuration procedure are recorded at the start of the log. 3.5.1 Starting the Terminal-Based Script To start the terminal-based basic configuration procedure, issue this command: #/usr/sbin/decnetsetup basic The procedure begins the configuration by displaying these informational messages: 3-10 Basic Configuration 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. ________________________ Note ________________________ If your display variable is set and no defaults file exists in your directory, the command-based script will ask you if you want to use the graphical user interface instead. ______________________________________________________ 3.5.2 Starting the Graphical Interface To invoke the graphical interface use the following command: # /usr/sbin/dxdecnetsetup 3.6 Specifying Your DECnet/OSI Node Name As you continue the configuration, the next step is to specify your DECnet/OSI node name. The DECnet/OSI node name is the full name of the node in the DECdns namespace, Local namespace, or DNS/BIND. If you are using the Local namespace, include LOCAL: as the nickname (prefix). If you are using the DECdns namespace, include your namespace nickname in the full name. (If you specify a Phase IV node name, the procedure automatically assumes you are using the Local namespace and asks you to confirm.) If you are using the DNS/BIND service, include DOMAIN: as the namespace nickname preceding the fully qualified domain name. For more information about the Local namespace, the DECdns distributed namespace, and the DNS/BIND distributed name service, see the DECnet/OSI Planning Guide. If you do not know which ones to use, consult your network manager. The node name uses the form: NamespaceNickname:.DirectoryPath.NodeObject Basic Configuration 3-11 For the Local namespace, specify LOCAL: as the namespace nickname. DECnet/OSI recognizes that a node full name beginning with LOCAL: as the namespace nickname is stored in the Local namespace. In this case, the node name uses the form: LOCAL:.DirectoryPath.Nodename The format of the full name you specify determines which name service is to be searched first when looking up names and addressing information. For more information about the search path, see the DECnet/OSI Network Management guide. Enter your DECnet/OSI (Phase V) node name at the prompt: What is the Phase V node name? [no default]: ________________________ Note ________________________ If you have installed DECnet/OSI before on this system, the procedure displays a default node name. ______________________________________________________ Use the following guidelines for selecting a node name: o The node name must begin with the nickname and a colon (:). o The directory path must begin with a dot (.). o The node name can be up to 255 characters long. o No part of the name can be a null string. o The only valid unquoted characters are letters, numbers, hyphens (-), underscores (_), and dollar signs ($). o Some other characters are allowed if they are enclosed in quotation marks. You can find a list of these characters in Appendix A of the DECnet/OSI DECdns Management guide. 3-12 Basic Configuration The following are some examples of DECnet/OSI node names: LOCAL:.TomThumb DOMAIN:.werner.afsg.comms.org XYZ_CORP:.sales.west_coast.WillyLoman Europe:.Erin.County_Cork.Bantry.Glengarriff_Road.MACotter You should carefully plan DECnet/OSI node names and ensure that each is unique within the namespace. If your network administrator has not assigned a unique node name for your system, be sure that you read the DECnet/OSI Planning Guide before you assign a node name for your system. This book also contains guidelines for using the Local namespace and information on how to set up a distributed or Local namespace. 3.6.1 Using a Local Namespace The Local namespace is a discrete, nondistributed namespace that exists on a single node and provides that node with a local database of name and addressing information. Depending on the number of address towers stored, the Local namespace is designed to scale to at least 100,000 nodes. The LOCAL: (or local:) namespace nickname is reserved to indicate that the information for a node is stored in the Local namespace. DECnet/OSI recognizes that a node full name beginning with LOCAL: is stored in a Local namespace. The following are typical node full names properly formatted for the Local namespace: LOCAL:.xyz.abc and local:.maximum. Unlike DECdns, the Local namespace does not employ backtranslation directories for address-to-node-name translation. You can configure a Local namespace on one node, selected nodes, or all nodes in the network. Use the following format to specify node names when you create a Local namespace: LOCAL:.your_nodename The configuration procedure generates the following local database files in /var/dna: dna_local_name_database_dat.dir dna_local_name_database_dat.pag Basic Configuration 3-13 dna_local_name_database_name.dir dna_local_name_database_name.pag dna_local_name_database_net.dir dna_local_name_database_net.pag dna_local_name_database_syn.dir dna_local_name_database_syn.pag 3.6.2 Using a DECdns Distributed Namespace If you plan to use a distributed namespace, the namespace nickname that you specify is the actual name of the distributed namespace where your system is registered. 3.6.3 Using the DNS/BIND Naming Service If you want to use DECnet applications over TCP/IP with DNS/BIND as the primary name service, enter the fully qualified domain name prefixed with the DOMAIN: nickname as in the following example: DOMAIN:.w-loman.sales.west-coast.org This automatically configures the DECnet over TCP/IP transport service, and lists "Domain" as the first naming service in the Session Control naming search path list. The use of this naming service does not exclude the use of either DECdns or Local naming services, both of which will also be included in the search list by default. 3.7 Giving Your System a Node Synonym This step is optional. You do not have to give your system a node synonym. This Phase IV style name is a synonym for the full name stored in the namespace. The node synonym is primarily a transition tool that allows you to use a Phase IV style node name for your DECnet/OSI node. Users and applications can then reference your node using this synonym rather than the full name of the node. If you were using DECnet Phase IV, consider using your Phase IV node name as your synonym. The synonym is required for Phase IV applications that can only handle Phase IV style node names. If your network has only DECnet/OSI or OSI systems, you may not need a synonym. 3-14 Basic Configuration 3.7.1 Specifying Your Node Synonym The configuration asks if you want to give your system a node synonym. The default node synonym is the first six characters of the node object. The synonym can be between one and six characters long and must be unique within your namespace. The node object is the string that follows the last period of your full name. For example, if you specify XYZ_CORP:.sales.west_coast.WillyLoman as a DECnet/OSI full name, the node object is WillyLoman and your default node synonym is WillyL. The following example shows a default node synonym: What is the Phase IV compatible synonym? [WillyL] At this prompt in the terminal-based script, you can: o Accept the default synonym by pressing Return. o Enter a new synonym and press Return. o Type two quotation marks ("") and press Return if you do not want to specify a synonym at this time. With the graphical interface, you can accept the default by not responding to the prompt, or you can enter a new synonym, or you can erase the default response so that no synonym is configured. If you want to give your system a node synonym later, use the decnet_register tool. 3.8 Communicating with Phase IV Nodes If your system needs to communicate with Phase IV nodes, you need a Phase IV compatible address. A DECnet Phase IV compatible address conforms to the Phase IV area and node limits; the area number is from 1 to 63, and the node number is from 1 to 1023, as in this example: 36.515. If no Phase IV systems exist on your network or you do not want to communicate with Phase IV systems, you do not need a Phase IV compatible address. If you do not want a Phase IV compatible address, go to Section 3.11. Basic Configuration 3-15 3.8.1 Supplying an Address Supply a Phase IV compatible address at this prompt: What is the Phase IV compatible node address? [0]: If you want your system to be able to communicate with Phase IV nodes, enter a Phase IV compatible address in response to the question. If you do not want a Phase IV compatible address, enter the number 0 and press Return. (With the graphical interface, leave the address field blank.) If you are unsure of your Phase IV compatible node address, contact your network manager. 3.9 Configuring Multiple Communications Devices The configuration procedure can determine whether your system has more than one communications device (there will be a pause while the procedure determines which devices are available). If your system has multiple synchronous devices, the terminal-based basic configuration procedure displays the names of the devices and asks you to list the devices you want to configure. The default is to configure all the listed devices (press Return). The graphics-based procedure is different. The graphics- based procedure displays a list of LAN interface devices if more than one exists on your system. Otherwise, no device list is displayed. The following example, from a terminal-based script, shows how to select two of four communications devices to use with DECnet/OSI. Enter the list of communications devices on which you will be running the DECnet Phase V software. If there is more than one device, separate them by spaces. [ln0 ln1 fta0 fta1 ]: ln0 fta1 FDDI routing circuits will be configured as CSMA-CD type circuits with the corresponding data-link block size. The script /var/dna/start_routing.ncl contains the commands to enable FDDI circuit support and the large packet support. Segregated mode is the default setting. For more information, see the (NET_MGMT) guide. 3-16 Basic Configuration 3.10 Configuring a Token Ring Communications Device If you have an unconfigured Token Ring communications device, you must supply a ring speed for the device at this prompt: The Token Ring interface operates at 16 Mbs or 4 Mbs. Please specify the speed at which the adapter should enter the ring. Enter the Token Ring speed [16]: The Token Ring interface operates at one of two speeds: 4 MB per second or 16 MB per second. All stations connected to the same ring must be configured to operate at the same speed. Determine the correct speed at which this device should run, by checking the speed of existing Token Ring stations or checking with the network manager. If your device is already configured or you do not have Token Ring, you are not prompted for the information. 3.10.1 Setting the Token Ring Station Speed DECnet/OSI for Digital UNIX stations in a Token Ring LAN can operate on either 4 or 16 MB per second data rates. A station can insert onto a Token Ring only at the ring's established data rate (ring speed). The station's ring speed can be set either by using the netsetup utility to configure the station's Token Ring adapter, or by the configuration procedure. Be aware of the ring speed of the Token Ring LAN where the station is to be inserted. If the ring speed is set to the wrong value then the ring insertion process will fail. If the station fails to insert or connect correctly, messages appear in the Session Manager window: vmunix: tra0: MAC_OPEN : tra0: Ring status: Ring recovery vmunix: Open error: Phase: Physical insertion; You can also query the state of the Token Ring adapter. For example: # ifconfig tra0 tra0: flags=8822 Basic Configuration 3-17 This indicates that the adapter is not active and that the station failed to insert on to the ring. The station has successfully inserted on to the ring if the same command yields: # ifconfig tra0 tra0: flags=8863 3.11 Confirming Your Answers and Starting the DECnet/OSI Software Before the terminal-based configuration procedure actually configures your system, it asks you to confirm your answers for the following values for your system: o Full DECnet/OSI name o Node synonym (if you have one) o Phase IV address (if you have one) o DECdts role (clerk) o Token Ring device speed o DECdns clerk or Local namespace You can choose from four ways to proceed with the terminal- based script: 1. If you are satisfied with your answers and want to continue the configuration, type continue and press Return. The procedure configures your system and saves your answers in a defaults file to use if you rerun the procedure. 2. If you want to change one (or more) of your answers, type restart and press Return. This action starts the configuration procedure again from the beginning with your previous answers supplied as default values to each question. 3. If you are satisfied with the answers but do not want to continue to configure your system, type stop and press Return. This stops the configuration procedure and saves your answers in a defaults file. 4. If you want to exit the configuration procedure and do not want to save your answers in a defaults file, type quit and press Return. 3-18 Basic Configuration With the graphical interface, you can view the answers you have supplied on the screen. You then have the following ways to proceed: 1. If you are satisfied with your answers and want to continue the configuration, select the Configure button. The procedure configures your system and saves your answers in a defaults file to use if you rerun the procedure. 2. If you want to change one (or more) of your answers, change them in the DECnet/OSI Setup window, or select the Reset button to return values to the previous answers supplied when the software was last configured. 3. If you want to exit the configuration procedure and do not want to save your answers in a defaults file, select the Cancel button. 4. If you are a root user, and you want to exit the configuration procedure saving your answers as defaults, use the Exit option in the File menu. If you are not a root user, the Exit option has the same effect as the Cancel button: it does not save your input as defaults. This example shows how to respond if you are satisfied with the answers you supplied to a terminal-based script: Please review the following information which you have supplied, and if it is correct enter "Continue", which will start the DECnet software and complete the configuration. If there is incorrect information, or you wish to change a particular value, enter "Restart" to begin the setup again. If the information is correct, but you do not wish to complete the configuration at this time, enter "Stop". This will save the values you have entered, which will appear as defaults when you rerun this procedure. You may enter "Quit" to abort this procedure, without saving the answers. Nodename: LOCAL:.coyote Node Synonym: coyote Phase IV Address: 47.723 Phase IV Prefix: 49:: Network Devices: ln0 Basic Configuration 3-19 This system will autoconfigure addresses. This system will be a DTSS clerk. This system will use the Local namespace This system will be configured to service MOP requests. Do you wish to complete this DECnet/OSI configuration? [continue] If you continue (c), the procedure: o Creates startup files o Modifies system files o Starts up the DECnet software Once the procedure starts to configure DECnet, do not stop it. During the startup process, you receive informational messages similar to these: Creating defaults file. Creating Initialization NCL scripts Creating /usr/sbin/decnetstartup Creating /usr/sbin/osi_applstartup Updating /var/dna/dna_version Modifying /usr/sbin/decnetshutdown Event Logging ... Configuring "CTF Collector Components " (CTABASE300) Creating Session Control Modifying /var/dss/dns/dns-names Starting DECnet/OSI Datalink ... Routing ... NSP ... OSI Transport ... Session Control ... Local Namespace successfully configured. Modifying /var/dss/dns/dns-names Node name reset to Local:.coyote Setting Session Control attributes DTSS ... Node Enabled ... Event Logging Event Logging ... DECnet/OSI RFC 1006 (OSI over TCP) has been enabled. rfc1006setup completed successfully. Initializing the Local Namespace Will create a new /var/dna/dna_local_name_database_nam.dir Directory Service: Local name file Registering the node: local:.coyote 3-20 Basic Configuration The configuration of DECnet/OSI is completed. You can test DECnet functionality with the utility /usr/sbin/dnet_check. This performs various local and remote functions, and requires an account (and password) on this system and one other DECnet node. After verifying that the system is operating properly with DECnet installed you may wish to remove the following saved files: - /var/dna/scripts/start_*.ncl.sav[n] Note: There is no guest account in your system. If you wish to allow default FAL access to this system from remote systems, you should create a guest account. This would allow access when no user name or password is specified. The password field for this account should be set to Nologin to prevent unauthorized access to your system. Alternatively, you could change the User Name attribute of the session control application "fal" to use a different account. See the Guide to Network Management for details. Note: This node has been configured to use the Local Namespace. If you wish to add, modify, or delete a node or its associated addressing information, you should use the utility /usr/sbin/decnet_register to add or change definitions. You may also use the /usr/sbin/update_nodes utility to copy a Phase IV nodes database or Phase V LNO load file from a remote system, as in the following example: /usr/sbin/update_nodes -dlocal 4.1002 This command will copy a DECnet address file from the remote system, and automatically populate the local naming file. Please refer to the installation guide for further details. decnetsetup completed successfully. 3.11.1 Additional Configuration Tasks After configuring DECnet/OSI, verify the basic configuration procedure as explained in Section 3.14. Note that you can perform the following additional configuration tasks, explained in the indicated sections: o Configure the DECnet-Internet Gateway - Section 3.12 o Configure the OSI applications software (FTAM and Virtual Terminal) - Section 3.13 Basic Configuration 3-21 3.12 Configuring the DECnet-Internet Gateway If you installed the DECnet-Internet Gateway subset, you can configure the software after you complete the basic configuration. Use the following command: # /usr/sbin/decnetsetup gateway For more details, see Chapter 5. 3.13 Configuring the OSI Applications Software If you installed the DECnet/OSI Base Components (DNABASE400) subset, OSI applications software (FTAM and Virtual Terminal) was installed on your system. You can configure the OSI applications software after you complete the basic configuration. Use the following command to start the OSI application configuration procedure: # /usr/sbin/osiapplsetup Chapter 7 contains detailed instructions on configuring the OSI applications software. 3.14 Verifying the Basic Configuration Procedure Once your system is registered in the namespace, the installation and configuration are finished. If necessary, perform the postinstallation tasks in Chapter 5, and then proceed to Chapter 6. Chapter 6 includes instructions on how to run the /usr/sbin/dnet_check configuration verification procedure (IVP). This procedure tests and exercises your DECnet/OSI communications software to ensure that you configured the software properly. 3-22 Basic Configuration 4 _________________________________________________________________ Advanced Configuration This chapter discusses the following about advanced configuration: o When to use the advanced configuration procedure and how to start it o Specifying your DECnet/OSI node name and node synonym o Communicating with Phase IV nodes o Using an alternate node synonym directory o Configuring network addresses o Configuring multiple communications devices o Configuring a Token Ring communications device o Configuring Digital Distributed Time Service (DECdts) o Configuring the DECnet-Internet Gateway o Configuring DECnet applications to run over a TCP/IP connection o Configuring to service MOP requests o Configuring DECnet/OSI to use Wide Area Networking Support for Digital UNIX and X.25 services o Configuring mailsetup o Configuring the OSI applications software (FTAM and Virtual Terminal) o Starting DECnet/OSI software o Configuring DECdns or the Local namespace Advanced Configuration 4-1 4.1 When to Use the Advanced Configuration Use the advanced configuration procedure with DECnet/OSI if you have any of the following configuration requirements: 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 configure your DECnet/OSI software to use wide-area networking (X.25) services. o You want to manually configure your network addresses. o You want to use an alternate node synonym directory. o You want to configure DECnet over TCP/IP software without using DNS/BIND as the primary name service. o You want to configure DECnet/OSI to service MOP requests. o You want to configure the DECnet-Internet Gateway. (You can use the basic configuration for this feature as well.) Before you run the advanced configuration procedure, fill out the checklist shown in Figure 4-1 to ensure that you have all necessary information. Figure 4-1 Advanced Configuration Checklist (continued on next page) 4-2 Advanced Configuration Figure 4-1 (Cont.) Advanced Configuration Checklist Advanced Configuration 4-3 4.1.1 About the Advanced Configuration Procedure The configuration procedure displays a series of questions that prompt you for information about your system's configuration. The following list describes the information you are asked to provide for your system during the configuration. Some of the information is optional and depends on your system's configuration: o DECnet/OSI (Phase V) node name o Phase IV compatible synonym o Phase IV compatible node address o Phase IV Prefix value for this network o Alternate node synonym directory o Network addresses (automatic or manual address configuration) o Communications devices o Token Ring speed for device o DECdts configuration (clerk or server) o DECnet-Internet Gateway configuration o Running DECnet applications over TCP/IP o Servicing MOP requests o Wide Area Networking Support for Digital UNIX and X.25 configuration At the end of the terminal-based configuration procedure, you are prompted to confirm the configuration values that you entered. If you are using the graphical interface, you are not prompted to confirm the configuration values. In either case, you can: o Quit the procedure without saving the values. o Save the entries and exit the procedure. o Restart the procedure (with the graphical interface, reset the values to previously saved defaults). 4-4 Advanced Configuration o Continue with the configuration by starting the DECnet /OSI software. 4.1.1.1 Changing Your Answers Do not be concerned if you make a mistake or supply the wrong information for a question. You can verify your answers before DECnet/OSI is actually configured. If you are using the terminal-based script, you can restart the configuration procedure to change your answers. If you are using the graphical interface, you can change your responses anytime before selecting the Configure button. You can also reset the values to those defined as defaults. 4.1.1.2 Default Values Many of the questions have default values associated with them. This information is contained in brackets at the end of the question, as in the following example: What is the Phase IV compatible synonym? [WillyL]: Using the terminal-based script, if the default value, in this case WillyL, is correct, press Return. Using the graphical interface, if the default value is correct, you need not respond. It will be configured automatically when you press the Configure button. If you are rerunning this procedure (or, using the graphical interface, resetting the values), the default values are based on the information that you supplied previously. 4.1.1.3 Stopping the Configuration Procedure You can review your answers to the prompts and exit the configuration procedure before configuring DECnet/OSI by pressing Ctrl/C in the terminal-based script, or by selecting the Cancel button in the graphical interface. Do not stop the configuration process once it starts to configure the DECnet/OSI software. To change any information after this point, finish the configuration, shut down DECnet/OSI, then rerun the procedure with the new information. Advanced Configuration 4-5 4.1.1.4 Getting Help The configuration procedure prompts you for information. If you need help responding to any of these prompts in the terminal-based script, enter a question mark (?) and press Return to view the help text. The graphical interface displays pointer-sensitive help messages in a Help box. 4.2 How DECnet/OSI Uses the Naming Search Path DECnet/OSI supports the Local namespace, the DECdns distributed name service, and the Domain Name Service (DNS /BIND). DECdns is Digital's distributed network naming service. DNS/BIND is needed if you want DECnet/OSI to run applications over TCP/IP. DNS/BIND provides for the use of node synonyms (for backward compatibility with older applications that cannot use long domain names). DECnet/OSI for Digital UNIX includes support for NSAP addresses in DNS/BIND (see the DECnet/OSI Network Management guide). For more information about the Local namespace, the DECdns distributed namespace, and the DNS/BIND distributed name service, see the DECnet/OSI Planning Guide. (For additional information about managing the DNS/BIND namespace, see the appropriate TCP/IP documentation.) If you are not sure which name service to use and in which order, consult your network manager. The order in which DECnet/OSI searches the available name services for node name and address information is determined by the naming search path. The naming search path is set up during DECnet/OSI configuration and applies to DECnet applications systemwide. The naming search path describes: o The order in which the name services are to be searched for names and addressing information o How DECnet/OSI should interpret any abbreviated node names entered by users. The search path includes naming templates that tell DECnet/OSI how to interpret any abbreviated node names entered by users. The primary name service (the name service to be searched first) is listed before the secondary name services. The secondary name services are listed in the order in which they are to be searched after the primary name service. 4-6 Advanced Configuration The ordering of the name services is very important. The first name service listed is the primary name service to use on the system. The primary name service is considered the first choice to use when looking up names and addressing information. The remaining name services listed are considered to be the secondary services to use on the system. The search path contains a list of name service keywords, each followed by a naming template that specifies a "defaulting rule" so users can enter shorter node names. Note that the search path information for a system is maintained in two separate search paths: o One for forward translation or naming (node-name-to- address translation). o One for backtranslation (address-to-node-name translation). 4.2.1 Configuring the Naming Search Path The DECnet/OSI configuration procedure sets up one or more name services on your system. You specify your node's full name properly formatted for the name service to be searched first. From this information, the configuration procedure constructs a properly formatted full name for the name service to be searched next. Running the configuration procedure creates /var/dna /decnet-dirsvc.conf, which contains the naming search path information for the node. Do not edit this file. If you must make changes to /var/dna/decnet-dirsvc.conf, use the NCL set commands described in Section 4.2.3 to modify the naming templates or rerun the configuration procedure to designate a new primary name service and change the order in which the name services are searched. If you specify a full name beginning with the namespace nickname LOCAL: (or local:), DECnet/OSI searches the Local namespace first for forward and back translation information. If DECnet/OSI does not find a Local namespace or the Local namespace does not contain name and addressing information for the specified node, then DECnet/OSI searches the DECdns namespace. If it does not find information for the node in the DECdns namespace, DECnet Advanced Configuration 4-7 /OSI then searches the Local namespace. If the information is not found in the Local namespace, and DECnet over TCP/IP is configured, DECnet/OSI then searches DNS/BIND. Similarly, if you specify a full name containing a namespace nickname for a DECdns namespace (for example, ABCDE:.xyz.abc), then DECnet/OSI searches the specified DECdns namespace (ABCDE:) first for forward and back translation information. If it does not find information for the node, DECnet/OSI then searches the Local namespace. If the information is not found in the Local namespace, and DECnet over TCP/IP is configured, DECnet/OSI then searches DNS/BIND. ________________________ Note ________________________ If your node is a DECdns server, the primary name service must be DECdns. ______________________________________________________ If the system administrator specified a fully qualified domain name prefixed with the DOMAIN: nickname, DECnet /OSI searches the DNS/BIND namespace first for forward and back translation information. If DNS/BIND does not contain name and addressing information for the specified node, then DECnet/OSI searches the Local namespace. If DECnet/OSI does not find a Local namespace, or if the Local namespace does not contain name and addressing information for the specified node, then DECnet/OSI searches the DECdns namespace. 4.2.2 Displaying the Search Path Information To display information about the search path maintained for forward translation or naming (node name to address translation), use the following command: $ ncl show session control naming search path 4-8 Advanced Configuration To display information about the search path maintained for backtranslation (address to node name translation), use the following command: $ ncl show session control backtranslation search path 4.2.3 Modifying the Naming and Backtranslation Search Paths Digital recommends that you rerun the configuration procedure to create a revised /var/dna/decnet-dirsvc.conf file whenever the name service information for the node requires modification. Whenever you run the configuration procedure, you are prompted to reenter your node full name. Include the LOCAL:, DECdns, or DOMAIN: namespace nickname to specify the primary name service. The naming search path set up by the configuration procedure contains an ordered list of name service keywords, each followed by a naming template that specifies a "defaulting rule" so users can enter shorter node names. In each template, the user-supplied portion of the name (usually the node's terminating name or rightmost simple name) is indicated with an asterisk (*). If you want the user-supplied name to be passed to the name service exactly as entered by the user, the template should simply be specified as follows: "*". Supply only one asterisk (*) per template. If more than one is supplied in the template, only the first occurrence is substituted with the user-supplied name. Any additional asterisks are passed to the name service as part of the full name. When you specify a template without an asterisk, the template string is passed to the name service unchanged. The following NCL set commands modify existing naming and backtranslation naming templates for a system. Advanced Configuration 4-9 ncl> ncl set session control naming search path = { - [directory service=DECdns,template=*], - [directory service=DECdns,template=ACME:*], - [directory service=DECdns,template=ACME:.MGMT.*], - [directory service=local,template=*], - [directory service=local,template=local:.*], - [directory service=local,template=LOCAL:*], - [directory service=DOMAIN,template=*] [directory service=DOMAIN,template="*.cid.ces.com"]} ncl> ncl set session control backtranslation search path = { - [directory service=DECdns,template=*], - [directory service=local,template=*], - [directory service=Domain,template=*]} Given the search path defined for forward translation in this example, a user-supplied name of accnt would be searched as follows, in the order shown: ___________________________________________________________ OrdeName_Searched_____Namespace_Searched___________________ 1. accnt DECdns 2. ACME:accnt DECdns 3. ACME:.MGMT.accnt DECdns 4. accnt Local 5. local:.accnt Local 6. LOCAL:accnt Local 7. accnt DNS/BIND 8.__accnt.cid.ces.com_DNS/BIND_____________________________ Given the search path defined for backtranslation searches in the preceding example, a user-supplied address would be searched exactly as specified by the user, first in the DECdns namespace, then the local namespace, and then the DNS/BIND namespace. For any names found in the DECdns or local namespace, NSAP addresses are returned. DECnet/OSI uses these addresses to create logical links using DECnet Phase IV or OSI CLNP (Connectionless Network Protocol) protocols. For any names found in the DNS/BIND namespace, DECnet/OSI returns an IP address and sets up a DECnet over TCP/IP connection. 4-10 Advanced Configuration 4.3 Starting the Configuration Procedure Before starting the terminal-based configuration procedure, you might want to create a log file of the configuration process. You can use this log file to keep track of the configuration options you have selected. Use the following command to create the log file: #script /var/dna/filename.log After you complete the configuration procedure, press Ctrl /D or type exit to save the log file. The graphical interface automatically logs messages to /var/dna/dxdecnetsetup_config.log. The settings used by the configuration procedure are recorded at the start of the log. 4.3.1 Starting the Terminal-Based Script To start the terminal-based advanced configuration procedure, issue this command: #/usr/sbin/decnetsetup advanced The procedure begins the configuration by displaying these informational messages: 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. ________________________ Note ________________________ If your display variable is set and no defaults file exists in your directory, the command-based script will ask you if you want to use the graphical user interface instead. ______________________________________________________ Advanced Configuration 4-11 4.3.2 Starting the Graphical Interface To invoke the graphical interface, use the following command: # /usr/sbin/dxdecnetsetup 4.4 Specifying Your DECnet/OSI Node Name As you continue the configuration, the next step is to specify your DECnet/OSI node name. The DECnet/OSI node name is the full name of the node, as used in the DECdns namespace, the Local namespace, or in the Domain Name Service (DNS/BIND). If you are using the Local namespace, include LOCAL: as the nickname (prefix). If you are using the DECdns namespace, include your namespace nickname in the full name. (If you specify a Phase IV node name, the procedure automatically assumes you are using the Local namespace and asks you to confirm.) If you are using the DNS/BIND service, include DOMAIN as the namespace nickname. The DECnet/OSI Planning Guide contains more information about the Local namespace, the DECdns distributed namespace, and the DNS/BIND distributed name service. If you do not know which name service to use, consult your network manager. The node name uses the form: NamespaceNickname:.DirectoryPath.NodeObject For the Local namespace, specify LOCAL: as the namespace nickname. DECnet/OSI recognizes that a node full name beginning with the LOCAL: in place of the DECdns namespace nickname is stored in the Local namespace. In this case, the node name uses the form: LOCAL:.DirectoryPath.Nodename The format of the full name you specify determines which name service is to be searched first when looking up names and addressing information. For more information about the search path, see Section 4.2. 4-12 Advanced Configuration Enter your DECnet/OSI (Phase V) node name at the prompt: What is the Phase V node name? [no default]: ________________________ Note ________________________ If you have installed DECnet/OSI before on this system, the procedure displays a default node name. ______________________________________________________ Use the following guidelines for selecting a node name: o The node name must begin with the nickname and a colon (:). o The directory path must begin with a dot (.). o The node name can be up to 255 characters long. o No part of the name can be a null string. o The only valid unquoted characters are letters, numbers, hyphens (-), underscores (_), and dollar signs ($). o Some other characters are allowed if they are enclosed in quotation marks. You can find a list of these characters in Appendix A of the DECnet/OSI DECdns Management guide. The following are some examples of DECnet/OSI node names: LOCAL:.TomThumb DOMAIN:.werner.afsg.comms.org XYZ_CORP:.sales.west_coast.WillyLoman Europe:.Erin.County_Cork.Bantry.Glengarriff_Road.MACotter You should carefully plan DECnet/OSI node names and ensure that each is unique within the namespace. If your network administrator has not assigned a unique node name for your system, be sure that you read DECnet/OSI Planning Guide before you assign a node name for your system. This book also contains guidelines for using the Local namespace and information on how to set up a distributed or Local namespace. Advanced Configuration 4-13 4.4.1 Using a Local Namespace The Local namespace is a discrete, nondistributed namespace that exists on a single node and provides that node with a local database of name and addressing information. Depending on the number of address towers stored, the Local namespace is designed to scale to at least 100,000 nodes. The LOCAL: (or local:) namespace nickname is reserved to indicate that the information for a node is stored in the Local namespace. DECnet/OSI recognizes that a node full name beginning with LOCAL: is stored in a Local namespace. The following are typical node full names properly formatted for the Local namespace: LOCAL:.xyz.abc and local:.maximum. Unlike DECdns, the Local namespace does not employ backtranslation directories for address-to-node-name translation. You can configure a Local namespace on one node, selected nodes, or all nodes in the network. Use the following format to specify node names when you create a Local namespace: LOCAL:.your_nodename The configuration procedure generates the following local database files in /var/dna: dna_local_name_database_dat.dir dna_local_name_database_dat.pag dna_local_name_database_name.dir dna_local_name_database_name.pag dna_local_name_database_net.dir dna_local_name_database_net.pag dna_local_name_database_syn.dir dna_local_name_database_syn.pag 4-14 Advanced Configuration 4.4.2 Using a DECdns Distributed Namespace If you plan to use a distributed namespace, the namespace nickname that you specify is the actual name of the distributed namespace where your system is registered. When you specify a DECdns namespace name or the LOCAL: namespace nickname, the configuration procedure automatically configures your system as a DECdns clerk. After configuring DECnet/OSI, you can use various DECdns commands and utilities to perform namespace activities. See the DECnet/OSI DECdns Management guide for more information. 4.4.3 Using the DNS/BIND Naming Service If you want to use DECnet applications over TCP/IP with DNS/BIND as the primary name service, enter the fully qualified domain name prefixed with the DOMAIN: nickname as in the following example: DOMAIN:.w-loman.sales.west-coast.org This automatically configures the DECnet over TCP/IP transport service, and lists DOMAIN as the first naming service in the Session Control naming search path list. The use of this naming service does not exclude the use of either DECdns or Local naming services, both of which will also be included in the search list by default. 4.5 Giving Your System a Node Synonym This step is optional. You do not have to give your system a node synonym. This Phase IV style name is a synonym for the full name stored in the namespace. The synonym can be between one and six characters long and must be unique within your namespace. The node synonym is primarily a transition tool that allows you to use a Phase IV style node name for your DECnet/OSI node. Users and applications can then reference your node using this synonym rather than the full name of the node. If you were using DECnet Phase IV, consider using your Phase IV node name as your synonym. The synonym is required for Phase IV applications that can only handle Phase IV style node names. If your network only has DECnet/OSI or OSI systems, you may not need a synonym. Advanced Configuration 4-15 4.5.1 Specifying Your Node Synonym The configuration asks if you want to give your system a node synonym. The default node synonym is the first six characters of the node object. The synonym can be between one and six characters long and must be unique within your namespace. The node object is the string that follows the last period of your full name. For example, if you specify XYZ_CORP:.sales.west_coast.WillyLoman as a DECnet/OSI full name, the node object is WillyLoman and your default node synonym is WillyL. The following example shows a default node synonym: What is your Phase IV compatible synonym? [WillyL]: At this prompt in the terminal-based script, you can: o Accept the default synonym by pressing Return. o Enter a new synonym and press Return. o Type two quotation marks ("") and press Return if you do not want to specify a synonym at this time. With the graphical interface, you can accept the default by not responding to the prompt, or you can enter a new synonym, or you can erase the default response so that no synonym is configured. If you want to give your system a node synonym later, you can do so using the decnet_register tool. 4.6 Communicating with Phase IV Nodes If your system needs to communicate with Phase IV nodes, you need a Phase IV compatible address. A DECnet Phase IV compatible address conforms to the Phase IV area and node limits; the area number is from 1 to 63, and the node number is from 1 to 1023, as in this example: 36.515. If no Phase IV systems exist on your network or you do not want to communicate with Phase IV systems, you do not need a Phase IV compatible address. If you do not want a Phase IV compatible address, go to Section 4.8. 4-16 Advanced Configuration 4.6.1 Supplying an Address Supply a Phase IV compatible address at this prompt: What is your DECnet Phase IV compatible node address ? [0]: If you want your system to be able to communicate with Phase IV nodes, enter a Phase IV compatible address in response to the question. If you do not want a Phase IV compatible address, enter the number 0 and press Return. (With the graphical interface, leave the address field blank.) If you are unsure of your Phase IV compatible address, contact your network manager. 4.6.2 Supplying a Phase IV Prefix If you choose to use a Phase IV compatible address, you must supply an additional piece of addressing information called a Phase IV prefix. DECnet/OSI systems reference all network addresses (including Phase IV addresses) using OSI address formats (network service access points -NSAPs). The Phase IV prefix and the Phase IV node address are used to construct a complete NSAP for this system. The DECnet/OSI systems within a single routing domain use this Phase IV prefix to form the Phase IV compatible NSAP. This prefix consists of the OSI address initial domain part (IDP) and possibly the preDSP portion (sometimes known as the high order DSP) of the domain specific part (DSP). The DECnet/OSI Planning Guide contains more information about NSAP formats. Enter your Phase IV prefix at this prompt: What is the Phase IV Prefix value for this network? [49::] The default value for the prefix is the number 49::, which specifies that your system is part of a private local network. This value is generally appropriate for networks that are not interconnected with other OSI networks. If your network is going to be connected with other OSI networks, you must enter a globally unique IDP. Advanced Configuration 4-17 If your organization has allocated its own IDP, you can enter that value instead of 49::. If you are in doubt about which prefix value to use, contact your network manager. ________________________ Note ________________________ If you are using an IDP other than 49::, the IDP must be globally unique. Your IDP must be assigned by an authorized standards organization, such as ANSI, or you must construct an IDP that you know will be unique (based on your telephone number, for instance). You can find out more information about IDPs by typing ? in response to the prompt. For a detailed description of how to construct an IDP and how to apply to a standards organization for an IDP, see the DECnet /OSI Planning Guide. ______________________________________________________ 4.7 Using an Alternate Node Synonym Directory If you have a large network and would like to use an alternate node synonym directory rather than using the default node synonym directory of .DNA_NodeSynonym, you may enter one at the following prompt. The value for the alternate node synonym directory must be a DECdns directory full name (for example: .USA_Synonyms). What is the node synonym directory in the XYZ_CORP namespace? [.DNA_NodeSynonym]: 4.8 Configuring Network Addresses Your system must have at least one unique network address in order to use DECnet/OSI communications features. DECnet /OSI systems can be multihomed, that is, they can have more than one network address. DECnet/OSI allows you to have up to three network addresses. Having multiple addresses allows you to have both a DECnet /OSI extended address and a Phase IV compatible address, so you can communicate with both Phase IV and DECnet/OSI systems on the same network. It also allows you to belong to more than one OSI network. This feature is particularly useful when you need to combine two (or more) networks. 4-18 Advanced Configuration Rather than have all the systems in both networks get new addresses that reflect the new combined network, those systems that need to participate in both networks can have an address in each one. Network addresses are sometimes referred to in OSI terminology as network entity titles (NETs). NETs are NSAPs with a selector of 00. There are two ways to configure NETs: by autoconfiguring addresses or by manually configuring addresses. 4.8.1 Choice 1: Autoconfiguring Addresses This method is the easiest way to configure NETs. If you have a DECnet/OSI Phase V conformant router (or intermediate system, IS) adjacent to your system (on the same LAN or connected to your system by a point-to- point link), you can let the router supply your node with network addresses. If you are configuring your system as part of a DECnet Phase V environment, you should answer Yes to the autoconfiguration question. If the network is a heterogeneous OSI environment, answer No in order to manually configure your system's network address(es). If you select autoconfiguration, all IDPs are set to the IDP used by the router. Select autoconfiguration by answering yes to the following question. Then go to Section 4.9. Will this system autoconfigure its network addresses? [y]: 4.8.2 Choice 2: Manually Configuring Addresses If you answer no to the autoconfiguration question, you must manually configure your NETs. In this case, your network manager must supply them to you or you must construct them yourself. If you know which NETs to use, you can continue to configure DECnet. If you have to construct your own NETs, refer to the DECnet/OSI Planning Guide for instructions. Continue this configuration only when you know which NETs to use. When you manually configure NETs, the procedure prompts you for network addresses. You must respond with at least one NET and you can supply up to three of them. This example shows how you would specify two NETs in the terminal-based script: Advanced Configuration 4-19 This system's current Node ID is: 08-00-2B-16-A8-72 Enter a Network Entity Title [0] (Enter 0 to continue): 39:250:FF-00-41:08-00-2B-16-A8-72:00 Enter a Network Entity Title [0] (Enter 0 to continue): 49::00-70:08-00-2B-16-A8-72:00 Enter a Network Entity Title (Enter 0 to continue): 0 NETs must be entered in Digital Network Architectur (DNA) format, which uses colons to separate fields and dashes to separate pairs of digits. Make sure that you include the 00 selector when you manually specify a NET. For more information on DNA and OSI NET formats, see the DECnet/OSI Planning Guide. The procedure presents you with a different series of prompts depending on whether you have specified a Phase IV compatible address. 4.8.2.1 If You Have a Phase IV Compatible Address If you are using a Phase IV compatible address, your NETs are used for the following purposes: o The first NET is your Phase IV compatible address. Though this address is used to communicate with Phase IV systems, it is translated into OSI address format. When you supply a Phase IV compatible address and prefix, the configuration procedure uses them to build a NET for you, which it then displays. For example: This system's current Node Id is 08-00-2B-16-A8-72 Setting the first NET (based on Phase IV compatible address and Phase IV Prefix) to: 49::00-24:AA-00-04-00-03-92:00 You cannot modify this NET. For more information on how Phase IV addresses are translated into OSI address format, see the DECnet/OSI Planning Guide. o The second NET is an additional DECnet/OSI address. You may enter a NET in response to the question. If you do not want another DECnet/OSI address, enter the number 0 and press Return. If you do this, you are not prompted for a third NET. 4-20 Advanced Configuration o The third NET is also an additional DECnet/OSI address. If you do not want another DECnet/OSI address, enter the number 0 and press Return. 4.8.2.2 If You Do Not Have a Phase IV Compatible Address If you are not using a Phase IV compatible address, your NETs are used for the following purposes: o The first NET is your first DECnet/OSI address. You must enter a NET in response to the question. o The second NET is an additional DECnet/OSI address. If you do not want another DECnet/OSI address, enter the number 0 and press Return. If you do this, you are not prompted for a third NET. o The third NET is also an additional DECnet/OSI address. If you do not want another DECnet/OSI address, enter the number 0 and press Return. 4.9 Configuring Multiple Communications Devices The configuration procedure can determine whether your system has more than one communications device (there will be a pause while the procedure determines which devices are available). If your system has multiple devices, the configuration procedure displays the names of these devices. You must select the devices you want to configure. The default is to configure all the listed devices. You can specify up to four communications device names. If your system has synchronous devices, the procedure lists these as well as the LAN devices. Using the terminal-based configuration procedure, configure synchronous devices by specifying the device names at the prompt, or else you can have the Wide Area Networking for Digital UNIX (X.25) software configure them separately. Likewise, using the graphical interface, configure the synchronous devices by selecting these devices manually. By default, only the LAN devices are selected. The following example, from a terminal-based script, shows how you would select two of four available LAN communications devices and a synchronous device to use with DECnet/OSI. Advanced Configuration 4-21 The following synchronous devices are available for use on this system. To configure the HDLC datalink using one of these devices, list the device name in the answer to the following question. Otherwise, they may be configured by the WAN communications software. Synchronous Devices: scc0 scc1 Enter the list of communications devices on which you will be running the DECnet Phase Vsoftware. If there is more than one device, separate them by spaces [te0 te1 fta1 fza0]: scc0 te0 fta1 FDDI routing circuits will be configured as CSMA-CD type circuits with the corresponding data-link block size. The script /var/dna/start_routing.ncl contains the commands to enable FDDI circuit support and the large packet support. Segregated mode is the default setting. For more information, see the DECnet/OSI Network Management guide. 4.10 Configuring a Token Ring Communications Device If you have an unconfigured Token Ring communications device, you must supply a ring speed for the device at this prompt: The Token Ring interface operates at 16 MB or 4 MB. Please specify the speed at which the adapter should enter the ring. Enter the Token Ring speed [16]: The Token Ring interface operates at one of two speeds: 4 MB per second or 16 MB per second. All stations connected to the same ring must be configured to operate at the same speed. Determine the correct speed at which this device should run, by checking the speed of existing Token Ring stations or checking with the network manager. If your device is already configured or you do not have Token Ring, you are not prompted for the information. 4.10.1 Setting the Token Ring Station Speed DECnet/OSI for Digital UNIX stations in a Token Ring LAN can operate on either 4 or 16 MB per second data rates. A station can insert onto a Token Ring only at the ring's established data rate (ring speed). The station's ring speed can be set either by using the netsetup utility to configure the station's Token Ring adapter, or by the decnetsetup utility. 4-22 Advanced Configuration Be aware of the ring speed of the Token Ring LAN where the station is to be inserted. If the ring speed is set to the wrong value, then the ring insertion process will fail. If the station fails to insert or connect correctly, messages appear in the Session Manager window: vmunix: tra0: MAC_OPEN : tra0: Ring status: Ring recovery vmunix: Open error: Phase: Physical insertion; You can also query the state of the Token Ring adapter. For example: # ifconfig tra0 tra0: flags=8822 This indicates that the adapter is not active and that the station failed to insert on to the ring. The station has successfully inserted on to the ring if the same command yields: # ifconfig tra0 tra0: flags=8863 4.11 Configuring DECdts Digital Distributed Time Service (DECdts) is included as part of the DECnet/OSI software to support components, such as network management and DECdns, that require time stamps. DECdts provides both clerk and server components. A DECdts clerk requests the time from DECdts servers which can provide the clerk with time synchronization services. DECdts servers have access to a list of synchronization services that they use to establish the network time. Most systems in a network should be configured as clerks and only some need to be servers. Configuring a system as a server does not necessarily impose any additional overhead on the system. Only one server on a LAN actually services clerk requests; the other servers are backups and one of them would become active only if the current server is unavailable. A typical LAN configuration would have three systems configured as servers and the rest of the systems configured as clerks, but you can have as few as one server. Advanced Configuration 4-23 If you do not know whether you should be a clerk or a server, contact your network administrator. For information on planning which systems should be clerks and which should be servers, refer to the DECnet/OSI Planning Guide. You can find a complete description of DECdts and its options in the DECnet/OSI DECdts Management guide. ________________________ Note ________________________ You can use a time synchronization service other than DECdts. If you are using such a service, you should not also configure DECdts as well. In that case, you should answer no to both the DECdts clerk and server questions. ______________________________________________________ 4.11.1 Configuring Your System as a DECdts Clerk or Server The terminal-based configuration procedure presents you with the following question: Will this system be configured as a DTSS clerk only? (y/n) [y]: If you want your system to be a clerk only, accept the default (yes) by pressing Return. If you want your system to be a DECdts server, follow these steps: 1. Answer the DTSS clerk-only question with no. 2. Answer the DTSS server question with yes. 4.12 Configuring the DECnet-Internet Gateway The next question appears only if you installed the DECnet- Internet Gateway subset. The question asks if you want to configure the DECnet-Internet Gateway software as follows (this example is from a terminal-based script). Will this system be configured as a DECnet-Internet Gateway? (y/n) [n]: If you want to configure the Gateway, answer yes to this question. If you are not going to use the Gateway, answer no. 4-24 Advanced Configuration If you copied the subset, but you do not want to configure it at this time, you can answer no and configure the software later using the following command: # /usr/sbin/decnetsetup gateway For more details, see Chapter 5. 4.13 Configuring DECnet Applications to Run Over a TCP/IP Connection If you have not specified the DOMAIN: namespace nickname in the Phase V node name, the procedure asks if you want to configure DECnet over TCP/IP. If you have specified DOMAIN: as the namespace nickname, the configuration procedure has already configured DECnet over TCP/IP with DNS/BIND as the primary name service. DOTI uses TCP/IP and BIND functionality provided by the Digital UNIX operating system. Before configuring DECnet /OSI, the TCP/IP and BIND functionality must first be configured on the Digital UNIX operating system. Use DOTI if you need to: o Link DECnet nodes using TCP/IP o Join two existing DECnet networks without renumbering o Run IP-only traffic in part of the backbone and want to continue using DECnet applications and user interfaces without extra costs and retraining To configure DOTI, answer yes to the following question (this example is from a terminal-based script). The procedure configures the required transport and naming capabilities on the system. Do you want to configure DECnet over TCP/IP? [y]: The procedure displays the following information: It is possible to configure DECnet/OSI so that DECnet applications can run over a TCP/IP connection, to access similarly configured remote DECnet/OSI systems. If you wish to configure this capability, answer "Yes" to the following question, and the required transport and naming capabilities will be configured on this system. For more details on using DECnet over TCP/IP, refer to the DECnet/OSI Network Management guide. Advanced Configuration 4-25 4.14 Configuring to Service MOP Requests You can configure DECnet/OSI to service MOP requests by answering yes to the following question: Do you want to service MOP requests? [y]: Answer yes if your system is to perform as a MOP server to service downline load and upline dump requests or to service certain loopback tests on the wide area network. Otherwise, answer no to reduce system overhead. 4.15 Confirming Your Answers and Starting the DECnet/OSI Software Before the terminal-based configuration procedure actually configures your system, it asks you to confirm your answers for the following values for your system (the values it asks you to confirm depend on your responses to configuration questions): o DECnet/OSI full name o Node synonym (if you have one) o Phase IV address (if you have one) o Phase IV prefix (if you have a Phase IV address) o Which device(s) will use DECnet/OSI protocols o Token Ring device speed o NETs (if you manually configured the addresses) o DECdts role (clerk or server) o Whether you want your system to be configured as a DECnet-Internet Gateway o Whether you want DECnet to service MOP requests o Whether you will run DECnet applications over TCP/IP o DECdns clerk or Local namespace There are four ways to proceed with the terminal-based script: 1. If you are satisfied with the answers you supplied and want to continue the configuration, type continue and press Return. The procedure configures your system and 4-26 Advanced Configuration saves your answers in a defaults file that it uses if you rerun the procedure. 2. If you want to change one (or more) of your answers, type restart and press Return. This action starts the configuration procedure over again from the beginning with your previous answers supplied as default values to each question. 3. If you are satisfied with the answers but you do not want to continue to configure your system, type stop and press Return. This stops the configuration procedure and saves your answers in a defaults file. 4. If you want to exit the configuration procedure and do not want to save your answers in a defaults file, type quit and press Return. With the graphical interface, you can view your answers on the screen. You then have the following ways to proceed: 1. If you are satisfied with your answers and want to continue the configuration, select the Configure button. The procedure configures your system and saves your answers in a default file to use if you rerun the procedure. 2. If you want to change one (or more) of your answers, change them in the DECnet/OSI Setup window, or select the Reset button to return values to the previous answers supplied when the software was last configured. 3. If you want to exit the configuration procedure and do not want to save your answers in a defaults file, select the Cancel button. 4. If you are a root user, and you want to exit the configuration procedure and save your answers as defaults, use the Exit option in the File menu. If you are not a root user, the Exit option has the same effect as the Cancel button; it does not save your input as defaults. Advanced Configuration 4-27 This example shows how to respond if you are satisfied with the answers you supplied to a terminal-based script: Please review the following information which you have supplied, and if it is correct enter "Continue", which will start the DECnet software and complete the configuration. If there is incorrect information, or you wish to change a particular value, enter "Restart" to begin the setup again. If the information is correct, but you do not wish to complete the configuration at this time, enter "Stop". This will save the values you have entered, which will appear as defaults when you rerun this procedure. You may enter "Quit" to abort this procedure, without saving the answers. Nodename: ACME:.plm.wolf Node Synonym: wolf Phase IV Address: 55.612 Phase IV Prefix: 49:: Network Devices: te0 This system will autoconfigure addresses. This system will be a DTSS clerk. This system will be a DNS clerk in the ACME namespace. This system will be configured to service MOP requests. This system will be configured to run DECnet over TCP/IP. Do you wish to complete this DECnet/OSI configuration? [continue] If you choose to continue, the procedure creates startup files, modifies system files, and starts up the DECnet software. Once the procedure starts to configure DECnet, do not stop it. During this startup process, you receive informational messages similar to these: Creating defaults file. Creating Initialization NCL scripts Modifying /sbin/decnetstartup Updating /var/dna/dna_version Modifying /sbin/decnetshutdown Event Logging ... Configuring "CTF Collector Components " (CTABASE300) Creating Session Control Modifying /var/dss/dns/dns-names Starting DECnet/OSI Datalink ... Routing ... NSP ... OSI Transport ... Session Control ... 4-28 Advanced Configuration Attempting to contact local DNS server...please wait. DNS clerk successfully configured. Modifying /var/dss/dns/dns-names Node name reset to ACME:.plm.wolf Setting Session Control attributes There will be a brief pause as the ACME namespace is checked, to see if this node is already registered. This node is registered in the ACME namespace. DTSS ... Node Enabled ... Event Logging Event Logging ... DECnet/OSI RFC 1006 (OSI over TCP) has been enabled. rfc1006setup completed successfully. MOP successfully configured Updating address towers for node object ACME:.plm.wolf ... done MOP successfully configured The configuration of DECnet/OSI is completed. You can test DECnet functionality with the utility /usr/sbin/dnet_check. This performs various local and remote functions, and requires an account (and password) on this system and one other DECnet node. After verifying that the system is operating properly with DECnet installed you may wish to remove the following saved files: - /var/dna/scripts/start_*.ncl.sav[n] You may run /usr/sbin/osiapplsetup to configure the OSI Applications (FTAM and Virtual Terminal). decnetsetup completed successfully. 4.15.1 Additional Configuration Tasks After configuring DECnet/OSI, verify the advanced configuration procedure as explained in Section 4.19. Note that you can perform the following additional configuration tasks, explained in the indicated sections: o Configure DECnet/OSI to use Wide Area Networking Support for Digital UNIX and X.25 services - Section 4.16 o Configure Mailsetup - Section 4.17 Advanced Configuration 4-29 o Configure the OSI applications software (FTAM and Virtual Terminal) - Section 4.18 4.16 Configuring DECnet/OSI to Use Wide Area Networking Support for Digital UNIX and X.25 Services DECnet/OSI for Digital UNIX and Wide Area Networking Support for Digital UNIX (the software product that implements X.25) are packaged separately. They can be used independently on the same system. However, DECnet/OSI for Digital UNIX software uses two different mechanisms for configuring and using the features of Wide Area Networking Support for Digital UNIX. These two configurations are completely optional, but might be desirable for use with certain applications or for particular network configurations. These two optional configurations can function individually or together on the same system. You can select either, or both, of the following configurations for DECnet/OSI to use Wide Area Networking Support for Digital UNIX and X.25 services: o You can configure the OSI Transport entity to use the Connection-Oriented Network Service (CONS) interface to X.25, enabling the use of OSI Transport classes 0 and 2 (TP0 and TP2). The Connection-Oriented Network Service (CONS) is an ISO specification for a reliable and transparent end- to-end data transfer function. OSI Transport can use CONS in addition to the Connectionless-Mode Network Service (CLNS) implemented by DECnet Routing. Note that applications using OSI Transport (for example, FTAM or Virtual Terminal) need to be configured to operate over CONS before they can use the CONS functionality. o You can configure the DECnet Routing entity, which provides CLNS, to use an X.25 circuit as a dynamically established data link to a remote system by establishing switched virtual circuits. Switched virtual circuits (SVCs) are established by configuring routing to use X.25 as a data link service, which creates a logical point-to-point connection to another system. The use of X.25 SVCs is completely transparent to both transports (NSP or 4-30 Advanced Configuration OSI Transport) and any application. X.25 is simply another communications path from the local end system to a remote system. If you want DECnet/OSI to use X.25 services, you should configure DECnet/OSI and Wide Area Networking Support for Digital UNIX separately. Also, make sure that both components work properly before you configure DECnet/OSI to use X.25 services. Use the instructions in this book to configure DECnet/OSI first. Then, use the information in the following sections to assist you in configuring X.25 software for use with DECnet/OSI. 4.16.1 Addressing Issues One requirement of both approaches outlined in Section 4.16 is the definition of reachable addresses. A reachable address defines a mapping between network service access points (NSAPs) and data terminal equipment (DTE) addresses used in X.25. An NSAP identifies a system in the network and is used by both the Network and Transport layers of DECnet/OSI. X.25 uses a DTE address to identify the end point of an SVC. Reachable addresses identify which NSAP or group of NSAPs should be sent over a particular X.25 circuit. Consider the following example of two systems connected by an X.25 network: ___________________________________________________________ ______System_A________________System_B_____________________ NSAP 49::00-5F:08-00-2B-16- 43:15082267643:0045:08002B16DE4F:21 A8-72:21 DTE___075527537_______________18628935742674_______________ The reachable address on System A specifies that if the destination NSAP matches the value 43:15082267643:0045:08002B16DE4F:21, then an X.25 circuit should be created by connecting to the DTE address 18628935742674. This example is a case of one-to-one NSAP to DTE mapping. The reachable address could also be set up such that any NSAP with the initial digits 43:15082267643 should be sent over that X.25 circuit, which would potentially cause many different NSAPs to be mapped to that particular X.25 circuit. The NCL commands to create Advanced Configuration 4-31 and initialize reachable addresses are created in the /var /dna/scripts/create_cons_ra.ncl script (for OSI Transport using CONS) and the /var/dna/scripts/create_rouv_ra.ncl script (for routing using X.25). An example of creating a reachable address for Routing using NCL is: ncl> create routing circuit x25_circuit-1 reachable address ughh_v - _ncl> address prefix /4145418715004108002b0ed41e ncl> set routing circuit x25_circuit-1 reachable address ughh_v - _ncl> dte address { 2267643 } ncl> set routing circuit x25_circuit-1 reachable address ughh_v - _ncl> mapping manual ncl> enable routing circuit x25_circuit-1 reachable address ughh_v Specify the address prefix when you create the routing circuit entity. You cannot modify this characteristic with the set command. If it is necessary to create a reachable address for either X25 Access or a Routing Circuit where the address prefix of the destination systems use a decimal format NSAP, you must use a leading slash (/) to specify the address prefix. NCL does not recognize decimal format NSAPs, NETs, or address prefixes, and will issue the message: Address Prefix convert failure : unrecognized AFI For example, to create an X25 Access reachable address for a remote system with the CONS NSAP address 36:00015085551212, enter the following NCL command: ncl> create x25 access reachable address REMOTE - _ncl> address prefix /3600015085551212 For further information regarding NSAPs and X.25 addressing issues, refer to the Wide Area Networking Support for Digital UNIX Release Notes. Another special addressing consideration is the definition of the OSI Transport attribute CONS NSAP Addresses, which defines the local set of NSAPs for operation over the Connection-Oriented Network Service. These are independent of the NSAPs used over DECnet Routing (CLNS), although the two sets may overlap. By default, the dnax25setup 4-32 Advanced Configuration configuration utility will configure a single CONS NSAP for OSI Transport, using an X.121 DTE address. Forming an NSAP from an X.121 address involves padding the X.121 address on the left with zeros until it is 14 digits long and then prefixing the resulting number with the digits "36"; the "36" indicates that the remainder of the NSAP is an X.121 address. For example, given the X.121 address 505212345678, the corresponding NSAP is 3600505212345678. Any incoming connection specifying an NSAP that is not configured will be rejected by OSI Transport. The configured NSAP must include any subaddress specified by the calling party. For example, when calling a system that accesses a public network through a gateway, it is not uncommon for the gateway to use a subaddress in the called address field to determine which of a number of possible systems (or applications) should receive the call. Suppose your system has access to a public network through a gateway, the gateway's DTE address is 505212345678, and the gateway recognizes subaddress 91 as referring to your system. Then the corresponding X.121 address is 50521234567891 and the NSAP is 3650521234567891. For a directly connected system that does not use subaddressing for OSI Transport, the applicable NSAP is determined by using the X.121 address as described elsewhere in this section. For further information regarding NSAPs and X.25 addressing issues, refer to the Wide Area Networking Support for Digital UNIX Release Notes. 4.16.2 How to Configure DECnet/OSI to Use X.25 To configure DECnet/OSI to use either of the X.25 features and to define reachable addresses for this purpose, use the command: # /usr/sbin/dnax25setup This configuration utility verifies that X.25 is configured and running on your system. If your system is configured properly, you are asked: Do you wish to configure DECnet to use the X.25 services? (y/n) [n]: ? Advanced Configuration 4-33 You should enter y to continue the configuration. You are then asked: Would you like to configure OSI Transport to use the CONS interface to X.25? (y/n) [y]: ? You are also asked: Would you like to configure Routing to use an X.25 circuit? (y/n) [y]: ? The details of each type of configuration are described in Section 4.16.2.1 and Section 4.16.2.2. Digital strongly recommends that you configure and test both DECnet/OSI and X.25 independently before attempting to configure DECnet/OSI to use X.25. Finally, the configuration utility dnax25setup assumes that any security or dedicated X.25 DTEs or DTE classes have been properly configured using the X.25 configuration utility, wansetup. Refer to the Wide Area Networking Support for Digital UNIX documentation for details about this tool. 4.16.2.1 Configuring OSI Transport to Use CONS By default, decnetsetup configures OSI Transport to use the Connectionless-Mode Network Service (CLNS) offered by the Routing entity. With dnax25setup, you can optionally configure OSI Transport to use CONS, which is offered by X.25. Answer y at the following prompt and applications that use OSI Transport can be connected over an X.25 link to a remote system. Would you like to configure OSI Transport to use the CONS interface to X.25? (y/n) [y]: The configuration script then asks you for the following information: o Names of the locally configured DTEs that you want OSI Transport to use o CONS NSAP values you want to use o Names of remote systems that you will access over X.25 circuits o The X.25 addresses of DTEs of the remote systems o NSAPs for the remote systems 4-34 Advanced Configuration An example of the complete configuration script for X.25 is included in Appendix B. When you have completed the information for all remote systems that you will be accessing, press Return. The configuration creates an OSI Transport template named "cons", and modifies the template "any" by adding support for OSI Transport classes 0 and 2. It also sets the CONS NSAP Address attribute. The NCL initialization scripts created by this section of dnax25setup in the /var/dna/scripts directory are start_tp_cons.ncl and create_cons_ra.ncl. Also, the start_osi_transport.ncl script in that same directory is modified. 4.16.2.2 Configuring Routing to Use an X.25 Dynamically Established Data Link The X.25 configuration script next asks if you want to configure routing to use an X.25 circuit as a dynamically established data link. Answer y at the following prompt: Would you like to configure Routing to use an X.25 circuit? (y/n) [y] This configures DECnet Routing (offering the Connectionless-Mode Network Services) to use an X.25 circuit as a dynamically established data link such that the X.25 connection is made only upon receipt of outgoing data and is cleared after a configurable period of inactivity. Unlike the use of OSI Transport over CONS, this use of X.25 services does not require any explicit knowledge of the Network layer by applications. These X.25 services may be used by both DECnet applications and OSI applications. The dnax25setup utility defines an X25 Access template and filter for use by the routing entity. In addition, for each X.25 circuit used by Routing, the utility creates one or more reachable address entities. These entities define the NSAP-to-DTE address mappings. If multiple security filters are defined for X.25, you are asked to choose the filters used to guard the Routing filter. If multiple DTE classes are defined for X.25, you are asked to choose the DTE class used for any reachable addresses defined. Advanced Configuration 4-35 The dnax25setup utility creates the following two ncl initialization scripts in the /var/dna/scripts directory: o start_rouv_x25.ncl o create_rouv_ra.ncl. Also, the utility modifies the start_routing.ncl file in that same directory. 4.16.2.3 Testing OSI Transport Over CONS After configuring OSI Transport to operate over the Connection-Oriented Network Service (CONS) interface (which requires the installation and configuration of the Wide Area Networking Support for Digital UNIX product), you can verify correct operation using the test program, /usr/field /netosiivp. The netosiivp program acts as either a client (initiator) or server (responder), depending upon command line arguments. To map names to NSAP values, create the file /etc/isonsaps and enter aliases of the form: name:ns=%x4145418715004108002B31883B21 You can list the OSI Transport NSAPs for a system using the command: ncl> show osi transport local nsap * To run this program as a responder or server, issue the command: # netosiivp -t cons -R To run this program as an initiator or client, use the command: # netosiivp -t cons -I name You can specify protocol classes, OSI Transport templates, and other options using command line arguments. The complete set of command line arguments available for this program is displayed if the program is executed with no command line arguments as follows: # netosiivp 4-36 Advanced Configuration 4.16.2.4 Using CONS Attributes If you have not configured OSI Transport to use the Connection-Oriented Network Services (which requires the Wide Area Networking Support for Digital UNIX product), attempting to use CONS-specific attributes, including CONS NSAP Addresses and CONS Filters fails with various NCL error messages. 4.16.3 Using dnax25setup to Complete X.25 Configuration After you configure DECnet/OSI and X.25, you need to run an additional configuration procedure (dnax25setup) which sets up the underlying support for running DECnet/OSI over X.25. Use the following command to start this configuration procedure: #/usr/etc/dnax25setup Follow the prompts or refer to the Wide Area Networking Support for Digital UNIX Systems Configuration Guide for explicit instructions on using this configuration procedure. 4.17 Configuring Mailsetup If you want to customize DECnet mail addresses so they are compatible with RFC 822, use the mailsetup utility. For further information, see the Digital UNIX reference page mailsetup(8). 4.18 Configuring the OSI Applications Software If you installed the DECnet/OSI Base Components (DNABASE400) subset, OSI applications software (FTAM and Virtual Terminal) was installed on your system. You can configure the OSI applications software after you complete the advanced configuration. Use the following command to start the OSI application configuration procedure: # /usr/sbin/osiapplsetup Chapter 7 contains detailed instructions on configuring the OSI applications software. Advanced Configuration 4-37 4.19 Verifying the Advanced Configuration Procedure Once your system is registered in the namespace, the installation and configuration are finished. If necessary, perform the postinstallation tasks in Chapter 5, and then proceed to Chapter 6. Chapter 6 includes instructions on how to run the /usr/sbin/dnet_check configuration verification procedure. This procedure tests and exercises your DECnet/OSI communications software to ensure that you configured the software properly. 4-38 Advanced Configuration 5 _________________________________________________________________ Postinstallation Tasks This chapter discusses the following postinstallation tasks: o Finishing the name service configuration o Performing namespace activities - Distributed namespace tasks - Local namespace tasks - Updating nodes o Configuring the DECnet-Internet Gateway Subsequent chapters discuss how to run the configuration verification procedure (Chapter 6) and how to configure the FTAM and Virtual Terminal applications (Chapter 7). The postinstallation tasks for distributed namespaces discussed in this chapter pertain to namespaces that already exist. To create a namespace and configure your system as a DECdns server for that namespace, see the DECnet/OSI DECdns Management guide. (The DECdns Server software subset must be installed on your system.) 5.1 Finishing the Name Service Configuration Once DECnet/OSI starts, the configuration procedure configures your system and attempts to register it in the namespace you specified in your DECnet/OSI full name. The specified namespace determines your primary name service. o If you are using a Local namespace as your primary name service, refer to Section 5.1.1. o If you are using DECdns as your primary name service, refer to Section 5.1.2. Postinstallation Tasks 5-1 o If you are using DNS/BIND, refer to Section 5.1.3. 5.1.1 Finishing the Local Namespace Configuration If you are using a Local namespace, the configuration procedure configures your system, then registers it in the Local namespace database. The script displays informational messages similar to the following: Note: This node has been configured to use the Local Namespace. If you wish to add, modify, or delete a node or its associated addressing information, you should use the utility /usr/sbin/decnet_register to add or change definitions. You may also use the /usr/sbin/update_nodes utility to copy a Phase IV nodes database or Phase V LNO load file from a remote system, as in the following example: /usr/sbin/update_nodes -dlocal 4.1002 This command will copy a DECnet address file from the remote system, and automatically populate the local naming file. Please refer to the installation guide for further details. Refer to Section 5.2.1 for information on how to copy node databases from remote nodes. Refer to the DECnet /OSI Network Management guide for information on how to manage node names in the Local namespace. If you have specified the Local namespace as the primary naming service, your system is configured as a DECdns clerk. If you plan to configure your system as a DECdns server in a new namespace, see the DECnet/OSI DECdns Management guide. (The DECdns Server software subset must be installed on your system.) 5.1.2 Finishing the DECdns Namespace Configuration If you are using a DECdns distributed namespace, the configuration procedure checks that a DECdns server for your namespace is on the same LAN as your system. When the server is found, the procedure configures your system as a DECdns clerk using that server in the namespace. In this case, you receive a completion message similar to the following: Attempting to contact local DNS server...please wait. DNS clerk successfully configured 5-2 Postinstallation Tasks The configuration procedure then attempts to register your system in the distributed namespace and displays at the end of the operation a message similar to the following: This node is registered in the XYZ_CORP namespace. If the automatic registration is successful, the advanced configuration is complete. See Section 5.2.2 for information about other namespace activities you might have to perform. Then, proceed to Chapter 6 for instructions on how to verify the configuration. The procedure is unable to register your node if: o The distributed namespace does not allow automatic registration o The server could not be found on the same LAN as your system o No distributed namespace exists If your namespace does not allow automatic registration, a message informs you that you must manually register your system. Your configuration is finished, but you will not be able to fully communicate with other systems or run the configuration verification procedure until your system is registered in the namespace. Refer to the DECnet /OSI Network Management guide for information on manually registering a system in a distributed namespace. If the server could not be found on the same LAN as your system, the configuration procedure prompts you for the correct address of the server to which you want to connect. You can specify a remote server, as explained in Section 5.1.2.1. However, if you know a server exists on the same LAN, check that the server is running or see your network administrator. If no distributed namespace exists, you can create a namespace and configure your system as the first DECdns server in that namespace by following the directions in the DECnet/OSI DECdns Management guide. Postinstallation Tasks 5-3 5.1.2.1 Connecting to a Remote Server in a DECdns Distributed Namespace If a DECdns server for your distributed namespace is not found on your LAN, the procedure prompts you to enter the address of the server you want: What is the network address of the server? You can respond to this question with the server's Phase IV compatible address (if it has one) or with the server's network service access point (NSAP). The NSAP is the network entity title (NET) with a valid transport selector. To find this information, contact the system administrator for that server. The administrator can get this information by running the dnsconfigure utility on the server and selecting to Show address information of this node. The server system may have a number of different NSAPs. You can use any of these NSAPs to connect to the server system, but you must enter the NSAP in the displayed format. After you enter the server's address, your system connects to the server and displays a confirmation message listing your namespace nickname and its namespace creation time stamp (NSCTS), as in this example: Your default namespace nickname is XYZ_CORP Your default namespace NSCTS is 00-12-34-56-77-A0-A1-A2-A3-A4-A5-A6-A7-B0 If you fail to connect to the remote server, you must reboot your system before you try to reconfigure DECnet /OSI. ________________________ Note ________________________ If you are joining a DECdns Version 1.1 namespace, make sure you have access to the remote server's sys$system:dns$default_file.dat. Refer to the DECnet /OSI DECdns Management guide for more information. ______________________________________________________ 5-4 Postinstallation Tasks 5.1.3 Finishing the DNS/BIND Configuration If you are using DNS/BIND as the primary name service, the configuration procedure automatically configures the DECnet over TCP/IP transport service, and it lists Domain as the first naming service in the Session Control naming search path list. For information about DNS/BIND, see the Digital UNIX Network Administration online reference manual that is part of the Digital UNIX online documentation set. Digital UNIX DNS/BIND supports NSAP addresses (see the DECnet/OSI Network Management guide). If you are using a DNS/BIND server supplied by another vendor, verify that it supports NSAP address records. 5.2 Performing Local and DECdns Namespace Activities You perform namespace tasks after installation. The tasks depend on whether you are using a Local or distributed namespace. Refer to the DECnet/OSI Network Management guide for information on how to manage node names in a Local or distributed DECdns namespace. 5.2.1 Local Namespace Tasks If you are using a Local namespace, several options are available for modifying and using the Local namespace including: o Creating or re-creating a Local namespace file o Updating address tower information o Loading the Local namespace file o Loading node definitions from a Phase IV node database into a Local namespace file o Clearing all information from a Local namespace file o Adding new node definitions into a Local namespace file You can find instructions on how to do these tasks in Section 5.2.1.1 and the DECnet/OSI Network Management guide. Postinstallation Tasks 5-5 5.2.1.1 Update_Nodes The update_nodes utility lets you update or create a local node's Phase IV database with information from a remote DECnet node's database. In addition, it lets you load the information that is retrieved into either a Local or a distributed namespace. The Phase IV local node's database is no longer used by DECnet/OSI; however, you may want to create one to aid in your transition: o You can use an existing local node's database in conjunction with decnet_register to populate your namespace with the Phase IV nodes in your network. Refer to the DECnet/OSI Network Management guide for details. o You can convert the MOP information stored in the local node's database to create the new MOP client database (using the update_mopdb tool). 5.2.1.2 Running Update_Nodes To run the update_nodes utility, you must become root and use this command format: update_nodes -d [Local|decdns] node-id where node-id is the DECnet node name or DECnet node address of the remote node whose database you are using for the update. Non-DECnet entries such as terminal servers, and parameters such as download parameters, are preserved except where conflicts occur. A conflict occurs when a node name received from the remote node already exists in the current database, but the node numbers do not match. In this case, the information received from the remote node is entered in the new database. However, any parameters associated with the node name are not entered. A record of all conflicts and any dropped parameters is kept in the file /usr/lib/dnet/update_nodes.log. 5-6 Postinstallation Tasks 5.2.1.3 Copying a DECnet Phase IV Node Database This example illustrates how to copy a DECnet Phase IV node database from another system and use it to populate the Local namespace file. # update_nodes 4.1002 -d Local 5.2.2 DECdns Distributed Namespace Tasks If you are using an existing DECdns distributed namespace, you might have to perform certain tasks after you configure the DECnet/OSI software on your system (the local node). This chapter serves as a checklist of these tasks. Certain tasks are documented in detail in the DECnet/OSI Network Management and DECnet/OSI DECdns Management guides. The namespace concepts are described in the DECnet/OSI DECdns Management guide. o If your system is joining a network that has other DECnet/OSI systems, see Section 5.2.2.1. o If your system is the first DECnet/OSI system on the network, and your network includes Phase IV nodes, see Section 5.2.2.2. o If your system is the first DECnet/OSI system on the network, and your network does not include Phase IV nodes, see Section 5.2.2.3. 5.2.2.1 Registering Subsequent DECnet/OSI Systems For subsequent DECnet/OSI systems brought up on the network, the only namespace activity you might have to perform is registering the system in the distributed namespace. Depending on several variables, the configuration procedure might have registered the local node in the distributed namespace during configuration. o If decnetsetup did register the node, you do not have to perform any namespace tasks; go to Chapter 6, which describes how to verify the configuration. o If decnetsetup did not register the node, manually register it now using decnet_register; after registering the system, you can go on to Chapter 6. Postinstallation Tasks 5-7 This message appears if the registration failed: This node could not be registered in the namespace. When this procedure completes you will have to manually register this node in the namespace. Refer to the "Postinstallation Tasks" chapter of the installation guide for more details, or contact your network manager. 5.2.2.2 First DECnet/OSI System on a Network with Phase IV Nodes Immediately after you install the first DECnet/OSI system on the network, use decnet_register for the following tasks: 1. Register all the existing Phase IV nodes in the distributed namespace. Refer to the DECnet/OSI Network Management guide. 2. Manually register your node in the namespace using decnet_register if decnetsetup displayed this message: This node could not be registered in the namespace. When this procedure completes you will have to manually register this node in the namespace. See the "Postinstallation Tasks" chapter of the installation guide for more details, or contact your network manager. For instructions on registering the system, refer to the DECnet/OSI Network Management guide. 3. Delete the local node's Phase IV name from .DNA_Node, if necessary. Your local node might be registered in .DNA_Node as a Phase IV node, if it was included in the nodes_p used to create the script for registering all existing Phase IV nodes. Refer to the DECnet/OSI Network Management guide. 4. Give authorized users access to the namespace by adding them to the .DNS_Admin and .DNA_Registrar access control groups. For information on the .DNS_Admin group, refer to the DECnet/OSI Planning Guide. For information on adding members to .DNA_Registrar, refer to the DECnet/OSI Network Management guide. After you complete each task, go to the next chapter to verify the configuration. 5-8 Postinstallation Tasks 5.2.2.3 First DECnet/OSI System on a Network with No Phase IV Nodes Immediately after you install the first DECnet/OSI system on the network, use decnet_register to perform these tasks: 1. Manually register your node in the namespace using decnet_register if decnetsetup displayed this message: This node could not be registered in the namespace. When this procedure completes you will have to manually register this node in the namespace. Refer to the "Postinstallation Tasks" chapter of the installation guide for more details, or contact your network manager. For instructions on registering the system, refer to the DECnet/OSI Network Management guide 2. Give authorized users access to the namespace by adding them to the .DNS_Admin and .DNA_Registrar access control groups. For information on the .DNS_Admin group, refer to the DECnet/OSI Planning Guide. For information on adding members to .DNA_Registrar, see the DECnet/OSI Network Management guide. After you complete each task outlined above, go to Chapter 6 to verify the configuration. 5.3 Configuring the DECnet-Internet Gateway Once you have the DECnet-Internet Gateway software installed, you must configure it into your system. Before configuring the gateway, however, you must shut down DECnet. To do this, issue the following commands: # decnetshutdown # decnetsetup gateway You can take all of the default answers for the questions that appear on the screen. However, be sure to answer yes to the following question: Will this system be configured as a DECnet/Internet Gateway? (y/n) [n] y Postinstallation Tasks 5-9 Configuring the DECnet-Internet Gateway onto your system causes the following modifications to occur to the /etc /inetd.conf file: # diff inetd.conf inetd.conf.sav2 56,57c56 < #ftp stream tcp nowait root /usr/sbin/ftpd ftpd < ftp stream tcp nowait root /usr/sbin/ftpd.gw ftpd - --- > ftp stream tcp nowait root /usr/sbin/ftpd ftpd # 5.3.1 Testing the DECnet-Internet Gateway The following examples illustrate commands you can use to test the DECnet-Internet Gateway. 1. While on node GLEPTO (OpenVMS), perform directory and copy operations as follows: a. Create a file on the OpenVMS system: Glepto>create testfile.dat this is a test file ^z b. Move the file to the IP-only node named GOOSE using the gateway SNDPPR: Glepto>copy testfile.dat sndppr"goose!guest1 digital"::"testfile"/log %COPY-I-CREATEDSTM, SNDPPR"goose!guest1 password"::"testfile" has been created i n stream format %COPY-S-COPIED, SYS$SYSROOT:[SYSMGR]TESTFILE.DAT;1 copied to SNDPPR"goose!guest1 password"::"testfile" (1 record) c. Request a directory of the remote user on node GOOSE through the gateway SNDPPR: Glepto>dir sndppr"goose!guest1 digital":: Directory SNDPPR"goose!guest1 password":: testfile bin/. Total of 2 files. 5-10 Postinstallation Tasks d. Copy the file back under a new name and type it out on the OpenVMS side: Glepto>copy sndppr"goose!guest1 digital"::"testfile" testfile1.dat Glepto>type testfile1.dat this is a test file Glepto> 2. While on node GOOSE (on the Digital UNIX system), do the same thing: a. Create a file on the Digital UNIX system (insert text in the file as in this example): # cat > testfile2 This is a test file of the gateway. ^D b. Move the file to the DECnet-only node named GLEPTO using the gateway SNDPPR, display it, then copy it back and type it out under a new name: # ftp sndppr Connected to sandpiper. 220 sandpiper.csp.acme.com FTP server (OSF/1 Version 5.60) ready. Name (sndppr:join): glepto::system 331 Password required for gateway access glepto::system. Password: 230 Access control info received for glepto/system. ftp> put testfile2 200 PORT command successful. 150 Opening data connection for glepto/system/password::testfile2 (16.66.80.33,1 032). 226 Transfer complete. local: testfile2 remote: testfile2 36 bytes sent in 0.0039 seconds (9.1 Kbytes/s) ftp> ls test* 200 PORT command successful. 150 Opening data connection for dls (16.66.80.33,1033). TEST.DIR;1 TEST.DIS;2 TESTFILE.DAT;1 TESTFILE1.DAT;1 TESTFILE2.;1 TESTRSH.COM;3 226 Transfer complete. Postinstallation Tasks 5-11 remote: test* 86 bytes received in 0.15 seconds (0.56 Kbytes/s) ftp> get testfile2.;1 testfile3 200 PORT command successful. 150 Opening data connection for glepto/system/password::testfile2.;1 (16.66.80.3 3,1034)(36 bytes). 226 Transfer complete. local: testfile3 remote: testfile2.;1 36 bytes received in 0.031 seconds (1.1 Kbytes/s) ftp> quit 221 Goodbye. # ls testfile* testfile2 testfile3 # cat testfile3 this is a test file of the gateway # To connect to remote systems using either set host on the OpenVMS side or telnet on the Digital UNIX (IP-only) side, the following example illustrates going from OpenVMS to Digital UNIX (through the gateway) and then back again: Glepto>set host sndppr Welcome to Digital UNIX (H2OBIRDS:.sandpiper) login: goose! Trying 16.66.80.33... Connected to goose.csp.acme.com. Escape character is '^]'. ULTRIX V4.3 (Rev. 44) (goose.csp.acme.com) login: root Password: Last login: Mon Jan 8 17:06:52 from sulak.csp.acme.d ULTRIX V4.3 (Rev. 44) System #4: Wed Feb 18 21:02:13 MDT 1996 UWS V4.3 (Rev. 10) # goose> # goose> telnet sndppr Trying 16.66.80.7... Connected to sandpiper. Escape character is '^]'. Digital UNIX (sandpiper.csp.acme.com) (ttyp3) 5-12 Postinstallation Tasks login: glepto:: UNAUTHORIZED ACCESS IS PROHIBITED Username: SYSTEM Password: Welcome to VAX/VMS version 6.0 on node GLEPTO Unauthorized access is prohibited. GLEPTO is running DEC TCP/IP Services for OpenVMS V3.0 Last interactive login on Monday, 08-FEB-1996 09:50 Last non-interactive login on Monday, 08-FEB-1996 09:45 Glepto> Postinstallation Tasks 5-13 6 _________________________________________________________________ Running the Configuration Verification Procedure The configuration verification procedure tests your DECnet /OSI configuration to ensure that you can communicate properly with other DECnet/OSI systems. The configuration verification procedure performs the following tasks: 1. Checks to see whether DECnet/OSI is running. 2. Tests whether your DECdns clerk is functioning. 3. Establishes a connection with another DECnet/OSI system. 4. Uses the connection (with another DECnet/OSI system) to copy files between that system and your own system. 5. Runs the loopback application to the remote system. 6.1 Configuration Verification Procedure Requirements To run the verification procedure, you must have both a user account and password on your local system, as well as a user account and password for a remote DECnet/OSI system. 6.2 Running the Configuration Verification Procedure To run the verification procedure, use the following command: # /usr/sbin/dnet_check Running the Configuration Verification Procedure 6-1 6.2.1 Supplying a Full Name Once you start the verification procedure, it prompts you to supply your node's DECnet/OSI full name. You can either accept the default full name by pressing Return or specify another full name (if you belong to an additional namespace for instance). The following example shows how you would accept the default full name: What is your Phase V node name? [XYZ_CORP:Sales.west_coast.WillyLoman]: If you specify a nondefault full name, the configuration verification procedure prompts you to confirm it before you can continue, as in the following example: What is your Phase V node name? [XYZ_CORP:.Sales.west_coast.WillyLoman]: abc_corp:.sales_management.wloman Your node name is abc_corp:.sales_management.wloman Is this correct? (y/n) [y]:y You can either accept this full name by pressing Return or reject it by typing n and pressing Return. If you reject the full name, you return to the full name prompt. 6.2.2 Checking the State of DECnet/OSI After you specify a full name, the configuration verification procedure tests to see if DECnet/OSI works by checking the state of the Routing, Session Control, and Node entities, as in the following example: The first test checks that some of the DECnet/OSI network management entities are running. Each of the following displays should indicate that the entity is in state "On". # ncl show Routing state Node 0 Routing AT 1996-01-01-15:18:02.614-05:00I----- Status State = On # ncl show Session Control state Node 0 Session Control AT 1996-01-01-15:18:03.306-05:00I----- 6-2 Running the Configuration Verification Procedure Status State = On # ncl show Node 0 state Node 0 AT 1996-01-01-15:18:03.933-05:00I----- Status State = On The state of all these entities should be On. If any of them are Off, DECnet/OSI is not running properly, and you should examine the /usr/sbin/decnetstartup script to verify that the entity in question is being started. (This script calls the /sbin/rc3.d/S28decnetosi script at reboot.) 6.2.3 Checking the DECdns Clerk If DECnet/OSI is running properly, and the configuration verification procedure determines that you are using DECdns, then the verification procedure issues an NCL command to ensure that your DECdns clerk is functioning. It performs this test by looking up your node object in the namespace you specified as part of your full name, as in the following example: The following command attempts to look up your node object in the DNS namespace. This is a simple way to test that the DNS Clerk is functioning correctly. # decnet_register show node ACME:.lkg.agn2au directory_service decdns Directory Service: DECdns Node name: ACME:.lkg.agn2au Phase IV synonym: AGN2AU Node address: 49::00-0C:AA-00-04-00-AF-30:21 (12.175) Node address: 49::00-0C:AA-00-04-00-AF-30:20 (12.175) Node address: 41:45418715:00-41:08-00-2B-30-7D-E6:21 Node address: 41:45418715:00-41:08-00-2B-30-7D-E6:20 Number of nodes reported on: 1 Running the Configuration Verification Procedure 6-3 If the configuration verification procedure cannot display your node object entry, take follow the steps: 1. Verify that the clerk is working by issuing the following command: # ncl show dns clerk state 2. If the clerk state is On, your system may not be registered in the namespace you specified. See Chapter 5. 3. Register your system in the namespace using the instructions in the DECnet/OSI Network Management guide. After you register your system, issue the following command, substituting your full name for the one in this example: # ncl update session control tower maintenance - ACME:.lkg.agn2au 4. If the clerk state is Off or you receive a message stating that the clerk entity was not created, issue the following command: # ncl do /var/dna/scripts/start_dns_clerk.ncl 6.2.4 Reaching a Remote System If your naming service is functioning properly, the configuration verification procedure checks to verify that your system can communicate with a remote system. To run this test, you must supply and verify the name of a remote system (you can also specify a Phase IV address), as in the following example: Enter the name of a remote node. You may use the node synonym if it matches the full name (for example, 'short' may be used instead of 'XYZ:.fac.short', but 'long' may not be used in place of 'XYZ:.fac.long_name'. Remote node name? [No Default]: notrix remote node notrix Is this correct? (y/n) [y]: The following command will check that the remote node you specified is reachable: # ncl show node notrix state 6-4 Running the Configuration Verification Procedure Node notrix AT 1996-01-01-15:18:35.265-05:00I12.367 Status State = On If the configuration verification procedure indicates that your system cannot reach the remote system, you should try to reach a different remote system. 6.2.5 Testing Local and Remote Systems The next group of tests attempts to copy files over the network using DECnet/OSI, and to run the loopback application. The first test copies a file to the local node using DECnet/OSI utilities, and if successful, the second test copies a file to and from the remote system you specified earlier. For each test, you are asked to provide the user account and password to be used for that system. For example: Enter user account on ACME:.lkg.agn2au [No Default]: thomas Enter password for user thomas on ACME:.lkg.agn2au [No Default]: # dcp /usr/sbin/dnet_check ACME:.lkg.agn2au/thomas/password/::dnetcheck.rnd # dcp ACME:.lkg.agn2au/thomas/password/::dnetcheck.rnd /usr/tmp/dnetcheck.lnd # cmp -s /usr/sbin/dnet_check /usr/tmp/dnetcheck.lnd # drm ACME:.lkg.agn2au/thomas/password/::dnetcheck.rnd # ncl loop loopback application name ACME:.lkg.agn2au, length 1, count 10, format 00 # ncl loop loopback application name ACME:.lkg.agn2au, length 2047, count 50 If any of these tests fail, check the /tmp/dnet_check.log log file for additional information. After these tests complete, the configuration verification procedure prompts you for the name of an user account and password on the remote system that you specified previously. Supply this information, as in the following example: Running the Configuration Verification Procedure 6-5 Enter user account on notrix [No Default]: thomas Enter password for user thomas on notrix [No Default]: # dcp /usr/sbin/dnet_check notrix/thomas/password/::dnetcheck.rnd # dcp notrix/thomas/password/::dnetcheck.rnd /usr/tmp/dnetcheck.lnd # cmp -s /usr/sbin/dnet_check /usr/tmp/dnetcheck.lnd # drm notrix/thomas/password/::dnetcheck.rnd # ncl loop loopback application name notrix, length 1, count 10, format 00 # ncl loop loopback application name notrix, length 2047, count 50 Removing log file /tmp/dnet_check.log Removing the file copied across the network # exit # If any of these tests fail, check the /tmp/dnet_check.log log file for additional information. The mirror application must run on both the local and the remote systems. If this test completes successfully, the configuration verification procedure is finished and DECnet/OSI for Digital UNIX is functioning properly. 6-6 Running the Configuration Verification Procedure Part III _________________________________________________________________ Configuration for FTAM and Virtual Terminal Part III explains how to configure the FTAM and Virtual Terminal software. It includes the following chapter: - Chapter 7 - Configuring FTAM and Virtual Terminal 7 _________________________________________________________________ Configuring FTAM and Virtual Terminal This chapter describes how to configure the FTAM and Virtual Terminal (VT) software on a Digital UNIX system. 7.1 FTAM and Virtual Terminal Installation FTAM and Virtual Terminal are now installed as part of the DECnet/OSI Base Component subset. The following OSI Application subsets have been eliminated: DNAAPPMANxxx, DNAAPPxxx and DNAAPPGWYxxx, where xxx is the version number. See Chapter 2 for instructions on installing DECnet/OSI. 7.2 FTAM and Virtual Terminal Terminology The following terms are discussed in this chapter: o An initiator, or client, is the program on one system that initiates a request to a program on another system, and awaits a response. o A responder, or server, is the program on a system that provides a response to a request initiated on another system. o A listener is a job running on the responding system that receives incoming requests from an initiating system and starts a responder to fulfill the incoming requests. Configuring FTAM and Virtual Terminal 7-1 7.3 About the OSI Application Entity Database The FTAM and VT applications require you to manage the OSI application entity database. This database stores addressing information for aliases that represent FTAM and VT applications and listeners. On Digital UNIX systems, the location of this file is: /etc/isoapplications The entries in the isoapplications database define aliases and contain information about local listeners, remote responders, and source addresses for local initiators. The aliases are used by local FTAM and VT initiators and listeners, and by users who specify these aliases in FTAM and VT commands. There are three types of formats that you can use in this isoapplications database. They are: o Address - Information on local listeners, remote applications, and local initiator source address. o Distinguished Name - X.500 Directory Service fixed entries. o Pattern - X.500 Directory Service variable entries. The isoapplications database can contain any combination of these formats. For detailed information on the Address, Distinguished Name, and Pattern formats, refer to Chapter 9 in DECnet/OSI FTAM and Virtual Terminal Use and Management. 7.4 Getting Started Configuring Initiating and Responding Entities This section provides basic configuration task checklist items and examples for setting up the initiating and responding systems, or entities. Refer to DECnet/OSI FTAM and Virtual Terminal Use and Management for detailed information about managing initiating and responding systems. If you are already familiar with configuring FTAM and VT, then you can proceed to Section 7.5. 7-2 Configuring FTAM and Virtual Terminal 7.4.1 Setting Up Responding Entities On Digital UNIX, you should run the osiapplsetup procedure to configure the local listeners for FTAM and VT. See Section 7.5 for information on the osiapplsetup procedure. However, you can also manually configure the listeners, or set up your own listeners by using the following task list. First define an alias for the local listener address, then start the listener for that alias. In this section, the Address format of isoapplications is used. The tasks to be performed on the responding entity system are as follows: 1. Determine the transport provider type to be used for the transport connection. The choices are: OSI Transport, RFC 1006, and CONS over X.25. The default is OSI Transport. 2. Collect the information needed to define an alias. Complete the Address format worksheet shown in Table 7-5 as follows: a. Choose an alias name for your listener. This name is local to your system and can be any name you choose. b. Specify whether the listener is for FTAM or VT. c. Determine the AP-title and AE-qualifier. FTAM and VT on Digital UNIX do not use these fields, so leave them blank. d. Determine the service access point (SAP) selectors (PSEL, SSEL, TSEL) to use. For more information on determining SAP selectors, refer to Section 9.6 in DECnet/OSI FTAM and Virtual Terminal Use and Management. e. Determine the network service access point (NSAP). The format of this field depends on which transport provider you are using. o For OSI Transport (default): Determine the local NSAP. o For RFC 1006: Determine the local Internet address and RFC 1006 daemon port (default RFC 1006 daemon port is 102). Configuring FTAM and Virtual Terminal 7-3 o For CONS over X.25: Determine the local X.25 NSAP. f. Specify the transport provider you selected in step 1 (OSI, RFC 1006, none for CONS). g. Determine the transport template you want to use. o For OSI Transport: Default template is default. o For RFC 1006: Do not specify a template. o For CONS over X.25: Use a CONS template. 3. Define the alias in isoapplications in Address format with the information you collected in the prior steps. You can edit this database using a text editor, or on Digital UNIX you can use the /usr/sbin/osiapplsetup procedure described in Section 7.5. 4. Start an FTAM or VT listener on the alias. Execute one of the following commands from superuser: # ftam_listener # vt_listener 7.4.2 Setting Up Initiating Entities A responding entity needs to be defined in the isoapplications database before you can access it. To get the information you need for an alias, you must contact the person responsible for configuring and managing the remote OSI system running FTAM or VT. The remote FTAM or VT implementation may be from Digital or from another vendor. You need to perform the following tasks on your system to set up the isoapplications database for a specific remote FTAM or VT application. 1. Determine the available transports between your Digital system and the remote OSI system and select one. 2. Collect the information needed to define an alias. Complete the Address format worksheet shown in Table 7-5 as follows: a. Choose an alias name for the remote responder. This name is local to your system and can be any name you choose. b. Specify whether the remote application is FTAM or VT. 7-4 Configuring FTAM and Virtual Terminal c. Obtain the AP-title and the AE-qualifier that the remote application requires, if any. If they are not required, leave these fields blank. d. Obtain the SAP selectors (PSEL, SSEL, TSEL) that the remote application requires. e. Obtain the NSAP of the remote application. The format of this field depends upon which transport provider you are using. o For OSI Transport: Obtain the remote NSAP. o For RFC 1006: Obtain the remote Internet address and RFC 1006 daemon port. o For CONS over X.25: Obtain the remote X.25 NSAP. f. Specify the transport provider you selected in step 1. g. Determine the local transport template you want to use. o For OSI Transport: Default template is default. o For RFC 1006: Do not specify a template. o For CONS over X.25: Use a CONS template. 3. Define the alias in isoapplications in Address format with the information you collected in the prior steps. You can edit this database using a text editor, or on Digital UNIX you can use the /usr/sbin/osiapplsetup procedure described in Section 7.5. Once the setup is complete, you can invoke initiator requests using the alias as defined in step 3. 7.4.3 Example: Performing an FTAM File Copy Use the task lists from Section 7.4.1 and Section 7.4.2 to configure your system to perform an FTAM file copy. In this example, you copy remote file system_a_filename on System-A, to file system_b_filename on System-B. System-A is the responding entity, and System-B is the initiating entity. System-A and System-B are Digital UNIX systems. Configuring FTAM and Virtual Terminal 7-5 Use the OSI Provider and use the following account information on System-A: username: system_a_user password: system_a_pwd Using information collected in Section 7.4.1, perform the following steps on responding entity System-A as superuser: 1. Determine the transport provider type. For this example, use OSI transport. 2. Perform the following tasks: a. Choose an alias. For this example, use example_alias. b. Specify FTAM or VT application. For this example, use FTAM. c. Determine AP-title and AE-qualifier. For this example, because it is a Digital system, they are not specified. d. Determine the SAP selectors. For this example, use %x000A.%x000B.%x000C. e. Determine the NSAP. For OSI transport, use the following ncl command to get the local NSAPs, and choose one. # ncl ncl> show osi transport local nsap * name Node 0 OSI Transport Local NSAP %X490004AA000400001321 AT 1995-08-17-16:10:04.805-04:00I23.041 Identifiers Name = %X490004AA000400001321 f. Specify the transport provider. For this example, use osi. Note that because this is the default provider, the provider=osi could be left out altogether. g. Determine the transport template. For this example, use default. Note that because this is the default template, the template=default could be left out altogether. 7-6 Configuring FTAM and Virtual Terminal 3. Define the alias in isoapplications: example_alias :FTAM:::%x000A.%x000B.%x000C. \ %X490004AA000400001321, \ provider=osi, template=default: 4. Start the FTAM listener: # ftam_listener example_alias Using information collected in Section 7.4.2, perform the following steps on initiating entity System-B as superuser: 1. Determine the available transports and choose one. For this example, use OSI transport. 2. Perform the following steps: a. Choose an alias. For this example, use system_a_ alias. b. Specify FTAM or VT. For this example, the remote application is FTAM. c. Obtain the AP-title and AE-qualifier. For this example, the responder does not require this information. d. Obtain the SAP selectors. For this example, the responder's SAP selectors are %X000A.%X000B.%X000C. e. Obtain the remote NSAP. For this example, the responder's OSI transport NSAP is %X490004AA000400001321. f. Specify the transport provider. For this example, use OSI. Note that because OSI is the default provider, you can omit it for this example. g. Determine the transport template. For this example, use default. Note that because default is the default template, you can omit it for this example. 3. Define the alias in isoapplications: system_a_alias :FTAM:::%X000A.%X000B.%X000C. \ %X490004AA000400001321, \ provider=osi,template=default: Configuring FTAM and Virtual Terminal 7-7 Once the setup is complete, you can start the FTAM copy command: # ocp system_a_alias/system_a_user/system_a_pwd::system_a_filename system_b_filename 7.4.4 Example: Performing a Virtual Terminal Login Use the task lists in Section 7.4.1 and Section 7.4.2 to configure your system to perform a Virtual Terminal login. In this example, you perform a VT ologin from System-B to System-A. System-A is the responding entity, and System-B is the initiating entity. System-A and System-B are Digital UNIX systems. Use the RFC 1006 provider and the following account information from System-A: username: system_a_user password: system_a_pwd Using information collected in Section 7.4.1, perform the following steps on responding entity System-A as superuser: 1. Determine the transport provider type. For this example, use RFC 1006. 2. Perform the following tasks: a. Choose an alias. For this example, use example_alias. b. Specify FTAM or VT application. For this example, use VT. c. Determine AP-title and AE-qualifier. For this example, because it is a Digital system, they are not specified. d. Determine the SAP selectors. For this example use AA.BB.CC. e. Determine the NSAP. For RFC 1006, use nslookup to get the Internet address, and use the default RFC 1006 daemon port of 102. 7-8 Configuring FTAM and Virtual Terminal # nslookup system-a Server: named.lkg.dec.com Address: 16.20.0.10 Name: system-a.lkg.dec.com Address: 16.20.8.42 f. Specify the transport provider. For this example, use rfc1006. g. Determine the transport template. For this example, since the transport provider is RFC 1006, no template is specified. 3. Define the alias in isoapplications: example_alias :VT:::AA.BB.CC. \ 16.20.8.42.102, \ provider=rfc1006: 4. Start the VT listener: # vt_listener example_alias Using information collected in Section 7.4.2, perform the following steps on initiating entity System-B as superuser: 1. Determine available transports and choose one. For this example, use RFC 1006. 2. Perform the following steps: a. Choose an alias. For this example, use system_a_ alias. b. Specify FTAM or VT. For this example, the remote application is VT. c. Obtain the AP-title and AE-qualifier. For this example, the responder does not require this information. d. Obtain the SAP selectors. For this example, the responder's SAP selectors are AA.BB.CC. e. Obtain the remote NSAP. For this example, the responder's RFC 1006 internet address is 16.20.8.42 and the daemon port is 102. f. Specify the transport provider. For this example, use rfc1006. Configuring FTAM and Virtual Terminal 7-9 g. Determine the transport template. Since the transport provider is RFC 1006, you must omit it for this example. 3. Define the alias in isoapplications: system_a_alias :VT:::AA.BB.CC. \ 16.20.8.42.102, \ provider=rfc1006: Once the setup is complete, you can start the VT ologin command: $ ologin system_a_alias OSF/1 (system-a.ftam.dec.com) ttyp4 login: system_a_user Password: system_a_pwd 7.5 About /usr/sbin/osiapplsetup The OSI Applications configuration procedure is /usr/sbin /osiapplsetup. It can configure addressing information about local and remote FTAM and Virtual Terminal applications. During the configuration, addressing information about local and remote FTAM and Virtual Terminal applications is added to the /etc/isoapplications file. Additionally, commands to start local FTAM and VT listeners automatically at system startup time are added to the /sbin/osi_ applstartup file. Refer to DECnet/OSI FTAM and Virtual Terminal Use and Management for more information on the FTAM and Virtual Terminal listeners. If you have the DXDABASE subset of the DEC X.500 Directory Service product installed on your system, then you have the option of configuring the OSI Applications to retrieve addressing information from the X.500 Directory. If you also have the DXDADXIM subset of the X.500 Directory Service software installed, then you may also use osiapplsetup to register addressing information about your local listeners in the X.500 Directory. 7-10 Configuring FTAM and Virtual Terminal Before you start osiapplsetup, you need to make some decisions and gather some information about the local and remote FTAM and Virtual Terminal applications. Therefore, you should complete the appropriate checklists for the osiapplsetup options you intend to use. If you intend to autoconfigure local addresses, complete the checklist in Table 7-1. If you intend to manually configure local addresses, complete the checklist in Table 7-2. If you intend to add aliases for remote applications to isoapplications, complete the checklist in Table 7-3. If you intend to add additional listeners to osi_applstartup, complete the worksheet in Table 7-4 for each listener. 7.5.1 About Configuring Local Addresses You may choose to autoconfigure or manually configure local addresses. Configuring local addresses consists of seven main parts. Each part is optional. 1. Define the aliases and addresses for local OSI Transport listeners and add corresponding entries in isoapplications. Note that OSI Transport listeners accept connections from both Connectionless-Mode Network Service (CLNS) and Connection-Oriented Network Service (CONS) over X.25. 2. Define the aliases and addresses for local RFC 1006 Transport listeners and add corresponding entries in isoapplications. 3. Define the addresses for the local source aliases and add corresponding entries in isoapplications. The source aliases are always "local_ftam" for FTAM and "local_vtp" for Virtual Terminal. The address associated with the corresponding source alias is provided by the application initiator at connection time (e.g., ocp uses "local_ftam"). If you choose not to assign addresses to the source aliases, then the address of the initiator is generated by the software at runtime. 4. If you have the DEC X.500 Directory Service product installed, you may define X.500 Distinguished Names for the local listeners, register the listeners in X.500 Directory, and add corresponding entries in isoapplications. Configuring FTAM and Virtual Terminal 7-11 5. Add commands to start local listeners to /sbin/osi_ applstartup. 6. Start the local listeners. 7. Run the FTAM and Virtual Terminal installation verification procedures (IVPs). The main difference between autoconfiguration and manual configuration is that with autoconfiguration, the osiapplsetup procedure automatically determines as many of the aliases and addresses as it can. With manual configuration, you determine the aliases and addresses yourself and enter the information in response to osiapplsetup prompts. The autoconfiguration option runs through all of the parts listed above to configure local addresses. The manual configuration option puts you into a submenu which has an option for each of the above parts, with the exception of adding listeners to osi_applstartup. There is no osi_ applstartup option in the manual configuration submenu because there is one in the main menu. 7.5.2 Getting Help, Stopping the Configuration Procedure, and Using Defaults The configuration procedure prompts you for information. If you need help responding to any of the configuration script prompts, type a question mark (?) and press Return to view the help text. You can stop the configuration procedure by typing Ctrl/C. Many of the questions have default values associated with them. This information is contained in brackets at the end of the question. Press Return if you want to use the default value, which is osi in the following example: Enter Transport Provider #1 Name [osi]: 7-12 Configuring FTAM and Virtual Terminal Table_7-1_Autoconfiguration_Checklist______________________ Question_______________________________________Yes__No_____ 1. Do you want to add the local listeners for < > < > OSI transport to isoapplications? ___________________________________________________________ 2. Do you want to add the local listeners for < > < > RFC 1006 transport to isoapplications? ___________________________________________________________ 3. Do you want to add the source < > < > aliases "local_ftam" and "local_vtp" to isoapplications? ___________________________________________________________ 4. Is the X.500 DXDABASE subset installed on < > < > the system? If no, go to question 7. ___________________________________________________________ 5. Do you want to retrieve addressing < > < > information from the X.500 Directory? If no, go to question 7. ___________________________________________________________ 6. Do you want to register the local < > < > listeners in the X.500 Directory and add corresponding entries in isoapplications? If yes, you need an X.500 Distinguished Name that identifies the local listener. Complete the following information: o Country name: _____________________________________________ o Organization name: _________________________________________ o Organizational unit(s): ______________________________________ (continued on next page) Configuring FTAM and Virtual Terminal 7-13 Table_7-1_(Cont.)_Autoconfiguration_Checklist______________ Question_______________________________________Yes__No_____ ___________________________________________________________ 7. Do you want to add entries to osi_ < > < > applstartup to start the local listeners at system startup? ___________________________________________________________ 8. Do you want to start up the local < > < > listeners? ___________________________________________________________ 9. Do you want to run the IVPs? < > < > If yes, you need the following information: o User ID: _________________________________________ o Password: _______________________________________ ___________________________________________________________ 7-14 Configuring FTAM and Virtual Terminal Table_7-2_Manual_Configuration_Checklist___________________ Question_______________________________________Yes__No_____ 1. Do you want to add the local listeners for < > < > OSI transport to isoapplications? If yes, fill out a form in Table 7-5 for each listener. The osiapplsetup procedure supplies a default for each item. Listeners can have only one NSAP. ___________________________________________________________ 2. Do you want to add the local listeners for < > < > RFC 1006 transport to isoapplications? If yes, fill out a form in Table 7-5 for each listener. The osiapplsetup procedure supplies a default for each item. Listeners can have only one NSAP. ___________________________________________________________ 3. Do you want to add the source < > < > aliases "local_ftam" and "local_vtp" to isoapplications? If yes, fill out a form in Table 7-5 for each source alias. The osiapplsetup procedure supplies a default for each item. Source aliases can have only one NSAP. ___________________________________________________________ 4. Is the X.500 DXDABASE subset installed on < > < > the system? If no, go to question 7. ___________________________________________________________ 5. Do you want to retrieve addressing < > < > information from the X.500 Directory? If no, go to question 7. ___________________________________________________________ (continued on next page) Configuring FTAM and Virtual Terminal 7-15 Table_7-2_(Cont.)_Manual_Configuration_Checklist___________ Question_______________________________________Yes__No_____ 6. Do you want to register the local < > < > listeners in the X.500 Directory and add corresponding entries in isoapplications? If yes, you need an X.500 Distinguished Name that identifies the local listener. Complete the following information: o Country name: _____________________________________________ o Organization name: _________________________________________ o Organizational unit(s): ______________________________________ ___________________________________________________________ 7. Do you want to start the local listeners? < > < > If yes, fill out a form in Table 7-4 for each listener. The alias must already exist in isoapplications. ___________________________________________________________ 8. Do you want to run the IVPs? < > < > If yes, you need the following information: o User ID: _________________________________________ o Password: _______________________________________ ___________________________________________________________ 7-16 Configuring FTAM and Virtual Terminal Table_7-3_Remote_Application_Checklist_____________________ Question_______________________________________Yes__No_____ 1. Is the X.500 DXDABASE subset installed on < > < > the system? If no, go to question 4. ___________________________________________________________ 2. Do you want to add entries of the < > < > Distinguished Name format? If yes, complete a form in Table 7-6 for each remote application. ___________________________________________________________ 3. Do you want to add entries of the Pattern < > < > format? If yes, you need to determine what your patterns(s) should look like. You may be able to get this information from your network DEC X.500 administration utility (DXIM) to examine the structure of the X.500 Directory information tree for your organization to determine what your Pattern format entries should be. Complete a form in Table 7-7 for each application. ___________________________________________________________ 4. Do you want to add entries of the Address < > < > format? If yes, complete a form in Table 7-5 for each remote_application.________________________________________ Configuring FTAM and Virtual Terminal 7-17 Table_7-4_Listener_Startup_Worksheet_____________________________ Configuration Information____________Answer/Entry______________________________ Application (FTAM or < > VT): Alias name: < > Queue length: < > _________________________________________________________________ 7-18 Configuring FTAM and Virtual Terminal Table_7-5_Address_Format_Worksheet_______________________________ Configuration Information____________Answer/Entry______________________________ Alias name: < > Application (FTAM or < > VT): AP-title: < > AE-qualifier: < > PSEL: < > SSEL: < > TSEL: < > NSAP(s): < > Transport provider < > name(s): Transport template < > name(s): _________________________________________________________________ Configuring FTAM and Virtual Terminal 7-19 Table_7-6_Distinguished_Name_Format_Worksheet____________________ Configuration Information____________Answer/Entry______________________________ Alias name: < > Application (FTAM or < > VT): Distinguished Name: a. Country name: < > b. Organization name: < > c. Organizational < > unit(s): d. Application- Same as the alias name.[3] process name:[1] e. Application-entity < > name:[2] Transport template < > list: [1]Corresponds_to_the_first_/cn=_in_the_Distinguished_Name.______ [2]Corresponds to the second /cn= in the Distinguished Name. [3]The application-process name is automatically set to the same as the alias name. _________________________________________________________________ 7-20 Configuring FTAM and Virtual Terminal Table_7-7_Pattern_Format_Worksheet_______________________________ Configuration Information____________Answer/Entry______________________________ Application (FTAM or < > VT): Distinguished Name: a. Country name: < > b. Organization name: < > c. Organizational < > unit(s): d. Application- *[3] process name:[1] e. Application-entity < > name[2]: Transport template < > list: [1]Corresponds_to_the_first_/cn=_in_the_Distinguished_Name.______ [2]Corresponds to the second /cn= in the Distinguished Name. [3]The application-process name is automatically set to an asterisk (*). _________________________________________________________________ 7.6 Starting the OSI Applications Configuration Procedure Before starting the configuration procedure, you can create a log file of the configuration process. You can use this log file to keep track of your configuration choices. Use the following command to create the log file: #script /var/dna/filename.log Configuring FTAM and Virtual Terminal 7-21 After you complete the configuration procedure, type Ctrl/D or "exit" to save the log file. To start the OSI applications configuration procedure, issue this command: #/usr/sbin/osiapplsetup DECnet/OSI for Digital UNIX Alpha FTAM and Virtual Terminal Configuration Procedure (c) Digital Equipment Corporation. 1993,1994,1995. All Rights Reserved. The FTAM and Virtual Terminal Configuration Procedure allows you to configure addressing information for FTAM and Virtual Terminal applications on both local and remote systems. The procedure displays the following menu: Please select one of the following choices: 1. Autoconfigure Local Addresses 2. Manually Configure Local Addresses 3. Add Aliases for Remote Applications to /etc/isoapplications 4. Add Commands to Start Listeners to /sbin/osi_applstartup 5. Exit the FTAM and Virtual Terminal Configuration Procedure For help at any time, enter a question mark at the prompt, or refer to the DECnet/OSI for Digital UNIX Installation Guide. Selection [5]: See Section 7.7 for a description of option 1, autoconfiguring local addresses. See Section 7.8 for a description of option 2, manually configuring local addresses. See Section 7.9 for a description of option 3, adding aliases for remote applications to isoapplications. See Section 7.10 for a description of option 4, adding commands to start listeners to /sbin/osi_applstartup. 7.7 Autoconfiguring Local Addresses To run the autoconfiguration procedure for local addresses, choose option 1 from the main menu. Before running the autoconfiguration procedure, you should complete the checklist in Table 7-1. The following message displays: Starting the autoconfiguration procedure... 7-22 Configuring FTAM and Virtual Terminal Part 1 of the autoconfiguration procedure is to configure the OSI Transport listeners for FTAM and VT: Starting configuration of local OSI Transport Listeners... The alias "srchr" will represent the FTAM and Virtual Terminal listeners for OSI Transport on your system. The following values will be used for your local OSI Transport listeners: srchr :FTAM:::%x0001.%x0001.%x0001. \ %X4700240408002BE5A3FC21, \ provider=osi,template=default: srchr :VT:::%x0001.%x0001.%x0002. \ %X4700240408002BE5A3FC21, \ provider=osi,template=default: Is this correct? (y/n) [y]: If you want to add the listed entries to isoapplications, enter y at the prompt. If you do not want to add them, enter n. If you enter y, the entries are added to isoapplications and the following message displays: Adding entries to /etc/isoapplications ... done. Part 2 of the autoconfiguration procedure is to configure the RFC 1006 Transport listeners for FTAM and VT: Starting configuration of local RFC1006 Transport Listeners... The alias "srchr-rfc1006" will represent the FTAM and Virtual Terminal listeners for RFC1006 Transport on your system. The following values will be used for your local RFC1006 Transport listeners: srchr-rfc1006 :FTAM:::%x0001.%x0001.%x0001. \ 16.2.99.60.102,provider=rfc1006: srchr-rfc1006 :VT:::%x0001.%x0001.%x0002. \ 16.2.99.60.102,provider=rfc1006: Is this correct? (y/n) [y]: As with the OSI Transport listeners, enter y to add the entries to isoapplications, and enter n to not enter them. If you enter y, the entries are added and the following message displays: Adding entries to /etc/isoapplications ... done. Configuring FTAM and Virtual Terminal 7-23 Part 3 of the autoconfiguration procedure is to configure the source aliases for FTAM and VT: Starting configuration of Source Aliases... The following values will be used for the "local_ftam" and "local_vtp": local_ftam :FTAM:::%x0001.%x0001.%x0001. \ %X4700240408002BE5A3FC21, \ provider=osi,template=default: local_vtp :VT:::%x0001.%x0001.%x0002. \ %X4700240408002BE5A3FC21, \ provider=osi,template=default: Is this correct? (y/n) [y]: As with the local listeners, enter y to add the entries to isoapplications, and enter n to not enter them. If you enter y, the entries are added and the following message displays: Adding entries to /etc/isoapplications ... done. Part 4 of the autoconfiguration procedure only appears if you have the DEC X.500 Directory Service product installed. In Part 4, you have the option of storing the addresses of the local FTAM and Virtual Terminal listeners in the X.500 Directory and the isoapplications file. The DEC X.500 Directory Service software is installed on your system. Would you like to configure DECnet/OSI FTAM and DECnet/OSI Virtual Terminal to be able to retrieve addressing information from the X.500 Directory? (y/n) [y]: If you wish to use X.500, enter y. DECnet/OSI FTAM and DECnet/OSI Virtual Terminal will be configured to retrieve addressing information from the X.500 Directory. The alias "srchr-x500" will represent the FTAM and Virtual Terminal listeners in Distinguished Name format on your system. Would you like to register the local FTAM and Virtual Terminal listeners represented by "srchr-x500" in the X.500 Directory? (y/n) [y]: y 7-24 Configuring FTAM and Virtual Terminal If you would like to enter the local FTAM and VT listeners in X.500 Directory, enter y. Then you are prompted for information to generate the X.500 Distinguished Names of the local FTAM and Virtual Terminal listeners. The /usr/sbin/osiapplsetup procedure assumes that your organization's Directory Service schema follows the schema supplied by Digital's X.500 Directory Service product. If you type a question mark (?) at any of the prompts, you receive information on valid values for a particular prompt. However, the /usr/sbin/osiapplsetup procedure does not check to make sure that the input you supply is valid. If your organization's Directory Service uses a schema that is different from the one provided by Digital's X.500 Directory Service product, then you may need to: 1. Register your local listeners via the DEC X.500 Directory Service Administration Facility directly. 2. Manually add the Distinguished Name entries for local listeners to the isoapplications file. Enter the country name: us Enter the organization name: local_org Enter the organizational unit: local_org_unit Enter the organizational unit: The following entries will be created in the X.500 Directory, with corresponding entries of the Distinguished Name format created in /etc/isoapplications: /c="us"/o="local_org"/ou="local_org_unit"/cn="srchr"/cn="ftam" /c="us"/o="local_org"/ou="local_org_unit"/cn="srchr"/cn="vt" Is this correct? (y/n) [y]: If you answer y, the configuration procedure uses the DEC X.500 Administration Facility to create one application process entry and two application-entity entries in the X.500 Directory. The presentation address displayed previously will be used as the value of the presentation- address attribute of the application-entity entries. Configuring FTAM and Virtual Terminal 7-25 Agreements in International OSI Implementors groups regarding the storage of Form2 (object identifier) AE- titles in the X.500 directory are still in draft form. Therefore, the /usr/sbin/osiapplsetup procedure does not prompt you for a Form2 AE-title. If there are errors in creating the entries, the following messages appear: osiapplsetup - Warning: X.500 DIB entries created with errors osiapplsetup - Warning: Please check /var/dna/dna_install.log for more information. Refer to the /var/dna/dna_install.log log file for additional information on the errors that occurred. You may need to check your X.500 configuration to solve the problem. If there are no errors in creating the entries, the following messages appear: Creating entries in the X.500 Directory ... done Adding entries to /etc/isoapplications ... done. If you answer n to the X.500 Directory entries being correct, osiapplsetup asks you again if you want to register your local listeners in X.500 Directory. Part 5 of the autoconfiguration procedure adds commands to start up local FTAM and VT listeners to /sbin/osi_ applstartup: The following entries will be added to the /sbin/osi_applstartup: /usr/sbin/ftam_listener srchr > /dev/console 2>&1 /usr/sbin/ftam_listener srchr-rfc1006 > /dev/console 2>&1 /usr/sbin/vt_listener srchr > /dev/console 2>&1 /usr/sbin/vt_listener srchr-rfc1006 > /dev/console 2>&1 Do you want to add the listeners to /sbin/osi_applstartup? (y/n) [y]: Enter y to add the entries to osi_applstartup, and enter n to not enter them. If you enter y, the entries are added and the following message displays: Modifying /sbin/osi_applstartup ... done. 7-26 Configuring FTAM and Virtual Terminal Part 6 of the autoconfiguration procedure starts up the listeners that were just added to /sbin/osi_applstartup: Would you like to start the listeners that were added to the /sbin/osi_applstartup file now that the installation is complete? (y/n) [y]: Enter y to start up the listeners, and enter n to not start them up. If you enter y, the listeners are started up and the following messages display: Starting FTAM listener ... /usr/sbin/ftam_listener srchr > /dev/console 2>&1 /usr/sbin/ftam_listener srchr-rfc1006 > /dev/console 2>&1 Starting VT listener ... /usr/sbin/vt_listener srchr > /dev/console 2>&1 /usr/sbin/vt_listener srchr-rfc1006 > /dev/console 2>&1 Listeners just added to the /sbin/osi_applstartup have been started. Part 7 of the autoconfiguration procedure runs the FTAM and VT IVPs: After verifying that the system is operating properly with DECnet/OSI FTAM and DECnet/OSI Virtual Terminal installed, you may wish to remove the following saved files: - /sbin/osi_applstartup.sav[n] - /etc/isoapplications.sav[n] The DECnet/OSI FTAM and DECnet/OSI Virtual Terminal Configuration Procedure is complete. Would you like to verify the configuration by running the FTAM and Virtual Terminal IVPs (y/n) [y]: Enter y to run the IVPs, and enter n to not run them. If you choose to run the IVPs, for the FTAM IVP you need a local initiator ID (user name) and password (note that the password does not echo). Configuring FTAM and Virtual Terminal 7-27 Beginning the FTAM Installation Verification Procedure... This script is executed after FTAM has been installed on your system. It verifies that FTAM has been properly installed and that network communication can take place between your local node and other nodes on the network. This test attempts to list a file over the network using FTAM. You will be asked for the initiator id and password for the local system. If at any time you wish to interrupt this test, enter ^C. Enter initiator id: smith Enter password for smith: ols :::ivpppm.ivpspm.ivptpm.%X47002402010A0408002BE5A3FC21:/smith/password::/ usr/sbin/ftam_check /usr/sbin/ftam_check IVP for FTAM is successful. Beginning the DECnet/OSI Virtual Terminal Installation Verification Procedure... This script is executed after Virtual Terminal has been installed on your system. It verifies that Virtual Terminal has been properly installed and that network communication can take place between your local node and other nodes on the network. This test attempts to transfer data over the network using Virtual Terminal. If at any time you wish to interrupt this test, enter ^C. /usr/sbin/vt_ivp /usr/sbin/vt_ivp.script /var/dna/vt_ivp.log # /usr/bin/ologin $VT_IVP_ADDRESS OSF1 (srchr.lkg.dec.com) (ttyp7) login: login: ^D ologin: control returned to local end system # Test successful IVP for Virtual Terminal is successful. Autoconfiguration of local address is now complete. 7-28 Configuring FTAM and Virtual Terminal 7.8 Manually Configuring Local Addresses To run the manual configuration procedure for local addresses, choose option 2 from the main menu. Before running the manual configuration procedure, you should complete the checklist in Table 7-2. The following message displays: Starting the manual configuration procedure... The manual configuration procedure consists of a submenu containing all of the parts of manual configuration. The only part missing is to add commands to start local listeners to /sbin/osi_applstartup. Use the main menu option 4 to perform this part of the procedure. The manual configuration submenu displays as follows: Please select one of the following choices: 1. Configure an OSI Transport Listener 2. Configure an RFC1006 Transport Listener 3. Define Source Aliases 4. Register Listeners in X.500 Directory 5. Start Listeners 6. Run IVPs 7. Exit For help at any time, enter a question mark at the prompt, or refer to the DECnet/OSI for Digital UNIX Installation Guide. Selection [7]: Each option in the manual configuration submenu corresponds to a part in the manual configuration procedure. You can choose which parts you want to execute. Use your answers from the checklist in Table 7-2 to determine the options you need to choose. The options in this menu are described in the following sections respectively. Configuring FTAM and Virtual Terminal 7-29 7.8.1 Configuring OSI Transport Listeners To configure the local listeners for the OSI Transport, choose option 1 in the manual configuration submenu. This option prompts you to enter values for one local listener. If you wish to configure more than one local listener (for example, one for FTAM and one for VT), you must choose option 1 multiple times, once for each OSI Transport listener. Note that an OSI Transport listener accepts connections from both CLNS and CONS over X.25. The osiapplsetup procedure provides defaults for most of the prompts. If you are satisfied with the default, press Return to accept it. Otherwise, enter your own value. The following script gives an example of configuring an OSI Transport listener for FTAM: Starting configuration of an OSI Transport Listener... You will be prompted for information used to generate an entry in /etc/isoapplications for one OSI Transport Listener. Enter the alias [srchr]: Enter Application (FTAM or VT): ftam Enter AP title: Enter AE qualifier: Enter Presentation Selector [%x0001]: Enter Session Selector [%x0001]: Enter Transport Selector [%x0001]: Enter NSAP [%X4700240408002BE5A3FC21]: Enter Transport Provider [osi]: Enter Transport Template [default]: srchr :FTAM:::%x0001.%x0001.%x0001. \ %X4700240408002BE5A3FC21,\ provider=osi,template=default: Do you want to add it to /etc/isoapplications (y/n): [y]? To add the entry displayed to isoapplications, enter y. To not add it, enter n. 7-30 Configuring FTAM and Virtual Terminal 7.8.2 Configuring RFC 1006 Transport Listeners To configure the local listeners for the RFC 1006 Transport, choose option 2 in the manual configuration submenu. This option prompts you to enter values for one local listener. If you want to configure more than one local listener (for example, one for FTAM and one for VT), you must choose option 2 multiple times, once for each RFC 1006 Transport listener. The osiapplsetup procedure provides defaults for most of the prompts. If you are satisfied with the default, press Return to accept it. Otherwise, enter your own value. The following script provides an example of configuring an RFC 1006 Transport listener for VT: Starting configuration of an RFC1006 Transport Listener... You will be prompted for information used to generate an entry in /etc/isoapplications for one RFC1006 Transport Listener. Enter the alias [srchr-rfc1006]: Enter Application (FTAM or VT): vt Enter AP title: Enter AE qualifier: Enter Presentation Selector [%x0001]: Enter Session Selector [%x0001]: Enter Transport Selector [%x0002]: Enter NSAP [16.2.99.60]: Enter Transport Provider [rfc1006]: srchr-rfc1006 :VT:::%x0001.%x0001.%x0002. \ 16.2.99.60.102, \ provider=rfc1006: Do you want to add it to /etc/isoapplications (y/n): [y]? To add the entry displayed to isoapplications, enter y. Otherwise, enter n. Configuring FTAM and Virtual Terminal 7-31 7.8.3 Configuring Source Aliases To configure the source aliases ("local_ftam" and "local_ vtp"), choose option 3 in the manual configuration submenu. This option prompts you to enter values first for "local_ ftam" and then for "local_vtp". The osiapplsetup procedure provides defaults for most of the prompts. If you are satisfied with the default, press Return to accept it. Otherwise, enter your own value. The following script gives an example of configuring the sources aliases for FTAM and VT: Starting configuration of source aliases "loca_ftam" and "local_vtp"... You will be prompted for information used to generate an entry in /etc/isoapplications for source aliases "local_ftam" and "local_vtp". The definition of source aliases is necessary only if you must always know the complete address of an initiator. If no source address is defined, then one is dynamically created at run time. Enter the alias [local_ftam]: Enter Application (FTAM or VT): FTAM Enter AP title: Enter AE qualifier: Enter Presentation Selector [%x0001]: Enter Session Selector [%x0001]: Enter Transport Selector [%x0001]: Enter NSAP [%X4700240408002BE5A3FC21]: Enter Transport Provider [osi]: Enter Transport Template [default]: local_ftam :FTAM:::%x0001.%x0001.%x0001. \ %X4700240408002BE5A3FC21, \ provider=osi,template=default: Do you want to add it to (y/n): [y]? Enter the alias [local_vtp]: Enter Application (FTAM or VT): VT 7-32 Configuring FTAM and Virtual Terminal Enter AP title: Enter AE qualifier: Enter Presentation Selector [%x0001]: Enter Session Selector [%x0001]: Enter Transport Selector [%x0002]: Enter NSAP [%X4700240408002BE5A3FC21]: Enter Transport Provider [osi]: Enter Transport Template [default]: local_vtp :VT:::%x0001.%x0001.%x0002. \ %X4700240408002BE5A3FC21, \ provider=osi,template=default: Do you want to add it to (y/n): [y]? 7.8.4 Configuring X.500 Entries for Local Listeners To define an X.500 Distinguished Name for local listeners, register the local listeners in X.500 Directory, and add the corresponding entries in isoapplications, choose option 4 in the manual configuration sub-menu. This option is only useful if you have DEC X.500 Directory Service software installed on your system. If you choose to enter the local listeners in X.500 Directory, then you are prompted for information to generate the X.500 Distinguished Names of the local FTAM and Virtual Terminal listeners. The /usr/sbin/osiapplsetup procedure assumes that your organization's Directory Service schema follows the schema supplied by Digital's X.500 Directory Service product. If you type a question mark (?) at any of the prompts, you will receive information on valid values for a particular prompt. However, the /usr/sbin/osiapplsetup procedure will not check to make sure that the input you supply is valid. If your organization's Directory Service uses a schema that is different from the one provided by Digital's X.500 Directory Service product, then you may need to: 1. Register your local listeners via the DEC X.500 Directory Service Administration Facility directly. Configuring FTAM and Virtual Terminal 7-33 2. Manually add the Distinguished Name entries for local listeners to the isoapplications file. Starting configuration of Distinguished Name format Listeners... You will be prompted for information used to generate the X.500 Distinguished Name for the local listeners which will be registered in X.500 Directory and added to /etc/isoapplications with the alias "srchr-x500". Enter the country name: us Enter the organization name: local_org Enter the organizational unit: local_org_unit Enter the organizational unit: The following entries will be created in the X.500 Directory, with corresponding entries of the Distinguished Name format created in /etc/isoapplications: /c="us"/o="local_org"/ou="local_org_unit"/cn="srchr"/cn="ftam" /c="us"/o="local_org"/ou="local_org_unit"/cn="srchr"/cn="vt" Is this correct? (y/n) [y]: If you answer y, the configuration procedure will use the DEC X.500 Administration Facility to create one application process entry and two application-entity entries in the X.500 Directory. The presentation address displayed previously will be used as the value of the presentation address attribute of the application entity entries. Agreements in International OSI Implementors groups regarding the storage of Form2 (object identifier) AE- titles in the X.500 Directory are still in draft form. Therefore, the /usr/sbin/osiapplsetup procedure does not prompt you for a Form2 AE-title. If there are errors in creating the entries, the following messages appear: osiapplsetup - Warning: X.500 DIB entries created with errors osiapplsetup - Warning: Please check /var/dna/dna_install.log for more information. Refer to the /var/dna/dna_install.log log file for more information on the errors that occurred. You may need to check your X.500 configuration to solve the problem. 7-34 Configuring FTAM and Virtual Terminal If there are no errors in creating the entries, the following messages appear: Creating entries in the X.500 Directory ... done Adding entries to /etc/isoapplications ... done. 7.8.5 Starting Listeners To start local FTAM and VT listeners, choose option 5 of the manual configuration submenu. This option prompts you to enter the alias name and queue length for each FTAM listener to start, and then for each VT listener to start. Each alias you specify must already exist in isoapplications. NOTE: This option does NOT add commands to /sbin/osi_ applstartup to start the listeners at system startup time (use option 4 of the main menu to perform this function). The following script gives an example of starting up the OSI Transport listeners for FTAM and VT: This part of the configuration procedure starts listeners. The questions that follow prompt you for an alias and a queue length. Press at the alias prompt when you have finished adding listeners. Adding listener for FTAM Enter the alias for the ftam_listener: srchr Enter queue length [10]: Adding listener for FTAM Enter the alias for the ftam_listener: Adding listener for VT Enter the alias for the vt_listener: srchr Enter queue length [10]: Adding listener for VT Enter the alias for the vt_listener: Starting FTAM listener ... Configuring FTAM and Virtual Terminal 7-35 /usr/sbin/ftam_listener -q 10 srchr >/dev/console 2>&1 Starting VT listener ... /usr/sbin/vt_listener -q 10 srchr >/dev/console 2>&1 7.8.6 Running the FTAM and VT IVPs To run the IVPs for FTAM and VT, choose option 6 of the manual configuration submenu. This option runs the FTAM IVP and then the VT IVP. For the FTAM IVP, you need a local initiator ID (user name) and password (note that the password does not echo). Beginning the FTAM Installation Verification Procedure... This script is executed after FTAM has been installed on your system. It verifies that FTAM has been properly installed and that network communication can take place between your local node and other nodes on the network. This test attempts to list a file over the network using FTAM. You will be asked for the initiator id and password for the local system. If at any time you wish to interrupt this test, enter ^C. Enter initiator id: smith Enter password for smith: ols :::ivpppm.ivpspm.ivptpm.%X47002402010A0408002BE5A3FC21:/smith/password::/ usr/sbin/ftam_check /usr/sbin/ftam_check IVP for FTAM is successful. Beginning the DECnet/OSI Virtual Terminal Installation Verification Procedure... This script is executed after Virtual Terminal has been installed on your system. It verifies that Virtual Terminal has been properly installed and that network communication can take place between your local node and other nodes on the network. This test attempts to transfer data over the network using Virtual Terminal. If at any time you wish to interrupt this test, enter ^C. /usr/sbin/vt_ivp /usr/sbin/vt_ivp.script /var/dna/vt_ivp.log # /usr/bin/ologin $VT_IVP_ADDRESS OSF1 (srchr.lkg.dec.com) (ttyp7) 7-36 Configuring FTAM and Virtual Terminal login: login: ^D ologin: control returned to local end system # Test successful IVP for Virtual Terminal is successful. 7.8.7 Exiting the Manual Configuration Procedure To exit the manual configuration procedure, choose option 7 from the submenu. The osiapplsetup procedure displays a list of all the entries that you have added to isoapplications during your manual configuration and returns you to the main menu. For example: Manual configuration of local addresses is now complete. The following entries have been added to /etc/isoapplications: srchr :FTAM:::%x0001.%x0001.%x0001. \ %X4700240408002BE5A3FC21,\ provider=osi,template=default: srchr :VT:::%x0001.%x0001.%x0002. \ %X4700240408002BE5A3FC21,\ provider=osi,template=default: srchr-rfc1006 :FTAM:::%x0001.%x0001.%x0001. \ 16.2.99.60.102, \ provider=rfc1006: srchr-rfc1006 :VT:::%x0001.%x0001.%x0002. \ 16.2.99.60.102, \ provider=rfc1006: local_ftam :FTAM:::%x0001.%x0001.%x0001. \ %X4700240408002BE5A3FC21, \ provider=osi,template=default: local_vtp :VT:::%x0001.%x0001.%x0002. \ %X4700240408002BE5A3FC21, \ provider=osi,template=default: srchr-x500 :FTAM:template=default:/c=us/o=local_org/ou=local_org_unit/cn=srchr/cn=ftam: srchr-x500 :VT:template=default:/c=us/o=local_org/ou=local_org_unit/cn=srchr/cn=vt: Configuring FTAM and Virtual Terminal 7-37 Please select one of the following choices: 1. Autoconfigure Local Addresses 2. Manually Configure Local Addresses 3. Add Aliases for Remote Applications to /etc/isoapplications 4. Add Commands to Start Listeners to /sbin/osi_applstartup 5. Exit the FTAM and Virtual Terminal Configuration Procedure For help at any time, enter a question mark at the prompt, or refer to the DECnet/OSI for Digital UNIX Installation Guide. Selection [5]: 7.9 Configuring Addresses for Remote FTAM and VT Applications To add aliases for remote FTAM and VT applications on your network, choose option 3 from the main menu. Before running this option, you should complete the checklist in Table 7-3. This part of the configuration procedure adds entries for remote applications on your network to the isoapplications file. If you have the DEC X.500 Directory Service product installed, you have the option of adding entries of the Distinguished Name format and the Pattern format to isoapplications. If you choose this option, you are prompted for information to generate the X.500 Distinguished Name of the remote application. You have the option of adding entries of the Address format regardless of whether X.500 is installed. If you have X.500 installed, you will see the following introductory messages: Starting configuration of a remote address... This part of the configuration procedure adds entries, for remote applications on your network, to the /etc/isoapplications file. You may choose to add entries of the Distinguished Name format, the Address format, or both. 7-38 Configuring FTAM and Virtual Terminal If you choose to add entries of the Distinguished Name format, then you will be prompted for the names of the relevant country, organization, organizational unit, application process, application entity and transport templates. If you choose to add entries of the Address format, then you will be prompted for the AP-title, AE-qualifier, Presentation selector (PSEL), Session selector (SSEL), Transport selector (TSEL), NSAPS, and Transport template and Transport provider for each NSAP. Press at the alias prompt when you have finished adding aliases of a particular format. If you do not have X.500 installed, you will see the following introductory messages: Starting configuration of a remote address... This part of the configuration procedure adds entries, for remote applications on your network, to the /etc/isoapplications file. You will be prompted for the AP-title, AE-qualifier, Presentation selector (PSEL), Session selector (SSEL), Transport selector (TSEL), NSAPS, and Transport template and Transport provider for each NSAP. Press at the alias prompt when you have finished adding entries. 7.9.1 Adding Distinguished Name Format Entries To enter Distinguished Name format entries to isoapplications, press Return at the following prompt. Otherwise, type n and press Return. NOTE: This section of the script only appears if you have X.500 installed. Would you like to add entries of the Distinguished Name format to /etc/isoapplications? (y/n) [y]: If you choose to enter Distinguished Name format entries, you are prompted for further information. Use the information you completed in the worksheets in Table 7-6 to reply to the questions, and after each entry, press Return. If the script shows a default entry for a field, Configuring FTAM and Virtual Terminal 7-39 press Return to accept the default, or enter a new value and press Return. To leave a field blank when there is no default, simply press Return. The entries are displayed for your review before entering them into isoapplications. The procedure then prompts you for information to add another Distinguished Name entry to isoapplications. If you choose not to add another entry, simply press Return. The /usr/sbin/osiapplsetup procedure assumes that your organization's Directory Service schema follows the schema supplied by Digital's X.500 Directory Service product. If you type a question mark (?) at any of the prompts, you receive information on valid values for a particular prompt. However, the /usr/sbin/osiapplsetup procedure does not check to make sure that the input you supply is valid. If your organization's Directory Service uses a schema that is different from the one provided by Digital's X.500 Directory Service product, then you may need to: 1. Register your local listeners via the DEC X.500 Directory Service Administration Facility directly. 2. Manually add Distinguished Name and Pattern format entries to the isoapplications file. The following script gives an example of adding one Distinguished Name format entry for a remote FTAM application: You will be prompted for information that will be used to generate Distinguished Name entries in /etc/isoapplications. The osiapplsetup procedure assumes that the alias is the value of the common name attribute of an application process entry in the X.500 Directory. Press at the alias prompt when you have finished adding Distinguished Name entries to /etc/isoapplications. Enter the alias [return if done]: intrpd Enter the Application (FTAM or VT): ftam Enter the country name : us Enter the organization name: org 7-40 Configuring FTAM and Virtual Terminal Enter the organizational unit: org_unit Enter the organizational unit: Enter the name of the FTAM entity [FTAM]: Enter the transport templates to be used [return when done]: The following Distinguished Name format entry will be added to /etc/isoapplications: intrpd :FTAM:template=default:/c=us/o=org/ou=org_unit/cn=intrpd/cn=ftam: Is this correct? (y/n) [y]: Added the following entry to /etc/isoapplications: intrpd :FTAM:template=default:/c=us/o=org/ou=org_unit/cn=intrpd/cn=ftam: You will be prompted for information that will be used to generate Distinguished Name entries in /etc/isoapplications. The osiapplsetup procedure assumes that the alias is the value of the common name attribute of an application process entry in the X.500 Directory. Press at the alias prompt when you have finished adding Distinguished Name entries to /etc/isoapplications. Enter the alias [return if done]: 7.9.2 Adding Address Format Entries If you have X.500 installed, the following question appears. To enter Address format entries to isoapplications, press Return at the following prompt. Otherwise, type n and press Return. NOTE: Other than this first question, this section of the script appears regardless of whether you have X.500 installed. Would you like to add entries of the Address format to /etc/isoapplications? (y/n) [y]: If you choose to enter Address format entries, you are prompted for further information. Use the information you completed in the worksheets in Table 7-5 to respond to the questions, and after each entry, press Return. When you have completed entering NSAPs, press Return at the NSAP prompt. Configuring FTAM and Virtual Terminal 7-41 Use Address format entries to define aliases for all three transports: OSI Transport using CLNS, OSI Transport using CONS over X.25, or RFC 1006 Transport. See the task lists in Section 7.4 for more information about what to specify in the Address format entry for each of these three transports. If the script shows a default entry for a field, press Return to accept the default, or enter a new value and press Return. To leave a field blank when there is no default, simply press Return. The following script gives an example of adding one Address format entry for a remote VT application using the OSI Transport with CLNS: Enter the alias: discvr Enter Application (FTAM or VT): vt Enter AP title: Enter AE qualifier: Enter Presentation Selector: %x0001 Enter Session Selector: %x0001 Enter Transport Selector: %x0002 Enter NSAP #1: %X490004AA000400FF1121 Enter Transport Provider #1 Name [osi]: Enter Transport Template #1 Name [default]: Enter NSAP #2: A system that has multiple addresses is called "multihomed." The DECnet/OSI Planning Guide discusses multihoming. Each Address format entry that you configure requires at least one NSAP value. However, osiapplsetup does not force you to enter this value. If you press Return when prompted to enter NSAP value #1, osiapplsetup assumes that you have completed the address configuration and continues with the next step, even though the NSAP field is empty. If you accidentally configure an application address without 7-42 Configuring FTAM and Virtual Terminal an NSAP value, you can correct the situation by editing isoapplications directly. The osiapplsetup procedure allows only five NSAPs to be entered for each Address format entry. If five NSAPs are not sufficient, you may add more NSAPs to the application address by editing isoapplications directly. Press Return at the "Enter NSAP:" prompt after you enter all the NSAPs for the application. After you enter the application address, the procedure displays the information you entered and asks you to confirm. You have entered the following alias: discvr :VT:::%x0001.%x0001.%x0002. \ %X490004AA000400FF1121, \ provider=osi,template=default: Is this correct (y/n) [y]? If you answer with n, you are prompted to re-enter the information for the remote application address. If you answer with y, the procedure prompts you to enter the alias for the next remote application. When you finish adding remote application addresses, press Return at the "Enter the alias:" prompt. The procedure responds: Modifying /etc/isoapplications...done. 7.9.3 Adding Pattern Format Entries If you have the DEC X.500 Directory Service product installed, you have the option of adding entries of the Pattern format to isoapplications. If you choose this option, you are prompted for information to generate the X.500 Pattern format entries. Use the information you completed in the worksheets in Table 7-7 to reply to the questions, and after each entry, press Return. If the script shows a default entry for a field, press Return to accept the default, or enter a new value and press Return. To leave a field blank when there is no default, simply press Return. Configuring FTAM and Virtual Terminal 7-43 The entries are displayed for your review before entering them into isoapplications. The /usr/sbin/osiapplsetup procedure assumes that your organization's Directory Service schema follows the schema supplied by Digital's X.500 Directory Service product. If you type a question mark (?) at any of the prompts, you receive information on valid values for a particular prompt. However, the /usr/sbin/osiapplsetup procedure does not check to make sure that the input you supply is valid. If your organization's Directory Service uses a schema that is different from the one provided by Digital's X.500 Directory Service product, then you may need to: 1. Register your local listeners via the DEC X.500 Directory Service Administration Facility directly. 2. Manually add Distinguished Name and Pattern format entries to the isoapplications file. The following script gives an example of adding two Pattern format entries: one for FTAM and one for VT. Starting configuration of Pattern format Listeners to /etc/isoapplications... This part of the configuration procedure creates entries of the Pattern format in /etc/isoapplications. The osiapplsetup procedure will create Pattern format entries of the following form: * :application:template_list:/c=country/o=organization/ou=org_unit /cn=*/cn=application_entity_name The alias part of the Pattern format entry matches all aliases passed to the FTAM and Virtual Terminal commands. osiapplsetup will assume that the alias is the value of the common name attribute of an application process entry in the X.500 Directory. Would you like to add entries of the Pattern format to /etc/isoapplications? (y/n) [y]: Enter the Application (FTAM or VT): ftam Enter the country name : us Enter the organization name: org Enter the organizational unit: org_unit 7-44 Configuring FTAM and Virtual Terminal Enter the organizational unit: Enter the name of the FTAM entity [FTAM]: Enter the transport templates to be used [return when done]: The following Pattern format entry will be added to the /etc/isoapplications file: * :FTAM:template=default:/c=us/o=org/ou=org_unit/cn=*/cn=ftam: Is this correct? (y/n) [y]: Writing Pattern entry to /etc/isoapplications ... done. Do you want to continue to add entries of the Pattern format to /etc/isoapplications? (y/n) [y]: Enter the Application (FTAM or VT): vt Enter the country name : us Enter the organization name: org Enter the organizational unit: org_unit Enter the organizational unit: Enter the name of the VT entity [VT]: Enter the transport templates to be used [return when done]: The following Pattern format entry will be added to the /etc/isoapplications file: * :VT:template=default:/c=us/o=org/ou=org_unit/cn=*/cn=vt: Is this correct? (y/n) [y]: Writing Pattern entry to /etc/isoapplications ... done. Do you want to continue to add entries of the Pattern format to /etc/isoapplications? (y/n) [y]: n 7.9.4 Exiting Remote Address Configuration After you have entered all of your remote addresses, when osiapplsetup is about to return to the main menu, osiapplsetup prints out a list of all the entries that have just been added to isoapplications. For example, for the case where you have X.500 installed, you will see the following (based on the examples in the previous sections): Configuring FTAM and Virtual Terminal 7-45 The following entries have been added in /etc/isoapplications. intrpd :FTAM:template=default:/c=us/o=org/ou=org_unit/cn=intrpd/cn=ftam: discvr :VT:::%x0001.%x0001.%x0002. \ %X490004AA000400FF1121, \ provider=osi,template=default: * :FTAM:template=default:/c=us/o=org/ou=org_unit/cn=*/cn=ftam: * :VT:template=default:/c=us/o=org/ou=org_unit/cn=*/cn=vt: 7.10 Configuring Local Listeners for Startup To add commands to start listeners at system startup to /sbin/osi_applstartup, choose option 4 from the main menu. This option prompts you to enter the alias name and queue length for each FTAM listener to add, and then for each VT listener to add. Each alias you specify must already exist in isoapplications. See the worksheet in Table 7-4 for what information you need about each listener you want to add. If you are configuring local addresses using the manual configuration procedure, you must use this option if you want to add commands to start local listeners to osi_applstartup. If you are configuring using the autoconfiguration procedure, you do not need to use this option unless you want to add more listeners at a later date or unless you told the autoconfiguration procedure to not add the listeners to osi_applstartup. The listeners that you specify in this option are added into the /sbin/osi_applstartup, and are automatically invoked at system startup time. The listener translates the alias to an address that contains the transport address on which the listener will wait for incoming connection requests. Make sure the alias you enter here was added to the isoapplications file during the previous configuration steps. The queue length is the number of outstanding transport connection requests to the listener for this alias that can be pending at any one time. The following script gives an example of adding commands to start one FTAM listener and one VT listener: 7-46 Configuring FTAM and Virtual Terminal Starting adding a listener to the /sbin/osi_applstartup... This part of the configuration procedure adds listener entries into the /sbin/osi_applstartup file. These listeners are automatically invoked at system startup time. The questions that follow prompt you for an an alias and a queue length. Press at the alias prompt when you have finished adding listeners. Adding listeners for FTAM Enter the alias for the ftam_listener: srchr Enter queue length [10]: Enter the alias for the ftam_listener: Adding listeners for VT Enter the alias for the vt_listener: srchr Enter queue length [10]: Enter the alias for the vt_listener: Modifying /sbin/osi_applstartup ... done. After osiapplsetup has added the commands to osi_ applstartup, it gives you the option of starting the listeners now. If you answer 'y' to the following prompt, the listeners are started. Would you like to start the listeners that were added to the /sbin/osi_applstartup file now that the installation is complete? (y/n) [y]: Starting FTAM listener ... /usr/sbin/ftam_listener -q 10 srchr >/dev/console 2>&1 Starting VT listener ... /usr/sbin/vt_listener -q 10 srchr >/dev/console 2>&1 Listeners just added to the /sbin/osi_applstartup have been started. Once the software is installed and functioning properly, you can delete prior versions of /sbin/osi_applstartup. The files you can delete have a .sav* extension, where "*" represents a version number. Configuring FTAM and Virtual Terminal 7-47 7.11 Rebuilding the Internal Table of Commands After you install the FTAM or Virtual Terminal software, enter the rehash command at the superuser prompt. This command tells the shell to rebuild its internal table of commands within the directories in your path. Refer to csh(1) in the online reference pages for more information about this command. # rehash 7.12 Verifying the Installation As mentioned earlier, the installation verification procedure (IVP) runs as part of the FTAM and Virtual Terminal software installation procedure. However, you can also run the IVP separately at any time after installing the software. You must be a superuser to run the IVP. To run the IVP, type /usr/sbin/ftam_check or /usr/sbin/vt_check and press Return at the system prompt. In the FTAM IVP, you are prompted for a valid user ID on the local system (initiator id) and the password for the local user ID. The password that you type is not displayed on the screen. 7.13 Verifying the FTAM-FTP Gateway Installation The FTAM IVP verifies that the FTAM-FTP Gateway has been installed by checking if the files are in the correct locations. To verify the FTAM-FTP Gateway installation by checking its operation, use the following two-part procedure. The first part of the procedure checks the OSI portion of the FTAM-FTP Gateway /usr/sbin/ftam2ftpd and the second part checks the Internet portion /usr/sbin/ftp2ftamd. 7.13.1 To Check the OSI Portion of the FTAM-FTP Gateway 1. Start up a responder in the background by executing the following command: /usr/sbin/ftam2ftpd alias & 7-48 Configuring FTAM and Virtual Terminal 2. Use the following command as a test: ols alias/user@localhost/password::/usr/sbin/ftam_check The user is the login name of a user on the FTAM system and password is the password for the specified user. 7.13.2 To Check the Internet Portion of the FTAM-FTP Gateway 1. Verify that the DECnet-Internet Gateway has been configured on your system by using these steps: - Issue the following command: # grep ftp /etc/inetd.conf - If you see the following line, your system has been properly configured to run the DECnet-Internet Gateway. Go to step 2. ftp stream tcp nowait root /usr/sbin/ftpd.gw ftpd - If you do not see the expected output, then issue the following command: # /usr/sbin/decnetsetup gateway After decnetsetup completes, go to step 2. 2. Start up a responder in the background using the following command: /usr/sbin/ftamd alias & 3. Use the following command to connect to your current node, which is used as the FTAM-FTP Gateway host: ftp localhost 4. At the name prompt (which displays localhost and the name of the user who initiated the FTP session), type in the FTAM alias and user name in the following format: Name (localhost::username): alias::user The user is the name of a user on that FTAM system. 5. At the password prompt, type in the password of the user. 6. Use the following command as a test: ls /usr/sbin/ftam_check Configuring FTAM and Virtual Terminal 7-49 7. End the FTP session by using the close or bye commands. 7-50 Configuring FTAM and Virtual Terminal Part IV _________________________________________________________________ Appendixes Part IV consists of the following appendixes that contain sample installations and configurations, and discuss software subsets and installation requirements: o Appendix A - Sample DECnet/OSI Installations o Appendix B - Sample DECnet/OSI Advanced and Basic Configurations o Appendix C - Software Subsets and Installation Requirements A _________________________________________________________________ Sample DECnet/OSI Installations This appendix includes the following sample installation logs: o Full-capability DECnet/OSI installation o DECnet for Small Configurations (DNALITE) installation o RFC 1006-only installation o MOP-standalone installation A.1 Sample Log for Full-Capability Installation The following is a sample installation log file for a full- capability installation. # setld -l . 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 Sample DECnet/OSI Installations A-1 - 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): - 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. Choices (for example, 1 2 4-6): 1-3 5-15 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 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 A-2 Sample DECnet/OSI Installations - 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 Press Return to display the next screen: - 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: File system space checked OK. 14 subset(s) will be installed. Loading 1 of 14 subset(s).... Copyright (c) Digital Equipment Corporation. 1993-1996. All Rights Reserved. Digital UNIX WAN Utilities Copying from /mnt (disk) Verifying Loading 2 of 14 subset(s).... DECnet/OSI Kernel Components Copying from /mnt (disk) Verifying Loading 3 of 14 subset(s).... Copyright (c) Digital Equipment Corporation. 1993-1996. All Rights Reserved. DECnet/OSI Network Management Copying from /mnt (disk) Verifying Loading 4 of 14 subset(s).... DECnet/OSI Base Components Copying from /mnt (disk) Verifying Sample DECnet/OSI Installations A-3 Loading 5 of 14 subset(s).... DECnet/OSI Gateways Copying from /mnt (disk) Verifying Loading 6 of 14 subset(s).... DECnet/OSI Network Management GUI Copying from /mnt (disk) Verifying Loading 7 of 14 subset(s).... DECnet/OSI Reference Pages Copying from /mnt (disk) Verifying Loading 8 of 14 subset(s).... DECnet/OSI MOP Utilities Copying from /mnt (disk) Verifying Loading 9 of 14 subset(s).... DECnet/OSI Transition Tools Copying from /mnt (disk) Verifying Loading 10 of 14 subset(s).... DECnet/OSI DECdns Server Copying from /mnt (disk) Verifying Loading 11 of 14 subset(s).... DECnet/OSI Miscellaneous Software Copying from /mnt (disk) Verifying Loading 12 of 14 subset(s).... DECnet/OSI Programming Tools Copying from /mnt (disk) Working....Tue Apr 2 12:46:07 EST 1996 Verifying Loading 13 of 14 subset(s).... Copyright (c) Digital Equipment Corporation. 1993-1996. All Rights Reserved. A-4 Sample DECnet/OSI Installations CTF Collector Components Copying from /mnt (disk) Verifying Loading 14 of 14 subset(s).... Copyright (c) Digital Equipment Corporation. 1993-1996. All Rights Reserved. CTF User Environment Copying from /mnt (disk) Verifying 14 of 14 subset(s) installed successfully. Linking "Digital UNIX WAN Utilities" Configuring "Digital UNIX WAN Utilities " (ZZAUTIL300) Configuring "DECnet/OSI Kernel Components " (DNAKBIN400) Configuring "DECnet/OSI Network Management " (DNANETMAN400) Modifying ./etc/magic ... done. 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) 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 T4.0-3, please perform the following step: Sample DECnet/OSI Installations A-5 - Configure or reconfigure DECnet/OSI by executing either of the following commands (the first is a graphical configuration utility and the second is terminal-based): # /usr/sbin/dxdecnetsetup # /usr/sbin/decnetsetup [basic|advanced] Please refer to the Installation Guide for details. Press to continue: Configuring "CTF User Environment " (CTAANAL300) # A.2 Sample Log for a DECnet for Small Configurations (DNALITE) Installation The following is a sample installation log file for a DNALITE installation. # setld -l . 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 the Return key 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 A-6 Sample DECnet/OSI Installations - 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 --- Enter your choices or press RETURN to display the next screen. Choices (for example, 1 2 4-6): 2 4 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): 2 4 You are installing the following optional subsets: - DECnet/OSI Standard Run-time Environment: DECnet/OSI Kernel Components - Lightweight DECnet Configuration Environment: DECnet for Small Configurations Is this correct? (y/n): y Checking file system space required to install selected subsets: File system space checked OK. 2 subset(s) will be installed. Loading 1 of 2 subset(s).... Sample DECnet/OSI Installations A-7 DECnet/OSI Kernel Components Copying from . (disk) Verifying Loading 2 of 2 subset(s).... Copyright (c) Digital Equipment Corporation. 1993-1996. All Rights Reserved. DECnet for Small Configurations Copying from . (disk) Working....Wed Feb 21 08:51:51 EST 1996 Verifying 2 of 2 subset(s) installed successfully. Configuring "DECnet/OSI Kernel Components " (DNAKBIN400) To complete your installation of DECnet/OSI for Digital UNIX V4.0-0, please perform the following step: - Configure or reconfigure DECnet by executing either of the following commands (the first is a graphical configuration utility and the second is terminal-based): # /usr/sbin/dxdecnetsetup # /usr/sbin/decnetsetup [basic|advanced] Please refer to the Installation Guide for details. Press to continue: Configuring "DECnet for Small Configurations " (DNALITE400) A.3 Sample Log for RFC 1006-Only Installation The following is a sample installation log file for an RFC 1006-only installation. # setld -l . 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 the Return key to continue: A-8 Sample DECnet/OSI Installations 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): 2 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 --- Enter your choices or press RETURN to display the next screen. Choices (for example, 1 2 4-6): 2-3 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): 2-3 Sample DECnet/OSI Installations A-9 You are installing the following optional subsets: - DECnet/OSI Standard Run-time Environment: DECnet/OSI Kernel Components DECnet/OSI Network Management Is this correct? (y/n): y Checking file system space required to install selected subsets: File system space checked OK. 2 subset(s) will be installed. Loading 1 of 2 subset(s).... DECnet/OSI Kernel Components Copying from . (disk) Verifying Loading 2 of 2 subset(s).... Copyright (c) Digital Equipment Corporation. 1993-1996. All Rights Reserved. DECnet/OSI Network Management Copying from . (disk) Working....Wed Feb 21 14:02:59 EST 1996 Verifying 2 of 2 subset(s) installed successfully. Configuring "DECnet/OSI Kernel Components " (DNAKBIN400) Configuring "DECnet/OSI Network Management " (DNANETMAN400) A.4 Sample Log for MOP-Standalone Installation The following is a sample log file for a MOP-standalone installation. 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 the Return key to continue: A-10 Sample DECnet/OSI Installations 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): 2 3 7 - 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. Choices (for example, 1 2 4-6): 2 3 7 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): 2-3 7 Sample DECnet/OSI Installations A-11 You are installing the following optional subsets: - DECnet/OSI Standard Run-time Environment: DECnet/OSI Kernel Components DECnet/OSI Network Management - Optional DECnet/OSI Components: DECnet/OSI MOP Utilities Is this correct? (y/n): y Checking file system space required to install selected subsets: File system space checked OK. 3 subset(s) will be installed. Loading 1 of 3 subset(s).... DECnet/OSI Kernel Components Copying from . (disk) Verifying Loading 2 of 3 subset(s).... Copyright (c) Digital Equipment Corporation. 1993-1996. All Rights Reserved. DECnet/OSI Network Management Copying from . (disk) Working....Mon Feb 26 08:43:23 EST 1996 Verifying Loading 3 of 3 subset(s).... DECnet/OSI MOP Utilities Copying from . (disk) Verifying 3 of 3 subset(s) installed successfully. Configuring "DECnet/OSI Kernel Components " (DNAKBIN400) Configuring "DECnet/OSI Network Management " (DNANETMAN400) To complete your installation of DECnet/OSI for Digital UNIX T4.0-3 MOP Utilities, please perform the following step: # /usr/sbin/mopsetup Please refer to the Installation Guide for details. Press to continue: Configuring "DECnet/OSI MOP Utilities " (DNAMOP400) A-12 Sample DECnet/OSI Installations B _________________________________________________________________ Sample DECnet/OSI Configurations This appendix includes the following sample configuration logs: o Advanced configuration o Basic configuration o RFC 1006-only configuration o MOP-standalone configuration o X.25 configuration o Configuration verification procedure B.1 Sample DECnet/OSI Advanced Configuration The following sample configuration procedure illustrates the use of decnetsetup in advanced mode. In this sample, the system has a Phase IV compatible address, configures its addresses automatically, is a DTSS clerk, is a DECdns clerk using a DECdns namespace, and will be configured to run DECnet over TCP/IP. # decnetsetup adv 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. Now you will be asked a few questions. If you need more information to answer a question, you can type ? at the prompts, or consult the DECnet/OSI installation guide. To configure DECnet, you need to know your full Phase V node name and network address(es). Please review the installation guide, and the checklists in particular, before continuing. Sample DECnet/OSI Configurations B-1 The Phase V node name is the full name of the node object in the local or distributed namespace. It includes the namespace nickname, and the full list of directories leading to the node object name, or in the case of Domain/BIND the fully qualified hostname. Examples of Phase V node names include: LOCAL:.TomThumb DOMAIN:.werner.afsg.comms.org XYZ_CORP:.sales.west_coast.WillyLoman Europe:.Erin.County_Cork.Bantry.Glengarriff_Road.MACotter The namespace nickname is terminated with a colon (:). The node object name must begin with a dot (.), and no element of the name (namespace name, directory, or node object name) can be a null string. What is the Phase V node name? [No Default]: ACME:.plm.wolf The node synonym is an alphanumeric character string echo between 1 and 6 characters long that contains at least one alphabetic character. If this system had previously been running DECnet Phase IV software, then the old nodename should be used as the synonym. If this system is joining a DECnet network for the first time, any name can be used for the synonym, as long as it meets the criteria listed above, and is unique within the network. If you do not enter a synonym, then this node will only be known by its full name. Enter a null string ("") to specify no synonym. What is the Phase IV compatible synonym? [wolf]: A Phase V system may or may not use a DECnet Phase IV style node address. A node address of 0 indicates that this Phase V system will be communicating with Phase V nodes only. If your network contains some systems running DECnet Phase IV, you may wish to specify a compatible address in order to communicate with them. If your network consists solely of Phase V and/or OSI systems, this may not be required. The DECnet Phase IV node address consists of an area number (between 1 and 63), and a node number within the area (between 1 and 1023). Should you specify a Phase IV address, you will also be prompted for the Initial Domain Part (IDP) of your network's OSI address. What is the Phase IV compatible node address? [0]: 55.612 B-2 Sample DECnet/OSI Configurations Having chosen a Phase IV compatible address for this system, you may also specify a Phase IV Prefix, which together with the node address forms the complete network address for this system. All nodes within a single addressing domain contain the same IDP in their network addresses. The default value of "49::" is the "private network" IDP, which is appropriate for a Phase IV DECnet network that contains some Phase V systems. Please contact your network manager if you are in doubt as to your network's Phase IV Prefix value, or indeed if you are unsure how to answer this question at all. What is the Phase IV Prefix value for this network? [49::]: If you have a large network and would like to use an alternate node synonym directory rather than using the default node synonym directory of ".DNA_NodeSynonym", you may enter one at the following prompt. The value for the alternate node synonym directory must be a DECdns directory full name (for example: .USA_Synonyms). What is the node synonym directory in the ACME namespace? [.DNA_NodeSynonym]: If this system is being configured in a DNA Phase V environment, you should answer "Yes" to the following question. If the network is a heterogeneous OSI environment, answer "No" in order to explicitly enter this system's network address(es). Will this system autoconfigure its network addresses? [y]: There will be a pause while this procedure determines what network controllers are available on the system. This procedure has attempted to determine what communications devices are configured on this system. If the default answer is chosen in the following question, all such devices will be initialized to run the DECnet/OSI software. If you wish to run DECnet on only certain devices, please choose them from the list below. Enter the list of communications devices on which you will be running the DECnet Phase V software. If there is more than one device, separate them by spaces. [tu0 fta0 tu1 ]: tu0 Will this system be configured as a DTSS clerk only? (y/n) [y]: Will this system be configured as a DECnet-Internet Gateway? (y/n) [n] It is possible to configure DECnet/OSI so that DECnet applications can run over a TCP/IP connection, to access similarly configured remote DECnet/OSI systems. If you wish to configure this capability, answer "Yes" to the following question, and the required transport and naming capabilities will be configured on this system. Sample DECnet/OSI Configurations B-3 Do you want to configure DECnet over TCP/IP? (y/n) [y]: Do you want this system to service MOP requests? (y/n) [y] n Please review the following information which you have supplied, and if it is correct enter "Continue", which will start the DECnet software and complete the configuration. If there is incorrect information, or you wish to change a particular value, enter "Restart" to begin the setup again. If the information is correct, but you do not wish to complete the configuration at this time, enter "Stop". This will save the values you have entered, which will appear as defaults when you rerun this procedure. You may enter "Quit" to abort this procedure, without saving the answers. Nodename: ACME:.plm.wolf Node Synonym: wolf Phase IV Address: 55.612 Phase IV Prefix: 49:: Network Devices: tu0 This system will autoconfigure addresses. This system will be a DTSS clerk. This system will be a DNS clerk in the ACME namespace. This system will be configured to run DECnet over TCP/IP. Do you wish to complete this DECnet/OSI configuration? [continue] Creating defaults file. Creating Initialization NCL scripts Modifying /sbin/decnetstartup Updating /var/dna/dna_version Modifying /sbin/decnetshutdown Event Logging ... Configuring "CTF Collector Components " (CTABASE300) Creating Session Control Modifying /var/dss/dns/dns-names Starting DECnet/OSI Datalink ... Routing ... NSP ... OSI Transport ... Session Control ... Attempting to contact local DNS server...please wait. DNS clerk successfully configured. Modifying /var/dss/dns/dns-names Node name reset to ACME:.plm.wolf Setting Session Control attributes B-4 Sample DECnet/OSI Configurations There will be a brief pause as the ACME namespace is checked, to see if this node is already registered. This node is registered in the ACME namespace. DTSS ... Node Enabled ... Event Logging Event Logging ... DECnet/OSI RFC 1006 (OSI over TCP) has been enabled. rfc1006setup completed successfully. Updating address towers for node object ACME:.plm.wolf ... done MOP successfully configured The configuration of DECnet/OSI is completed. You can test DECnet functionality with the utility /usr/sbin/dnet_check. This performs various local and remote functions, and requires an account (and password) on this system and one other DECnet node. After verifying that the system is operating properly with DECnet installed you may wish to remove the following saved files: - /var/dna/scripts/start_*.ncl.sav[n] Note: There is no guest account in your system. If you wish to allow default FAL access to this system from remote systems, you should create a guest account. This would allow access when no user name or password is specified. The password field for this account should be set to Nologin to prevent unauthorized access to your system. Alternatively, you could change the User Name attribute of the session control application "fal" to use a different account. See the Guide to Network Management for details. You may run /usr/sbin/osiapplsetup to configure the OSI Applications (FTAM and Virtual Terminal). decnetsetup completed successfully. # Sample DECnet/OSI Configurations B-5 B.2 Sample DECnet/OSI Basic Configuration The following sample configuration procedure illustrates the use of decnetsetup in basic mode. In this sample, the system has a Phase IV address, autoconfigures its addresses, services MOP requests (by default), is a DECdns clerk in the Local namespace, and is a DTSS clerk. # decnetsetup basic 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. Now you will be asked a few questions. If you need more information to answer a question, you can type ? at the prompts, or consult the DECnet/OSI installation guide. To configure DECnet, you need to know your full Phase V node name and network address(es). Please review the installation guide, and the checklists in particular, before continuing. The Phase V node name is the full name of the node object in the local or distributed namespace. It includes the namespace nickname, and the full list of directories leading to the node object name, or in the case of Domain/BIND the fully qualified hostname. Examples of Phase V node names include: LOCAL:.TomThumb DOMAIN:.werner.afsg.comms.org XYZ_CORP:.sales.west_coast.WillyLoman Europe:.Erin.County_Cork.Bantry.Glengarriff_Road.MACotter The namespace nickname is terminated with a colon (:). The node object name must begin with a dot (.), and no element of the name (namespace name, directory, or node object name) can be a null string. What is the Phase V node name? [No Default]: LOCAL:.plm.coyote The node synonym is an alphanumeric character string echo between 1 and 6 characters long that contains at least one alphabetic character. If this system had previously been running DECnet Phase IV software, then the old nodename should be used as the synonym. If this system is joining a DECnet network for the first time, any name can be used for the synonym, as long as it meets the criteria listed above, and is unique within the network. If you do not enter a synonym, then this node will only be known by its full name. Enter a null string ("") to specify no synonym. B-6 Sample DECnet/OSI Configurations What is the Phase IV compatible synonym? [coyote]: A Phase V system may or may not use a DECnet Phase IV style node address. A node address of 0 indicates that this Phase V system will be communicating with Phase V nodes only. If your network contains some systems running DECnet Phase IV, you may wish to specify a compatible address in order to communicate with them. If your network consists solely of Phase V and/or OSI systems, this may not be required. The DECnet Phase IV node address consists of an area number (between 1 and 63), and a node number within the area (between 1 and 1023). Should you specify a Phase IV address, you will also be prompted for the Initial Domain Part (IDP) of your network's OSI address. What is the Phase IV compatible node address? [0]: 47.723 There will be a pause while this procedure determines what network controllers are available on the system. This procedure has attempted to determine what communications devices are configured on this system. If the default answer is chosen in the following question, all such devices will be initialized to run the DECnet/OSI software. If you wish to run DECnet on only certain devices, please choose them from the list below. Enter the list of communications devices on which you will be running the DECnet Phase V software. If there is more than one device, separate them by spaces. [tu0 tu1 ]: The DECnet-Internet Gateway subset has not been installed on this system. If you wish to use this capability, please use the setld utility to load this subset. See the installation guide for details. The DECnet/OSI MOP Utilities subset has not been installed on this system. If you wish to use this capability, please use the setld utility to load this subset. See the installation guide for details. Please review the following information which you have supplied, and if it is correct enter "Continue", which will start the DECnet software and complete the configuration. If there is incorrect information, or you wish to change a particular value, enter "Restart" to begin the setup again. If the information is correct, but you do not wish to complete the configuration at this time, enter "Stop". This will save the values you have entered, which will appear as defaults when you rerun this procedure. You may enter "Quit" to abort this procedure, without saving the answers. Sample DECnet/OSI Configurations B-7 Nodename: LOCAL:.plm.coyote Node Synonym: coyote Phase IV Address: 47.723 Phase IV Prefix: 49:: Network Devices: tu0 tu1 This system will autoconfigure addresses. This system will be a DTSS clerk. This system will use the Local Namespace This system will be configured to service MOP requests. Do you wish to complete this DECnet/OSI configuration? [continue] Creating defaults file. Creating Initialization NCL scripts Creating /sbin/decnetstartup Creating /usr/sbin/osi_applstartup Updating /var/dna/dna_version Modifying /sbin/decnetshutdown Event Logging ... Configuring "CTF Collector Components " (CTABASE300) Creating Session Control Modifying /var/dss/dns/dns-names Starting DECnet/OSI Datalink ... Routing ... NSP ... OSI Transport ... Session Control ... Local Namespace successfully configured. Modifying /var/dss/dns/dns-names Node name reset to LOCAL:.plm.coyote Setting Session Control attributes DTSS ... Node Enabled ... Event Logging Event Logging ... DECnet/OSI RFC 1006 (OSI over TCP) has been enabled. rfc1006setup completed successfully. Initializing the Local Namespace Will create a new /var/dna/dna_local_name_database_nam.dir Directory Service: Local name file Registering the node: local:.plm.coyote The configuration of DECnet/OSI is completed. B-8 Sample DECnet/OSI Configurations You can test DECnet functionality with the utility /usr/sbin/dnet_check. This performs various local and remote functions, and requires an account (and password) on this system and one other DECnet node. After verifying that the system is operating properly with DECnet installed you may wish to remove the following saved files: - /var/dna/scripts/start_*.ncl.sav[n] Note: There is no guest account in your system. If you wish to allow default FAL access to this system from remote systems, you should create a guest account. This would allow access when no user name or password is specified. The password field for this account should be set to Nologin to prevent unauthorized access to your system. Alternatively, you could change the User Name attribute of the session control application "fal" to use a different account. See the Guide to Network Management for details. Note: This node has been configured to use the Local Namespace. If you wish to add, modify, or delete a node or its associated addressing information, you should use the utility /usr/sbin/decnet_register to add or change definitions. You may also use the /usr/sbin/update_nodes utility to copy a Phase IV nodes database or Phase V LNO load file from a remote system, as in the following example: /usr/sbin/update_nodes -dlocal 4.1002 This command will copy a DECnet address file from the remote system, and automatically populate the local naming file. Please refer to the installation guide for further details. decnetsetup completed successfully. # Sample DECnet/OSI Configurations B-9 B.3 Sample RFC 1006 Configuration The following sample configuration procedure illustrates the use of rfc1006setup to configure RFC1006. # /usr/sbin/rfc1006setup DECnet/OSI for Digital UNIX V4.0-0 DECnet/OSI RFC 1006 (OSI over TCP) Configuration Procedure. There will be a pause while this procedure gathers some information from your system. Event Logging ... DECnet/OSI RFC 1006 (OSI over TCP) has been enabled. rfc1006setup completed successfully. # B.4 Sample MOP-Standalone Configuration The following sample configuration procedure illustrates the use of mopsetup to configure MOP-standalone software. # /usr/sbin/mopsetup Help can be obtained at any prompt by entering '?' Press Carriage Return to continue: *** MOP Main Menu *** 1) Configure MOP 2) Start MOP 3) Stop MOP 4) Manage MOP Clients 5) Manage MOP Circuits x) EXIT Enter your choice: 1 Enter the list of communications devices on which you will be running the DECnet Phase V software. If there is more than one device, separate them by spaces. [ln0 fta0 ]: MOP succesfully configured. Press Carriage Return to continue: *** MOP Main Menu *** B-10 Sample DECnet/OSI Configurations 1) Configure MOP 2) Start MOP 3) Stop MOP 4) Manage MOP Clients 5) Manage MOP Circuits x) EXIT Enter your choice: B.5 Sample X.25 Configuration ________________________ Note ________________________ If you want to configure the Wide Area Networking Support for Digital UNIX software (X.25) for use with Version 4.0 of DECnet/OSI for Digital UNIX, use the release of the Wide Area Networking Support for Digital UNIX software that is currently available for Digital UNIX Version 4.0. See the latest Wide Area Networking Support for Digital UNIX Software Product Description (SPD) for product release information. ______________________________________________________ This example shows the configuration script for X.25, taken from the section in decnetsetup that asks about configuring OSI transport for the CONS interface. Would you like to configure OSI Transport to use the CONS interface to X.25? (y/n) [y]: You may configure OSI Transport to use one or more of the locally configured DTEs. Enter one or more DTE names: [ TNET_L-1 ] The currently defined set of CONS NSAP address(es), as derived from your local DTE addresses, is: /3600000002267643 Do you wish to define any additional CONS NSAP values? (y/n) [n]: ? Sample DECnet/OSI Configurations B-11 One or more of the CLNS NSAP values may also be used as a CONS NSAP for this system. If you answer "yes" to this question, one will be chosen and added to the set shown above. If you answer "no" then no changes will be made. You may modify the set at any time by using the NCL commands: add osi transport cons nsap address {value} remove osi transport cons nsap address {value} To make a permanent change to the set you should edit the file /var/dna/scripts/start_tp_cons.ncl, where these values are stored. Do you wish to define any additional CONS NSAP values? (y/n) [n]: y The local NSAP 41:45418715:00-41:08-00-2B-0E-D4-1E:21 will be added to the set of CONS NSAP addresses. Enter the name of a remote system to which data will be sent over an X.25 circuit: [No Default] ? You should enter the name of a remote system, which will be used as the name of the X.25 reachable address entity. You may enter any alphanumeric value for the name. Enter the name of a remote system to which data will be sent over an X.25 circuit: [No Default] remsys Enter the X.25 Address of the DTE corresponding to system remsys: (DTE Address): [No Default] ? Enter the DTE address associated with remote system remsys, which will be used to make the X.25 circuit connection. Enter the X.25 Address of the DTE corresponding to system remsys: (DTE Address): [No Default] 12322 Enter an NSAP (or NSAP prefix) corresponding to system remsys: (NSAP): [/3600000000012322] Enter the name of a remote system to which data will be sent over an X.25 circuit: [No Default] Adding TP CONS support to start_osi_transport.ncl Restarting OSI Transport...done B-12 Sample DECnet/OSI Configurations B.6 Sample Configuration Verification Procedure The following is a sample configuration verification procedure log that you might see when you issue a /usr /sbin/dnet_check command. # dnet_check DECnet/OSI for Digital UNIX V4.0-0 DECnet/OSI Configuration Verification 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. This script should be executed after DECnet/OSI has been installed and configured on your system. It verifies that network communication can take place between your local node and other remote nodes on the network. It also verifies that your local node can communicate with itself. During the tests which follow you will be asked a few questions. If you require further information, enter a question mark (?) and explanatory text will be provided. Of course, you will be prompted again for the requested information. What is your Phase V node name? [ACME:.plm.wolf]: The first test checks that some of the DECnet/OSI network management entities are running. Each of the following displays should indicate that the entity is in state "On". # ncl show Routing state Node 0 Routing AT 1996-02-06-14:41:49.539-04:00I62.657 Status State = On # ncl show Session Control state Node 0 Session Control AT 1995-02-06-14:41:50.086-04:00I62.657 Status State = On # ncl show Node 0 state Sample DECnet/OSI Configurations B-13 Node 0 AT 1996-02-06-14:41:50.571-04:00I62.657 Status State = On The following command attempts to look up your node object in the DECdns namespace. This is a simple way to test that the DNS Clerk is functioning correctly. # decnet_register show node ACME:.plm.wolf directory_service decdns Directory Service: DECdns Node name: ACME:.plm.wolf Phase IV synonym: wolf Node address: 49::00-04:AA-00-04-00-98-12:21 (55.612) Node address: 49::00-04:AA-00-04-00-98-12:20 (55.612) Node address: 41:45418715:00-41:08-00-2B-E4-63-8C:21 Node address: 41:45418715:00-41:08-00-2B-E4-63-8C:20 Number of nodes reported on: 1 Enter the name of a remote node? [No Default]: ACME:.plm.nan.abiss remote node ACME:.nan.abiss Is this correct? (y/n) [y]: The following command will check that the remote node you specified is reachable: # ncl show node ACME:.nan.abiss state Node ACME:.nan.abiss AT 1996-02-06-14:42:38.202-04:00I0.386 Status State = On The next group of tests attempts to copy files over the network using DECnet/OSI, and to run the loopback application. The first test will copy a file to the local node using DECnet/OSI utilities, and if successful, the second test will copy a file to and from the remote system you specified earlier. For each test, you will be asked to provide the user account and password to be used for that system. B-14 Sample DECnet/OSI Configurations Enter user account on ACME:.plm.wolf [No Default]: don Enter password for user don on ACME:.plm.wolf [No Default]: # dcp /usr/sbin/dnet_check ACME:.plm.wolf/don/password/::dnetcheck.rnd # dcp ACME:.plm.wolf/don/password/::dnetcheck.rnd /usr/tmp/dnetcheck.lnd # cmp -s /usr/sbin/dnet_check /usr/tmp/dnetcheck.lnd # drm ACME:.plm.wolf/don/password/::dnetcheck.rnd # ncl loop loopback application name ACME:.plm.wolf, length 1, count 10, format 00 # ncl loop loopback application name ACME:.plm.wolf, length 2047, count 50 Enter user account on ACME:.nan.abiss [No Default]: don Enter password for user don on ACME:.nan.abiss [No Default]: # dcp /usr/sbin/dnet_check ACME:.nan.abiss/don/password/::dnetcheck.rnd # dcp ACME:.nan.abiss/don/password/::dnetcheck.rnd /usr/tmp/dnetcheck.lnd # cmp -s /usr/sbin/dnet_check /usr/tmp/dnetcheck.lnd # drm ACME:.nan.abiss/don/password/::dnetcheck.rnd # ncl loop loopback application name ACME:.nan.abiss, length 1, count 10, format 00 # ncl loop loopback application name ACME:.nan.abiss, length 2047, count 50 Removing log file /tmp/dnet_check.log Removing the file copied across the network # Sample DECnet/OSI Configurations B-15 C _________________________________________________________________ Software Subsets and Installation Requirements C.1 DECnet/OSI for Digital UNIX Software Subsets Table C-1 describes the DECnet/OSI for Digital UNIX subsets. Use this information to determine the amount of disk space, as well as which subsets to install. Chapter 2 gives more details about the total disk space required for each type of installation. Table_C-1_Summary_of_DECnet/OSI_Software_Subsets_and_Disk_Space__ Disk Space Subset________Name______________(KB)+______Dependencies__________ CTF CTABASE300 1986 Digital UNIX Base Collector /usr System (OSFBASE400), Component 486 CTF Utilities /var (ZZAUTIL300) CTF User CTAANAL300 4342 Digital UNIX Base Environment System (OSFBASE400), CTF Collector Component (CTABASE300) +Except_for_the_CTABASE300,_CTAANAL,_and_ZZAUTIL300_subsets,_an__ installation of any one or more of the following subsets requires an additional 2000 KB in /var (continued on next page) Software Subsets and Installation Requirements C-1 Table C-1 (Cont.) Summary of DECnet/OSI Software Subsets and Disk __________________Space__________________________________________ Disk Space Subset________Name______________(KB)+______Dependencies__________ DECdns DNADECDNSSRV400 1015 DECnet/OSI Base Server /usr Components (DNABASE400), Digital UNIX Base System (OSFBASE400), DECnet/OSI Transition Tools (DNATRANSITION400) DECnet DNALITE400 10131 DECnet/OSI for Small /usr Kernel Components Configurations (DNAKBIN400) Components DECnet DNABASE400 6266 Digital UNIX Base /OSI Base /usr System (OSFBASE400), Components DECnet/OSI Network Management (DNANETMAN400) DECnet/OSI DNAGATEWAYS400 254 DECnet/OSI Base Gateways /usr Components (DNABASE400) DECnet/OSI DNAKBIN400 0 Digital UNIX Base Kernel /usr System (OSFBASE400) Components 1405 /var DECnet/OSI DNAUTIL400 1365 Digital UNIX Base Miscellaneous /usr System (OSFBASE400) Software +Except_for_the_CTABASE300,_CTAANAL,_and_ZZAUTIL300_subsets,_an__ installation of any one or more of the following subsets requires an additional 2000 KB in /var (continued on next page) C-2 Software Subsets and Installation Requirements Table C-1 (Cont.) Summary of DECnet/OSI Software Subsets and Disk __________________Space__________________________________________ Disk Space Subset________Name______________(KB)+______Dependencies__________ DECnet DNAMOP400 423 DECnet/OSI /OSI MOP /usr Network Management Utilities (DNANETMAN400) DECnet/OSI Kernel Components (DNAKBIN400), DECnet/OSI Kernel Components (DNAKBIN400) DECnet/OSI DNANETMAN400 11027 Digital UNIX Base Network /usr System (OSFBASE400) Management DECnet/OSI DNANETMANGUI400 2281 DECnet/OSI Network /usr Network Management Management (DNANETMAN400) Graphical User Interface DECnet/OSI DNAPGMR400 6644 Digital UNIX Base Programming /usr System (OSFBASE400) Tools DECnet/OSI DNAMAN400 65 Digital UNIX Document Reference /usr Preparation Tools Pages (OSFDCMT400) DECnet/OSI DNATRANSITION400 1095 Digital UNIX Base Transition /usr System (OSFBASE400), Tools DECnet/OSI Base Components (DNABASE400) +Except_for_the_CTABASE300,_CTAANAL,_and_ZZAUTIL300_subsets,_an__ installation of any one or more of the following subsets requires an additional 2000 KB in /var (continued on next page) Software Subsets and Installation Requirements C-3 Table C-1 (Cont.) Summary of DECnet/OSI Software Subsets and Disk __________________Space__________________________________________ Disk Space Subset________Name______________(KB)+______Dependencies__________ Digital ZZAUTIL300 1228 Digital UNIX Base UNIX WAN /usr System (OSFBASE400) Utilities 245 +Except_for_the_CTABASE300,_CTAA/var_and_ZZAUTIL300_subsets,_an__ installation of any one or more of the following subsets requires an additional 2000 KB in /var _________________________________________________________________ C-4 Software Subsets and Installation Requirements _________________________________________________________________ Index A Basic configuration (cont'd) _______________________________ requirements, 3-1 Address sample script, B-6 supplying for Phase IV, 4-17 starting, 3-10 Addressing issues stopping, 3-4 for X.25, 4-31 Advanced configuration, 2-22 C______________________________ checklist, 4-2, 4-3 Changing answers, 3-3, 4-5 communication devices, 4-2 Characters, valid for full DECdts server, 4-2 description, 4-4 name, 3-12, 4-12, 4-13 namespace, 4-2 Checking for previous versions requirements, 4-2 of DECnet/OSI, 2-3 sample script, B-1 Checklist starting, 4-11 Advanced configuration, 4-2, stopping, 4-5 4-3 when to use, 4-2 Basic configuration, 3-2 Alternate node synonym, 4-18 Choosing configuration Answers procedures, 2-21 changing, 3-3, 4-5 Clerk confirming, 3-18, 4-26 DECdns, 3-19 Autoconfiguring network DECdts, 3-19, 4-23 addresses, 4-19 CLNS, 4-30, 4-35 Autoregistration Communications devices by decnetsetup, 5-3 configuring Token Ring, 4-22 multiple, 3-16, 4-21 B______________________________ selecting, 4-21 Backup Configuration before starting installation, checklist, 3-2, 4-2, 4-3 2-3 finishing for DECdns clerk, Basic configuration, 2-22 5-2 checklist, 3-2 finishing for DNS/BIND, 5-5 DECdts clerk, 3-1 finishing for Local namespace defaults, 3-1 , 5-2 Index-1 Configuration (cont'd) CTF User Environment subset, finishing for name service, 1-7 5-1 graphical interface, 2-23, D______________________________ 2-25 DECdns, 3-5, 4-6 interfaces, 2-22 default, 3-5 planning, 3-2, 4-2, 4-3 distributed namespace, 3-14, procedures, 2-21 4-15 stopping, 7-12 full name, 3-11, 4-12 tasks, 1-1 Local namespace, 3-14, 4-14 terminal-based interface, Local Naming Option, 1-1 2-22 remote server, 5-4 verification program, 3-22 valid characters, 3-12, verifying advanced procedure, 4-12, 4-13 4-38 DECdns clerk Configuration verification configuring, 4-15 procedure DECdns namespace activities, requirements, 6-1 5-5 running, 6-1 DECdns Server subset, 1-7 sample script, B-13 DECdts Configuring clerk role, 4-23 DECdns clerk, 5-2 configuring, 4-23 DECdts clerk, 4-24 default, 3-5 DECdts server, 4-24 server role, 4-23 DECnet-Internet Gateway, DECnet for Small Configurations 3-22, 4-24 , 1-4 network addresses, 4-18 choosing installation, 2-9, Configuring OSI applications 2-10 software, 3-22, 4-37 configuration, 3-1 Confirming disk space, 1-12, 2-3 answers, 3-18, 4-26 installation, 1-12, 1-13 example, 4-28 performing installation, Connecting to remote server, 2-15 5-4 sample installation script, CONS, 4-30 A-6 configuring OSI transport to DECnet-Internet Gateway use CONS, 4-34 configuring, 2-18, 3-22, CONS attributes, 4-37 4-24, 5-9 Continuing the configuration, decnetsetup command, 3-22, 3-18, 3-19, 4-26, 4-27 4-24 CTF Collector Component subset testing, 5-10 , 1-7 DECnet/OSI node name, 3-11, 4-12 Index-2 DECnet/OSI Base Components DNA format for NETs, 4-20 subset, 1-6 DNALITE DECnet/OSI Gateways subset, configuration, 3-1 1-8 DNALITE installation, 1-4 DECnet/OSI installation choosing, 2-9, 2-10 performing, 2-15 disk space, 1-12, 1-13 DECnet/OSI Kernel Components disk space requirements, 2-3 subset, 1-6 optional subsets, 1-13 DECnet/OSI Miscellaneous performing, 2-15 Software subset, 1-9, 1-14 required subsets, 1-12 DECnet/OSI MOP Utilities DNS/BIND subset, 1-10 configuring, 5-5 DECnet/OSI Network Management for TCP/IP service, 3-14, Graphical User Interface 4-15 subset, 1-10 naming service, 3-14, 4-15 DECnet/OSI Network Management dnsconfigure, 5-4 subset, 1-6 Domain namespace, 3-14, 4-15 DECnet/OSI Programming Tools DOTI subset, 1-10 See TCP/IP DECnet/OSI Reference Pages DTSS subset, 1-10, 1-14 default, 3-5 DECnet/OSI subsets, 1-4 DECnet/OSI Transition Tools, E______________________________ 1-11 End System PAK, 1-17 DECnet/OSI using X.25, 4-30, Extended addresses, 4-18 4-35 Extended System PAK, 1-18, 4-2 Default node synonym, 3-14, 4-16 F______________________________ values, 3-3, 4-5, 7-12 First DECnet/OSI system, 1-1, Deleting old versions of 4-2 DECnet/OSI, 2-3 FTAM Deleting subsets, 2-4 See also OSI applications Digital UNIX WAN Utilities autoconfiguring local subset, 1-11 addresses, 7-22 Disk space configuring, 3-22, 4-37, 7-1 checking, 2-2 configuring local addresses requirements, 2-2 manually, 7-29 Distributed namespace configuring local listeners using, 3-14, 4-15 Distribution media, 2-2 manually, 7-46 CD-ROM, 2-11 configuring remote FTAM mounting, 2-11 addresses, 7-38 DECnet/OSI subset, 1-6 initiating entities, 7-2 installation, 7-1 Index-3 FTAM (cont'd) Installation (cont'd) osiapplsetup, 7-10 DNALITE sample script, A-6 responding entities, 7-2 full-capability sample script terminology, 7-1 , A-1 FTAM-FTP Gateway MOP-standalone sample script, verifying installation of, A-10 7-48 RFC 1006-only sample script, Full name, 3-11, 4-12 A-8 Local namespace, 3-14, 4-14 tasks, 1-1 valid characters, 3-12, verifying, 7-36, 7-48 4-12, 4-13 Installation subsets Full-capability DECnet/OSI DECnet for Small sample installation script, Configurations, 1-12 A-1 full-capability DECnet/OSI, Full-capability DECnet/OSI 1-5, 1-7 installation, 1-4 MOP-standalone installation, choosing, 2-9, 2-10 1-15 disk space, 1-5, 2-2 RFC 1006-only installation, optional subsets, 1-7 1-14 required subsets, 1-5 Installation types, 1-4, 2-9, 2-10 G______________________________ Installation verification Guest account, 2-8 procedure after installation, 7-36 H______________________________ running, 7-36 Help, 3-4, 4-6, 7-12 See also IVP, 7-36 Installation Verification I Procedure _______________________________ after installation, 7-48 IDP running, 7-48 default, 4-17 See also IVP, 7-48 standards, 4-18 Intermediate system, 4-19 supplying, 4-17 IVP, 3-22, 4-38, 6-1 Initiating entities configuring, 7-2 J______________________________ setting up, 7-4 Joining a namespace, 5-4 installation using Remote Installation K Service (RIS), 2-12 _______________________________ Installation Kernel rebuild, 1-3 DECnet for Small Configurations sample script, A-6 disk space requirements, 2-2 Index-4 L______________________________ N______________________________ Listeners Name Service starting, 7-35 finishing configuration, 5-1 LMF, 2-6 primary, 3-5, 4-6 Local namespace, 3-5, 3-13, search path, 3-5, 4-6 3-14, 4-6, 4-7, 4-14 secondary, 3-5, 4-6 creating, 3-13, 4-14 Namespace finishing configuration, 5-2 creating DECdns, 5-1, 5-2, Local namespace activities, 5-3 5-5 creating Local, 3-13, 4-14 Local Naming Option, 1-1 DECdns, 3-14, 4-15 Log file distributed, 5-3 creating, 3-10, 4-11, 7-21 DNS/BIND, 3-14, 4-15 Local, 3-13, 4-14, 5-2 M______________________________ PAK requirements, 1-18 Mail addresses registering nodes in, 5-3 customizing, 4-37 VAX DNS Version 1, 1-2 Mailsetup, 4-37 Namespace activities Manually configuring network copying node database, 5-7 addresses, 4-19 DECdns, 5-7 MOP, 2-17 distributed namespace, 5-7 configuring DECnet/OSI to local, 5-5 manual registration, 5-9 service MOP requests, 3-5, Phase IV registration, 5-8 4-26 registering first system (no installing without DECnet Phase IV), 5-9 /OSI, 2-17 registering first system running standalone, 2-17 (Phase IV), 5-8 MOP-standalone configuration, registering systems, 5-7 2-17 update_nodes, 5-6 sample script, B-10 running, 5-6 MOP-standalone installation, updating node database, 5-6 2-9, 2-17 Namespace nickname, 3-11, 4-12 choosing, 2-10 DNS/BIND, 3-11, 4-12 disk space, 1-15, 2-3 Local namespace, 3-12, 3-14, sample script, A-10 4-12, 4-14 subsets, 1-15 valid characters in, 3-12, subsets for, 1-16 4-12, 4-13 Multihoming systems, 4-18 NET, 4-19 autoconfiguring, 4-19 default, 4-20 DNA format, 4-20 example, 4-19 manually configuring, 4-19 Index-5 NET (cont'd) OSI Transport Listeners transport selector field, configuring, 7-30 4-20 osiapplsetup, 7-10 Network address autoconfiguring, 4-19 P______________________________ configuring, 4-18 PAK manually configuring, 4-19 End System, 1-17 Node ID, 4-20 Extended System, 1-18, 4-2 Node name, DECnet/OSI, 3-11, Phase IV 4-12 compatible address, 4-20 Node Object, 3-14, 4-16 compatible synonym, 3-14, Node registration 4-15 automatic, 5-3 supplying address, 4-17 Node synonym supplying prefix, 4-17 default, 3-14, 4-16 Phase IV compatible address, Phase IV compatible, 3-14, 3-15, 4-16 4-15 Postinstallation tasks, 5-1 to registering later, 3-15, 5-13 4-16 Previous version of DECnet specifying none, 3-15, 4-16 /OSI, 2-4 using alternate directory, Privileges 4-18 See Superuser NSAP, 4-17 O Q______________________________ _______________________________ Quitting the configuration, Online reference manual 3-18, 3-19, 4-27 See DECnet/OSI for Digital UNIX Reference Pages R subset _______________________________ OSI application entity Reachable address database, 7-2 creating with decimal format OSI applications address prefix, 4-32 See also FTAM, Virtual Rebuilding the internal table Terminal of commands, 7-48 installing, 2-16, 2-18 Remote server, 5-4 subset in, 1-6 access, 5-4 OSI Applications gateways, 1-9 address, 5-4 OSI Applications Reference Responding entities Pages, 1-11, 1-14 configuring, 7-2 OSI applications software setting up, 7-3 configuring, 3-22, 4-37 Restarting the configuration, OSI configuration 3-18, 3-19, 4-27 starting, 7-21 Index-6 RFC 1006 configuration Starting (cont'd) sample script, B-10 OSI applications RFC 1006 Transport Listeners configuration, 7-21 configuring, 7-31 Stopping RFC 1006-only configuration, advanced configuration, 4-5 2-16 basic configuration, 3-4 RFC 1006-only installation, configuration, 3-18, 4-27, 1-4, 1-15, 2-16 7-12 choosing, 2-9, 2-10 Subsets, 1-4 disk space, 1-14, 2-3 copying, 2-11 sample script, A-8 copying to disk, 2-11 subsets, 1-14 deleting, 2-4 rfc1006setup, 2-16 previous version of DECnet Router, 4-19 /OSI, 2-4 Routing and X.25, 4-35 selecting, 2-12 verifying, 2-19 S______________________________ Superuser, 2-2, 2-6 Search path, 3-5, 4-6 backtranslation, 3-6, 4-7 T______________________________ configuring, 3-5, 3-7, 4-7 TCP/IP decnet-dirsvc.conf file, configuring, 4-25 3-5, 3-7, 3-8, 4-7, 4-9 PAK for, 1-17 displaying, 3-8, 4-8 running DECnet applications, file, 3-5, 3-7, 4-7 4-25 modifying, 3-8, 4-9 Token Ring naming, 3-6, 4-7 configuring device, 4-22 naming template, 3-6, 3-8, setting station speed, 4-22 4-7, 4-9 TP0, 4-30 primary name service, 3-5, TP2, 4-30 4-6 secondary name service, 3-5, U______________________________ 4-6 /usr/sbin/dnet_check, 3-22 Server DECdts, 4-23 V Set load command, 2-12 _______________________________ Set load command options Valid characters setld -v, 7-48 for namespace nickname, Software subsets, 1-4 3-12, 4-12, 4-13 Source Aliases VAX DNS Version 1 namespace, configuring, 7-32 1-2 Starting Verification procedure advanced configuration, 4-11 sample script, B-13 basic configuration, 3-10 creating a log file, 3-10, 4-11, 7-21 Index-7 Verifying installation, 7-36, X.500 Entries 7-48 configuring for local Version 1 name server, 5-4 listeners, 7-33 Version checking, 2-3 Virtual Terminal (VT) See also OSI applications autoconfiguring local addresses, 7-22 configuring, 3-22, 4-37, 7-1 configuring local addresses manually, 7-29 configuring local listeners manually, 7-46 configuring remote VT application addresses, 7-38 DECnet/OSI subset, 1-6 initiating entities, 7-2 installation, 7-1 osiapplsetup, 7-10 responding entities, 7-2 terminology, 7-1 W______________________________ Wide Area Networking Support for Digital UNIX configuring support for, 4-30 X______________________________ X.25 addressing issues, 4-31 configuring DECnet/OSI to use X.25, 4-33 configuring support for, 4-30 X.25 configuration sample script, B-11 X.25 Services configuring for Digital UNIX, 4-30 to 4-36 testing for Digital UNIX, 4-36 Index-8